Slackware This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
05-12-2006, 06:00 AM
|
#1
|
LQ Newbie
Registered: May 2006
Posts: 8
Rep:
|
swaret dependency problems on slack 10.2
Hey, I'm working with a fresh install of slackware 10.2. I haven't done anything on this machine yet except configure my ethernet card to work and install swaret to upgrade all the packages. After installpkg'ing swaret, I do:
swaret --update
swaret --upgrade
After this the dependency check fails and it shows I have a bunch of missing libraries. So, I do:
swaret --dep
This returns pretty much the same errors that came up after the upgrades. This is the probably the 4th time I've formatted slackware and reinstalled because of this happening, since I cant run KDM after the upgrades have been applied. I thought having a completely fresh install might help since the times before it was on a system that I had already semi-configured and I thought that maybe I did something in my configuration that would have interfered with the upgrade but I guess that wasn't it.
BTW I'm a total linux newbie, this is my first time ever using Linux outside of fiddling with knoppix and having a ssh shell account.
Here is my log for swaret.log for reference:
eulogy.sixbit.org/swaret.log
^^^I would have made a hyperlink but I'm not allowed to do that until I make 3 posts.
Thanks.
EDIT: I just read a few posts on here and it looks like it could be that I'm using "current" with swaret and I have have 10.2 installed. I had no idea there was a difference, I thought 10.2 WAS the current. Please don't hesitate to reply if you think its something else though. I'm going to redo the whole process tomorrow after I get some sleep and I'll post an update.
Last edited by tedious46; 05-12-2006 at 06:12 AM.
|
|
|
05-12-2006, 06:34 AM
|
#2
|
Senior Member
Registered: Aug 2003
Location: UK
Distribution: Slackware
Posts: 3,467
Rep: 
|
10.2 stays at 10.2 while current will be updated from time to time with new or newer packages.
Using any auto-upgrading tool like swaret will upgrade existing packages but will not add any new packages needed unless you tell it to. Therefore have a good read of the current changelog to see any extras that you need to install.
Recently acl and attr packages were added to current and IIRC they do affect kde and possibly kdm.
|
|
|
05-12-2006, 06:54 AM
|
#3
|
Slackware Contributor
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 8,559
|
Slackware-current is the name for the development of Slackware. If you want a stable system, you better stay with one of the stable releases; 10.2 being the most recent of those.
The slackware-current tree can be considered as a "snapshot" of the development, and therefore can contain serious bugs from one day to the other, that may render your system unuseable. The people that install slackware-current should realize thy are running bleeding-edge and in fact are Slackware beta-testers. Bugs can pop up and you're encouraged to report them to volkerdi at slackware dot com.
You can follow the progress of the slackware-current development process by reading the Slackware Current (pre-release) ChangeLog
By the way, was swaret configured by default to use slackware-current, or did you change the default? After the release of any Slackware version, whenever patches and bugfixes are released, they are placed into the /patches directory of that particular release (like here for Slackware 10.2 for instance: http://slackware.mirrors.tds.net/pub...ches/packages/) and swaret is smart enough to go looking there for the updates it should install on your freshly installed system.
Eric
|
|
|
05-12-2006, 09:32 AM
|
#4
|
Member
Registered: Feb 2004
Location: NY
Distribution: Debian (Testing)
Posts: 219
Rep:
|
The guide at the top of the page thats stickied that everyone points too says to change it to "current" :P
|
|
|
05-12-2006, 09:49 AM
|
#5
|
Slackware Contributor
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 8,559
|
Quote:
Originally Posted by Zaskar
The guide at the top of the page thats stickied that everyone points too says to change it to "current" :P
|
Hm, so I notice. I do not agree with that though. I think it can open a can of worms, especially when new Slackware users are urged to read that guide and proceed without knowing what might happen to them if they suddenly find themselves being migrated from Slackware-10.2 to slackware-current!!!
Apart from that, I would not point new Slackware users to Swaret myself at all, either...
If I were you I'd contact the writer of that guide and tell him about the dangers of unknowingly and unwantingly upgrading to -current as the result of this.
Eric
|
|
|
05-12-2006, 12:05 PM
|
#6
|
LQ Newbie
Registered: May 2006
Posts: 8
Original Poster
Rep:
|
Quote:
Originally Posted by Alien Bob
By the way, was swaret configured by default to use slackware-current, or did you change the default?
|
I changed the default.
|
|
|
05-12-2006, 12:50 PM
|
#7
|
Senior Member
Registered: Aug 2003
Location: UK
Distribution: Slackware
Posts: 3,467
Rep: 
|
Quote:
Originally Posted by Alien Bob
After the release of any Slackware version, whenever patches and bugfixes are released, they are placed into the /patches directory of that particular release (like here for Slackware 10.2 for instance: http://slackware.mirrors.tds.net/pub...ches/packages/) and swaret is smart enough to go looking there for the updates it should install on your freshly installed system.
|
Slackpkg does check for patches though, and I recommend that people use it rather than a 3rd party tool. Slackpkg should be in /extras iirc. But of course READ THE CHANGELOG before using anything to upgrade.
|
|
|
05-12-2006, 01:36 PM
|
#8
|
LQ Newbie
Registered: May 2006
Posts: 8
Original Poster
Rep:
|
Quote:
Originally Posted by dive
But of course READ THE CHANGELOG before using anything to upgrade.
|
The changelog for every package that I'm going to upgrade?
|
|
|
05-12-2006, 02:10 PM
|
#9
|
Senior Member
Registered: Aug 2003
Location: UK
Distribution: Slackware
Posts: 3,467
Rep: 
|
|
|
|
05-12-2006, 03:47 PM
|
#10
|
Slackware Contributor
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 8,559
|
Quote:
Originally Posted by tedious46
The changelog for every package that I'm going to upgrade?
|
If you have installed slackware-current: YES
If you have installed a stable official release (like 10.2): NO
The ChangeLog of Slackware-current is for those who want to run on bleeding edge. It is the way to check if there are critical issues that were resolved, or if there are important changes in the package sets. Remember that after any official Slackware release, nothing new gets added - only updates to packages will be released in order to squash bugs that are discovered after release.
Slackware-current however, sees new packages added regularly. Also, other packages can be removed from the tree during development (remember all of Gnome went down the pipe for instance?).
You must not and should not depend on a tool like swaret which is not part of Slackware, to keep your system sane if you are running slackware-current. The Slackware forum here at LQ is full of threads started by people borking their system after letting swaret loose on the -current tree.
Eric
|
|
|
05-13-2006, 04:34 AM
|
#11
|
LQ Newbie
Registered: May 2006
Posts: 8
Original Poster
Rep:
|
Alright, I redid the whole process and everything worked out fine except my video settings for X11 are a little off now. The resolution, color depth, and refresh rates are all screwed up. I ran xorgsetup first to see if it would be able to autoconfigure my optimal settings, but I still got the same problem. So, I read a tutorial on how to use xorgconfig, and set that up as best as I could. My video card wasnt in the list of cards to choose from, so I just chose a (generic) driver. This helped but it still isn't as good as it could be. I know this because when I boot knoppix my resoultion is perfect and the color depth is 32 instead of the 24 that xorgconfig configures. When booting I can see that knoppix automatically recognizes my exact video card and sets the optimal settings. I looked at the X11 configuration file for my knoppix boot, but it is older than the one X11 currently uses on my machine (knoppix still uses the XF86Config file instead of xorg.conf). What should I do to get the settings for X11 on knoppix to be used on my machine? Would I have to manually find the drivers that knoppix has for my video card and monitor? Or can I just import the settings from the XF86Config file to the xorg.conf file somehow?
|
|
|
All times are GMT -5. The time now is 02:51 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|