| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| howtos:slackware_admin:systemupgrade [2018/11/17 00:25 (UTC)] – [System Upgrade using SlackPkg] enzuru | howtos:slackware_admin:systemupgrade [2021/08/04 17:31 (UTC)] (current) – In Slackware 14.2 and earlier, the aaa_glibc-solibs package was called glibc-solibs! alienbob |
|---|
| </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 upgrade 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 ''aaa_glibc-solibs'' package manually, immediately after upgrading ''slackpkg'': <code> |
| # slackpkg upgrade glibc-solibs | # slackpkg upgrade aaa_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 ''aaa_glibc-solibs'' package prevents the library linking errors by providing the correct "''GLIBC''" symbols. |
| | <note important>In Slackware 14.2 and earlier, the ''aaa_glibc-solibs'' package was called ''glibc-solibs''</note> |
| |
| * Let ''slackpkg'' update the computer to the new Slackware release: <code> | * Let ''slackpkg'' update the computer to the new Slackware release: <code> |
