Difference between revisions of "How to upgrade Salix 13.1 to 13.37"
(→Obsolete packages: CHANGES_AND_HINTS.TXT added) |
(→Upgrading packages) |
||
Line 25: | Line 25: | ||
The upgrade slapt-get itself (along with its dependencies): | The upgrade slapt-get itself (along with its dependencies): | ||
slapt-get -i slapt-get | slapt-get -i slapt-get | ||
− | |||
− | |||
Install the new util-linux package: | Install the new util-linux package: | ||
slapt-get -i util-linux | slapt-get -i util-linux | ||
spkg -d util-linux-ng | spkg -d util-linux-ng | ||
+ | And then upgrade all other package. It's always safer to us to their new versions: | ||
+ | slapt-get --upgrade | ||
'''DO NOT''' use: | '''DO NOT''' use: | ||
slapt-get --dist-upgrade | slapt-get --dist-upgrade |
Revision as of 08:50, 14 April 2011
(This page is work in progress. It will be finalized after Slackware and Salix 13.37 have been released.)
Contents |
Preparing for the upgrade
You first need to change the default repositories to the ones for Slackware and Salix 13.37. Open file /etc/slapt-get/slapt-getrc and change all "13.1" instances to "current". Also make sure the Slackware repositories have an OFFICIAL priority. Example setups are show below:
i486 architecture
SOURCE=http://salix.enialis.net/i486/slackware-current/:OFFICIAL SOURCE=http://salix.enialis.net/i486/slackware-current/extra/:OFFICIAL SOURCE=http://salix.enialis.net/i486/current/:PREFERRED
x86_64 architecture
SOURCE=http://salix.enialis.net/x86_64/slackware-current/:OFFICIAL SOURCE=http://salix.enialis.net/x86_64/slackware-current/extra/:OFFICIAL SOURCE=http://salix.enialis.net/x86_64/current/:PREFERRED
After you make the changes, run
slapt-get -u
Upgrading packages
The combined spkg-pkgtools package has been removed in Salix 13.37. The original Slackware pkgtools are being used, along with a separate spkg package. So, you'll need to replace the spkg-pkgtools package with spkg + pkgtools:
slapt-get -i spkg pkgtools spkg -d spkg-pkgtools
Upgrade your glibc package:
slapt-get -i glibc
The upgrade slapt-get itself (along with its dependencies):
slapt-get -i slapt-get
Install the new util-linux package:
slapt-get -i util-linux spkg -d util-linux-ng
And then upgrade all other package. It's always safer to us to their new versions:
slapt-get --upgrade
DO NOT use:
slapt-get --dist-upgrade
in any case. Although it might seem to be the best option for upgrading to a different version, it really isn't.
Upgrade your udev package, it's locked for upgrades in /etc/slapt-get/slapt-getrc so you have to ask for it explicitly:
slapt-get -i udev
Obsolete packages
Some packages have been obsoleted and should be removed. Some have been replaced by new packages. You can do this automatically with:
slapt-get --remove-obsolete --remove
Careful, because this will also remove all personal packages that you might have installed, if any. If you want a complete list of the obsolete packages, read the Slackware and Salix changelogs and look for entries marked with "Removed". And it's never a bad idea to have a look at the Slackware CHANGES_AND_HINTS.TXT file:
i486 changelogs
Slackware:
- ftp://ftp.ntua.gr/pub/linux/slackware/slackware-current/ChangeLog.txt
- ftp://ftp.ntua.gr/pub/linux/slackware/slackware-current/CHANGES_AND_HINTS.TXT
Salix:
x86_64 changelogs
Slackware:
- ftp://ftp.ntua.gr/pub/linux/slackware/slackware64-current/ChangeLog.txt
- ftp://ftp.ntua.gr/pub/linux/slackware/slackware64-current/CHANGES_AND_HINTS.TXT
Salix:
Upgrading the kernel
Run:
ls /var/log/packages/kernel*
to see which kernel packages you have installed and do a slapt-get -i for each one of them.
If you have switched to the kernel-generic package instead of the default kernel-huge package, don't forget to recreate the initrd.gz file which will be needed for booting you upgraded system. If you're still using the default kernel-huge package, an initrd is not needed anyway and you needn't be concerned about it.
After upgrading the packages, don't forget to edit your /etc/lilo.conf file accordingly and run:
lilo -v
to inform the bootloader about the kernel upgrade.
Configuration files
After doing all the upgrades, run:
dotnew
to accept or reject new configuration files. Make sure that you DO NOT replace your /etc/passwd, /etc/shadow or /etc/group files. If you do, you will lose all users/groups/passwords you have in your system. However, even if you do, you can get the old files back, they will be kept in the same locations, with an .orig suffix.