Package: dput Version: 0.9.6.3+nmu1 Severity: wishlist I've just managed to upload a package with UNRELEASED in the changelog. Apparently this is a common failure mode for people using sbuild (#677673, #647028, and a bunch of hits on google) since it puts the distribution into the .changes file's Distribution field.
However sbuild does put the changelog entry into the .changes, like so: .. Distribution: sid .. Changes: qcontrol (0.4.2+svn-r40-2) UNRELEASED; urgency=low .. It seems that the attempts to get this fixed in the archive and/or lintian (the two bugs referenced above) are stalled and/or difficult to implement. I wonder if it would be possible for dput to include a safety catch for this case? Specifically a mismatch between the Distribution field and the release given in the Changes field. Ian. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages dput depends on: ii gnupg 1.4.12-6 ii python 2.7.3~rc2-1 dput recommends no packages. Versions of packages dput suggests: ii lintian 2.5.10.2 pn mini-dinstall <none> ii openssh-client 1:6.0p1-3 ii rsync 3.0.9-3 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
