Hi Ian, Quoting Ian Jackson (2018-08-04 18:15:47) > Thanks for the report. This is a very new tool and as you can see it has > some rough edges both in docs and (at least) error messages.
no problem! I'm happy to report the bugs I find. ^^ > > I just wanted to try out using git-debrebase with my package img2pdf which > > is currently maintained using dgit. Having read the dgit-maint-debrebase > > man page, I did: > I did dgit clone img2pdf and it appears to have no patches. I'm not sure why > you think you need git-debrebase ? Because I wanted to add one. > If you really want to use it (eg you are about to start a patch queue) you > will need git-debrebase convert-from-gbp. > > Which bits of dgit-maint-debrebase gave you the impression you could > just dgit clone without doing more ? (You're the 2nd perso to think > this, but I think your context is different...) I was reading the dgit-maint-debrebase man page wrongly. Here is where I tripped: Firstly, I was reading the section "converting an existing package" because obviously the package already existed and thus the section "initial debianisation" didn't apply to me. Still correct so far. I then had to decide between "no existing git history" and "existing git history using another workflow". I read both sections and decided for "no existing git history" for the following reasons: - "existing git history using another workflow" cloned from salsa as an example but I was using dgit, so no salsa (or former alioth) is involved - "existing git history using another workflow" mentioned a command called "git debrebase convert-from-gbp" but I was not using gbp so I thought it would not apply to my package - "no existing git history" on the other hand showed a command that I *do* use when I want to work with my package: "dgit clone foo" Thus, I concluded that "git history" was probably referring to "a gbp based workflow on salsa" which was not the case for me. Thus I thought I should just follow the instructions given in "no existing git history". > > Use of uninitialized value $r[2] in join or string at > > /usr/bin/git-debrebase line 935. > > at /usr/share/dgit/gdr/perl5/Debian/Dgit.pm line 127. > > Debian::Dgit::__ANON__("Use of uninitialized value \$r[2] in join or > > string at /usr/bi"...) called at /usr/bin/git-debrebase line 935 > > main::walk("813ddd3849b33668d7120276a1219038411cc075") called at > > /usr/bin/git-debrebase line 1267 > > main::cmd_new_upstream() called at /usr/bin/git-debrebase line 1864 > > This error message is fixed in git but not in 6.4. > My current branch says this instead: > > git-debrebase: error: found unprocessable commit, cannot cope; bare > dgit dsc import: (commit d3481fe48afe150f38f331048abe6452b8389723) > (d.0x30 0x32) > > Related UI bugs are: > > #905005 Want better user hinting for unprocessable commits > #905279 Suggest `dgit convert-from-dgit-view` sometimes > > Ian. Okay, that would tell me that it cannot cope with a commit that was created by dgit very early on in my git history. From this error message I would still not know what to do next. Thanks! cheers, josch
signature.asc
Description: signature