Your message dated Mon, 13 Jan 2025 22:39:56 +0000
with message-id <e1txt6c-00hh8f...@fasolo.debian.org>
and subject line Bug#1091505: fixed in ruby3.3 3.3.6-1.1
has caused the Debian Bug report #1091505,
regarding ruby3.3: Tries to access Internet during build
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.)
--
1091505: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1091505
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ruby3.3
Version: 3.3.5-2
Tags: ftbfs trixie sid
User: debian...@lists.debian.org
Usertags: ftbfs-during-trixie-support-period
Dear maintainer:
During a rebuild of all packages in unstable in the year 2028, your package
failed to build:
--------------------------------------------------------------------------------
[...]
[26565/26632] Bug::Time::Test_New#test_nano_new = 0.00 s
[26566/26632] Bug::Time::Test_New#test_timespec_new = 0.00 s
[26567/26632] Bug::Time::Test_New#test_timespec_now = 0.00 s
1) Failure:
TestGemBundledCA#test_accessing_rubygems
[/<<PKGBUILDDIR>>/test/rubygems/test_bundled_ca.rb:47]:
rubygems.org is not verifiable using the included certificates. Error was:
SSL_connect returned=1 errno=0 peeraddr=[2a04:4e42:400::483]:443 state=error:
certificate verify failed (certificate has expired)
2) Failure:
TestGemBundledCA#test_accessing_www_rubygems
[/<<PKGBUILDDIR>>/test/rubygems/test_bundled_ca.rb:51]:
www.rubygems.org is not verifiable using the included certificates. Error was:
SSL_connect returned=1 errno=0 peeraddr=[2a04:4e42:200::483]:443 state=error:
certificate verify failed (certificate has expired)
3) Failure:
TestGemBundledCA#test_accessing_new_index
[/<<PKGBUILDDIR>>/test/rubygems/test_bundled_ca.rb:59]:
index.rubygems.org is not verifiable using the included certificates. Error
was: SSL_connect returned=1 errno=0 peeraddr=[2a04:4e42:200::483]:443
state=error: certificate verify failed (certificate has expired)
4) Failure:
TestGemBundledCA#test_accessing_staging
[/<<PKGBUILDDIR>>/test/rubygems/test_bundled_ca.rb:55]:
staging.rubygems.org is not verifiable using the included certificates. Error
was: SSL_connect returned=1 errno=0 peeraddr=[2a04:4e42::483]:443 state=error:
certificate verify failed (certificate has expired)
Finished tests in 617.171218s, 43.0464 tests/s, 10265.7493 assertions/s.
26567 tests, 6335725 assertions, 4 failures, 0 errors, 179 skips
ruby -v: ruby 3.3.5 (2024-09-03 revision ef084cc8f4) [x86_64-linux-gnu]
make[2]: *** [uncommon.mk:945: yes-test-all] Error 4
make[2]: Leaving directory '/<<PKGBUILDDIR>>'
make[1]: *** [debian/rules:137: override_dh_auto_test-arch] Error 2
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:102: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--------------------------------------------------------------------------------
The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here:
https://people.debian.org/~sanvila/build-logs/ftbfs-future/
About the archive rebuild: This is an effort to keep trixie free from FTBFS bugs
during its lifetime as a supported distribution, as explained here:
https://lists.debian.org/debian-devel/2024/05/msg00414.html
(While they are not yet, please note that the bugs will be RC for trixie)
The build was made using sbuild and a reduced chroot with only
build-essential packages.
If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.
If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.
Thanks.
--- End Message ---
--- Begin Message ---
Source: ruby3.3
Source-Version: 3.3.6-1.1
Done: Sebastian Andrzej Siewior <sebast...@breakpoint.cc>
We believe that the bug you reported is fixed in the latest version of
ruby3.3, 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 1091...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sebastian Andrzej Siewior <sebast...@breakpoint.cc> (supplier of updated
ruby3.3 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: SHA512
Format: 1.8
Date: Fri, 10 Jan 2025 21:56:50 +0100
Source: ruby3.3
Architecture: source
Version: 3.3.6-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team
<pkg-ruby-extras-maintain...@lists.alioth.debian.org>
Changed-By: Sebastian Andrzej Siewior <sebast...@breakpoint.cc>
Closes: 1087954 1091505
Changes:
ruby3.3 (3.3.6-1.1) unstable; urgency=medium
.
* Non-maintainer upload.
* Fix test failures with OpenSSL 3.4 (Closes: #1087954).
* Skip test_bundled_ca, it access internet (Closes: #1091505).
Checksums-Sha1:
85376536b133e979eb7ad20d648e228c1518b1be 2571 ruby3.3_3.3.6-1.1.dsc
7f0fbe67705255ddbf756eff2f7cb52c18621f66 63660 ruby3.3_3.3.6-1.1.debian.tar.xz
Checksums-Sha256:
094cfab76ac386cbabb3dbb30fab6cc41bfff06d4be3df0d47b03a2001c30a61 2571
ruby3.3_3.3.6-1.1.dsc
c502b6cae2f8474ffaaafe388f54e897d2f54f77e7f25a45c3eea3e8e5ae65cf 63660
ruby3.3_3.3.6-1.1.debian.tar.xz
Files:
77d95c47ee5bdfe3c270c10c4da542be 2571 ruby optional ruby3.3_3.3.6-1.1.dsc
81f9cd73d988419dd7b98e7ce279621c 63660 ruby optional
ruby3.3_3.3.6-1.1.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEZCVGlf/wqkRmzBnme5boFiqM9dEFAmeBidsACgkQe5boFiqM
9dGEGQ//Ql0tkMzUS80Cm97xi8/1KbRq2QWoHCjjBp4ZkBNTqX2v1IDNfq/eX++B
RIZJ/QaI8T+4r+gihNQvn/GAWVohJ0CqIJ5wKCNalsKIcvwTThU+3d1uOUr5yS6I
THemAduR9P/HBhO1yQpAKeB7sRe+4T7RF96V/aBcvGA8VLuCekCowMx3g/qD4FD1
7UVSXc+4eJN6L6ArIXmGhhRKfqnIvGxoZyoPoDPMR0m1G/zGngAA3Kd/ijqu1nKm
28S+ma2uJCR+mWuQLgFLwAGhL9u59ojhhPbpmCtXTECrAkOm1Qx3Nw94GPHHXof2
6NekXDZI6+ivIatZ26MnMhYrY+1JVkQ8Wga2FQ8Yr/LNXN2mCmLhs6K99MeLr9yB
vw4qRSicO17xgfbAk0jEgbRTvQZZJ5gQkrFGGAYCd0O0LF36ouTjsAbOMuQCfcYM
5TN5hbZznIbsWFtxITdJ2QWni7pu6xGIuGAwNJ5apWCB3BI9YhzRLMVXdweQqZOL
cdRTpWmeOtrboqftuq9u0/1bkkpG0PPWLAGy7420L5OzqWeUt5Yod7phEdEv76Ki
WK+PZByqOFx8w+gmH5h+NETf3g7NC8XO+bI8Cku07PU3UgYtHcNE9WruglroZVPi
13ksHSCXfBel+uqYx131KKwgfsnuixUz/y1yVRE7e9fioWj0AIY=
=Gc78
-----END PGP SIGNATURE-----
pgp3enpdAFey0.pgp
Description: PGP signature
--- End Message ---
