LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
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
 
LinkBack Search this Thread
Old 12-21-2005, 12:34 AM   #1
jrdioko
Member
 
Registered: Oct 2002
Distribution: Debian 6.0.2 (squeeze)
Posts: 944

Rep: Reputation: 30
Downgraded packages with Slack upgrade


I had discussed this in a previous thread, but I don't remember coming to any resolution so I thought I'd try again to figure something out. I'm going to be upgrading my Slack version again, and I'd like to avoid the biggest annoyance with my past upgrade: when going through and upgrading every package (as part of UPGRADE.TXT), every package gets replaced, even those with a higher version number. For example, I keep gaim up to date, but the upgrade will downgrade the new version to whatever package is in the new version of Slack. Is there a way to directly avoid this, or, if not, at least a way to see a list of which existing packages were replaced with new ones so I can manually go through and check for downgrades?

Along the same lines, is there a list of newly installed packages, so I can see things like firefox/thunderbird packages being installed when I already have them on my system, duplicate packages being installed for checkinstall packages I already have but for whatever reason didn't get named right, etc.?

What does everyone else to do avoid these issues?
 
Old 12-21-2005, 02:17 AM   #2
shilo
Senior Member
 
Registered: Nov 2002
Location: Stockton, CA
Distribution: Slackware 11 - kernel 2.6.19.1 - Dropline Gnome 2.16.2
Posts: 1,132

Rep: Reputation: 49
Quote:
Originally Posted by jrdioko
I'd like to avoid the biggest annoyance with my past upgrade: when going through and upgrading every package (as part of UPGRADE.TXT), every package gets replaced, even those with a higher version number. For example, I keep gaim up to date, but the upgrade will downgrade the new version to whatever package is in the new version of Slack. Is there a way to directly avoid this,
Here's what I do:

Add your initials to packages you create
Use SWareT to upgrade
Pay attention when my initials pop up

Same goes for third party stuff. They should have initials in the package name. If they don't, add them before installing.

Quote:
Originally Posted by jrdioko
or, if not, at least a way to see a list of which existing packages were replaced with new ones so I can manually go through and check for downgrades?
Check out /var/log/removed_packages. You can grep the word upgraded, sort by date, etc. if you like.

Quote:
Originally Posted by jrdioko
Along the same lines, is there a list of newly installed packages, so I can see things like firefox/thunderbird packages being installed when I already have them on my system, duplicate packages being installed for checkinstall packages I already have but for whatever reason didn't get named right, etc.?

What does everyone else to do avoid these issues?
Most would say the ChangeLog. Me too, but nowadays, I use the RSS feed. Really simple method for checking updates. Same thing, but easier to notice changes.
 
Old 12-21-2005, 08:34 AM   #3
dunric
Member
 
Registered: Jul 2004
Distribution: Slackware
Posts: 411

Rep: Reputation: 39
You can avoid such problems by:
  • giving unique/non-conflicting names to your custom or third party packages, like adding underscore to them (gaim_-1.5.1.i486-1, mozilla-firefox_-1.6-i686-3xyz, etc.) upgradepkg */*.tgz won't touch them.
  • use some third party tools like slackpkg or slapt-get. You can "blacklist" them to prevent their upgrade or AFAIK slapt-get even checks and compares package versions.
  • after a complete upgrade rebuild your packages against updated system. It will ensure in addition there won't be any potential broken dependencies.
 
Old 01-01-2006, 05:04 PM   #4
jrdioko
Member
 
Registered: Oct 2002
Distribution: Debian 6.0.2 (squeeze)
Posts: 944

Original Poster
Rep: Reputation: 30
Thanks for the advice all.

Quote:
Originally Posted by shilo
Most would say the ChangeLog. Me too, but nowadays, I use the RSS feed. Really simple method for checking updates. Same thing, but easier to notice changes.
How do you get the RSS for the ChangeLog, anyway?
 
Old 01-01-2006, 05:41 PM   #5
cathectic
Member
 
Registered: Sep 2004
Location: UK, Europe
Distribution: Slackware64
Posts: 761

Rep: Reputation: 34
http://www.slackware.it/en/rss/
 
  


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
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Slack upgrade downgrades packages jrdioko Slackware 13 08-18-2005 04:48 PM
Using Slack 10's 2.6.7 kernel packages on Slack 10.1? SocialEngineer Slackware 1 03-05-2005 11:53 AM
What first upgrade kernel or upgrade slack 10.0 to current Kelean Slackware 7 01-16-2005 06:54 PM
what happen if gcc is downgraded vijaysh Linux - Software 4 01-01-2005 04:20 PM
suddenly having ftp login problems since i downgraded libsafe so i could add sites Amaris4GOW Linux - General 2 04-09-2004 01:07 PM


All times are GMT -5. The time now is 03:19 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