why does sbocheck/slackpkg want to downgrade certain packages?
1 Attachment(s)
I have slightly modified a few slackbuilds, built and installed the packages. Now it looks like sbocheck wants to downgrade them. I didn't make any changes in /usr/sbo/repo but copied the modified slackbuilds to my home folder. Is there some quirk/convention of naming that is causing problems?
Code:
> sbocheck Also, slackpkg+ wants to downgrade my qemu which was built and installed by sboinstall: |
You need to blacklist your SBo packages
In /etc/slackpkg/blacklist Code:
[0-9]+_SBo |
Perhaps for a better understanding: Slackware's package tools do not know the concept of higher/lower version numbers. Just different versions.
|
In other words, slackpkg will always prefer the version of a pkg who came from the repo you defined in slackpkgplus.conf, whatever the version
Code:
REPOPLUS=( slackpkgplus alienbob restricted ) |
Quote:
For example, I can't install kmod-zfs-5.10.35-2.0.4.tgz because there's a package called kmod-28-x86_64-3 installed. So I just rename it to zfsmodules-blah.blah.tgz. (The kmod-zfs-XXXX.tgz name is chosen automatically by something in the zfs-2.0.4 configure scripts.) These modules need to be rebuilt whenever the kernel changes, so I keep being reminded to ask about the naming of packages. |
Quote:
In the case of your two packages, here's how pkgtools see them kmod-zfs-5.10.35-2.0.4 and kmod-28-x86_64-3 So, your kmod-zfs package has a dash in the version, which pkgtools doesn't detect and it is also missing the arch and build/tag. So, pkgtools thinks that kmod is the program name, zfs is the version, 5.10.35 is the arch, and 2.0.4 is the build/tag. To fix the version, you'll need to swap the dash for an underscore (5.10.35_2.0.4) and then adding the arch and build/tag will fix the rest of the package name. Once the package name is fixed, you'll be able to install it properly with no conflit from the stock kmod package. |
Quote:
|
Quote:
and determining for the pkg that will be installed Code:
REPOPLUS=( slackpkgplus alienbob slackers restricted ) Code:
REPOPLUS=( slackpkgplus slackers alienbob restricted ) And, It doesn't matter whether the version of the 2nd repo is higher or not |
I have the same problem to the OP with sbotools, and wondered if anyone has an equivalent solution to those mentioned for slackpkg and slackpkg+?
I'm using ponce's SlackBuilds tree for Slackware64 -current, and sometimes use these SlackBuilds as a basis for my own builds where the SlackBuild is out of date and I need (or want) a newer release from upstream. I don't change the sbo tree, like slackmensch I make a copy and edit the the SlackBuilds scripts elsewhere on my system. It leads to situations like this: Code:
$ sudo sbocheck |
AFAIK, sbotools allows you to override packages from the SBO repo with packages from a local repo.
from documentation on sbotools.conf Quote:
|
Ah yes, thank you! LOCAL_OVERRIDES works perfectly if you keep your own SlackBuild files in the same format as SBo uses, and correctly formatted. I had read the fine manual but misunderstood what that option would do.
Andrew |
All times are GMT -5. The time now is 12:29 PM. |