SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
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.?
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.
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.
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
