glibc-2.32 mass rebuild

avian · 01-23-2021, 10:21 PM

Quote:

Originally Posted by slackerDude

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?

slackpkg will do it all, but will quit itself when after it updates itself, forcing you to then do another update and upgrade-all.

I noticed that on a VM, so on my main system, i did a "slackpkg update ; slackpkg upgrade slackpkg pkgtools ; slackpkg update ; slackpkg upgrade-all" and the process was smoother, without the interruption in the middle.

edit: sorry i didnt notice you said "including slackbuilds".. slackpkg doesnt upgrade slackbuilds.

drgibbon · 01-23-2021, 10:24 PM

Quote:

Originally Posted by slackerDude

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

By default (without installing slackpkg+), slackpkg handles just the Slackware binaries that Pat puts out (i.e., normal Slackware packages). SBo is separate from that.

Quote:

Originally Posted by slackerDude

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

The usual way is:

Code:

slackpkg update
slackpkg install-new
slackpkg upgrade-all
# optional*
slackpkg clean-system

If slackpkg itself has been updated, it will update itself, then quit. So you need to start from the beginning again.

*Some people don't like "clean-system" because they don't keep a blacklist file (so it would offer to remove anything not in the main tree, all your SBo packages, etc). I like it to catch removed packages, and I just keep a blacklist so it doesn't touch the stuff I want to keep (SBo, plus a few other things that I've removed and don't want to be prompted about).

Quote:

Originally Posted by slackerDude

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?

I think it's straightforward enough that anyone could customize it for their own system, and it's probably good that people learn how to use slackpkg instead of a single command. I have a shell script which is just*:

Code:

#!/usr/bin/env bash

slackpkg -batch='on' update
slackpkg install-new
slackpkg upgrade-all
slackpkg clean-system

and then I alias 'up' to `sudo /usr/local/sbin/theupgradescript` (with sudo configured to let my user run that script without a password), so it becomes a matter of two characters. But in some cases you still need to know the basics, e.g., -batch-'on' will make slackpkg answer "n" if no changes are found, but sometimes you might want to force that with `slackpkg update` and 'y'. Anyway, there's many ways to do it, but slackpkg is very handy.

*This should be updated with some logic and `slackpkg check-updates` at the start, but I found that it doesn't give back a meaningful return value, so I didn't get around to making it work in a script.

AlleyTrotter · 01-23-2021, 10:51 PM

Quote:

Originally Posted by ljb643

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.

In UPGRADE.TXT in the base directory of the current iso
Pat recommends the upgrade order as follows:

0. Put your machine in single-user mode:
telinit 1

1. Upgrade your glibc shared libraries. This is important, or things
might go haywire during the next part of the upgrade:

upgradepkg slackware/a/glibc-solibs-*.txz

2. Upgrade your package utilities and related tools:

upgradepkg slackware/a/pkgtools-*.txz
upgradepkg slackware/a/tar-*.txz
upgradepkg slackware/a/xz-*.txz
upgradepkg slackware/a/findutils-*.txz

3. Upgrade everything else (and install new packages):

HTH
John

gmgf · 01-24-2021, 01:24 AM

Quote:

Originally Posted by ljb643

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.

I confirme this problem, it seem this problem occurs if the glibc-2.32 was not already installed before the mass rebuild.

teoberi · 01-24-2021, 04:13 AM

Mass rebuild OK on all my servers.

dodoLQ · 01-24-2021, 05:14 AM

Ok here, did it manually using the Changelog, upgradepkg and inspecting few .new files

pchristy · 01-24-2021, 05:24 AM

Worked fine on 3 out of 4 here. Had a hiccup on my main desktop which stalled trying to launch into kde. A quick check of the logs showed a lot of fsck errors on my home directory for some reason. I fired up systemrescuecd and carried out a thorough check on the affected drive and partitions, and now its fine!

I have no idea why this happened, as "home" is on a separate drive from the system (system is on a ssd). Never had an issue with it previously, and no SMART errors showing. Other partitions on the same drive were OK.

Just one of those things, I guess, but I will be monitoring it closely!

--
Pete

GazL · 01-24-2021, 05:38 AM

Quote:

Originally Posted by AlleyTrotter

In UPGRADE.TXT in the base directory of the current iso
Pat recommends the upgrade order as follows:

...snip...

3. Upgrade everything else (and install new packages):

HTH
John

Personally, I'd split 3 into two separate operations:
3. install new
4. upgrade the rest.

but otherwise, yes, that's the approach I take.

P.S. As I was already fully up to date and Pat said there were no changes only rebuilds in this batch, I just did a #find /etc -name "*.new" -delete to save myself some effort with the dot-news.

brianL · 01-24-2021, 09:08 AM

No problems here just using slackpkg.

TheTKS · 01-24-2021, 11:29 AM

Quote:

Originally Posted by TheTKS

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.

...

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

A note to myself, but posting here in case it's useful for anyone else.

This kind of download error during slackpkg upgrade-all is usually no big deal. It happens from time to time on my mirror, and I run this to clean up:

Code:

# slackpkg reinstall [packagename]

What threw me off in this update was these two things happening during the same session of slackpkg upgrade-all:
- There was a slackpkg update
- There was a download error for a few packages

Once slackpg updated itself and interrupted the upgrade (its normal behaviour), I immediately tried to reinstall those packages that experienced download errors, which gave me the message:

Code:

The package list is missing.
Before you install|upgrade|reinstall anything you need to run:

        # slackpkg update

I ran slackpkg update, tried again to reinstall, which gave me the message:

Code:

No packages match the pattern for reinstall.

After puzzling over what to do next, I eventually figured out that in this situation, all you need to do is continue the upgrade normally. On running slackpkg upgrade-all again, Slackpkg picks up files that didn't download correctly.

After future mass rebuilds, and when there is also a slackpkg update, I will do the following update steps (that apply for that particular update) in this order:

1. # slackpkg update
2. Steps in UPGRADE.TXT as @AlleyTrotter reminded above, steps 1 & 2 (and step 0 if needed)
3. # slackpkg upgrade slackpkg
4. # slackpkg update
5. # slackpkg install-new
6. # slackpkg upgrade-all
7. # slackpkg clean-system
8. kernel upgrades, if any

All is still well on my Slackware64 -current

TKS

trollog · 01-24-2021, 03:38 PM

2 Machines upgraded without issue, one lilo/bios the other EFI..

1 minor hiccup on the third, an EFI machine. The kernel was inadvertantly updated from 5.10.8 to 5.10.10
which messed up rebooting, but probably could have been avoided if I paid more attention. I have kernel*
blacklisted, but somehow it disregarded the blacklist. No big problems though. For the magnitiude of this
upgrade, things went pretty smooth. I can't complain. Likely as not, if I had paid closer attention I could
have caught the unintended kernel upgrade before it happened. Still, for the other 2, it was an effortless
push button affair that occurred without hiccups.

slac · 01-24-2021, 04:15 PM

Quote:

Originally Posted by trollog

1 minor hiccup on the third, an EFI machine. The kernel was inadvertantly updated from 5.10.8 to 5.10.10
which messed up rebooting, but probably could have been avoided if I paid more attention. I have kernel*
blacklisted, but somehow it disregarded the blacklist.

I am not sure but that happened probably because slackpkg itself was upgraded thus overriding configuration files at /etc/slackpkg (?)

slac · 01-24-2021, 04:17 PM

Quote:

Originally Posted by GazL

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.

Would you mind to explain how were you planning to do so?

Maybe I'll the do the same when glibc-2.33 comes out.

GazL · 01-24-2021, 06:53 PM

Quote:

Originally Posted by slac

Would you mind to explain how were you planning to do so?

Maybe I'll the do the same when glibc-2.33 comes out.

Easiest way is to pass mitigations=off as a kernel parameter at boot time. Not sure how much difference it will make though.

glorsplitz · 01-24-2021, 07:17 PM

When running current and 15(?) arrives, can you just change the mirror from current to 15(?) and slackpkg update, install-new, upgrade-all?