Hi! On Thu, 2025-02-13 at 12:34:52 +0100, Chris Hofstaedtler wrote: > On Thu, Feb 13, 2025 at 10:50:39AM +0100, Guillem Jover wrote: > > On Wed, 2025-02-12 at 04:16:29 +0100, Thorsten Glaser wrote: > > > dpkg 1.22.13 implemented a backwards-incompatible change, > > > violating Policy (which states the default value is most > > > certainly *not* “no”) and breaking builds of packages. > > [..] > > > Is this with an out of archive package? If so dpkg-deb should have > > warned about the problem, otherwise this was then probably missed in > > one of the mass rebuilds, but I'd be happy to try make this change > > more smooth. I was pondering about perhaps adding a NEWS entry in the > > dpkg-dev package, although that still does not help with CI systems and > > similar. (That's why I'm not closing this right away.) > > >From what I can tell from other mails, I believe the package in > question is openjdk-8 (unstable only); see bug #1095746.
Ah, thanks for the context. In that case, going by that bug report, it looks like openjdk-8 was most probably already buggy, and this seems like another instance of what was reported in: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1093766#10 Thanks, Guillem
