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 revision Previous revision
Last revision Both sides next revision
howtos:slackware_admin:systemupgrade [2013/02/03 21:06 (UTC)]
alienbob Moved "Java considerations" to bottom of article.
howtos:slackware_admin:systemupgrade [2013/02/18 11:49 (UTC)]
tallship [System Upgrade using SlackPkg] fix spelling
Line 60: Line 60:
 </​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.

In Other Languages
QR Code
QR Code howtos:slackware_admin:systemupgrade (generated for current page)