Hello,

I've been attempting to get my slack 9.1 box all up-to-date before tackling a kernel rebuild (i've read that this is a good idea). I'm a bit confused by the output from #swaret --update which follows at the end of this post. Am I correct in assuming that the errors that I am getting don't matter because the file lists and checksums are being d/l'ed from another server?

Thanks alot,

plan9 (as in the movie, not the OS)

#swaret --update

swaret 1.6.2-1

[ ftp://ftp.nluug.nl/pub/os/Linux/dist...ckware-current ]
### Fetching CHECKSUMS List File... DONE!
FILELIST List File is up-to-date!
Packages Descriptions up-to-date!
Extra Packages Descriptions up-to-date!
ChangeLog up-to-date!
[ http://users.lichtsnel.nl/pub/slackware ]
### Fetching 'BlazeBox' CHECKSUMS List File... DONE!
'BlazeBox' FILELIST List File is up-to-date!
'BlazeBox' Packages Descriptions up-to-date!
[ http://heart.cuore.org/packages/slackware ]
### Fetching 'CuoreDOTORG' CHECKSUMS List File... DONE!
'CuoreDOTORG' FILELIST List File is up-to-date!
'CuoreDOTORG' Packages Descriptions up-to-date!
[ ftp://ftp.linuxpackages.net/pub/Slackware-9.1 ]
### Fetching 'LinuxPackagesDOTNET.FTP' CHECKSUMS List File... FAILED!
### Fetching 'LinuxPackagesDOTNET.FTP' FILELIST List File... FAILED!
### Fetching 'LinuxPackagesDOTNET.FTP' PACKAGES List File for Packages... FAILED!
[ http://www3.linuxpackages.net/Slackware-9.1 ]
### Fetching 'LinuxPackagesDOTNET.HTTP' CHECKSUMS List File... FAILED!
### Fetching 'LinuxPackagesDOTNET.HTTP' FILELIST List File... DONE!
### Fetching 'LinuxPackagesDOTNET.HTTP' PACKAGES List File for Packages... FAILED!
[ http://packs.slack.it/ ]
### Fetching 'SlackPack' CHECKSUMS List File... DONE!
### Fetching 'SlackPack' FILELIST List File... DONE!
### Fetching 'SlackPack' PACKAGES List File for Packages... DONE!
=> Generating 'SlackPack' List Files... DONE!
[ http://gurno.com/adam/slack/ ]
### Fetching 'GurnoDOTCOM' CHECKSUMS List File... DONE!
'GurnoDOTCOM' FILELIST List File is up-to-date!
'GurnoDOTCOM' Packages Descriptions up-to-date!
[ http://slackpacks.tchelinux.com.br/ ]
### Fetching 'TcheLinux' CHECKSUMS List File... DONE!
### Fetching 'TcheLinux' FILELIST List File... FAILED!
### Fetching 'TcheLinux' PACKAGES List File for Packages... DONE!

Open /etc/swaret.conf and remove the mirrors you don't need.

Well, I just spent some time in /etc/swaret.conf file and it appears to me as though there is a level of redundacy when declaring the Mirrors and Repositories. It seems to me that it would be set this way so that if there was a problem getting a file, swaret would look else where for it. It also seems strange to me that upon a successful get, swaret would continue to try all of the other Mirrors and Repositories anyways.

Am I close?

Thanks,

9

I think I got it, I did some more editing of /etc/swaret.conf and here is what the output looks like now:

bash-2.05b# swaret --update
swaret 1.6.2-1

[ ftp://ftp.nluug.nl/pub/os/Linux/dist...ckware-current ]
### Fetching CHECKSUMS List File... DONE!
FILELIST List File is up-to-date!
Packages Descriptions up-to-date!
Extra Packages Descriptions up-to-date!
ChangeLog up-to-date!
[ http://users.lichtsnel.nl/pub/slackware ]
### Fetching 'BlazeBox' CHECKSUMS List File... DONE!
'BlazeBox' FILELIST List File is up-to-date!
'BlazeBox' Packages Descriptions up-to-date!

bash-2.05b#

I guess so. I'm using 1.6.1, which uses the first working mirror. I think in 1.6.2 it's supporting multiple mirrors, so you can update official slackware packages, and also third party packages. But if a mirror doesn't work, there's no point having it in swaret.conf.

So, all you need is a slackware-current mirror. Linuxpackages.net is also useful, but they recently changed the way their servers work, so you'll have to change the url to get it working properly.

I found out this one works best for me "swaret-1.6.3_test2-noarch-1.tgz".