Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #189645 > unrolled thread

Upgrading to stretch (jessie-backports question)

Started byJohn Naggets <hostingnuggets@gmail.com>
First post2017-12-07 18:10 +0100
Last post2017-12-07 18:40 +0100
Articles 9 — 4 participants

Back to article view | Back to linux.debian.user

Contents

  Upgrading to stretch (jessie-backports question) John Naggets <hostingnuggets@gmail.com> - 2017-12-07 18:10 +0100
    Re: Upgrading to stretch (jessie-backports question) Tom Furie <tom@furie.org.uk> - 2017-12-07 18:20 +0100
      Re: Upgrading to stretch (jessie-backports question) Greg Wooledge <wooledg@eeg.ccf.org> - 2017-12-07 18:40 +0100
        Re: Upgrading to stretch (jessie-backports question) John Naggets <hostingnuggets@gmail.com> - 2017-12-07 20:20 +0100
          Re: Upgrading to stretch (jessie-backports question) Brian <ad44@cityscape.co.uk> - 2017-12-07 20:30 +0100
          Re: Upgrading to stretch (jessie-backports question) Greg Wooledge <wooledg@eeg.ccf.org> - 2017-12-07 20:40 +0100
            Re: Upgrading to stretch (jessie-backports question) John Naggets <hostingnuggets@gmail.com> - 2017-12-07 21:10 +0100
              Re: Upgrading to stretch (jessie-backports question) Brian <ad44@cityscape.co.uk> - 2017-12-07 22:00 +0100
      Re: Upgrading to stretch (jessie-backports question) John Naggets <hostingnuggets@gmail.com> - 2017-12-07 18:40 +0100

#189645 — Upgrading to stretch (jessie-backports question)

FromJohn Naggets <hostingnuggets@gmail.com>
Date2017-12-07 18:10 +0100
SubjectUpgrading to stretch (jessie-backports question)
Message-ID<uU7Ql-yK-3@gated-at.bofh.it>
Hi,

I am currently using Debian 8 and have enabled the jessie-backports
repository with the following line in
/etc/apt/sources.d/backports.list:

deb http://ftp.debian.org/debian jessie-backports main contrib

The only reason for this is that I am using ZFS on jessie for some
data disks/partitions. Now I would like to do a dist-upgrade from
jessie to stretch and was wondering how to handle the
jessie-backports.

Should I for example before doing the dist-upgrade to stretch delete
the APT jessie-backports source? or should I simply leave it and do a
dist-upgrade as usual?

Best regards,
John

[toc] | [next] | [standalone]

#189647

FromTom Furie <tom@furie.org.uk>
Date2017-12-07 18:20 +0100
Message-ID<uU801-BR-7@gated-at.bofh.it>
In reply to#189645

[Multipart message — attachments visible in raw view] — view raw

On Thu, Dec 07, 2017 at 06:02:04PM +0100, John Naggets wrote:

> Should I for example before doing the dist-upgrade to stretch delete
> the APT jessie-backports source? or should I simply leave it and do a
> dist-upgrade as usual?

Is there a reason not to switch to your backports source to stretch at
the same time as the others?

Cheers,
Tom

-- 
If I traveled to the end of the rainbow
As Dame Fortune did intend,
Murphy would be there to tell me
The pot's at the other end.
		-- Bert Whitney

[toc] | [prev] | [next] | [standalone]

#189648

FromGreg Wooledge <wooledg@eeg.ccf.org>
Date2017-12-07 18:40 +0100
Message-ID<uU8jo-I6-23@gated-at.bofh.it>
In reply to#189647
On Thu, Dec 07, 2017 at 06:37:27PM +0100, John Naggets wrote:
> On Thu, Dec 7, 2017 at 6:11 PM, Tom Furie <tom@furie.org.uk> wrote:
> 
> > Is there a reason not to switch to your backports source to stretch at
> > the same time as the others?
> 
> If I understand correctly doing that I will end up with the ZFS
> packages for unstable (Debian 10) after running a dist-upgrade? Is my
> understanding correct?

No.  Backports have to be specifically requested.

[toc] | [prev] | [next] | [standalone]

#189653

FromJohn Naggets <hostingnuggets@gmail.com>
Date2017-12-07 20:20 +0100
Message-ID<uU9Sb-1Kr-9@gated-at.bofh.it>
In reply to#189648
On Thu, Dec 7, 2017 at 6:39 PM, Greg Wooledge <wooledg@eeg.ccf.org> wrote:

> No.  Backports have to be specifically requested.

Aha I get it. So by changing my APT sources.list for backports from
jessie-backports to stretch-backports all my ZFS packages will simply
get upgraded to the official/main Debian (non backports) stretch ZFS
packages?

Actually moving on the Debian stretch I would not need anymore the
backports because the ZFS packages are included in stretch. So could I
just get rid of my backports APT source by deleting my list file
beforehand and then simply do a dist-upgrade?

[toc] | [prev] | [next] | [standalone]

#189654

FromBrian <ad44@cityscape.co.uk>
Date2017-12-07 20:30 +0100
Message-ID<uUa1Q-1PI-11@gated-at.bofh.it>
In reply to#189653
On Thu 07 Dec 2017 at 20:17:58 +0100, John Naggets wrote:

> On Thu, Dec 7, 2017 at 6:39 PM, Greg Wooledge <wooledg@eeg.ccf.org> wrote:
> 
> > No.  Backports have to be specifically requested.
> 
> Aha I get it. So by changing my APT sources.list for backports from
> jessie-backports to stretch-backports all my ZFS packages will simply
> get upgraded to the official/main Debian (non backports) stretch ZFS
> packages?
> 
> Actually moving on the Debian stretch I would not need anymore the
> backports because the ZFS packages are included in stretch. So could I
> just get rid of my backports APT source by deleting my list file
> beforehand and then simply do a dist-upgrade?

That's exactly it.

-- 
Brian.

[toc] | [prev] | [next] | [standalone]

#189656

FromGreg Wooledge <wooledg@eeg.ccf.org>
Date2017-12-07 20:40 +0100
Message-ID<uUabw-1Ut-5@gated-at.bofh.it>
In reply to#189653
On Thu, Dec 07, 2017 at 08:17:58PM +0100, John Naggets wrote:
> On Thu, Dec 7, 2017 at 6:39 PM, Greg Wooledge <wooledg@eeg.ccf.org> wrote:
> 
> > No.  Backports have to be specifically requested.
> 
> Aha I get it. So by changing my APT sources.list for backports from
> jessie-backports to stretch-backports all my ZFS packages will simply
> get upgraded to the official/main Debian (non backports) stretch ZFS
> packages?

Yes, assuming the package names are the same and the dependencies are
satisfied.

> Actually moving on the Debian stretch I would not need anymore the
> backports because the ZFS packages are included in stretch. So could I
> just get rid of my backports APT source by deleting my list file
> beforehand and then simply do a dist-upgrade?

My personal recommendation would be to comment out (or delete) the
old backports line(s).  If in the future you find yourself wanting
stretch-backports (from buster) then add the new backports line at
that time.

[toc] | [prev] | [next] | [standalone]

#189657

FromJohn Naggets <hostingnuggets@gmail.com>
Date2017-12-07 21:10 +0100
Message-ID<uUaEy-2lg-17@gated-at.bofh.it>
In reply to#189656
On Thu, Dec 7, 2017 at 8:29 PM, Greg Wooledge <wooledg@eeg.ccf.org> wrote:

>> Actually moving on the Debian stretch I would not need anymore the
>> backports because the ZFS packages are included in stretch. So could I
>> just get rid of my backports APT source by deleting my list file
>> beforehand and then simply do a dist-upgrade?
>
> My personal recommendation would be to comment out (or delete) the
> old backports line(s).  If in the future you find yourself wanting
> stretch-backports (from buster) then add the new backports line at
> that time.

I think I will go for that variant as it makes the most sense to me.

What about third-party APT repositories sources such as for MongoDB,
Nextcloud, etc, would one simply replace "jessie" with "stretch" in
the sources files at the same time as for the official Debian APT
repositories before running a dist-upgrade?

[toc] | [prev] | [next] | [standalone]

#189660

FromBrian <ad44@cityscape.co.uk>
Date2017-12-07 22:00 +0100
Message-ID<uUbqW-2CC-3@gated-at.bofh.it>
In reply to#189657
On Thu 07 Dec 2017 at 21:02:38 +0100, John Naggets wrote:

> On Thu, Dec 7, 2017 at 8:29 PM, Greg Wooledge <wooledg@eeg.ccf.org> wrote:
> 
> >> Actually moving on the Debian stretch I would not need anymore the
> >> backports because the ZFS packages are included in stretch. So could I
> >> just get rid of my backports APT source by deleting my list file
> >> beforehand and then simply do a dist-upgrade?
> >
> > My personal recommendation would be to comment out (or delete) the
> > old backports line(s).  If in the future you find yourself wanting
> > stretch-backports (from buster) then add the new backports line at
> > that time.
> 
> I think I will go for that variant as it makes the most sense to me.

It doesn't make any difference. The update and upgrade will not get
any packages from jessie-backports. But, whatever suits you.
 
> What about third-party APT repositories sources such as for MongoDB,
> Nextcloud, etc, would one simply replace "jessie" with "stretch" in
> the sources files at the same time as for the official Debian APT
> repositories before running a dist-upgrade?

By all means. Whether they have stretch versions is a different
matter.

-- 
Brian

[toc] | [prev] | [next] | [standalone]

#189649

FromJohn Naggets <hostingnuggets@gmail.com>
Date2017-12-07 18:40 +0100
Message-ID<uU8jo-I6-25@gated-at.bofh.it>
In reply to#189647
On Thu, Dec 7, 2017 at 6:11 PM, Tom Furie <tom@furie.org.uk> wrote:

> Is there a reason not to switch to your backports source to stretch at
> the same time as the others?

If I understand correctly doing that I will end up with the ZFS
packages for unstable (Debian 10) after running a dist-upgrade? Is my
understanding correct?

Currently I have the following packages from jessie-backports:

ii  dh-python                        2.20170125~bpo8+1
all          Debian helper tools for packaging Python libraries and
applications
ii  dkms                             2.3-2~bpo8+1
all          Dynamic Kernel Module Support Framework
ii  libnvpair1linux                  0.6.5.9-2~bpo8+1
amd64        Solaris name-value library for Linux
ii  libuutil1linux                   0.6.5.9-2~bpo8+1
amd64        Solaris userland utility library for Linux
ii  libzfs2linux                     0.6.5.9-2~bpo8+1
amd64        OpenZFS filesystem library for Linux
ii  libzpool2linux                   0.6.5.9-2~bpo8+1
amd64        OpenZFS pool library for Linux
ii  spl                              0.6.5.9-1~bpo8+1
amd64        Solaris Porting Layer user-space utilities for Linux
ii  spl-dkms                         0.6.5.9-1~bpo8+1
all          Solaris Porting Layer kernel modules for Linux
ii  zfs-dkms                         0.6.5.9-2~bpo8+1
all          OpenZFS filesystem kernel modules for Linux
ii  zfs-zed                          0.6.5.9-2~bpo8+1
amd64        OpenZFS Event Daemon
ii  zfsutils-linux                   0.6.5.9-2~bpo8+1
amd64        command-line tools to manage OpenZFS filesystems

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web