Bug#841414: dgit clone fails with "Cannot allocate memory"

2016-10-20 Thread Sean Whitton
There are a lot of settings you can tweak to make git's repacking do better on low memory hosts. On my 256MB VM: athena /home/git % cat .gitconfig [pack] windowMemory = 10m packSizeLimit = 25m threads = 1 It might be that you just need to tweak these settings. -- Sean

Bug#841414: dgit clone fails with "Cannot allocate memory"

2016-10-20 Thread Johannes Schauer
Hi, Quoting Ian Jackson (2016-10-20 12:51:41) > Johannes Schauer writes ("Bug#841414: dgit clone fails with "Cannot allocate > memory""): > > I was unable to reproduce it after having tried to "dgit clone > > botch" for the fifth time.

Bug#841414: dgit clone fails with "Cannot allocate memory"

2016-10-20 Thread Ian Jackson
Johannes Schauer writes ("Bug#841414: dgit clone fails with "Cannot allocate memory""): > I was unable to reproduce it after having tried to "dgit clone > botch" for the fifth time. ?! > So fortunately, I was able to make > another upload of

Bug#841414: dgit clone fails with "Cannot allocate memory"

2016-10-20 Thread Johannes Schauer
Hi, Quoting Ian Jackson (2016-10-20 12:16:29) > Johannes Schauer writes ("dgit clone fails with "Cannot allocate memory""): > > Can you reproduce this problem? How can it be fixed? > > I can reproduce it. I will investigate. I was unable to reproduce it after having tried to "dgit clone botch"

Bug#841414: dgit clone fails with "Cannot allocate memory"

2016-10-20 Thread Ian Jackson
Package: dgit Johannes Schauer writes ("dgit clone fails with "Cannot allocate memory""): > I recently pushed the latest release of my package src:botch to dgit. Now I > tried to clone the repository and I continue getting: > > $ dgit clone botch > canonical suite name for unstable is sid >