This might be related might not... I've had in the past update media
that got hosed... One of the things I noticed was that even though I did
remove the media .... I still couldn't get to any of the other locations
either. What I found was that in /etc/urpmi the file urpmi.cfg still
carried the "listing" for the problematic location. Then since urpmi
could read that a location should exist according to this file, but
there where no files in /var/lib/urpmi it would balk and not do
anything. If you do urpmi.update (don't name a media to update.) you'll
get the list of things that urpmi thinks it should be able to update. If
something is listed here that shouldn't be that indicates that you have
"orphaned" entries in urpmi.cfg. Removing the lines between the { and }
that indicate an orphaned media and then redoing as I did the first
time, seemed to get me back on track again.
James
On Tue, 2003-01-14 at 19:32, Jim C wrote:
> I've also had trouble. I tried to create a disk with the updated rpms
> on it and tried to add it as a source. Needless to say it did not go well.
>
> Jim C.
>
> Steffen Barszus wrote:
> > On Wednesday 15 January 2003 02:21, Mark Weaver wrote:
>
>
>
>
> ______________________________________________________________________
>
> Want to buy your Pack or Services from MandrakeSoft?
> Go to http://www.mandrakestore.com
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
