Your message dated Mon, 28 Mar 2022 19:49:04 +0000
with message-id <e1nyvmo-000ijc...@fasolo.debian.org>
and subject line Bug#1008192: fixed in autopkgtest 5.21
has caused the Debian Bug report #1008192,
regarding libmojolicious-perl: Recommends of libmojolicious-perl contains build 
profile syntax
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1008192: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008192
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libmojolicious-perl
Version: 9.22+dfsg-1
Severity: normal
Control: clone -1 -2 -3
Control: reassign -2 autopkgtest
Control: severity -2 important
Control: reassign -3 lintian

Dear all,

Recently autopkgtest changed the way that the needs-recommends
restriction is implemented. That has caused some fall out. One case of
fall out is made apparent by src:libmojolicious-perl. The d/control
file [1] has this:
"""
Recommends: libcpan-meta-yaml-perl,
            libcpanel-json-xs-perl,
            libev-perl (>= 4.32),
            libfuture-asyncawait-perl (>= 0.52) <!nocheck>,
"""

Note that the last line has a *build* profile. Apparently that's
stripped off when the "real" Recommends field is generated, but it
doesn't belong there and it potentially harms tools that process
d/control.

I suggest:
1) libmojolicious-perl fixes its d/control (I'll provide a patch shortly)
2) autopkgtest should become more robust
3) lintian adds a check on this

Thanks for reading

Paul

[1] 
https://tracker.debian.org/media/packages/libm/libmojolicious-perl/control-9.22dfsg-1

--- End Message ---
--- Begin Message ---
Source: autopkgtest
Source-Version: 5.21
Done: Paul Gevers <elb...@debian.org>

We believe that the bug you reported is fixed in the latest version of
autopkgtest, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1008...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Paul Gevers <elb...@debian.org> (supplier of updated autopkgtest package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Mon, 28 Mar 2022 21:20:12 +0200
Source: autopkgtest
Architecture: source
Version: 5.21
Distribution: unstable
Urgency: medium
Maintainer: Debian CI team <team...@tracker.debian.org>
Changed-By: Paul Gevers <elb...@debian.org>
Closes: 979450 1008192
Changes:
 autopkgtest (5.21) unstable; urgency=medium
 .
   [ Paul Gevers ]
   * testdesc.py: reduce_restrictions instead of only reduce_arch
     (Closes: #1008192)
   * spec: improve wording of skip-not-installable
   * testdesc: work around variables in d/control
   * spec: be more specific what @recommends@ means
 .
   [ Antonio Terceiro ]
   * autopkgtest-build-lxc: update container configuration (Closes: #979450)
Checksums-Sha1:
 1f29a6a558d2f5561c1250870c598641022c4125 1695 autopkgtest_5.21.dsc
 95d94c4dfc414179a0ada047784ed591a0548b32 197620 autopkgtest_5.21.tar.xz
Checksums-Sha256:
 c3093ba8a622f19eb637893a989201b3d37705797846d6a33a31dd92ef2358ae 1695 
autopkgtest_5.21.dsc
 8bbed702ae2045b09b71ded1d75b71c9f473a59b1e54adc6f2c00e8763581fc6 197620 
autopkgtest_5.21.tar.xz
Files:
 baee1222060d0bdd488c48f868df4e67 1695 devel optional autopkgtest_5.21.dsc
 727184052450a2d1949410fe21798539 197620 devel optional autopkgtest_5.21.tar.xz

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmJCDFkACgkQnFyZ6wW9
dQqRzwgAhBz1pRY5a4lx//jtgvj+6+F/8g5yumMopKUdCNBepKWqTz4q0rUcbg3h
T4ph336fx2cqmx2/j4YnataZxdOySfPKF00b8geZ0GdlM04CMYudLad0EhHO7cAL
PbQWQaSoGztkthhrwNfl33cx/HZIZfEWAM02B40tuDcOI7eVDZn+dzbIYhfrAsuM
5ExWRq3DtpDFt/uP5czAX1D4HmseYP8yPo9YctOK76afWf/uHJClbutMprhJL2c4
N6uxKLS0k2UwLknxAngGff1NbO1KLvPmrMcWHzjuhFp0uXlKa9ZkVfSv8z0MLQPb
FQ0Gmh6ySI9c6/2b9qAsfcFFmob+Og==
=+RiP
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to