slackpkg upgrade-all questions
Coupla questions ... in /etc/slackpkg/blacklist I had 'libreoffice', yet when I ran slackpkg upgrade-all I got:
Code:
libreoffice-5.4.2-x86_64-1alien Code:
libreoffice Question 2: I upgraded several Slackware64 14.2 systems at the beginning of July and the kernel was upgraded to 4.4.132. I had one more system to go which I just did today (Aug 11), yet it did not upgrade the kernel. This system is still at 4.4.88. The kernel is not blacklisted in /etc/slackpkg/blacklist. Why? |
Quote:
Are you using Alien Bob's repository? What you have is two of each package installed. At some point you must have ran installpkg with libreoffice. You need to run removepkg on one of the set. Alternatively you should be able to run 'slackpkg remove libreoffice' and then select which packages to remove. I'd go with the older version, then run 'slackpkg reinstall libreoffice' for the newer packages. Quote:
The first libreoffice is enough to blacklist the last two. Quote:
Question 2: Quote:
What does 'slackpkg search kernel' ouutput? |
On thing at a time:
Quote:
Code:
# slackpkg search kernel Code:
#kernel-firmware Code:
# slackpkg upgrade-all |
Hello,
Can you post the output of : Code:
$ ls /var/log/packages/kernel* SeB |
Quote:
|
Quote:
Code:
# ls /var/log/packages/kernel* Quote:
You're right about the uninstalled/upgrade thing. Doing the same search on another computer gives: Code:
> slackpkg search kernel Perhaps things are out-of-wack for some reason. Maybe I should just manually install the 4.4.144 kernel modules and I should be back on track? |
THIS WORKS, for me at least. When changing mirrors OR when experiencing problems, empty this directory
Code:
rm /var/lib/slackpkg/* |
Hello,
Quote:
-- SeB |
Thanks for the advice. I mostly went the route of phenixia2003's method B. Gordie's idea of completely wiping the /var/log/packages directory seemed a bit extreme. A one-by-one install of the new kernel as I proposed in post #6 would be the same as phenixia2003's suggestion, but phenixia2003's idea would do them all at once.
|
When is the last time you ran 'slackpkg update'?
That 'slackpkg search kernel' you posted with all the kernels uninstalled is odd. Your package database must be broken. There should be a kernel showing as installed. Running 'slackpkg update' and force it to run if asked might fit it. What does 'uname -r' show? |
Back to the first question ...
Quote:
Quote:
Quote:
My other Slackware systems exhibit this same problem, so I will experiment by removing the duplicate package and seeing if the blacklist prompt goes away. |
Quote:
Even though slackpkg does not handle 3rd party packages, you got this because slackpkg detected a problem, in this case duplicate packages. Code:
libreoffice-5.4.2-x86_64-1alien A choice of 'i' would have resulted in: Code:
Okay - slackpkg won't do anything now, but please, do something to fix it. Quote:
Quote:
Quote:
Key point to remember, slackpkg is only for Slackware packages. Slackpkg does not work with 3rd party packages like libreoffice. The way to handle third party packages it to install them from a directory say /home/non-slack/packages/. For a first time install 'installpkg' is proper. For updated packages, 'upgradepkg' is what should be run. Another option would be to run 'upgradepkg --install-new --reinstall' on the desired packages. This way the package will be installed if new and upgraded in already installed. If you remove the duplicate packages the messages will go away. In fact you will get this as a response to 'slackpkg upgrade-all': Code:
Checking local integrity... DONE For example: with one set of libreoffice packages installed run 'slackpkg search libreoffice' the result will be: Code:
Looking for libreoffice in the package list. Please wait... DONE Putting entries in /etc/slackpkg/blacklist for 3rd part packages only serves to keep them from appearing when you run 'slackpkg clean-system' |
Yup, you (chrisretusn) are right, "When you have two of the same packages installed, slackpkg will still give you that message because it see a problem that needed to be fixed." One of the machines had 2 older versions of LibreOffice. I got the same message. I removed the older two (leaving the current version) and 'slackpkg upgrade-all' gave no error message. So, having two of the same package gives the error message regardless of blacklisting. Good to know. I'll update my documentation to specify removing the older libreoffice package before installing the new one. slackpkg and sbopkg remove the old package automatically. I guess I wrongly assumed installpkg would do the same.
Anyway, problems solved! Thanks |
Quote:
|
Quote:
I would have a directory called /home/non-slack/packages/ In that directory would be all of the 3rd party packages I have installed or want to install. In the case of libreoffice, from that directory, I would remove the old libreoffice files e.g., 'rm libreoffice*.txz'. Then download the new libreoffice files I want to install. Run 'upgradepkg libreoffice*.txz'. This will upgrade the installed libreoffice to the new. Quote:
|
All times are GMT -5. The time now is 05:56 AM. |