On Jan 06 2017, Ian Jackson <[email protected]> wrote:
> Control: forcemerge 849041 -1
>
> Nikolaus Rath writes ("Bug#850469: dgit: Can't push: corrupted object"):
>> remote: dgit-repos-server: reject: corrupted object
>> 1bc3c1e2d353386487d7d8e7740ebd21f369b107 (missing metadata)
>
> Unfortunately dgit 2.13 has a critical bug. It generates corrupted
> commits. See my message to d-d-a:
> https://lists.debian.org/debian-devel-announce/2017/01/msg00001.html
>
>> Help would be appreciated :-).
>>
>> Is this version number really burned now, or can I still do an
>> upload with dput?
>
> It's worse than that. Your git history needs to be rewritten.
> I will write in a moment with advice on what you should do about that.
I did read that message. But the affected package isn't in the list, and
I believe this is the first time that I'm actually uploading this
package with dgit.
> In the meantime, you have three choices:
>
> 1. Wait for advice from me on how to rewrite your history
>
> 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 :-).
I am not sure how to strip the commit though - as far as I can tell it
exists in limbo without any associated branch...?
Best,
-Nikolaus
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
