From: Stoiko Ivanov <s.ivanov@proxmox.com>
To: Uwe Sauter <uwe.sauter.de@gmail.com>
Cc: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] Update to ZFS 2 available – breaks dependencies
Date: Wed, 24 Feb 2021 12:40:53 +0100 [thread overview]
Message-ID: <20210224124053.6a2216b7@rosa.proxmox.com> (raw)
In-Reply-To: <806e6159-3ca1-530a-ff98-99ac4a4ced05@gmail.com>
On Wed, 24 Feb 2021 11:50:03 +0100
Uwe Sauter <uwe.sauter.de@gmail.com> wrote:
> Am 24.02.21 um 11:11 schrieb Stoiko Ivanov:
> > On Wed, 24 Feb 2021 10:56:49 +0100
> > Uwe Sauter <uwe.sauter.de@gmail.com> wrote:
> >
> >> Hi all,
> >>
> >> since yesterday, 2021-02-23, updates for ZFS 2.0.3 are available.
> >> Currently my systems have 0.8.5 installed. When trying to update using aptitude I get a popup reading:
> >>
> >> ###################
> >> Some packages were broken and have been fixed:
> >>
> >> Keep the following packages at their current version:
> >> libnvpair2linux [Not Installed]
> >> libuutil2linux [Not Installed]
> >> libzfs3linux [Not Installed]
> >> libzpool3linux [Not Installed]
> >> zfs-initramfs [0.8.5-pve1 (now, stable)]
> >> zfs-zed [0.8.5-pve1 (now, stable)]
> >> zfsutils-linux [0.8.5-pve1 (now, stable)]
> >> ###################
> > With ZFS 2.0.0 most shipped libraries got bumped to new major versions
> > (and new package names)
> > e.g.
> > libnvpair1linux -> libnvpair2linux
> >
> > usually this gets resolved correctly (and worked here on many systems)
> > by running `apt full-upgrade` (instead of `apt upgrade`)
> >
> > It has been a while since I worked with `aptitude` - but did you
> > run `aptitude full-upgrade`?
> >
> > else - does it work if you upgrade using `apt full-upgrade`?
>
> ################################
>
> # apt update
> Hit:1 http://ftp-stud.hs-esslingen.de/debian buster InRelease
> Hit:2 http://ftp-stud.hs-esslingen.de/debian buster-updates InRelease
> Hit:3 http://ftp-stud.hs-esslingen.de/debian-security buster/updates InRelease
> Hit:4 http://ftp-stud.hs-esslingen.de/debian buster-backports InRelease
> Hit:5 http://download.proxmox.com/debian/ceph-octopus buster InRelease
> Hit:6 http://download.proxmox.com/debian/pve buster InRelease
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> 15 packages can be upgraded. Run 'apt list --upgradable' to see them.
>
> # aptitude full-upgrade
> The following NEW packages will be installed:
> libnvpair2linux{ab} libuutil2linux{ab} libzfs3linux{ab} libzpool3linux{ab}
> pve-headers-5.4.98-1-pve{a}
> pve-kernel-5.4.98-1-pve{a}
> The following packages will be REMOVED:
> pve-headers-5.4.78-2-pve{u}
> The following packages will be upgraded:
> libproxmox-backup-qemu0 libpve-common-perl libpve-guest-common-perl libpve-storage-perl
> pve-container pve-firmware
> pve-headers-5.4 pve-kernel-5.4 pve-kernel-helper pve-manager pve-qemu-kvm spl zfs-initramfs
> zfs-zed zfsutils-linux
> 15 packages upgraded, 6 newly installed, 1 to remove and 0 not upgraded.
> Need to get 0 B/159 MB of archives. After unpacking 296 MB will be used.
> The following packages have unmet dependencies:
> libzfs3linux : Breaks: libzfs2linux but 0.8.5-pve1 is installed
> libzpool3linux : Breaks: libzpool2linux but 0.8.5-pve1 is installed
> libnvpair2linux : Breaks: libnvpair1linux but 0.8.5-pve1 is installed
> libuutil2linux : Breaks: libuutil1linux but 0.8.5-pve1 is installed
> The following actions will resolve these dependencies:
>
> Keep the following packages at their current version:
> 1) libnvpair2linux [Not Installed]
> 2) libuutil2linux [Not Installed]
> 3) libzfs3linux [Not Installed]
> 4) libzpool3linux [Not Installed]
> 5) zfs-initramfs [0.8.5-pve1 (now, stable)]
> 6) zfs-zed [0.8.5-pve1 (now, stable)]
> 7) zfsutils-linux [0.8.5-pve1 (now, stable)]
>
>
>
> Accept this solution? [Y/n/q/?] q
> Abandoning all efforts to resolve these dependencies.
> Abort.
>
> ################################
>
> Looks like I'm not getting the same updates as you do. I'll wait a few days and check back.
could you try with `apt` instead of `aptitude`
I just tried - and get the same issues when running aptitude (which uses a
different resolver for conflicts) - apt is working fine though :)
Alternatively you should also be able to upgrade by cycling a few times
through aptitudes suggestions.
>
> Thanks,
>
> Uwe
>
> > I hope this helps!
> > Regards,
> > stoiko
> >
> >
> >>
> >> Could someone advice (possible from Proxmox team) advice on how to apply the updates in this
> >> particular situation?
> >>
> >>
> >> Regards,
> >>
> >> Uwe
> >>
> >> _______________________________________________
> >> pve-user mailing list
> >> pve-user@lists.proxmox.com
> >> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
> >>
> >>
> >
> >
>
>
next prev parent reply other threads:[~2021-02-24 11:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 9:56 Uwe Sauter
2021-02-24 10:11 ` Stoiko Ivanov
2021-02-24 10:50 ` Uwe Sauter
2021-02-24 11:40 ` Stoiko Ivanov [this message]
2021-02-24 11:56 ` Uwe Sauter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210224124053.6a2216b7@rosa.proxmox.com \
--to=s.ivanov@proxmox.com \
--cc=pve-user@lists.proxmox.com \
--cc=uwe.sauter.de@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox