LinuxQuestions.org - [SOLVED] Upgraded to Slackware64-current.

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Upgraded to Slackware64-current. (https://www.linuxquestions.org/questions/slackware-14/upgraded-to-slackware64-current-4175655839/)

Upgraded to Slackware64-current.

I upgraded to current yesterday :)

My apologies in advance if the answer is obvious but I have a question about one instruction.

I used Alien Bob's rsync_current.sh script to create a local mirror and upgraded my system using Pat's instructions in UPGRADE.TXT with a few modifications such as which packages to remove, etc.

From /slackware/slackware64-current/UPGRADE.TXT:

Quote:

...

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

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

2. Upgrade your package utilities and related tools:

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

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

upgradepkg --install-new /root/slackware/*/*.t?z

...

I understand why we upgrade glibc first, but...

is the reason we update the package tools and related tools before the rest of the system, rather than with the rest of the system, because we want to use the new package tools as soon as possible? Because of security updates, etc? Is there a different reason, or more reasons?

Any clarification would be greatly appreciated.

Thank you.

Quote:

Originally Posted by Mechanikx (Post 6006103)

is the reason we update the package tools and related tools before the rest of the system, rather than with the rest of the system, because we want to use the new package tools as soon as possible?

Yes

Or you can grab Alien Bob's liveslak. That's what I did, but I was working with a brand-new drive.

There's also an ISO for Slackware64-current.

http://bear.alienbase.nl/mirrors/sla...4-current-iso/

Hello,

Quote:

Originally Posted by Mechanikx (Post 6006103)

I am not running Slackware-current but my assumption is that the package management system has had major changes that have to be applied first so that they be fully effective before installing other packages. This includes the migration of the package database and directories from /var/log to /var/lib/pkgtools. If I am wrong, please someone correct me.

Quote:

Originally Posted by Didier Spaier (Post 6006159)

This includes the migration of the package database and directories from /var/log to /var/lib/pkgtools.

And the usage of the newest tar version instead of the 1.13 release that was used by the older pkgtools package:

Quote:

echo "WARNING: pkgtools are unstable with tar > 1.13."
echo " You should provide a "tar-1.13" in your \$PATH."

This was changed early in the pkgtools-15.0 series of updates.

@garpu @hitest

For my first upgrade I wanted to try the manual method. I enjoyed it so I'm going to stick with it. But thank you for your recommendations. It's much appreciated :)

Quote:

Originally Posted by Didier Spaier (Post 6006159)

Hello,

I am not running Slackware-current but my assumption is that the package management system has had major changes that have to be applied first so that they be fully effective before installing other packages. This includes the migration of the package database and directories from /var/log to /var/lib/pkgtools. If I am wrong, please someone correct me.

That makes sense. Thank you :)

Quote:

Originally Posted by ehartman (Post 6006166)

And the usage of the newest tar version instead of the 1.13 release that was used by the older pkgtools package:
This was changed early in the pkgtools-15.0 series of updates.

Great. Thank you :)

I know I'm late to this, but there can be many reasons to upgrade the package tools before the rest of the system. Didier and ehartman have covered some of the recent reasons, but another major one happened quite a few years back when Pat added support for multiple compression options for packages and started compressing his packages using xz.

If you had simply upgraded the whole distro at once, you would not have had support for the new .txz packages that Pat had in the repo.

Quote:

Originally Posted by bassmadrigal (Post 6007749)

If you had simply upgraded the whole distro at once, you would not have had support for the new .txz packages that Pat had in the repo.

In fact the gzip package in 13.0 (64bit) was one of the few packages left in .tgz form too, so that you could unpack the distributed pkgtools:

Quote:

a/pkgtools-13.0-noarch-3.tgz: Rebuilt.

The xz package itself was still the 12.x one so with the new pkgtools you could then unpack all of the new .txz archives