Johannes Schauer writes ("Bug#841414: Should occasionally run git-gc in
dgit-repos"):
> for a couple of days I have tried to do the following:
>
> $ dgit clone botch
> canonical suite name for unstable is sid
> fetching existing git history
> remote: warning: suboptimal pack - out of memory
> remote: error: Out of memory, malloc failed (tried to allocate 39463959 bytes)
> remote: error: failed to read object 6589076593033b14cbf88501a33f125114cdc244
> at offset 147000846 from
> ./objects/pack/pack-4c586b14374007fb92d278d8767e35f9c324f0a5.pack
> remote: fatal: packed object 6589076593033b14cbf88501a33f125114cdc244 (stored
> in ./objects/pack/pack-4c586b14374007fb92d278d8767e35f9c324f0a5.pack) is
> corrupt
> remote: aborting due to possible repository corruption on the remote side.
> fatal: protocol error: bad pack header
> dgit: failed command: git fetch -p -n -q https://git.dgit.debian.org/botch
> '+refs/tags/archive/debian/*:refs/dgit-fetch/debian/tags/archive/debian/*'
> '+refs/tags/debian/*:refs/dgit-fetch/debian/tags/debian/*'
> '+refs/dgit/sid:refs/dgit-fetch/debian/dgit/sid'
> dgit: subprocess failed with error exit status 128
>
> Is this an issue on my side or is this a problem with the dgit
> infrastructure?
Thanks for this report. This is an infrastructure issue. I will try
to fix it for you...
Ian.
