On Thu, Mar 27, 2014 at 05:14:47PM -0700, Nikolaus Rath wrote: > I'm trying to upload a source package created with > svn-buildpackage. However: > $ svn-buildpackage -S -d -nc > [...] > dpkg-buildpackage -S -d -nc > dpkg-buildpackage: source package python-dugong > dpkg-buildpackage: source version 2.2+dfsg-2 > dpkg-buildpackage: source distribution unstable > dpkg-buildpackage: source changed by Nikolaus Rath <Nikolaus@rath.org> > dpkg-source --before-build python-dugong-2.2+dfsg > dpkg-source: info: using options from python-dugong-2.2+dfsg/debian/source/options: --compression=xz --compression-level=6 --extend-diff-ignore=\.pyc$ --tar-ignore=*.pyc > dpkg-source: info: applying use-local-intersphinx.patch > dpkg-buildpackage: warning: building a source package without cleaning up as you asked; it might contain undesired files > dpkg-source -b python-dugong-2.2+dfsg > dpkg-source: info: using options from python-dugong-2.2+dfsg/debian/source/options: --compression=xz --compression-level=6 --extend-diff-ignore=\.pyc$ --tar-ignore=*.pyc > dpkg-source: info: using source format `3.0 (quilt)' > dpkg-source: info: building python-dugong using existing ./python-dugong_2.2+dfsg.orig.tar.gz > dpkg-source: info: building python-dugong in python-dugong_2.2+dfsg-2.debian.tar.xz > dpkg-source: info: building python-dugong in python-dugong_2.2+dfsg-2.dsc > dpkg-genchanges -S >../python-dugong_2.2+dfsg-2_source.changes > dpkg-genchanges: including full source code in upload > dpkg-source --after-build python-dugong-2.2+dfsg > dpkg-source: info: using options from python-dugong-2.2+dfsg/debian/source/options: --compression=xz --compression-level=6 --extend-diff-ignore=\.pyc$ --tar-ignore=*.pyc > dpkg-source: info: unapplying use-local-intersphinx.patch > dpkg-buildpackage: full upload (original source is included) > $ dput mentors python-dugong_2.2+dfsg-2_source.changes > Checking signature on .changes > gpg: Signature made Thu 27 Mar 2014 05:09:41 PM PDT > gpg: using RSA key 0xD113FCAC3C4E599F > gpg: Good signature from "Nikolaus Rath <Nikolaus@rath.org>" [ultimate] > gpg: Signature policy: http://www.rath.org/gpgpolicy.html > Good signature on python-dugong_2.2+dfsg-2_source.changes. > Checking signature on .dsc > gpg: Signature made Thu 27 Mar 2014 05:09:39 PM PDT > gpg: using RSA key 0xD113FCAC3C4E599F > gpg: Good signature from "Nikolaus Rath <Nikolaus@rath.org>" [ultimate] > gpg: Signature policy: http://www.rath.org/gpgpolicy.html > Good signature on python-dugong_2.2+dfsg-2.dsc. > Checksum doesn't match for python-dugong_2.2+dfsg-2.dsc > I have no idea what may have caused this. Can someone give me a hint > where I should be looking for the cause of this? Your quoted output looks incomplete. The svn-buildpackage command shows no signing of the .dsc or .changes file, and the dput shows that they're signed. Is it possible that you re-signed the .dsc after signing the .changes, thus changing its checksum? -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ slangasek@ubuntu.com vorlon@debian.org
Attachment:
signature.asc
Description: Digital signature