Hi,
Quoting Ian Jackson (2015-09-26 12:21:58)
> Johannes Schauer writes ("Bug#800060: dgit push failed with checksum
> mismatch"):
> > I just started using dgit and tried to use it for my package botch.
> >
> > After having built it with
> >
> > $ dgit -wdd sbuild -d unstable --debbuildopt=--changes-option=-S
> Can you send me a copy of the .dsc, and the .debian.tar.xz, which you
> probably still have lying around ?nope, because I had to do an upload real quick because of an autoremoval. What I did was to: $ dgit clone botch [import new upstream version 0.15, fix something in ./debian and git commit my changes] $ dgit -wdd sbuild -d unstable --debbuildopt=--changes-option=-S $ dgit push So really nothing tricky. I would like to reproduce this myself but as far as I see it, this is tricky because `dgit clone` will now not do the same thing anymore because the git repository already exists and I cannot just do `dgit push` some tests because that will do an actual upload. Could the problem be related to how sbuild prepares the .changes file? For example with above command, the changes file will be named botch_0.15-1_source.changes while in the log I posted it talked about botch_0.15-1_multi.changes? If you tell me how I can reproduce this myself without breaking anything in the Debian archive, I can also give it another go. I would not mind throwing the current botch dgit git history away for testing purposes as I just started. Thanks! cheers, josch
signature.asc
Description: signature
