glibc-2.32 mass rebuild

LuckyCyborg · 01-23-2021, 03:43 PM

Quote:

Originally Posted by garpu

Yeah, I was pleasantly surprised at the fact that nothing broke. That kind of an update on another distro would've been a complete cluster.

Yeah, sure...

If worth something, last week I updated an openSUSE Tumbleweed box, which was not touched since around 3 months. I had around 4000 packages to update and the system survived well after this mega-update.

I should confess that for doing this 4000 packages update I had just to push a button in a popup from Plasma5 system tray, then to wait?

So, maybe you should use also another distributions to see what they do today?

The Linux ecosystem evolved much in the last 20 years. Very much.

RadicalDreamer · 01-23-2021, 04:06 PM

slackpkg was rebuilt. I suggest updating it first.

hitest · 01-23-2021, 04:28 PM

Quote:

Originally Posted by RadicalDreamer

slackpkg was rebuilt. I suggest updating it first.

Slackpkg will prompt you to re-run slackpkg after you run slackpkg upgrade-all.

TheTKS · 01-23-2021, 04:35 PM

Quote:

Originally Posted by RadicalDreamer

slackpkg was rebuilt. I suggest updating it first.

Yup. I forgot to do this and ended up needing an extra step or two to complete the upgrade (the big rebuild of Jan 22 - my mirror hasn't loaded the Jan 23 updates yet.)

Otherwise everything went smoothly, and all is well on my Slackware64 -current.

As always, watch for new configs. I kept my existing modified /etc/inittab, /etc/slackpkg/blacklist and /etc/slackpkg/slackpkg.conf, allowed all others to be overwritten.

TKS

EDIT: what @hitest wrote later, in post 25. My upgrade was complicated by a few download errors during slackpkg upgrade-all that I had to clean up for the upgrade to complete.
ex.

Code:

==============================================================================
  WARNING! One or more errors occurred while slackpkg was running
------------------------------------------------------------------------------
coreutils-8.32-x86_64-2.txz.asc:        md5sum

drgibbon · 01-23-2021, 05:26 PM

@ljb643 Is that after `slackpkg update; slackpkg install-new; slackpkg upgrade-all`, or something else?

ljb643 · 01-23-2021, 05:32 PM

Quote:

Originally Posted by drgibbon

@ljb643 Is that after `slackpkg update; slackpkg install-new; slackpkg upgrade-all`, or something else?

Something else. I'm using upgradepkg, not slackpkg.

Does anyone know if slackpkg takes extra precautions to avoid this situation? Like maybe having its own statically linked "xz"? Then again, I'm not really sure what went wrong. Why did my xz break and not gzip?

drgibbon · 01-23-2021, 06:07 PM

Yes, `slackpkg upgrade-all` installs the upgrades in the correct order.

ljb643 · 01-23-2021, 06:14 PM

Quote:

Originally Posted by ljb643

...Turned out that after aaa_elflibs replaced libc, xz will not work...

No, I was wrong, aaa_elflibs does not contain libc. So that isn't it. But I see that xz uses liblzma that is in fact replaced by aaa_elflibs, so maybe that is the cause.

Edit: Yes, that looks like the cause. xz uses liblzma.so.5. Installing aaa_elflibs replaces this file. If I unpack aaa_elflibs-15.0-x86_64-30.txz and then check it on a system without the new glibc I get this:

Code:

$ ldd lib64/liblzma.so.5.2.5 
lib64/liblzma.so.5.2.5: /lib64/libc.so.6: version `GLIBC_2.32' not found (required by lib64/liblzma.so.5.2.5)

truepatriot76 · 01-23-2021, 06:14 PM

Quote:

Originally Posted by hitest

Slackpkg will prompt you to re-run slackpkg after you run slackpkg upgrade-all.

Unfortunately that was lost on me - I did upgrade-all and went to bed last night. Oh well... almost done with the upgrade, again. (finger's crossed)

hitest · 01-23-2021, 06:32 PM

Quote:

Originally Posted by truepatriot76

Unfortunately that was lost on me - I did upgrade-all and went to bed last night. Oh well... almost done with the upgrade, again. (finger's crossed)

No worries. After upgrade-all finishes downloading everything it will stop when it upgrades slackpkg. At the command prompt re-run slackpkg update, then slackpkg install-new ,and slackpkg upgrade-all again. After you run slackpkg upgrade-all again it will find all of the downloaded packages and start installing them.

Edit: added later: slackpkg wants to rebuild its database after it is upgraded. Once you've done that then the installation process continues normally.

truepatriot76 · 01-23-2021, 07:07 PM

All is well, so far. Wondering what, if any, impact the new glibc will have on MATE. So far everything is functioning as it should. My pesky NM applet freeze/unresponsiveness is back again with activation of a VPN, however.

ljb643 · 01-23-2021, 08:20 PM

Quote:

Originally Posted by drgibbon

Yes, `slackpkg upgrade-all` installs the upgrades in the correct order.

Thanks. Looks like the correct thing to do is to upgrade these in order and before everything else, if they are new: pkgtools, glibc-solibs, aaa_elflibs, readline, sed; then everything else. So I'll try again, this time do glibc-solibs before aaa_elflibs.

slackerDude · 01-23-2021, 08:41 PM

This is why I just pick a specific build / ISO, go to a new partition (I have 3 or 4 available), install everything, then copy over any config stuff..

I can never keep straight exactly which order these things are supposed to happen in. Or what to watch out for, or remember.

Not a criticism of Slackware per se, just that I don't has much time to dig into everything as I used to, and I've forgotten a bunch of stuff. In the early days (mid 90s), I used to update kernels regularly and kind of had it down. These days, more likely than not, I screw something up..

drgibbon · 01-23-2021, 08:59 PM

Why not just use slackpkg then? I can't see any reason for doing it manually other than wanting to learn about the system.

slackerDude · 01-23-2021, 09:58 PM

Quote:

Originally Posted by drgibbon

Why not just use slackpkg then? I can't see any reason for doing it manually other than wanting to learn about the system.

So slackpkg does it all? Including upgrading slackbuilds, etc?

And what is the canonical order? I couldn't understand if I need to run
slackpkg update; slackpkg install-new; slackpkg upgrade-all

and then run all of that again? Or some of that again?

If it's always the same, couldn't someone write a "update_system" script that does all of that and keeps it up to date?