swaret screw up my slack!!!!!!!!!

ha...ha.. i won't use swaret anymore.....i have to install fresh slack after upgrade....

what will not work? If swaret.conf is set to 10.0 there should be no issues. When it is set to current is where problems may arise. If you have a command prompt try swaret --dep then install the files listed.

i set it to current.....i took me 10 hrs to download 300MB packages and the result was very amazing.......it mess up my slack

slapt-get is pretty good, just leave the stock config in /etc to slackware's ftp and jaos is in there too, don't use any of those other mirrors at LinuxPackages.net as a mirror as they tend to screw things up too...

current is where the problems happen. Use 10.0 and only upgrade what you need to. Also always run "swaret --dep" after swaret does its own dep check. I have had the same problems. Current=not stable or even untested.

i already have the current packages inside my hard drive (from swaret) and how to update these packages using slapt-get??

Originally posted by H2O-linux current is where the problems happen. Use 10.0 and only upgrade what you need to. Also always run "swaret --dep" after swaret does its own dep check. I have had the same problems. Current=not stable or even untested.

i am using 10.0 right now & i execute the dep check after installing the current packages....

slapt-get is a tool that is basically apt-get from debian, i only used it to download & install upgrades from slackware's ftp, i guess you can add a location on your harddrive as a source, i never did it that way tho, i usually just run upgradepkg *tgz in a directory that has all the upgrades and in a separate directory i keep extra packages i just run installpkg *tgz

If you install Slack 10 and upgrade to current afterwards your installation is going to get hammered. Make sure you upgrade all of your 10.0 packages first, THEN upgrade to current.

That's how I do it and have not had any problems.

This is strange, I haven't had a problem doing an upgrade to current, although I almost killed it updating only one package (X) at a time.

Well, I'm on the other side of that coin I had Slack 10.0 and updated all the packages....then tried upgrading to current(using slapt-get and swaret --dep), which broke my machine, I had all kinds of errors, I've reinstalled so I don't remember them all. But some were I couldn't compile any programs, my nvidia drivers would no longer recognize even if I used an older module, even after I made sure to change out all the *.new conf files with the older ones(and I checked to make sure there wasn't some option that was gone in the newer configs..). For me and my machine, staying away from slack-current is a good idea.

Basically what swaret do is download and install/upgrade packages in your system, nothing more

But be advised that upgrade a package often install .new config files that may need to be
tweaked (and remove .new in filename)

Also when upgrading, avoid upgrade all packages at the same time if you are not sure what
will be upgraded and in which order, do that step by step.

I use swaret and have no problem with current, I have to say that I think twice when swaret
ask me if I want to download and install a package, I generally separate swaret upgrade into
logic steps, then check the .new config file if any, do the config change and then continue
the upgrade for other packages

Don't shoot the messenger; Swaret isn't the problem.

Kent

Originally posted by keefaz Basically what swaret do is download and install/upgrade packages in your system, nothing more But be advised that upgrade a package often install .new config files that may need to be tweaked (and remove .new in filename) Also when upgrading, avoid upgrade all packages at the same time if you are not sure what will be upgraded and in which order, do that step by step. I use swaret and have no problem with current, I have to say that I think twice when swaret ask me if I want to download and install a package, I generally separate swaret upgrade into logic steps, then check the .new config file if any, do the config change and then continue the upgrade for other packages

well it sounds to me what you're saying is if you're going to do a swaret upgrade to current, practice extreme caution, because swaret doesn't check for dependencies while it installs...which I also found out the hard way.

And oxleyk I agree, I'm a dumbass, but swaret should come with a warning saying use at your own risk....which it might have, I never took the time to read all the documentation on it. There have been cases where I used swaret to install xine, and it crashed my system. Then again I always wanted a new system, I heard these ECS motherboards are crap now...ah well all I was saying for the most part is use caution when upgrading your packages.

Swaret isn't really an official slackware application, so by default it's a use-at-your-own-risk application. That said, I use it to do completely unattended upgrades on a production machine. That box only updates the 10.0 files.

My home computer gets updated to current about every week. The things you have to be careful with swaret is never upgrade the kernel with swaret, don't upgrade lilo or swaret itself with swaret.

No, swaret doesn't do much dependency checking, but it does virtually automate the process of finding and installing updates to Slackware. For that reason alone, I find it indespensable.