Nikolaus Rath writes ("Re: Bug#850469: dgit: Can't push: corrupted object"):
> On Jan 06 2017, Ian Jackson <ijack...@chiark.greenend.org.uk> wrote:
> > 2. If the faulty merge commit 1bc3c1e2d353 is at the top of your
> > history and not buried in it, you can perhaps strip it off and try
> > dgit push again with dgit 2.14. You can use `git fsck --no-dangling'
> > to check if that's the only faulty commit.
>
> Ah, that must be the case then. So I used dgit for the first time and it
> immediately corrupted my history :-).
Sorry!
> I am not sure how to strip the commit though - as far as I can tell it
> exists in limbo without any associated branch...?
Oh, in that case you win. I think if you install 2.14 or 2.16 and run
`dgit quilt-fixup' it will generate a fresh uncorrupted merge, then.
If so you can bump the revision to 1.1 and the push should work.
Ian.
