Re: failed updates

2013-12-12 Thread Bill Davidsen
Frank McCormick wrote: On 08/12/13 07:31 AM, Michael Schwendt wrote: On Sat, 7 Dec 2013 20:23:42 -0700, Chris Murphy wrote: http://mirror.csclub.uwaterloo.ca/fedora/linux/updates/19/i386/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates Trying other mirror.

Re: failed updates

2013-12-09 Thread Wolfgang S. Rupprecht
Tim ignored_mail...@yahoo.com.au writes: Allegedly, on or about 07 December 2013, Wolfgang S. Rupprecht sent: I do see that on my IPv6 systems whenever the stupid Netgear 3700v4 router craps out after 2-4 days uptime and needs a reboot. The Fedora machinery thinks IPv6 still works, but the

Re: failed updates

2013-12-08 Thread Michael Schwendt
On Sat, 7 Dec 2013 20:23:42 -0700, Chris Murphy wrote: http://mirror.csclub.uwaterloo.ca/fedora/linux/updates/19/i386/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates Trying other mirror. I'm getting this message for pretty much every mirror on an F20

Re: failed updates

2013-12-08 Thread Frank McCormick
On 08/12/13 07:31 AM, Michael Schwendt wrote: On Sat, 7 Dec 2013 20:23:42 -0700, Chris Murphy wrote: http://mirror.csclub.uwaterloo.ca/fedora/linux/updates/19/i386/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates Trying other mirror. I'm getting this message

Re: failed updates

2013-12-08 Thread Ed Greshko
On 12/08/13 21:59, Frank McCormick wrote: Well that solves the problem. What I don't understand is that so few reported the difficulties. Well it could be that some of us never got yum-3.4.3-119 installed. Was it ever pushed to updates or was it only in updates-testing? I updated earlier

Re: failed updates

2013-12-08 Thread Frank McCormick
On 08/12/13 09:16 AM, Ed Greshko wrote: On 12/08/13 21:59, Frank McCormick wrote: Well that solves the problem. What I don't understand is that so few reported the difficulties. Well it could be that some of us never got yum-3.4.3-119 installed. Was it ever pushed to updates or was it

failed updates

2013-12-07 Thread Frank
Just tried to update my Fedora 19 with yum check-update. It seems every mirror has a problem: http://mirror.csclub.uwaterloo.ca/fedora/linux/updates/19/i386/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates Trying other mirror.

Re: failed updates

2013-12-07 Thread Ed Greshko
On 12/08/13 08:03, Frank wrote: Just tried to update my Fedora 19 with yum check-update. It seems every mirror has a problem: http://mirror.csclub.uwaterloo.ca/fedora/linux/updates/19/i386/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates Trying other mirror.

Re: failed updates

2013-12-07 Thread Wolfgang S. Rupprecht
Ed Greshko ed.gres...@greshko.com writes: On 12/08/13 08:03, Frank wrote: Just tried to update my Fedora 19 with yum check-update. It seems every mirror has a problem: http://mirror.csclub.uwaterloo.ca/fedora/linux/updates/19/i386/repodata/repomd.xml: [Errno -1] repomd.xml does not match

Re: failed updates

2013-12-07 Thread Frank
On 07/12/13 07:08 PM, Ed Greshko wrote: On 12/08/13 08:03, Frank wrote: Just tried to update my Fedora 19 with yum check-update. It seems every mirror has a problem: http://mirror.csclub.uwaterloo.ca/fedora/linux/updates/19/i386/repodata/repomd.xml: [Errno -1] repomd.xml does not match

Re: failed updates

2013-12-07 Thread Frank
On 07/12/13 07:25 PM, Wolfgang S. Rupprecht wrote: Ed Greshko ed.gres...@greshko.com writes: On 12/08/13 08:03, Frank wrote: Just tried to update my Fedora 19 with yum check-update. It seems every mirror has a problem:

Re: failed updates

2013-12-07 Thread Chris Murphy
On Dec 7, 2013, at 5:03 PM, Frank bea...@videotron.ca wrote: http://mirror.csclub.uwaterloo.ca/fedora/linux/updates/19/i386/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates Trying other mirror. I'm getting this message for pretty much every mirror on an F20

Re: failed updates

2013-12-07 Thread Tim
Allegedly, on or about 07 December 2013, Wolfgang S. Rupprecht sent: I do see that on my IPv6 systems whenever the stupid Netgear 3700v4 router craps out after 2-4 days uptime and needs a reboot. The Fedora machinery thinks IPv6 still works, but the packets never make it past the router