HI Guillaume - I dont' think this is for me....will call you in am
DENISE OSHESKY | Systems Analyst III IT-Technical Support P.O. Box 3590, Honolulu, HI. 96811 Phone: (808) 544-5607 | Cell: (808) 954-5410 | Fax: (808) 532-4846 denise.oshe...@centralpacificbank.com | http://www.centralpacificbank.com ________________________________ From: Guillem Jover <guil...@debian.org> Sent: Wednesday, October 9, 2019 9:26 PM To: Ansgar <ans...@debian.org>; 942...@bugs.debian.org <942...@bugs.debian.org> Subject: Bug#942087: dpkg-source and dpkg-genchanges disagree how .dsc should be named if version ends with +b1 ***** This message originated outside of Central Pacific Bank's email system. Please verify the sender before opening attachments, clicking on links, or providing information. For suspicious email please contact Information Security ***** . Control: reassign -1 dpkg-dev/1.18.25 On Thu, 2019-10-10 at 08:15:07 +0200, Ansgar wrote: > Package: dpkg > Version: 1.18.25 > Severity: normal > For the Secure Boot support in Debian we automatically generate source > packages that include the signatures (linux-signed-*) from files > shipped in linux-image-amd64-signed-template below > /usr/share/code-signing/linux-image-amd64-signed-template/source-template > (plus detached signatures). > > With the first binNMU the changelog used 5.2.17+1+b1 as the version > and this caused disagreement between different parts of dpkg. > dpkg-source generates linux-signed-amd64_5.2.17+1+b1.dsc, but > dpkg-genchanges strips the trailing +b1 from the version: > > +--- > | [dpkg-source -b .] > | dpkg-source: warning: unknown information field 'Rules-Requires-Root' in > input data in general section of control info file > | dpkg-source: info: using source format '3.0 (native)' > | dpkg-source: info: building linux-signed-amd64 in > linux-signed-amd64_5.2.17+1+b1.tar.xz > | dpkg-source: info: building linux-signed-amd64 in > linux-signed-amd64_5.2.17+1+b1.dsc > | dpkg-genchanges: warning: unknown information field 'Rules-Requires-Root' > in input data in general section of control info file > | dpkg-genchanges: error: cannot read ../linux-signed-amd64_5.2.17+1.dsc: No > such file or directory > | Something went wrong, you can inspect the build to figure out what. The > temporary directory is /tmp/codesignzg_o_do4 > | Command '['dpkg-genchanges', '-S', '-DDistribution=sid', '-UCloses', > '-O../linux-signed-amd64_5.2.17+1+b1_source.changes']' returned non-zero exit > status 2 > +--- > > The first changelog entry is > > +--- > | linux-signed-amd64 (5.2.17+1+b1) sid; urgency=low > | > | * Sign kernel from linux 5.2.17-1+b1 > | > | * Binary-only non-maintainer upload for amd64; no source changes. > | * build against perl 5.30.0 > | > | -- amd64 / i386 Build Daemon (x86-ubc-01) > <buildd_amd64-x86-ubc...@buildd.debian.org> Sun, 06 Oct 2019 15:07:42 +0000 > +--- > > I'll suggest to work around this by mangling the version a bit more > and use .b1 instead of +b1, but the disagreement seems to be a bug in > dpkg. It looks to me that the problem might actually be the missing binary-only=yes key/value in the changelog header though, which the original should have? Could you check whether that would completely fix this? Thanks, Guillem
