Re: [gentoo-user] Problem with libcrypt transition
On Sun, Apr 10, 2022 at 05:32:26PM +0200, Arve Barsnes wrote > On Sun, 10 Apr 2022 at 15:32, Walter Dnes wrote: > > > I know that the news item gives dire warnings about not unmerging > > glibc. Can I safely unmerge virtual/libcrypt and replace it? > > > > > Sure, but you would probably get the same errors. I'm suspecting you have > some USE flags configured which creates the conflict. Possibly you have set > the USE="crypt" for glibc. I removed virtual/libcrypt and asked a new build, It whined about requiring "static-libs". So I tried that. Lo and behold... = [thimk2][root][~] USE="static-libs" emerge -pv -1 virtual/libcrypt These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild U ] sys-libs/glibc-2.34-r10:2.2::gentoo [2.33-r1:2.2::gentoo] USE="multiarch ssp (static-libs) -audit -caps (-cet) -compile-locales (-crypt*) (-custom-cflags) -doc -gd -headers-only (-multilib) -multilib-bootstrap -nscd -profile (-selinux) -static-pie -suid -systemd% -systemtap -test (-vanilla)" 17,047 KiB [ebuild N ] virtual/libcrypt-2:0/2::gentoo USE="static-libs" 0 KiB [ebuild N ] sys-libs/libxcrypt-4.4.27:0/1::gentoo USE="(compat) (split-usr) static-libs (system) -test" 605 KiB Total: 3 packages (1 upgrade, 2 new), Size of downloads: 17,651 KiB = Notes... 1) Updating glibc 2) pulling in virtual/libcrypt-2 3) pulling in sys-libs/libxcrypt-4.4.27 4) ***NO BLOCKER MESSAGES*** I'll run it for real and let you guys know how things went. -- Walter Dnes I don't run "desktop environments"; I run useful applications
Re: [gentoo-user] Problem with libcrypt transition
On Sun, 10 Apr 2022 at 15:32, Walter Dnes wrote: > I know that the news item gives dire warnings about not unmerging > glibc. Can I safely unmerge virtual/libcrypt and replace it? > > Sure, but you would probably get the same errors. I'm suspecting you have some USE flags configured which creates the conflict. Possibly you have set the USE="crypt" for glibc. Regards, Arve
Re: [gentoo-user] Problem with libcrypt transition
On Sun, 10 Apr 2022 09:32:21 -0400, Walter Dnes wrote: > I know that the news item gives dire warnings about not unmerging > glibc. Can I safely unmerge virtual/libcrypt and replace it? I don't see why not, it is only a virtual and doesn't actually install anything. -- Neil Bothwick There is absolutely no substitute for a genuine lack of preparation. pgpHpk_FbdCTT.pgp Description: OpenPGP digital signature
Re: [gentoo-user] Problem with libcrypt transition
On Sun, Apr 10, 2022 at 08:02:30AM +0200, Arve Barsnes wrote > > Hard to tell from your output what the status of any conflicts are > on your system. As the message correctly indicates, it cannot upgrade > glibc because virtual/libcrypt-1 requires the older version. > > What would portage complain about before you excluded it? I got the exact same error message. > As mentioned in the news item, most upgrades should have just happened on > its own without user interference, so it might also be as simple as > re-running the @world command with --backtrack=1000 See attachment world.txt.gz > What is the output from: > emerge -1va =virtual/libcrypt-2 See attachment lc2.txt.gz I know that the news item gives dire warnings about not unmerging glibc. Can I safely unmerge virtual/libcrypt and replace it? -- Walter Dnes I don't run "desktop environments"; I run useful applications world.txt.gz Description: application/gzip lc2.txt.gz Description: application/gzip
Re: [gentoo-user] Problem with libcrypt transition
On Sun, 10 Apr 2022 at 04:35, Walter Dnes wrote: > To quote Rowan and Martin "Later... that very same evening" (7 hours > and 265 packages) it finished. Now to tackle libcrypt. How do I handle > the following? As near as I can tell from the news item, glibc's > internal libcrypt is being replaced by an external libxcrypt but the > details are vague.. > Hard to tell from your output what the status of any conflicts are on your system. As the message correctly indicates, it cannot upgrade glibc because virtual/libcrypt-1 requires the older version. What would portage complain about before you excluded it? What is the output from: emerge -1va =virtual/libcrypt-2 As mentioned in the news item, most upgrades should have just happened on its own without user interference, so it might also be as simple as re-running the @world command with --backtrack=1000 Regards, Arve
Re: [gentoo-user] Problem with libcrypt transition
Walter Dnes wrote: > I'm a bit late updating a Lenovo laptop. Emerge wouldn't run due to a > conflict with virtual/libcrypt. As a workaround, I ran... > > time emerge --changed-use --deep --update @world --exclude virtual/libcrypt > > To quote Rowan and Martin "Later... that very same evening" (7 hours > and 265 packages) it finished. Now to tackle libcrypt. How do I handle > the following? As near as I can tell from the news item, glibc's > internal libcrypt is being replaced by an external libxcrypt but the > details are vague.. > > = > [thimk2][root][~] emerge -pv --changed-use --deep --update @world > > These are the packages that would be merged, in order: > > Calculating dependencies... done! > > Total: 0 packages, Size of downloads: 0 KiB > > WARNING: One or more updates/rebuilds have been skipped due to a dependency > conflict: > > sys-libs/glibc:2.2 > > (sys-libs/glibc-2.34-r10:2.2/2.2::gentoo, ebuild scheduled for merge) > USE="multiarch ssp (static-libs) -audit -caps (-cet) -compile-locales > (-crypt) (-custom-cflags) -doc -gd -headers-only (-multilib) > -multilib-bootstrap -nscd -profile (-selinux) -static-pie -suid -systemd > -systemtap -test (-vanilla)" conflicts with > sys-libs/glibc[crypt(+),static-libs(+)] required by > (virtual/libcrypt-1-r1-1:0/1::gentoo, installed) USE="static-libs" > > > > !!! The following installed packages are masked: > - virtual/libcrypt-1-r1::gentoo (masked by: package.mask) > /usr/portage/profiles/base/package.mask: > # Sam James (2021-11-22) > # Mask the older libcrypt virtual (which accepted glibc[crypt]) to ease > # dependency resolution. In a fair number of cases, this has helped > # upgrades go through cleanly. > # Read the news item if you need help! > # (This mask is undone in musl profiles where the transition is not yet being > # made.) > # bug #699422. > > For more information, see the MASKED PACKAGES section in the emerge > man page or refer to the Gentoo Handbook. > = > There's a news item on this. In case you don't have it for some reason, here's the info from it. [78] 2021-10-18 migrating from glibc[crypt] to libxcrypt in stable root@fireball / # eselect news read 78 2021-10-18-libxcrypt-migration-stable Title migrating from glibc[crypt] to libxcrypt in stable Author Andreas K. Hüttel Author Sam James Posted 2021-10-18 Revision 1 The implementation of libcrypt.so within glibc has been deprecated for a long time and will be removed in the near future. For this reason, we are following other distributions (where this has been tested for years already) and switching to the external libxcrypt implementation, now also in stable installations. This will be a regular update, and in nearly all cases you will not have to take any action and not observe any problems. If you hit issues, please read on. ## Upgrades before 2021-11-01 We do recommend, however, that your system is *fully* up to date first. This is a standard recommendation but in this specific case, it is useful to have a simplified depgraph to ensure that Portage is able to smoothly calculate an upgrade path. Please take the opportunity to fully upgrade your systems now, before the migration occurs, to simplify matters This change will occur on 2021-11-01 for stable users. ~arch users by default should already have switched. ## General advice We also recommend being in a root shell (not via 'sudo' or similar tools) so that if any issues occur during the upgrade, you are not locked out of the console. It is not expected that any such issues will occur but this is a precaution. It is also recommended that users do _not_ have FEATURES="collision-protect" enabled because it is aggressive in protecting even orphaned files. Instead, use FEATURES="unmerge-orphans" which is almost identical in behaviour. ## Delaying the migration *or* circular dependencies If for whatever reason you do *not* wish to switch now - which is only delaying the inevitable - you need to take the following steps: * unmask and enable the crypt USE flag of sys-libs/glibc * mask the system USE flag of sys-libs/libxcrypt * mask >=virtual/libcrypt-2 * unmask virtual/libcrypt:0/1 If hitting circular dependencies involving Python 3.10, see the wiki for more details [3], but the same steps listed above must be taken (mask newer libcrypt temporarily, do a world upgrade, then unmask). ## Migrating early If you wish to manually migrate now, there are a series of steps described on the wiki (see below), but the outline is: * unforce the crypt USE flag of sys-libs/glibc and disable it * unmask the system and split-usr (if applicable) USE flag of sys-libs/libxcrypt and enable it * unmask
[gentoo-user] Problem with libcrypt transition
I'm a bit late updating a Lenovo laptop. Emerge wouldn't run due to a conflict with virtual/libcrypt. As a workaround, I ran... time emerge --changed-use --deep --update @world --exclude virtual/libcrypt To quote Rowan and Martin "Later... that very same evening" (7 hours and 265 packages) it finished. Now to tackle libcrypt. How do I handle the following? As near as I can tell from the news item, glibc's internal libcrypt is being replaced by an external libxcrypt but the details are vague.. = [thimk2][root][~] emerge -pv --changed-use --deep --update @world These are the packages that would be merged, in order: Calculating dependencies... done! Total: 0 packages, Size of downloads: 0 KiB WARNING: One or more updates/rebuilds have been skipped due to a dependency conflict: sys-libs/glibc:2.2 (sys-libs/glibc-2.34-r10:2.2/2.2::gentoo, ebuild scheduled for merge) USE="multiarch ssp (static-libs) -audit -caps (-cet) -compile-locales (-crypt) (-custom-cflags) -doc -gd -headers-only (-multilib) -multilib-bootstrap -nscd -profile (-selinux) -static-pie -suid -systemd -systemtap -test (-vanilla)" conflicts with sys-libs/glibc[crypt(+),static-libs(+)] required by (virtual/libcrypt-1-r1-1:0/1::gentoo, installed) USE="static-libs" !!! The following installed packages are masked: - virtual/libcrypt-1-r1::gentoo (masked by: package.mask) /usr/portage/profiles/base/package.mask: # Sam James (2021-11-22) # Mask the older libcrypt virtual (which accepted glibc[crypt]) to ease # dependency resolution. In a fair number of cases, this has helped # upgrades go through cleanly. # Read the news item if you need help! # (This mask is undone in musl profiles where the transition is not yet being # made.) # bug #699422. For more information, see the MASKED PACKAGES section in the emerge man page or refer to the Gentoo Handbook. = -- Walter Dnes I don't run "desktop environments"; I run useful applications
