Hi,

Quoting Johannes Schauer (2015-09-26 13:21:17)
> 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.

my new upstream upload of botch failed due to a weird error in the test suite
so I have some opportunities to test this more without creating any damage. And
indeed I am now able to reproduce this bug!

I did the following:

$ dgit clone botch       # clone the existing repo
$ cd botch
$ uscan --force-download # to get the upstream version because there was no
                         # successful upload of 0.15 to debian yet
$ dch -i                 # create a dummy changelog entry
$ dch -r                 # fixup the distribution value in d/changelog
$ git add debian/changelog
$ git commit -m "dgit test upload"
$ DEB_BUILD_OPTIONS=nocheck dgit -wdd sbuild -d unstable 
--debbuildopt=--changes-option=-S
$ dgit push
[...]
Checksum doesn't match for ../botch_0.15-2.debian.tar.xz
dgit: failed command: dput ftp-master ../botch_0.15-2_multi.changes
dgit: subprocess failed with error exit status 1
! Push failed, while uploading package(s) to the archive server.
! You can retry the upload of exactly these same files with dput of:
!   $changesfile
! If that .changes file is broken, you will need to use a new version
! number for your next attempt at the upload.


The DEB_BUILD_OPTIONS=nocheck is required because as I said earlier, the
testsuite currently fails.

You should see the results of the steps I executed in the current dgit
repository.

Please feel free to do further experiments with the botch repo to reproduce
this problem. You cannot break much - nothing in the archive depends on botch
and I don't think anybody besides me and Helmut Grohne are using it.

Thanks!

cheers, josch

Attachment: signature.asc
Description: signature

Reply via email to