Nikolaus Rath writes ("Re: Bug#850005: dgit push without dgit build-source"):
> On Jan 09 2017, Ian Jackson <ijack...@chiark.greenend.org.uk> wrote:
> > I just tried this with 2.13, using one of the tests from the dgit test
> > suite, and it prints the message only once. I think this may have
> > been a mispaste somehow ?
>
> No, this was definitely for real. I know because it got my attention.
How odd.
> I have tried [ to repro ], but not it fails differently:
>
> With the python-llfuse from alioth:
Can you please be more specific about this repro attempt ?
> $ dgit --dpm push
> canonical suite name for unstable is sid
> downloading
> http://ftp.debian.org/debian//pool/main/p/python-llfuse/python-llfuse_1.1.1+dfsg-5.dsc...
> last upload to archive has NO git hash
> using existing python-llfuse_1.1.1+dfsg.orig.tar.xz
> using existing python-llfuse_1.1.1+dfsg-5.debian.tar.xz
> dgit: file python-llfuse_1.1.1+dfsg-5.debian.tar.xz has hash
> 274028fa7ad8efa8cd563f9f21af2049b101b4500caa907e36b10a9f738a8280 but .dsc
> demands hash d1d8ee5c6b4a8a136145c7019cdaabbdf3be13671c97142971891222229c1c87
> (perhaps you should delete this file?)
> ! Push failed, while checking state of the archive.
> ! You can retry the push, after fixing the problem, if you like.
>
> (The .dsc file was just created by debuild -S). Is there a way to
> circumvent this problem to reproduce the original problem?
This message is also mysterious to me. Can you run the above with
dgit -D ? Does the .dsc contain the wrong or right hash of
python-llfuse_1.1.1+dfsg-5.debian.tar.xz ?
Thanks,
Ian.
--
Ian Jackson <ijack...@chiark.greenend.org.uk> These opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
