[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.

Welcome to the Slackware Documentation Project

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
howtos:systemupgrade [2012/09/21 12:27 (UTC)] – Incorporate the feedback from the discussion page. alienbobhowtos:systemupgrade [2012/09/21 13:50 (UTC)] – Add instructions for a multilib system. alienbob
Line 87: Line 87:
  
 <note tip>Bottom-line: you can trust slackpkg to perform a system upgrade safely, but it will need your brains and care.</note> <note tip>Bottom-line: you can trust slackpkg to perform a system upgrade safely, but it will need your brains and care.</note>
 +
 +
 +
 +===== Multilib considerations =====
 +
 +If you are upgrading a multilib 64-bit Slackware computer, there are additional considerations to make.
 +
 +A multilib installation means that you have replaced Slackware's 64-bit ''gcc'' and ''glibc'' packages with multilib versions (ie.e. supporting both 32-bit and 64-bit binaries). Also, you have installed a set of "converted" 32-bit Slackware packages on your 64-bit multilib Slackware. These modifications are all needed to allow you to run and compile 32-bit software.
 +
 +When upgrading such a system, you must of course upgrade the standard Slackware packages, but separately you must upgrade the multilib-specific packages with new versions which you can obtain from http://slackware.com/~alien/multilib/
 +
 +  * First (if you use slackpkg), you must blacklist all these multilib packages so that they will not be accidentally replaced or removed during a system upgrade. If you don't blacklist them, you will face a lot of manual de-selections in "''slackpkg clean-system''". \\ Starting with the release of ''[[http://slackware.com/~alien/multilib/14.0/|compat32-tools]]'' for Slackware 14.0 you can simply add two lines to the ''/etc/slackpkg/blacklist'' file: <code>
 +[0-9]+alien
 +[0-9]+compat32
 +</code> Then you will manually have to download and upgrade the multilib packages. In the below example I will use Slackware 14.0 as the release to which you will be upgrading.
 +  * Download the multilib packages suitable for your new Slackware release from a mirror, like this: <code>
 +# rsync -av rsync://taper.alienbase.nl/mirrors/people/alien/multilib/14.0/ multilib-14.0/
 +</code> This command will create a new subdirectory "''multilib-14.0''" in your current directory with all packages inside
 +  * install/upgrade the existing ''gcc'' and ''glibc'' packages, and ''compat32-tools'': <code>
 +# cd multilib-14.0
 +# upgradepkg --install-new *.t?z
 +</code>
 +  * Upgrade the set of converted 32-bit Slackware packages (often referredto as the "//compat32//" packages): <code>
 +# upgradepkg --install-new slackware64-compat32/*-compat32/*.t?z
 +</code> Alternatively you can run the "''massconvert32.sh''" script which will have been installed as part of the ''compat32-tools'' package. Pass it a 32-bit Slackware package directory (or a 32-bit Slackware mirror URL) as parameter and that will create a set of converted "''compat32''" packages which you can then install. You would only have to do this if you suspect that the content of the "''slackware64-compat32''" directory is not up to date.
  
  

Trace:

howtos:systemupgrade ()