tl;dr: use `dgit --for-push clone` and carry on.
Rob Browning writes ("Re: Bug#1076117: dgit: crashes with a remote memory error
on clone"):
> Ian Jackson <[email protected]> writes:
> > But, this repo seems very large. Is there something in it that
> > shouldn't be there?
>
> Hmm, I'm not exactly sure what's there. I was actually trying to clone
> it to understand the situation (I'm very new to dgit), because an
> attempt to push the latest release had failed.
The two seem similar in size. I tried cloning both and they took
comparable lengths of time (2m44 from salsa, 3m18 from push.dgit.d.o).
My laptop spent a long time "Resolving deltas".
So I think this means that the repo contents being not as intended, is
not the cause of the perf problems - it's just a large project with a
large history.
> I've been told that our arrangement is a bit unusual for (current) dgit
> because in addition to hosting multiple Debian distributions in the
> repo, we need to host multiple source packages for the dfsg split, and
> for guile, multiple X.Y versions (until recently, this was also true for
> Emacs).
...
> deb/{emacs,emacs-non-dfsg}/d/{sid,bookworm,...}/{upstream,master}
I think you mean you have these multiple git branches with the
different versions? That seems fine to me.
> For now, I've been advised to just use a temporary clone for dgit
> commands so that it won't introduce incompatible branches/tags/etc. into
> the normal working repo(s).
I don't know who advised you to do this, nor do I known what your git
workflow is, but you should be able to work on everything in one git
tree. Whats important is to keep the *branches* separate, and run the
right command(s) on the right branch.
OTOH there is nothing actually wrong with having multiple trees if you
prefer to work that way, aside from the space wastage.
So I recommend for now you use `dgit clone --for-push`. I'm often
available for more timely consultation via OFTC irc, where I'm Diziet.
Regards,
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.
