Bug#895004: dpkg: Dpkg::Version manpage documents workflows that reject version "0"

2018-04-05 Thread Niels Thykier
Package: dpkg Version: 1.19.0.5 Severity: minor Hi, There are some examples in Dpkg::Version that (if followed) would imply that the problem will reject the version number "0" despite it being valid. Example: """ boolean evaluation When the Dpkg::Version object is used in a boolean e

Bug#894441: dpkg-buildpackage: SOURCE_DATE_EPOCH must ignore bin-nmu changelog entries. Breaks M-A:same

2018-04-05 Thread Holger Levsen
On Thu, Apr 05, 2018 at 05:43:58PM +0200, Jean-Michel Vourgère wrote: > So, during compilation: > SOURCE_DATE_EPOCH must ignore bin-nmu changelog entries > because it breaks Multi-Arch:same on bin-nmu. > > During dpkg-deb (: > SOURCE_DATE_EPOCH must *not* ignore bin-nmu changelog entries > because

Bug#894441: dpkg-buildpackage: SOURCE_DATE_EPOCH must ignore bin-nmu changelog entries. Breaks M-A:same

2018-04-05 Thread Jean-Michel Vourgère
On Friday, 30 March 2018 15:02:31 CEST Chris Lamb wrote: > [ https://lists.debian.org/debian-security/2017/05/msg00011.html ] On Friday, 30 March 2018 20:15:33 CEST Sven Joachim wrote: > [ https://bugs.debian.org/843773 ] Thanks a lot guys for pointing out that issue! Basically, when doing bin-n

Bug#894965: dpkg-architecture should stop warning about unset CC

2018-04-05 Thread Helmut Grohne
Package: dpkg-dev On Thu, Apr 05, 2018 at 04:28:48PM +0200, to...@tuxteam.de wrote: > - Need to set CC > > Yes, the warning was clear enough, but I was a bit surprised > I had to set CC like so: The warning you are talking about likely is this one: | dpkg-architecture: warning: specified GNU sy