AutoPkg

I have 8.1 installed and just installed AutoPkg and edited the config file so that it checks for slackware-current. It says that I am up to date. So I am wondering is if AutoPkg will update from 8.1 to current, and if so, how do I configure it.

If I recall, It can be done by just changing the conf file to slackware-current. However, I did that once and the system was totally unstable after it completed. Had to wipe it out and reinstall. Not a problem with AutoPkg, I think, just too many differences between the two versions or the current tree wasn't very stable as yet. That was about 5 or 6 months ago. So your mileage may vary.

I was also wondering if anyone has ever used AutoSlack which is available at the link below.

http://freshmeat.net/projects/autoslack/?topic_id=861

I figure I will give this a try and report back the results

Without any fanfare or explanation, the only auto-updating program for Slackware, autopkg, has changed its name to swaret. The "new" program's information can be found at its freshmeat page. Most likely it was to prevent confusion with an earlier project with the same name. Swaret can be found . here

I have used swaret and it works very well. As for upgrading from 8.1 to current...I had all sorts of problems because current is based on gcc-3.2. What I did was just a base install of 8.1 (installed the "a" packages) and networking ("n"). Then I upgraded glibc-solibs, then pkgtools, then "a" packages, then my networking packages (n"). Then I used swaret to install the rest of the packages I wanted. Compiled a custom kernel from 2.4.20 src, and have had no problems at all.

Thank you for show me 'swaret'! Very great tool! One question:

Is a 'swaret --upgrade a' really safe? I mean, does it really work?

And what if Slackware 9.0 is released: What do I have to change to get still the newest packages? Current would become 9.0!

I would imagine that when 9.0 is released, there then would be another current...sometime shortly after. I have used swaret --upgrade -a, with no problems whatsoever.

One must also consider the config file... it is within the config file that you set the directory path, therefore you can just change the path swaret uses when 9.0 becomes official and remain operational.

Yeah great. On 03:00/morning, I tried a --upgrade -a well. It fucked up my total system.

Error on each cmd: ERROR: GLIBC 2.3 not found. Well, as I don't love to recompile my whole system, I reinstall Slackware. PS: See my other thread, I got problems to set up my ADSL connection.

Well I am sorry to hear that but you must remember you still need to follow the upgrade instructions that are posted on the slackware site. They state that you must upgrade the gblic first, otherwise everything will go crazy. You can find the upgrade howto here

If you are upgrading packages from 8.1 to slack-current, you FIRST need to upgrade glibc-solibs*.tgz, and pkgtools-*.tgz. then the other packages can be upgraded.

Well DaOne, you forgot to mention an important step that makes all that possible...
Put your machine in single-user mode with the command
telinit 1
Your best bet is to read the UPGRADE.TXT, I put a link in my previous post. After you do that, then swaret will become a valuable asset.

Well yes, it says to telinit 1. But I have done it without changing to single-user mode. Never had a problem. But you are right...to be on the safe side...FOLLOW THE INSTRUCTIONS. Thanks for clearing that up gadfly.

Originally posted by gadfly Well I am sorry to hear that but you must remember you still need to follow the upgrade instructions that are posted on the slackware site. They state that you must upgrade the gblic first, otherwise everything will go crazy. You can find the upgrade howto here

As I typed 'swaret --upgrade -a' and hit 'return', I knew, that I forgot something...

Thank you guys, next time I'll be smarter But it wasn't so bad, 'cause a long time ago I wanted to repartition my harddisk... I put too much space into /home

[Yes, I know I could change this without complete reinstall]