Help answer threads with 0 replies.
Go Back > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Slackware This Forum is for the discussion of Slackware Linux.


  Search this Thread
Old 03-04-2010, 04:14 PM   #16
Slackware Contributor
Registered: Jun 2002
Location: New Zealand
Distribution: Slackware
Posts: 999

Rep: Reputation: 227Reputation: 227Reputation: 227

There are plenty of complete mirrors around.

Switch to a complete mirror.
upgradepkg aaa_elflibs manually and make sure you haven't blacklisted anything unusual in /etc/slackpkg/blacklists

Maybe also try
slackpkg install-new
Old 03-04-2010, 04:37 PM   #17
Senior Member
Registered: Mar 2004
Location: Prince Rupert, B.C., Canada
Distribution: Slackware64-current, OpenBSD 5.8
Posts: 4,700

Rep: Reputation: 762Reputation: 762Reputation: 762Reputation: 762Reputation: 762Reputation: 762Reputation: 762
Originally Posted by GrapefruiTgirl View Post
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.


Thank you very much for this post! I became concerned that I was perhaps doing something illegal by rsynching my -current images with OSUOSL. I am very thankful that they are willing to host our distro.
Old 03-04-2010, 09:15 PM   #18
Senior Member
Registered: Nov 2003
Distribution: Slackware 14.1
Posts: 1,027
Blog Entries: 4

Rep: Reputation: 127Reputation: 127
I switched to the osu repo and got everything installed but now can't startx, seems to be missing the intel driver.
Old 03-04-2010, 09:52 PM   #19
Senior Member
Registered: Nov 2003
Distribution: Slackware 14.1
Posts: 1,027
Blog Entries: 4

Rep: Reputation: 127Reputation: 127
Ok, the log file for x shows the inteldriver loading. Xorgsetup just blanks the display and nothing but the power button works so something is messed up there. What's the easiest way to roll back?


current, gslapt, repositories, slackware, slaptget

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
yum Error: Cannot retrieve repository metadata (repomd.xml) for repository: base. glowe Linux - Newbie 4 07-19-2010 08:42 PM
yum fails with error: Cannot retrieve repository metadata (repomd.xml) for repository dmendonsa Fedora 6 02-10-2010 08:23 PM
Cannot retrieve repository metadata (repomd.xml) for repository ukwho Fedora 6 07-04-2009 04:41 AM
Error: Cannot retrieve repository metadata (repomd.xml) for repository: atrpms. stioanid Linux - Software 3 12-13-2008 02:22 AM
repository problem mkhan919 Ubuntu 2 04-17-2007 04:59 AM

All times are GMT -5. The time now is 06:58 PM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration