Hi Michael, Michael Vogt wrote: > On Thu, May 11, 2006 at 08:15:07PM -0700, David Liontooth wrote: > >> Michael Vogt wrote: >> >>> On Wed, May 10, 2006 at 10:05:14PM -0700, David Liontooth wrote: >>> Can you please attach the output of: >>> # apt-get update -o Debug::PkgAcquire::Diffs=true >>> >>> >> That's a long one: >> > [..] > >> Fetched 3390kB in 2m53s (19.5kB/s) >> Failed to fetch >> ftp://ftp.de.debian.org/debian/dists/unstable/Release.gpg Connection >> timeout >> Reading package lists... Done >> E: Some index files failed to download, they have been ignored, or old >> ones used instead. >> > > Hm, the log looks ok (except for the http timeout of course), what > exactly is the problem? Did something went wrong with the upgrade? > Is your packages file or pkgcache.bin corrupted? > I saw the unexpected files being downloaded and assumed quite mistakenly there was a problem. Now I understand and applaud the new arrangement. Perhaps a note could have accompanied the upgrade? This is after all a major change in behavior, and good news to boot! > > >>> You can get the old apt behaviour back (no pdiff support) with: >>> # apt-get update -o Acquire::PDiffs=False >>> >>> >> Thank you! This won't help wajig, however, though of course if this is >> intended behavior in apt, wajig can presumably be modified to work >> around it. What's the added benefit of the pdiff patch? >> > [..] > > The pdiff patch will only download "diffs" (ed-style) for the Packages > index files. This means that for a daily update you have to get ~50kb > instead of the usually 3-4Mb. > > >> #366678: wajig show no longer shows any packages >> > [..] > > I have no idea why wajig does not work with apt 0.6.44. I would be > interessted to know how it interfaces with apt to help fixing this > problem. I will be glad to help you making it "harmonize with a > madman". I'm usually around on irc in #ubuntu-devel if you want to > discuss it with fast turn-around. > Thank you for the offer; I've let the wajig author and maintainer know.
Please close this bug report; it was submitted in error. Best wishes, David -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
