Your message dated Mon, 08 Apr 2024 18:04:42 +0000
with message-id <e1rttmi-00dcuc...@fasolo.debian.org>
and subject line Bug#1068589: fixed in gem2deb 2.2.3
has caused the Debian Bug report #1068589,
regarding gem2deb: autopkgtest needs update for new version of ruby3.1: "libc6 
(>= 2.2.5)", "libruby3.1t64 (>= 3.1.0~preview1)", "ruby | ruby-interpreter\n"] 
expected to include 'ruby (>= something)'
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.)


-- 
1068589: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068589
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gem2deb
Version: 2.2.2
Severity: serious
X-Debbugs-CC: ruby...@packages.debian.org
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:ruby3.1

Dear maintainer(s),

With a recent upload of ruby3.1 (in the time_t transition) the autopkgtest of gem2deb fails in testing when that autopkgtest is run with the binary packages of ruby3.1 from unstable. It passes when run with only packages from testing. In tabular form:

                       pass            fail
ruby3.1                from testing    3.1.2-8.3
gem2deb                from testing    2.2.2
all others             from testing    from testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of ruby3.1 to testing [1]. Of course, ruby3.1 shouldn't just break your autopkgtest (or even worse, your package), but it seems to me that the change in ruby3.1 was intended and your package needs to update to the new situation.

If this is a real problem in your package (and not only in your autopkgtest), the right binary package(s) from ruby3.1 should really add a versioned Breaks on the unfixed version of (one of your) package(s). Note: the Breaks is nice even if the issue is only in the autopkgtest as it helps the migration software to figure out the right versions to combine in the tests.

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=ruby3.1

https://ci.debian.net/data/autopkgtest/testing/amd64/g/gem2deb/44893387/log.gz

42s W: Inconsistent version numbers: lib/gem2deb/version.rb says 2.1, debian/changelog says 2.2.2
 42s => Unit tests

...

108s test: multibinary source package should inject dependency on ruby (>= something). : F 108s =============================================================================== 108s Failure: test: multibinary source package should inject dependency on ruby (>= something). (Gem2DebTest): 108s ["libc6 (>= 2.2.5)", "libruby3.1t64 (>= 3.1.0~preview1)", "ruby | ruby-interpreter\n"] expected to include 'ruby (>= something)'.
108s   <false> is not true.
108s /tmp/autopkgtest-lxc.f1vq6prr/downtmp/build.NZh/src/test/integration/gem2deb_test.rb:83:in `block (3 levels) in <class:Gem2DebTest>' 108s /tmp/autopkgtest-lxc.f1vq6prr/downtmp/build.NZh/src/test/integration/gem2deb_test.rb:87:in `instance_exec' 108s /tmp/autopkgtest-lxc.f1vq6prr/downtmp/build.NZh/src/test/integration/gem2deb_test.rb:87:in `block in create_test_from_should_hash' 108s ===============================================================================

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message ---
Source: gem2deb
Source-Version: 2.2.3
Done: Antonio Terceiro <terce...@debian.org>

We believe that the bug you reported is fixed in the latest version of
gem2deb, 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 1068...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Antonio Terceiro <terce...@debian.org> (supplier of updated gem2deb 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, 08 Apr 2024 13:45:25 -0300
Source: gem2deb
Architecture: source
Version: 2.2.3
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 
<pkg-ruby-extras-maintain...@lists.alioth.debian.org>
Changed-By: Antonio Terceiro <terce...@debian.org>
Closes: 1068589
Changes:
 gem2deb (2.2.3) unstable; urgency=medium
 .
   * dh_ruby_fixdepends: extract package name into a variable
   * dh_ruby_fixdepends: workaround presence of libruby3.1t64
     (Closes: #1068589)
Checksums-Sha1:
 af9504a0ffeca262f64ac41aa48a50db224c3291 2317 gem2deb_2.2.3.dsc
 2724ee07a17c8189ca52e8de729c7e64fa5e713e 79980 gem2deb_2.2.3.tar.xz
 efd88578adb9536184192343f37052bbc21f9f72 13883 gem2deb_2.2.3_source.buildinfo
Checksums-Sha256:
 c4c9167a4390b1bddb26372708c4ec54e1e8f0e409e9eb72afcdc0a2b9e138e2 2317 
gem2deb_2.2.3.dsc
 2fbd92abf4b34501b4b2d87f48058546e0cf84a7003d3850ada0942ad5700348 79980 
gem2deb_2.2.3.tar.xz
 24086043db247ffb5f6a3389db87e9817103a35b96b987e5362673e3270b2d8a 13883 
gem2deb_2.2.3_source.buildinfo
Files:
 7662e21e38b6bb524ce23917c3c15a1a 2317 ruby optional gem2deb_2.2.3.dsc
 57cd14e1dcdb16ab6cf62fd764049f45 79980 ruby optional gem2deb_2.2.3.tar.xz
 e82a66dfdac8c58e3e29431a684a7293 13883 ruby optional 
gem2deb_2.2.3_source.buildinfo

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

iQIzBAEBCAAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAmYULycACgkQ/A2xu81G
C94DtRAA9OY5KQHx+Co4M45XpxlH4eGqJfnpUiXjWS4E6CyNIAebtlrBKNWpkXj9
LOFGa2hNg4EJOFwKPDJf83SfZyv8PRyFvLLe9wN0diBn0Q50Lbo7JmnDNPbJRHR5
acZyBGAN8IrqmVz4WYiBBy3+eASMidJgP0tu9ObE+CHBGgqQDdJ9oIZdOKe2jpP5
GR9qXupTNKK7LYJ2stTJhmub23qAddi5E7BMMMEIe705TKyqjwhyYOyOOIx9bXvg
aF85Uc2GQQVVCxgqVvpfxEgGsgwqThnEY4zSq9IB6yFqI9YEZBb53jOVAU8yLOcQ
p3/8GOCw28UjWQ/BcNV7IlOnBgEOz++oCcIa6YiLg2KSsMEdHCU81XCgyRp7oH4x
+1Nk2AXBgN3OCVG2GGP0P3gGPjUL5Mbld2HDlYrkZkE6UWYbyYw235BXihURjLlj
GJkr8uWgkCaKtHR2XT9y+bSIrrv2HJPmsbrv721S9G1hgrloZaAj33aWWO3jIclF
ZAxXb0DD0Tz116UtR2nEBD2aXBhrtXQGDHYY3AAIn5wPGhBYICNUJD7+HOgIQsLZ
tcGe+hhff+pdMNAyVg3ivUDgEOzzlJ5vKz5cJ7/J0kGrJdLwZDZ52OukItKOA/Tk
FGHGW2yAqLqeKzmm3eKVZsvEH3TdTMsSB7OAVd14h7iLS6UNBgc=
=UaJG
-----END PGP SIGNATURE-----

Attachment: pgpCiav9ZnyGn.pgp
Description: PGP signature


--- End Message ---

Reply via email to