How to maintain a sane slackware64-current with Eric Hameleers multilib and ktown?
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.
I've got listed packages from slackware repository and from multilib.
There were some twin packages greyed on both repositories, some multilib packages were outdated.
So I'm confused, what to install.
As I understand, multilib package replaces the original one - only multilib in installed, and original Slackware package is removed.
So when there is a list, I selected multilib twins (some outdated) and deselect originals.
Is that correct?
I've got listed packages from slackware repository and from multilib.
There were some twin packages greyed on both repositories, some multilib packages were outdated.
So I'm confused, what to install.
As I understand, multilib package replaces the original one - only multilib in installed, and original Slackware package is removed.
So when there is a list, I selected multilib twins (some outdated) and deselect originals.
Is that correct?
Sounds like something is mixed up. I've never seen items grayed out before. Usually if something is messed up like duplicate packages and such, you are prompted to fix it.
Is /etc/slackpkg/mirrors pointing to a slackware64-current mirror?
Is your PKGS_PRIORITY and are your MIRRORPLUS entries the same as shown in post #14 above.
The only packages that are similar in slackware64-current and multilib are these ('slackpkg search _multilib'). Note the "_multilib" in the command. The rest consist of compat32-tootls and several compat32 packages.:
As I understand, multilib package replaces the original one - only multilib in installed, and original Slackware package is removed.
That is only true for the gcc and glibc packages. The rest (with package names that all end on "-compat32") is installed alongside the original Slackware package (its name being the same without the "-compat32" at the end). Those two packages share no binary data so the one does not replace the other.
Quote:
So when there is a list, I selected multilib twins (some outdated) and deselect originals.
Is that correct?
Sometimes the packages in my multilib repository are outdated because I have more things to do than converting Slackware's 32bit packages and putting them in my multilib repository every day. The fact that sometimes some are outdated is harmless. If it bothers you, I provide the massconvert32.sh script as part of the compat32-tools package, and that script can create up-to-date "-compat32" packages for you.
And, never de-select those 'original packages' you see in slackpkg - those are the updates to original Slackware packages that are waiting to be installed.
The above multilib version is outdated. So which one to install with slackpkg+, as both are listed?
Yeah, I sort of misunderstood. Eric has already answered. I cannot remember the last time I have encountered an issue with the compat32 version being older than the slackware64-current version. The only thing I currently use multilib for is Steam.
This is what 'slackpkg search libcap' produces on my system.
The slackware64 repository package as Eric says should never be unchecked.
"slackpkg upgrade-all" on my system produces:
Code:
root@racermach:~# 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
This is because the compat32 package version installed matches the package version in the multilib repository.
On whate base slackpkg decides which packages from slackware repository are unselected?
On picture, MPlayer, alsa-lib and gst-plugins-good packages are installed, older versions. Should be selected also (for upgrade).
The screenshot attached is from todays upgrade.
I noted in your slackpkgplus.conf listing you posted above that you have GREYLIST=on. Could you post the results of
Code:
cat /etc/slackpkg/greylist | grep -Ev '(^ *#|^$)'
BTW Today's -current update was:
Code:
Mon Jan 20 22:37:58 UTC 2020
a/aaa_terminfo-6.1_20200118-x86_64-1.txz: Upgraded.
d/make-4.3-x86_64-1.txz: Upgraded.
d/python-setuptools-45.1.0-x86_64-1.txz: Upgraded.
l/ncurses-6.1_20200118-x86_64-1.txz: Upgraded.
n/alpine-2.22-x86_64-1.txz: Upgraded.
xap/mozilla-firefox-68.4.2esr-x86_64-1.txz: Upgraded.
This is a bugfix release.
For more information, see:
https://www.mozilla.org/en-US/firefox/68.4.2/releasenotes/
https://bugzilla.mozilla.org/show_bug.cgi?id=1602726
MPlayer-20200103-x86_64-1 (Fri Jan 3 22:41:57 UTC 2020)
alsa-lib-1.2.1.2-x86_64-2 (Tue Dec 31 05:17:04 UTC 2019
gst-plugins-good-1.16.2-x86_64-1 (Wed Dec 4 19:00:33 UTC 2019)
What does 'slackpkg search MPlayer' show?
What does 'slackpkg search alsa-lib' show?
What does 'slackpkg search gst-plugins-good' show?
Last edited by chrisretusn; 01-21-2020 at 05:45 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
