> On 3/14/07, Joe Olivas <[EMAIL PROTECTED]> wrote: >> On Wed, 14 Mar 2007 12:04:18 -0700, Aaron Griffin >> <[EMAIL PROTECTED]> wrote: >> >> > On 3/14/07, Aaron Griffin <[EMAIL PROTECTED]> wrote: >> >> I'd like to here back from you all >> > I'd like to hear* back from you all >> >> I wish I had kept the output, but I've had problems with pacman3 failing >> on packages in testing while doing -Su. It would output that the >> package >> didn't exist, then when I ran it again, it would download the on which >> package it failed, then fail on the next package. >> >> This problem would repeat on each package throughout testing until all >> packages had downloaded. I didn't put much effort into keeping track of >> everything, so I didn't bother filing a likely unhelpful report. But I >> thought I'd at least share it here. If it happens again, I'll copy the >> output... > > Are you sure this wasn't/isn't a mirror problem? Perhaps you were > syncing as the mirror itself was?
Possible, but it has happened at least twice with pacman3, and had never before happened in the past 3 years on numerous machines. > Did it output that the package didn't exist _on the server_, or that > it didn't exist _locally_ ? Did it happen to say that the package was corrupted? Nothing about a corrupt package. It was something like "Failed to get package xyz from some.archlinux.mirror" then it exited. I would run it again with -Su (hopefully eliminating mirror sync problems) and it would get the package xyz, then fail with the same message for the next package in testing. I wish I could be more helpful. I'll run another update when I get home to see if I get the same results. -Joe _______________________________________________ arch mailing list [email protected] http://www.archlinux.org/mailman/listinfo/arch
