LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 03-04-2011, 08:02 PM   #1
kingbeowulf
Member
 
Registered: Oct 2003
Location: WA
Distribution: Slackware64 14.1, Slackware 14.1
Posts: 526

Rep: Reputation: 140Reputation: 140
slackpkg flags newer packages for update


I have noticed a curious behavior in slackpkg for a while. I sometimes upgrade to a newer version of a standard Slackware package, without using slackpkg. When I next run slackpkg, it flags the older file versions to "upgrade" even though newer packages are installed. These newer packages were created and installed via the standard slackbuild-installpkg route, for example libgpod and hplip to support newer devices.

Otherwise, top notch tool.

Is there a way to fix this?
 
Old 03-04-2011, 08:28 PM   #2
escaflown
Member
 
Registered: May 2009
Location: Canada
Distribution: Slackware
Posts: 237

Rep: Reputation: 30
slackpk will gladly skip all the packages you list in /etc/slackpkg/blacklist. If you don't want slackpkg to update a particular package, just add it to /etc/slackpkg/blacklist.
Alternatively, you can do a "slackpkg blacklist {Pattern|File}" from the console.
"man slackpkg" is your best friend when it comes to using slackpkg.
 
Old 03-04-2011, 08:33 PM   #3
kingbeowulf
Member
 
Registered: Oct 2003
Location: WA
Distribution: Slackware64 14.1, Slackware 14.1
Posts: 526

Original Poster
Rep: Reputation: 140Reputation: 140
Well...that doesn't quite answer my question, and is obvious. The packages I update to newer versions are part of the standard slackware package set - but slack's versions are OLDER. When slackpkg scans for *updates* should it not skip these newer packages? I don't want to blacklist them, in case a newer package pops up in /patches.

I tried to email the maintainer, but the email bounced back.
 
Old 03-04-2011, 08:42 PM   #4
T3slider
Senior Member
 
Registered: Jul 2007
Distribution: Slackware64-14.1
Posts: 2,293

Rep: Reputation: 712Reputation: 712Reputation: 712Reputation: 712Reputation: 712Reputation: 712Reputation: 712
As long as you run `slackpkg update` before doing `slackpkg upgrade-all`, for example, *official* packages that were upgraded using pkgtools should be ignored as long as there isn't an update in patches/. I'd check your /etc/slackpkg/mirrors file and make sure to update the package lists before running `slackpkg upgrade-all` or similar. I upgrade glibc in runlevel 1 out of paranoia and use pkgtools instead of slackpkg for those sorts of packages, and slackpkg happily figures out that I have the latest version the next time I run `slackpkg upgrade-all`. There is no bug in 13.1 as far as I can see...
 
Old 03-04-2011, 08:54 PM   #5
disturbed1
Senior Member
 
Registered: Mar 2005
Location: USA
Distribution: Slackware
Posts: 1,133
Blog Entries: 6

Rep: Reputation: 223Reputation: 223Reputation: 223
Quote:
Originally Posted by beowulf999 View Post
These newer packages were created and installed via the standard slackbuild-installpkg route, for example libgpod and hplip to support newer devices.

Otherwise, top notch tool.

Is there a way to fix this?
There is not a way to fix this. (It's really not broken )The reason being is that slackpkg only looks at the packages available in the Slackware mirror. If the currently available Slackware package is at a different version than what is installed on your PC, slackpkg will upgrade it. This is the way pkgtools in general works. Most of us think of upgrade as meaning an increase in version number. upgradepkg should be thought of and used as replace. I particularly like this feature!!!

Slackpkg's goal and purpose is to keep Slackware pristine and inline with Slackware provided packages.

And yes, I have the same issue. As I routinely run a handful of newer packages than stock Slackware. A small PITA to uncheck the packages. Or as stated above, blacklist them. If you do blacklist them, keep up with the changelog, that way when Slackware does update the package you'll be aware of it.

If you are not already, subscribe to the mailing list. This will notify you of security updates to stable releases. RSS feeds are available for current. slackpkg also has the check-updates option.
http://www.slackware.com/lists/

Last edited by disturbed1; 03-04-2011 at 08:59 PM. Reason: added mailing list info
 
1 members found this post helpful.
Old 03-05-2011, 07:09 AM   #6
allend
Senior Member
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 3,486

Rep: Reputation: 856Reputation: 856Reputation: 856Reputation: 856Reputation: 856Reputation: 856Reputation: 856
This behaviour is a deliberate design decision. It allows for the reversion of a package to a previous version, which can and has happened. The ability to handle reversions should be considered when assessing alternative package managers.
 
1 members found this post helpful.
Old 03-05-2011, 07:11 AM   #7
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,335

Rep: Reputation: Disabled
This is not a bug. Slackware's package management tools not distinguish "old" from "new". They only care about "different". This is by design.

Eric

Edit: allend was a bit faster :-)
 
1 members found this post helpful.
Old 03-05-2011, 07:29 AM   #8
allend
Senior Member
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 3,486

Rep: Reputation: 856Reputation: 856Reputation: 856Reputation: 856Reputation: 856Reputation: 856Reputation: 856
Never, ever faster! Just started a lot earlier :-)
 
Old 03-06-2011, 08:15 PM   #9
kingbeowulf
Member
 
Registered: Oct 2003
Location: WA
Distribution: Slackware64 14.1, Slackware 14.1
Posts: 526

Original Poster
Rep: Reputation: 140Reputation: 140
good enough. Its not how I would've done it but I can see the reasoning. The "why does it do that" itch has been scratched. thanks, all.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
upgrading to newer packages charlie_lab Linux From Scratch 2 06-05-2009 07:21 AM
Make slackpkg prefer /extra over /slackware when listing packages to update rignes Slackware 1 06-02-2007 07:00 PM
Slackpkg cannot find packages, swaret can mago Slackware 42 04-28-2007 01:35 AM
newer packages in debian black_man Debian 1 11-11-2004 04:25 PM
Newer packages on an older system? Pathian Slackware 1 07-07-2004 03:32 PM


All times are GMT -5. The time now is 10:03 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration