There seems to be a lot of people hitting this:
* https://forums.debian.net/viewtopic.php?f=17=152419
*
https://www.reddit.com/r/debian/comments/qcwpfr/sudo_is_completely_broken_after_i_accidentally/
Thus I am posting this to clarify things:
Release notes of Debian 11 (bullseye)
On Oct 10, Otto Kekäläinen wrote:
> Yeah, but one should be able to skip at least one release, right? What
No.
> Could you please consider if the libcrypt1 change was done in a way so
> that at least Buster to Bookworm upgrades would work?
This has already been discussed: feel free to do the
On Sun, Sep 26, 2021 at 9:27 PM Marco d'Itri wrote:
>
> On Sep 27, Otto Kekäläinen wrote:
>
> > Seems this libcrypt1 change not only affects upgrades from Stretch,
> > but in some cases even upgrades from Buster:
> Buster to Bookworm still means skipping a release.
Yeah, but one should be able
On Sep 27, Otto Kekäläinen wrote:
> Seems this libcrypt1 change not only affects upgrades from Stretch,
> but in some cases even upgrades from Buster:
Buster to Bookworm still means skipping a release.
--
ciao,
Marco
signature.asc
Description: PGP signature
Hello!
Seems this libcrypt1 change not only affects upgrades from Stretch,
but in some cases even upgrades from Buster:
- https://salsa.debian.org/mariadb-team/galera-4/-/jobs/2008098
- https://salsa.debian.org/mariadb-team/galera-4/-/jobs/2008103
I wonder if there is some workaround? Could we
This issue is a bit nasty though, as if a user encounters it,
recovering with apt is impossible as dpkg depends on perl and will not
run if libcrypt1 got broken:
$ apt -y install libcrypt1
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to
Thanks for a quick reply. I understand why libc6 maintainers prefer
not to touch the dependencies they have unless the issue is severe.
I guess the workaround for this is to manually start the upgrade by
installing perl-base before upgrading the rest of the system.
Control: tag -1 wontfix
On Sep 06, Marco d'Itri wrote:
> If the fix (Breaks perl-base in libc6?) does not have too many
> collateral effects then it may be worth implementing it anyway even if
> 9 -> 12 upgrades are not officially supported.
Upgrades to Debian 11 work because libc6 used to
On Sep 06, Otto Kekäläinen wrote:
> Something in the upgrade logic to adopt the new pacakge is lacking
> when upgrading libc6 as the system ends in a situation where
> libcrypt.so.1 is removed before the replacement from a new package is
> installed.
Yes, I think that this happens because
Package: libcrypt1
The file /lib/x86_64-linux-gnu/libcrypt.so.1 used to be in package
libc6 on Stretch and Buster until it was split off into a separate
libcrypt in Bullseye (and in Sid).
Something in the upgrade logic to adopt the new pacakge is lacking
when upgrading libc6 as the system ends
10 matches
Mail list logo
