| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision |
| howtos:slackware_admin:systemupgrade [2012/10/01 20:22 (UTC)] – old revision restored. alienbob | howtos:slackware_admin:systemupgrade [2013/02/18 11:49 (UTC)] – [System Upgrade using SlackPkg] fix spelling tallship |
|---|
| </code> That final ''new-config'' command is there so that you can view the difference betweeen your old and the new ''slackpkg'' configuration files, in particular ''/etc/slackpkg/mirrors'' and ''/etc/slackpkg/blacklist'' are files you have to check. Overwriting ''/etc/slackpkg/slackpkg.conf'' is usually recommended. | </code> That final ''new-config'' command is there so that you can view the difference betweeen your old and the new ''slackpkg'' configuration files, in particular ''/etc/slackpkg/mirrors'' and ''/etc/slackpkg/blacklist'' are files you have to check. Overwriting ''/etc/slackpkg/slackpkg.conf'' is usually recommended. |
| |
| * A new Slackware release usually has a newer version of the GNU C libraries. The new packages are compiled against that new ''glibc'' version. In order to prevent an upgrsde failure, you need to upgrade the ''glibc-solibs'' package manually, immediately after upgrading ''slackpkg'': <code> | * A new Slackware release usually has a newer version of the GNU C libraries. The new packages are compiled against that new ''glibc'' version. In order to prevent an upgrade failure, you need to upgrade the ''glibc-solibs'' package manually, immediately after upgrading ''slackpkg'': <code> |
| # slackpkg upgrade glibc-solibs | # slackpkg upgrade glibc-solibs |
| </code> Let me give an example of such potential failure: when ''slackpkg install-new'' installs the ''libusb-compat'' package, your ''gpg'' command stops working because it links against libusb.so which will be overwritten with the version from the new ''libusb-compat'' package. The new library needs the new ''glibc'' package, ''gpg'' stops working because of the library linking error, and ''slackpkg'' will stop the system upgrade because it wants to check every package's gpg signature before upgrading it. Upgrading the ''glibc-solibs'' package prevents the library linking errors by providing the correct "''GLIBC''" symbols. | </code> Let me give an example of such potential failure: when ''slackpkg install-new'' installs the ''libusb-compat'' package, your ''gpg'' command stops working because it links against libusb.so which will be overwritten with the version from the new ''libusb-compat'' package. The new library needs the new ''glibc'' package, ''gpg'' stops working because of the library linking error, and ''slackpkg'' will stop the system upgrade because it wants to check every package's gpg signature before upgrading it. Upgrading the ''glibc-solibs'' package prevents the library linking errors by providing the correct "''GLIBC''" symbols. |
| # upgradepkg --install-new slackware64-compat32/*-compat32/*.t?z | # 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. | </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. |
| | |
| | |
| | ===== Java considerations ===== |
| | |
| | Slackware used to install a //Java Run-time Engine// prior to the 14.0 release (the JRE binaries were originally Sun's and later distributed by Oracle after it bought Sun). \\ But Oracle changed the re-distribution license so that Slackware (just like all other distributions) was no longer permitted to ship these Java binaries as part of the distribution. When you perform a //system upgrade// to Slackware 14.0, an old version of the //JRE// will stay behind on your system. This version "6u25" has several critical vulnerabilities and you should remove it manually from your computer as fast as possible, using the command <code>removepkg jre</code> If you need Java then please have a look in the "''/extra/source/java''" directory of the Slackware 14 release. You will find a script there to create a Slackware package from the most recent Java software from Oracle, which you can then install using the "''installpkg''" command. See also our Wiki article "[[howtos:software:java|Java in Slackware]]" |
| |
| |
