Sean Whitton writes ("Bug#841383: dgit: splitbrain push fails if package was 
previously pushed without splitbrain"):
> Package: dgit
> Version: 2.3
> Severity: normal
> 
> classic-theme-restorer is maintained in a team gbp repository.  It
> didn't have any quilt patches before, so I'd made an upload using dgit.
> I just added a new quilt patch, and now I can't upload with --quilt=gbp.
> 
>     hephaestus ~/src/classic-theme-restorer % dgit --quilt=gbp push
                                                     ^^^^^^^^^^^
>     canonical suite name for unstable is sid
>     warning: git fetch 
> +refs/tags/archive/debian/*:refs/dgit-fetch/sid/tags/archive/debian/* 
> +refs/tags/debian/*:refs/dgit-fetch/sid/tags/debian/* 
> +refs/dgit/sid:refs/dgit-fetch/sid/dgit/sid created 
> refs/dgit-fetch/sid/heads/master; this is silly, deleting it.

What ?!

>     dgit: split brain (separate dgit view) may be needed (--quilt=gbp).

This message is slightly comedic in context.

>     Use of uninitialized value $_ in pattern match (m//) at /usr/bin/dgit 
> line 4364.

This is probably due to the git second-guessing above.

> On a second try, I get slightly different output:
> 
>     hephaestus ~/src/classic-theme-restorer % dgit --quilt=gbp push
>     canonical suite name for unstable is sid
>     downloading 
> http://ftp.debian.org/debian//pool/main/c/classic-theme-restorer/classic-theme-restorer_1.5.7-1.dsc...
>     last upload to archive specified git hash
>     using existing classic-theme-restorer_1.5.7.orig.tar.xz
>     Format `3.0 (quilt)', need to check/update patch stack
>     dgit: split brain (separate dgit view) may be needed (--quilt=gbp).
>     Use of uninitialized value $_ in pattern match (m//) at /usr/bin/dgit 
> line 4364.
>     ! Push failed, while preparing your push.
>     ! You can retry the push, after fixing the problem, if you like.
> 
> `debcheckout classic-theme-restorer` will get you what I'm trying to
> push, if that helps, including a pristine-tar branch.

Thanks.

I will look at this later today.

Ian.

Reply via email to