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 11:11:40 +0100 [thread overview]
Message-ID: <20210224111140.0af49108@rosa.proxmox.com> (raw)
In-Reply-To: <d95acf82-c3c1-b94d-4f49-3e01d54d6894@gmail.com>
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`?
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 10:11 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 [this message]
2021-02-24 10:50 ` Uwe Sauter
2021-02-24 11:40 ` Stoiko Ivanov
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=20210224111140.0af49108@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.