SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
and the question asking me whether I wanted to blacklist, ignore, etc. I also tried 'libreoffice*' and '[0-9]+alien', still I got the question. So, I answered "Blacklist" and it made the following entries in /etc/slackpkg/blacklist:
I don't see why none of my blacklist specifications worked, esp. the 1st one with just 'libreoffice' since it added that same string automatically. Why the 'dict..' and 'kde..' suffixes? Shouldn't the string 'libreoffice' be a wildcard for anything containing that string?
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?
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:
and the question asking me whether I wanted to blacklist, ignore, etc. I also tried 'libreoffice*' and '[0-9]+alien', still I got the question. So, I answered "Blacklist" and it made the following entries in /etc/slackpkg/blacklist:
Well that is what you told slackpkg to do, so it blacklisted libreoffice.
The first libreoffice is enough to blacklist the last two.
Quote:
I don't see why none of my blacklist specifications worked, esp. the 1st one with just 'libreoffice' since it added that same string automatically. Why the 'dict..' and 'kde..' suffixes? Shouldn't the string 'libreoffice' be a wildcard for anything containing that string?
Slackpkg made the blacklist entries based on what was shown where your were given the option to blacklist, it took the three base package names and blacklist them as requested. Slackpkg does not know your eventual intentions, so it took care of all by blacklisting as requested. When I run in to this situation, I just ignore, you will be dropped out of slackpkg so you can handle the situation.
Question 2:
Quote:
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?
Not enough information to answer. If the default kernel entries (commented out) in blacklist are not commented out then slackpkg should have upgraded the kernel packages.
Which *should* mean my kernel gets updated. However, when I run 'slackpkg ugrade-all' I get:
Code:
# slackpkg upgrade-all
Checking local integrity... DONE
Looking for packages to upgrade. Please wait... DONE
No packages match the pattern for upgrade. Try:
/usr/sbin/slackpkg install|reinstall
$ ls /var/log/packages/kernel*
$ ls /var/log/packages/slackpkg*
Code:
# ls /var/log/packages/kernel*
/bin/ls: cannot access '/var/log/packages/kernel*': No such file or directory
# ls /var/log/packages/slackpkg*
/var/log/packages/slackpkg-2.82.1-noarch-3
Quote:
Originally Posted by ponce
if it's uninstalled it cannot be upgraded, right?
I regularly update half-a-dozen or more Slackware computers quarterly, sometimes, but not always, updating the kernel -- which I do simply by commenting out the kernel modules in the blacklist file. My logfiles on this particular computer indicate I updated from kernel 4.4.75 to 4.4.88 last October, so this has worked before. Not sure what's up this time.
You're right about the uninstalled/upgrade thing. Doing the same search on another computer gives:
Code:
> slackpkg search kernel
Looking for kernel in package list. Please wait... DONE
The list below shows all packages with name matching "kernel".
[ upgrade ] - kernel-firmware-20170914git-noarch-1 --> kernel-firmware-20180727_b01151b-noarch-1
[ upgrade ] - kernel-generic-4.4.88-x86_64-1 --> kernel-generic-4.4.144-x86_64-1
[ upgrade ] - kernel-headers-4.4.88-x86-1 --> kernel-headers-4.4.144-x86-1
[ upgrade ] - kernel-huge-4.4.88-x86_64-1 --> kernel-huge-4.4.144-x86_64-1
[ upgrade ] - kernel-modules-4.4.88-x86_64-1 --> kernel-modules-4.4.144-x86_64-1
[ upgrade ] - kernel-source-4.4.88-noarch-1 --> kernel-source-4.4.144-noarch-1
[uninstalled] - kernel-module-ecryptfs-4.4.14-x86_64-1
and the 4.4.88 packages *are* in /var/log/packages on that machine.
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?
# ls /var/log/packages/kernel*
/bin/ls: cannot access '/var/log/packages/kernel*': No such file or directory
If I understand well, you have several Slackware computers with kernel 4.4.88 that you want to upgrade to 4.4.144, but, one of these has its package database broken (ie. the files /var/log/packages/kernel-*-4.4.88-* have been deleted, or vanished). In that case, you can fix the broken database using files from one of the other computers with the same architecture :
A. If at least one of the other computers has not been upgraded :
1. Copy the files /var/log/packages/kernel*4.4.88* from this computer to the computer whose packages database is broken
2. upgrade to the latest kernel.
B. If all the other computers has been upgraded :
1. Copy the files /var/log/removed_packages/kernel*4.4.88* of one of these computer to the computer whose packages database is broken.
2. On the computer whose package database is broken, remove the suffix "-upgraded-<DATA>-<TIME>" from the copied files, like in example below :
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.
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.
I've used wget to retrieve Alien Bob's libreoffice from Alien Bob's repository, then used installpkg to install it/them.
Quote:
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:
and the question asking me whether I wanted to blacklist, ignore, etc. I also tried 'libreoffice*' and '[0-9]+alien', still I got the question. So, I answered "Blacklist" and it made the following entries in /etc/slackpkg/blacklist:
Well that is what you told slackpkg to do, so it blacklisted libreoffice.
The first libreoffice is enough to blacklist the last two.
I get that. However, when I initially ran the upgrade-all I already had "libreoffice" in the blacklist. I understood, as you say, that the "first libreoffice is enough to blacklist". But, it did not. I got the the blacklist/ignore message anyway. Perhaps this has something to do with my having two package versions out there, but nevertheless I would have though the blacklist entry for libreoffice would have still prevented any checking on this package.
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.
It's an add-on to slackpkg to handle 3rd party packages with slackpkg; which is why I asked. For now I wouldn't consider installing slackpkg+ until you understand a bit more how slackpkg works.
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
libreoffice-6.0.2-x86_64-1alien
libreoffice-dict-en-5.4.2-x86_64-1alien
libreoffice-dict-en-6.0.2-x86_64-1alien
libreoffice-kde-integration-5.4.2-x86_64-1alien
libreoffice-kde-integration-6.0.2-x86_64-1alien
You can (B)lacklist, (R)emove, or (I)gnore these packages.
Select your action (B/R/I):
You chose 'b' so, the base package name was added to the blacklist file.
A choice of 'i' would have resulted in:
Code:
Okay - slackpkg won't do anything now, but please, do something to fix it.
A choice of 'r' would have resulted in a dialog for you to select which packages to remove.
Quote:
I've used wget to retrieve Alien Bob's libreoffice from Alien Bob's repository, then used installpkg to install it/them.
Something I would do as well. Now if you already had libreoffice installed. Then that would not be a thing I would do. If you had 5.4.2 installed already, running 'installpkg' on 6.0.2 would install that set of packages, resulting in two libreoffice installs.
Quote:
I get that. However, when I initially ran the upgrade-all I already had "libreoffice" in the blacklist. I understood, as you say, that the "first libreoffice is enough to blacklist". But, it did not. I got the the blacklist/ignore message anyway. Perhaps this has something to do with my having two package versions out there, but nevertheless I would have though the blacklist entry for libreoffice would have still prevented any checking on this package.
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.
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.
This is what I would do. Not knowing the exact state of your setup. Run 'removepkg libreoffice' to remove all of libreoffice. Then run 'installpkg *.txz' with the version of libreoffice you want installed. -OR- Alternatively run 'upgradepkg --install-new --reinstall *.txz with the version of libreoffice you want installed.
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
Looking for packages to upgrade. Please wait...
No packages match the pattern for upgrade. Try:
/usr/sbin/slackpkg install|reinstall
As already mentioned, slackpkg does not work with 3rd party packages.
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
No package name matches the pattern.
running 'ls /var/log/packages/libreoffice*' will show that libreoffice is indeed installed.
Putting entries in /etc/slackpkg/blacklist for 3rd part packages only serves to keep them from appearing when you run 'slackpkg clean-system'
Last edited by chrisretusn; 08-14-2018 at 06:06 AM.
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.
Gordie's idea of completely wiping the /var/log/packages directory seemed a bit extreme.
Read it again -- he didn't suggest that. That would be an excellent way of completing hosing package management on your system, though. (I did that once by accident. Woops.)
I'll update my documentation to specify removing the older libreoffice package before installing the new one.
You don't need to do that. I don't know that layout of your system, so I will use what I would do.
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
