On Wed, Aug 26, 2009 at 02:35:21PM -0400, Daniel Richard G. wrote: > Package: apt-cacher > Version: 1.6.8 > > I am testing apt-cacher with checksumming enabled. > > I start the server with an empty cache directory tree and no database > file (such that the database has to be created from scratch), and then > run "apt-get update" on two client machines (in this case, an Ubuntu 32- > and 64-bit system). I start both instances of apt-get as simultaneously > as possible, to increase the odds of running into concurrency issues. If > everything works correctly, I stop the server, empty the cache, delete > the database, and start over. > > Lo and behold, every few iterations, I get something like this: > > $ ./apt-cacher2 -c apt-cacher.conf.testing > debug [21354]: Listening on 0.0.0.0:3142 > *** glibc detected *** ./apt-cacher2 > [ubuntu/dists/jaunty/universe/binary-amd64/Packages.bz2]: corrupted > double-linked list: 0x08b5bc30 *** > ======= Backtrace: =========
My understanding is that if perl itself blows up like this, it is a perl, or more-likely in this case libberkeleydb bug. I suggest resumbmitting against that package. Or I can reassign Mark -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
