Rob Browning writes ("Bug#1076117: dgit: crashes with a remote memory error on
clone"):
> $ dgit clone emacs-non-dfsg
> canonical suite name for unstable is sid
> fetching existing git history
> remote: error: Out of memory, malloc failed (tried to allocate 6880549
> bytes)
> remote: fatal: failed to read object
> 619d4b4412b96fba759869304ffa936b712a55e1: Cannot allocate memory
> 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/emacs-non-dfsg
> '+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'
>
> (I vaguely wondered if that might be git mmap on a large repository
> and/or a 32-bit host.)
This is an infrastructure problem. You'll see I have filed
[rt.debian.org #9567].
git.dgit.debian.org is the public mirror. As a full Debian Project
Member, you have access to the internal origin server. If you say
dgit --for-push clone ... it will use that instead. Hopefully that
will work for you.
But, this repo seems very large. Is there something in it that
shouldn't be there?
Ian.
--
Ian Jackson <[email protected]> These opinions are my own.
Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.
