Your message dated Sat, 18 Jan 2014 12:49:52 +0100 with message-id <[email protected]> and subject line Re: Bug#735840: Please allow binary file debian/upstream-signing-key.pgp by default has caused the Debian Bug report #735840, regarding Please allow binary file debian/upstream-signing-key.pgp by default to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 735840: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735840 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: dpkg-dev Version: 1.17.6 Severity: wishlist File: /usr/bin/dpkg-source For some time the debian/watch configuration file provides a way to verify the pgp signature of upstream sources. It requires a keyring file put in debian/ subdirectory. It result wit a following error: dpkg-source: error: unwanted binary file: debian/upstream-signing-key.pgp anytime the dpkg-source is run. Please allow the debian/upstream-signing-key.pgp file by default, without need of adding it into debian/source/include-binaries. Regards Artur -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11-2-amd64 (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages dpkg-dev depends on: ii base-files 7.2 ii binutils 2.24-2 ii bzip2 1.0.6-5 ii libdpkg-perl 1.17.6 ii make 3.81-8.3 ii patch 2.7.1-4 ii xz-utils 5.1.1alpha+20120614-2 Versions of packages dpkg-dev recommends: ii build-essential 11.6 ii clang-3.3 [c-compiler] 1:3.3-16 ii fakeroot 1.20-3 ii gcc [c-compiler] 4:4.8.2-1 ii gcc-4.4 [c-compiler] 4.4.7-6 ii gcc-4.6 [c-compiler] 4.6.4-5 ii gcc-4.7 [c-compiler] 4.7.3-9 ii gcc-4.8 [c-compiler] 4.8.2-12 ii gnupg 1.4.16-1 ii gnupg2 2.0.22-3 ii gpgv 1.4.16-1 ii libalgorithm-merge-perl 0.08-2 Versions of packages dpkg-dev suggests: ii debian-keyring 2013.12.13 -- no debconf information -- Wyjaśnienie odwołujące się do przetrwania, niczego nie wyjaśnia, dopóki nie wyjaśni się, dlaczego przetrwanie przetrwało /Pierre Bourdieu, Jean Claude Passeron "Reprodukcja"/
--- End Message ---
--- Begin Message ---Hi! On Sat, 2014-01-18 at 12:24:01 +0100, Artur R. Czechowski wrote: > On Fri, Jan 17, 2014 at 08:47:17PM -0500, James McCoy wrote: > > For what it's worth, I intend to address #720957 (allow armored > > keyrings) soon to allow using this functionality with 1.0 source > > packages, but this would also address the warning. (Nice, thanks!) > That's a much better solution! My first try was also with armored keyring. Right, I was going to propose exactly that. > So, note to the maintainers of dpkg: from my point of view #735840 can be > closed without remorse. Great, then I think I'd prefer that too, instead of hardcoding such path in there, closing with this mail. (As a side note, I'd rather have liked to use something like debian/upstream/whatever.ext, and was considering filing a bug report, which could be followed by allowing to have debian/upstream/watch, but it's probably too late for the latter. :/ ) Thanks, Guillem
--- End Message ---
