LinuxQuestions.org - [SOLVED] slackpkg+: how to keep one package in slackware being upgraded by a 3rd party repos?

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - slackpkg+: how to keep one package in slackware being upgraded by a 3rd party repos? (https://www.linuxquestions.org/questions/slackware-14/slackpkg-how-to-keep-one-package-in-slackware-being-upgraded-by-a-3rd-party-repos-4175527483/)

slackpkg+: how to keep one package in slackware being upgraded by a 3rd party repos?

Dear slackpkg+ers,

A followup from an earlier question: I am using slackpkg+ to maintain AlienBOB's ktown but one package there, harfbuzz, breaks his libreoffice. His recommendation is to downgrade harfbuzz back to the version in slackware64-current, which seems to work fine.

However now slackpkg+ wants to upgrade harfbuzz to the ktown version again.

My slackpkgplus.conf file has the following:

Code:

REPOPLUS=( slackpkgplus alienbobcurrent alienbob ktown4 ktown5)



PKGS_PRIORITY=( ktown5:.* ktown4:.* )



MIRRORPLUS['alienbob']=http://taper.alienbase.nl/mirrors/people/alien/sbrepos/14.1/x86_64/

MIRRORPLUS['alienbobcurrent']=http://taper.alienbase.nl/mirrors/people/alien/sbrepos/current/x86_64/

MIRRORPLUS['slackpkgplus']=http://slakfinder.org/slackpkg+/

MIRRORPLUS['ktown4']=http://taper.alienbase.nl/mirrors/alien-kde/current/latest/x86_64/

MIRRORPLUS['ktown5']=http://taper.alienbase.nl/mirrors/alien-kde/current/testing/x86_64/

and so I am guessing the way to go is to replace

Code:

ktown5:.*

inside PKGS_PRIORITY with

Code:

ktown5:<regexp indicating everything except harfbuzz>

(and similarly for ktown4). However, this is beyond my regexp vocabulary.

Can anyone help?

Many thanks,

Michael

Slapackg+ has a blacklist option.
It will let you "blacklist" the package so slackpkg will ignore any updates or upgrades to it.

Thanks for the reply. Yes I'm aware of the blacklist option. The only issue with that is that if there is a subsequent update of that package in -current then it will be missed.

Cheers,

Michael

Yes, even though you can use any automatic tools. It's recommended to read the changelog and make any necessary changes

Quote:

Originally Posted by michaelslack (Post 5280574)

Thanks for the reply. Yes I'm aware of the blacklist option. The only issue with that is that if there is a subsequent update of that package in -current then it will be missed.

Cheers,

Michael

Then the greylist might be a better option for you.

Solved (thanks to phenixia2003)

Upgrade slackpkg+ to 1.4.0 and put
PKGS_PRIORITY=( patches:harfbuzz slackware64:harfbuzz ktown5 ktown4 )
in your config file.

Minor note: README is missing from /slackpkg+/src

mmm.

there is it.
But apache hide it. If you point directly you can see it.
http://slakfinder.org/slackpkg+/src/README

I will fix when I've time.

However you can also see it on sourceforge
http://sourceforge.net/p/slackpkgplu...ster/tree/src/

I see... ;)

I like to build things makes me feel good. Pulled it from the package. :)

Perfect, thank you phenexia2003

Quote:

Originally Posted by phenixia2003 (Post 5282078)

Hello,

... the issue reported by michaelslack would have easily been fixed with the priorities rules below :

Code:

PKGS_PRIORITY=( patches:harfbuzz slackware64:harfbuzz ktown5:.* ktown4:.* )

Terrific! Marking as solved.

Cheers,

Michael