Anyone else having a repository problem for current?
 

I am using Gslapt version 0.5.2b with slapt-get 0.10.2c and when I try to update I get this error message.

I have tried http ones also but get the same message except instead of FTP: it is HTTP:. Is anyone else having this problem? Are the repositories experiencing difficulties? Is my personal system to blame? Am I an idiot?

Any help given will be greatly appreciated.

Shawn

You may wish to use slackpkg as that is the program that we support. I've had no problems upgrading -current using slackpkg.
Just my :twocents:.

So slapt-get and Gslapt aren't supported?

No. I would switch over to slackpkg, it is an awesome program that is part of the slackware installation.

http://www.slackpkg.org/documentation.html

I have it and have used it. Will give it a try. Still does not answer the original question though.

I haven't had any problems with my -current repository.

Just did the download/upgrade to current an hour ago using the oregon state mirror.

Yeah, that's my mirror. It works very well. :)

Yeah it's not listed as the fastest, but I had issues a few times with the one I had been using (which I won't mention by name) but OSU has worked for me everytime I've used it.

I quit using the OSU mirror after reading this post. OSU requests that only primary/secondary mirrors use their service, which I assume doesn't mean end users pulling a personal copy. I switched to the Virginia Tech Bioinformatics lab (mirrors.vbi.vt.edu) to rsync from. I haven't seen any posted or requested restrictions on the use of their mirror.

Ok here's my newbish showing. Since I use the ftp mirror rather than the rsync mirror I'm not sure if that post would pertain to my usage or not? I just uncommented the line for it in slackpkg.conf.

Good point, I'm not sure. I wouldn't have a problem grabbing incidental packages via ftp from them, but I wouldn't download entire isos or upgrade to current from them. I take their request to mean "please use our bandwidth sparingly", which I respect whether I'm using ftp or rsync. I appreciate that they help distribute Slackware to other mirrors, so I try not to abuse them.

Well I tried slackpkg and the upgrade did not finish. Now I can not get into the system. So I am at a loss.

Same here, bunch of packages missing from the repo so half installed and can't get into xwindows now

FWIW, when slack13/64 was still in -current stage (before it was ever released stable) I was using Oregon State rsync mirror, with Robby's rsync-mirror script. Upon seeing the "Warning" message from their rsync server (mentioned at the post linked above) I emailed the OSUOSL lab and inquired about it, and about whether or not I, as an end user, should not be using their rsync service for personal updates. I got a reply a day or two later, telling me that it was perfectly OK for me to be doing what I was doing.

NOTE/DISCLAIMER: I too always respect such wishes of mirrors -- their bandwidth is graciously donated to them in some cases, and to us in all cases, so it may be best to err on the cautious side in this case. Since I believe I no longer have a copy of that email from them, I cannot prove that they said it was OK, so again, err on the cautious side.
I may have posted that email on LQ here somewhere, because that issue arose before, which *might* have been why I emailed them in the first place. Also, I took it to mean specifically the rsync service, as opposed to both rsync and other methods, but that may be a wrong interpretation. If you do come across it, please provide us the location.
Maybe I should email them again..

Anyhow, back on track: "-current repos", on any particular mirror, might be in a semi-available state at any given time, due to the mirror itself being updated at the very moment YOU are trying to download from it.
I dunno if this has ever happened to me, but so far so good as I am using OSUOSL's ftp server to upgrade to current as we speak. It's in the /xap/ folder right now.

Sasha