SlackwareThis Forum is for the discussion of Slackware Linux.
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've had good luck before with Swaret upgrading to the current. The last two days been trying to do that on a new system I just put together and I keep getting a boatload of dep issues. Mostly with libgnomekey something or other. So should I just wait until the next release or how should I go about this? Is the next release going to be soon? There are alot of packages, it appears anyways, and major ones that are upgraded.
Only Patrick Volckerding knows when the next release will be out.
But a few people here think that there is indication that it's not going to be long...
Eg, pkgtool has been updated to version 9.2 in current very recently.
My guess would be that we see a new release within the next two or three months, probably sooner.
The safest, but most tedious way to upgrade is to download what you want and use upgradepkg, then. Your install will most likely work afterwards, but there will be some config files to be edited by hand.
Since you're doing a fresh install, the easiest way is just to install with the packages in -current.
One method is to make your own ISO. Check out the README and other documentation in the isolinux directory of your favorite Slackware mirror.
Another option (and the one I've used several times) is to download everything under slackware-current/slackware to a partition on your hard drive (you can use any of the number of LiveCD distributions to accomplish this) and then point Slackware to that directory during setup.
Upgrading only upgrades existing packages, it does not install new packages that may be needed after an upgrade. Libgnomekey is part of the gnome-keyring package. Just pick a part of the package and look for it. IE the following...
root@desktop1:# swaret --list key
Listing all available Packages...
gnome-keyring-0.2.1-i486-1 (101 kB) [Status: INSTALLED]
If it isn't installed do a
root@desktop1:# swaret --install key
If you upgraded everything you can do
after this, find all of the missing components. You can also do this for gnome or kde after you upgrade:
Swaret --install gnome
Swaret --install kde
It will tell you that package blah blah is already installed until it gets to the one that you are missing. Tell it yes and whaaaaa laaaaaa!
Swaret is close to automatic but not quite.
After you finish, look for all files that end in .new by doing
Replace the old ones if you haven't changed anything. Look to see first and move over any info that you need to.
Look the dep problem is because by default swaret only has a url for dependencies for swaret... Open up your swaret.conf file and where it shows the dependency urls copy one from the main repositories and paste it there then save it... then do swaret --update then swaret --dep.
You obviously didnt do what i told you to do... Copy one of the url for the repositories and place it in the dep area and changed the begging to the DEP_ROOT. Then do swaret --update then swaret --dep. If that doesnt work you just cant handle a nice distro... Because its something U did not the distro.. I hate it when users say its the distro its the user.. The distro cant do anything without being told what to do.