Holger writes: > On Thu, Dec 18, 2025 at 01:53:10PM +0100, Guillem Jover wrote: > > I'd usually have provided a patch to fix this, but in this > > particular > > case at least one of the failures is due to the push to confuse the > > native source vs version concept, [...] > > was that a recent commit to devscripts? (and can you identify it, > cause if so, reverting it might be the easiest short term fix/migation > here...)
No, it was not any kind of change to devscripts. The (relevant) parts of history are as follows: In 1996 I wrote dpkg-source. The 1.0 native source format (ie, a dsc with tarball and no diff) could be used with a version number with a revision. In 2008, source format 3.0 was introduced. "3.0 (native)" could be used with a version number with a revision. Sound time around 2012/2013, some folks decided that native source formats with non-native version numbers (ie, with revisions) ought to be abolished. They persauded the dpkg maintainer to forbid it. A small change was made to the source code of src:dpkg to forbid it (in 3.0 only): https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700177#5 This decision was controversial. The main bug about it was filed in 2014: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737634 Apparently this was causing trouble for Ubuntu. I believe Ubuntu reverted the prohibition in a downstream change to dpkg-source. I dodn't agree with this restriction, and it was getting in the way of git transition work, so eventually I filed a bug asking the TC. The TC confirmed that It is not a bug of any severity for a package with a non-native version number to use a native source package format. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007717#384 Unfortuantely this didn't result in any change to the behaviour of dpkg-source. In May this year I filed a bug asking the TC to please explicitly overrule the dpkg maintainer: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106402 A week or two ago in mid-December, the dpkg maintainer uploaded a change to dpkg-source. This change does not simply remove the disputed check. It also reorganises related APIs in libdpkg-perl. One of those reorganisations is to depcreate the `is_native` method. That method (which I don't think there is anything wrong with, and whose name and behaviour is completely compliant with policy) now produces a new (polemical) deprecation warning. I suggest that for devscripts, we should suppress the deprecation warning surrounding this method. as helpfully suggested by the dpkg maintainer, here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1123630#37 An example of how to do this can be found in git-deborig (which is now in src:dgit, but used to be in devscripts): https://salsa.debian.org/dgit-team/dgit/-/blob/12ffde31f88a7b21f1f50d363e8938bbb3991878/git-deborig#L73 (Although you might want to write $version->is_native instead of using indirect method syntax.) I hope this helps. Thanks, Ian. -- Ian Jackson <[email protected]> These opinions are my own. Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.
