Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.bugs.rc > #407166 > unrolled thread

Bug#1123581: devscripts: Fails autopkgtests with dpkg >= 1.23.0

Started byGuillem Jover <guillem@debian.org>
First post2025-12-18 14:00 +0100
Last post2025-12-19 17:30 +0100
Articles 4 — 3 participants

Back to article view | Back to linux.debian.bugs.rc


Contents

  Bug#1123581: devscripts: Fails autopkgtests with dpkg >= 1.23.0 Guillem Jover <guillem@debian.org> - 2025-12-18 14:00 +0100
    Bug#1123581: devscripts: Fails autopkgtests with dpkg >= 1.23.0 Ian Jackson <ijackson@chiark.greenend.org.uk> - 2025-12-19 17:30 +0100
      Bug#1123581: devscripts: Fails autopkgtests with dpkg >= 1.23.0 Ian Jackson <ijackson@chiark.greenend.org.uk> - 2025-12-23 20:50 +0100
    Processed: Re: Bug#1123581: devscripts: Fails autopkgtests with  dpkg >= 1.23.0 "Debian Bug Tracking System" <owner@bugs.debian.org> - 2025-12-19 17:30 +0100

#407166 — Bug#1123581: devscripts: Fails autopkgtests with dpkg >= 1.23.0

FromGuillem Jover <guillem@debian.org>
Date2025-12-18 14:00 +0100
SubjectBug#1123581: devscripts: Fails autopkgtests with dpkg >= 1.23.0
Message-ID<M3lLP-3PB5-5@gated-at.bofh.it>
Source: devscripts
Source-Version: 2.25.31
Severity: serious

Hi!

With the new dpkg >= 1.23.0 release series, which contains several
deprecations that emit warnings and is more strict when parsing data,
the autopkgtests for this package are failing, making it also affect
dpkg's own migration.

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, and changes to solve that make as
little sense to me as the introduction of the confusion, and I'd
rather not endorse this by providing a patch that I disagree with.
Sorry! :/

Thanks,
Guillem

[toc] | [next] | [standalone]


#407243

FromIan Jackson <ijackson@chiark.greenend.org.uk>
Date2025-12-19 17:30 +0100
Message-ID<M3LwB-47iX-3@gated-at.bofh.it>
In reply to#407166
Control: block -1 by 1123630

I went to look at this failure.  There is one failing autopkgtest,
`shunit2` [1]:

It says things like this:

   81s  expected:<mk-origtargz warn: No files matched excluded pattern as the last matching glob: exclude-dir1> but was:<using Dpkg::Version->is_native() has been made incoherent and confusing on some dpkg vendors; it is deprecated as not having portable semantics anymore at /tmp/autopkgtest-lxc.qhukk53x/downtmp/build.r05/src/lib/Devscripts/MkOrigtargz/Config.pm line 132.

There are quite a lot of these.  They seem to be error-case tests,
that check for particular error messages.  The tests are disrupted
because in each case an additional deprecation warning is printed
about Dpkg::Version->is_native().

In #1123630 I have asked the dpkg maintainer to reconsider this new
warning.  If we /were/ to make a code change to devscripts, it's not
clear what devscripts ought to do instead.  The only option I thought
of so far is to do an ad-hoc, open-coded, m/-/ on the version string.
I suggest we wait for guidance from the dpkg maintainer.

It's hard to see the wood for the trees, but I think this is the only
kind of failure.

Ian.

[1]
 https://ci.debian.net/packages/d/devscripts/testing/amd64/67253139/#L1798
 et seq

-- 
Ian Jackson <ijackson@chiark.greenend.org.uk>   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.

[toc] | [prev] | [next] | [standalone]


#407511

FromIan Jackson <ijackson@chiark.greenend.org.uk>
Date2025-12-23 20:50 +0100
Message-ID<M5gyl-58M0-5@gated-at.bofh.it>
In reply to#407243
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 <ijackson@chiark.greenend.org.uk>   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.

[toc] | [prev] | [next] | [standalone]


#407244 — Processed: Re: Bug#1123581: devscripts: Fails autopkgtests with dpkg >= 1.23.0

From"Debian Bug Tracking System" <owner@bugs.debian.org>
Date2025-12-19 17:30 +0100
SubjectProcessed: Re: Bug#1123581: devscripts: Fails autopkgtests with dpkg >= 1.23.0
Message-ID<M3LwB-47iX-7@gated-at.bofh.it>
In reply to#407166
Processing control commands:

> block -1 by 1123630
Bug #1123581 [src:devscripts] devscripts: Fails autopkgtests with dpkg >= 1.23.0
1123581 was not blocked by any bugs.
1123581 was not blocking any bugs.
Added blocking bug(s) of 1123581: 1123630

-- 
1123581: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1123581
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.bugs.rc


csiph-web