swaret --upgrade says my slack9 pkgs are all up to date. wazzup?
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.
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.
swaret --upgrade says my slack9 pkgs are all up to date. wazzup?
i had 9.1 in, and swaret 1.6.0 worked fine. i wiped everything and installpkg swaret 1.6.1, and it chronically claimed i was uptodate.
so i backed-up on /home/cache, reformatted everything but /home, and cdrom-installed 9.0, installed swaret 1.6.1, renamed ~conf.new, edited ~conf for VERSION=current, and #out the kernel exclude, changed filesearch to =1, copied ENGLISH to the lang file, rebooted just in case. did < updatedb && swaret --update && swaret --upgrade -a && swaret --purge >
it clicked along nicely, made the exclude list, then whined that i was up to date and didn't need anything.
stupid machine. how do i outsmart it?
I spotted a topic about this on the forums on the swaret site. Some people were able to fix it by changing some numbers but I cannot recall. Check out this link:
i tried hacking the scripts, tried juggling the ROOTs, (what happened to .nl and .no??), and even the slack ftp is wierded up.
there is something major in glitchland at Slack. i just wiped my swaret files, loaded the swaret-1.3.1 off the slack9.1 #2 cdrom, and caressed it to run.
guess what my console said????
it ain't in the box, folks. mr. volkerding has problems, i think.
luck -O.
Close the string, please. i don't think we/re gonna find a solution here.
.
After removing /var/swaret completely and then running "swaret --update" and "swaret --upgrade -a", I'm upgrading all my packages to slackware-current.
This wasn't working for me this morning, so something has changed today to make this work.
edit: over 300 MB of new packages to download!! Maybe I should do this more than once a month.
i just made an idiot out of myself at swaret.org. don't use the -2 noarch on the home page.
go to the downloads link, and installpkg and configure -3 noarch. changes in files have made earlier versions defunct.
havalottafun!
-O
All users need to upgrade to 1.6.1-3 2004-02-18
Due to changes in the FILELIST.TXT file, all users need to upgrade to 1.6.1-3.
As root, enter:
wget http://www.swaret.org/files/stable/s...1-noarch-3.tgz
upgradepkg swaret-1.6.1-noarch-3.tgz
#'select all', Copy, and Paste into /etc/swaret.conf. these are from the abnormallinux lists.
#set RAMDONR=1 and you won't get any chronic 64k slowups from australia
#RSYNC= is available for all of these sites as well
luck -O.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.