Package: pbuilder Version: 0.229.3 Severity: normal Hi there,
While building the cvc4 package for upload, I tried setting SOURCE_ONLY_CHANGES=yes in order to generate a *_source.changes file. Everything was apparently fine, but when I tried to upload to changes file, I got the following error: $ dput ftp-master cvc4_1.6-2_source.changes Uploading cvc4 using ftp to ftp-master (host: ftp.upload.debian.org; directory: /pub/UploadQueue/) running allowed-distribution: check whether a local profile permits uploads to the target distribution running protected-distribution: warn before uploading to distributions where a special policy applies running checksum: verify checksums before uploading Bad checksums on cvc4_1.6-2_source.changes: Checksum mismatch for file cvc4_1.6-2.dsc: b65d2b868fd05a6aeb7606e5f03a05f3 != f83d68e6a9f76c3a887d3ff6e7b498f9 Comparing the cvc4_1.6-2_source.changes file against the cvc4_1.6-2_amd64.changes file, one can see that the checksum for the cvc4_1.6-2.dsc file is indeed different between them. In the end, I had to do a normal upload. I'm using gbp buildpackage with pbuilder behind the curtains, and my config files are: $ cat .pbuilderrc # Automatically sign builds. AUTO_DEBSIGN=yes PDEBUILD_PBUILDER=cowbuilder BUILDRESULT=$PWD/../ SOURCE_ONLY_CHANGES=yes $ cat .gbp.conf #### Config file for git-buildpackage [DEFAULT] pristine-tar = True # Tell git-buildpackage how to clean the source tree. This is needed # for pbuilder. cleaner = fakeroot debian/rules clean # This is how we invoke pbuilder, arguments passed to git-buildpackage # will be passed to dpkg-buildpackage in the chroot. builder = /usr/bin/git-pbuilder [import-orig] # Always merge the upstream/ branch onto the master/ branch. merge = True [buildpackage] # Always sign tags sign-tags = True # My key ID keyid = BLABLA # Always use git-pbuilder git-pbuilder = True # ... and always make sure that our builder is pbuilder. git-builder = pbuilder [dch] full = True release = True spawn-editor = always [clone] verbose = True Any advices on what's going on? Thanks, -- Sergio GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 Please send encrypted e-mail if possible http://sergiodj.net/
signature.asc
Description: PGP signature
