SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
my systems (slackware64-current) are running now after the massive upgrade. It seems that one has to do
at first. Also be sure that you configure for DOWNLOAD_ALL=on in /etc/slackpkg/slackpkg.conf
Problem is that gnutls, p11 and nettle have to be upgraded/installed in order to get the upgraded version of wget running. On my server where DOWNLOAD_ALL=on is configured the "slackpkg upgrade-all" went well, but since wget was broken I could not run "slackpkg install-new".
I had to rebuild google-chrome.
USB was no longer working until I rebooted the system.
slackpkg install-new is always recommended to be executed before upgrade-all as new packages may be introduced
even if the order is correct, we still need to download wget manually first because it will install like the following:
- nettle (install-new)
- p11 (install-new)
- gnutls (upgrade-all) <- wget is now broken due to changes in gnutls
- wget (upgradepkg manually)
about USB, i didn't test before reboot, so i didn't aware of it
Thanks to willysr and markush - I had a very uneventful upgrade. I do have 3 dead links to delete, but I'm gonna be sure before I delete them. For the moment, everything seems just fine! That said, I am only about 4 minutes running..... hehehe!
Well, if you're running current-32bit, the p11-kit packages is missing, you'll find it in sources/n/ the others are located in the n series.
If you need p11-kit, you need the sourcpackage and the slackbuildscript, both in the same directory, then make the slackbuildscript executable and run it, you'll find the package in /tmp (this is only necessary for 32bit).