glibc-2.32 mass rebuild
 

Bandwidth.

In ChangeLog.txt:

... And prepare for the glibc-2.33:

Could someone explain the reasoning behind this rebuild against the upgraded glibc other than test if the package still builts?

Well, is not only about "still building" but also about "still working" because between versions the libraries slightly differ as behavior.

Take as example the lack of "sys/sysctl.h" from the latest GLIBC, and with stubs which returns "ENOSYS", as is debated there: https://www.linuxquestions.org/quest...-h-4175689085/

Generally, the programs are capable to auto-configure at build time regarding what features are available. That's WHY when a library is upgraded, is much better to rebuild the programs which depends on it, to take the last set of available features.

How on GLBIC depends everything, the result is this mass rebuild.

However, those mass rebuilds are not a thrilling new invention, in fact all major distributions do them for consistency.

This mass rebuild upgrade process has taught me a valuable lesson about specifying a domestic FTP mirror. Big shout-out to the Nara Institute of Sci & Tech.

Yep, but Pat did warn us, in the changelog, a couple of days ago that it was coming.

IMO it's worth doing these mass updates at least once a cycle close to release -- especially this cycle, as it has been such a long time.

I just wish upgradepkg was a little faster. Took quite a while to apply that lot here. The duplicate scanning has always been slow, but since the meltdown mitigations, its really noticeable. If I'd thought, I'd have disabled them at boot while I applied this lot. Oh, well, next time.

One way of doing a mass rebuild of SBo packages:

Yes it took quite some time, particularly on my slowest unit. The upgrade went without a hitch.

Done the mass rebuild update & upgrade on my Thinkpad X200 (T410 next). Thought it was going to be a nerve-wracking, hair-raising, experience. But it wasn't. My nerves aren't wracked, and I'm still bald. :)

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.

I had no problems save Facebook crashed and shut down 1/2 the world last night causing downloads to take forever. Should have waited until later, set er up and gone to bed. Then it would be all over by morning.

all up and running here as well,
download from local mirror was almost faster than the slackpkg upgrade-all, it went through.

All done, everything seems to work still.

Forgot to say: Thanks, Pat! :hattip:

Thanks!

Glad it worked for everyone else, but total 'crash and burn' here.

After upgradepkg did aaa_elflibs, every other package failed with "ERROR: Package ... did not install correctly. You may need to install your old package to avoid problems. Make sure the new package is not corrupted."

Trying to use installpkg to go forward or backward failed with "external compression utility ... missing".

Turned out that after aaa_elflibs replaced libc, xz will not work - complains about libc.so.6 version GLIBC_2.32 not found. Without xz, you can't install anything, including xz.

I noticed that gzip still worked, so I copied the previous aaa_elflibs package to another system, unxz it, gzip it, copy it back, and was able to install it then and revert. Now I'll try to clean up and figure out what to do next.