Happy Tuesday everyone - Bear with me while I set up the question:
I recently decided to start following current (x86_64).
I have both slackpkg and slackpkgplus installed (and basically configured the way I have them on my 14.2 host, which is on different hardware than concerns my current question). The slackpkgplus configuration is so I can follow packages from SBo, AlienBob (including some of AlienBob's restricted packages) as well.

I decided to get up to date with the Dec. 25 Changelog

Normally, I just issue:

But I noticed that some new packages were recently added.
So, I issued:

I found it odd that I was given a choice to install
opus-1.1-x86_64-1 from my configured AlienBob repository,
when I was expecting to find
opus-1.3_beta-x86_64-1 from my chosen slackware mirror.

I ended up issuing:
(which worked just fine), and now I don't see the AlienBob version (which is ok). But my questions are the following:

Why didn't opus-1.3_beta show up in my original install-new list?
Now that I've installed it, why don't I see opus-1.1 from AlienBob?
(Ultimately I guess my question is why do these two packages sometimes seem to be different versions of the same package, and sometimes not?)

Under the theory that my slackpkgplus.conf settings are driving this, here are what might be relevant from there.

My real ultimate question is how do I make sure that I haven't missed any install-new opportunities?

Also, I have never been interested in multi-lib and it is not involved.

TIA

Also, for everyone who believes, I hope Santa was good to you.

Correction: Now that I have opus-1.3_beta-1 installed (slackware mirror); opus-1.1-1 (alienbob) is shown as a possible from upgrade-all list. Looks like I should add it to my greylist file. Still a little confused, though.

A repository listed in PKGS_PRIORITY will have priority over the official Slackware repository. As "alienbob" is configured in your PKGS_PRIORITY, it means that if a package is present in both alienbob repository and official Slackware repository, then slackpkg would select the one from alienbob.

From "man 5 slackpkgplus.conf"

As a first step, you can greylist opus. The opus package in alienbob repository (current) will probably be soon removed since opus was added to official Slackware current.

1 members found this post helpful.

I implemented the better alternative and removed opus from my -current repository... your issue should be resolved.

1 members found this post helpful.

Thank you both - although I know I read the manpage on slackpkgplus.conf, it obviously happened on a day when I was not paying attention. Oops.

So, What my basic take on this is that in PKGS_PRIORITY I should list only specific packages that I know I don't want overridden (i.e. I shouldn't put a repository name there unless I also qualify it with a package name, like I have with vlc and ffmpeg.

Alien Bob: very much a thank you for all your hard work. Also thank you for removing opus. And, although you've probably already noticed it, a similar situation may come up regarding ninja.

If you are unsure, for a list of package additions you can have a look at
http://bear.alienbase.nl/mirrors/sla..._AND_HINTS.TXT
and try a few searches like slackpkg search talloc to see if the packages come up as installed.

For the alienbob general repository, agreed, but for multilib and (I'm pretty sure) ktown it would be in fact OK to have the full-repository priority, because those do need to replace a few Slackware base packages, but you are not using those anyway.

2 members found this post helpful.