Your message dated Sun, 20 Feb 2022 22:50:47 +0000 with message-id <e1nlv2v-000hlx...@fasolo.debian.org> and subject line Bug#1005448: fixed in ruby-certificate-authority 1.0.0-1 has caused the Debian Bug report #1005448, regarding ruby-certificate-authority: FTBFS: ERROR: Test "ruby3.0" failed: NoMethodError: 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.) -- 1005448: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005448 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: ruby-certificate-authority Version: 0.2.0~434c15cd-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220212 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > NoMethodError: > undefined method `[]=' for #<OpenSSL::Config sections=["default"]> > Did you mean? [] > # ./lib/certificate_authority/certificate.rb:229:in `block in > merge_options' > # ./lib/certificate_authority/certificate.rb:228:in `each' > # ./lib/certificate_authority/certificate.rb:228:in `merge_options' > # ./lib/certificate_authority/certificate.rb:95:in `block in sign!' > # ./lib/certificate_authority/certificate.rb:93:in `each' > # ./lib/certificate_authority/certificate.rb:93:in `sign!' > # ./spec/units/certificate_spec.rb:366:in `block (3 levels) in <top > (required)>' > > Finished in 0.56569 seconds (files took 0.20536 seconds to load) > 196 examples, 17 failures, 3 pending > > Failed examples: > > rspec ./spec/units/certificate_spec.rb:295 # > CertificateAuthority::Certificate X.509 V3 Extensions on Signed Certificates > should support BasicConstraints > rspec ./spec/units/certificate_spec.rb:300 # > CertificateAuthority::Certificate X.509 V3 Extensions on Signed Certificates > should support subjectKeyIdentifier > rspec ./spec/units/certificate_spec.rb:305 # > CertificateAuthority::Certificate X.509 V3 Extensions on Signed Certificates > should support authorityKeyIdentifier > rspec ./spec/units/certificate_spec.rb:310 # > CertificateAuthority::Certificate X.509 V3 Extensions on Signed Certificates > should order subjectKeyIdentifier before authorityKeyIdentifier > rspec ./spec/units/certificate_spec.rb:317 # > CertificateAuthority::Certificate X.509 V3 Extensions on Signed Certificates > should support keyUsage > rspec ./spec/units/certificate_spec.rb:322 # > CertificateAuthority::Certificate X.509 V3 Extensions on Signed Certificates > should support extendedKeyUsage > rspec ./spec/units/certificate_spec.rb:182 # > CertificateAuthority::Certificate X.509 V3 Extensions on Signed Certificates > SubjectAltName should have a subjectAltName if specified > rspec ./spec/units/certificate_spec.rb:188 # > CertificateAuthority::Certificate X.509 V3 Extensions on Signed Certificates > SubjectAltName should NOT have a subjectAltName if one was not specified > rspec ./spec/units/certificate_spec.rb:194 # > CertificateAuthority::Certificate X.509 V3 Extensions on Signed Certificates > SubjectAltName should replace email:copy with email address > rspec ./spec/units/certificate_spec.rb:213 # > CertificateAuthority::Certificate X.509 V3 Extensions on Signed Certificates > AuthorityInfoAccess should have an authority info access if specified > rspec ./spec/units/certificate_spec.rb:228 # > CertificateAuthority::Certificate X.509 V3 Extensions on Signed Certificates > CrlDistributionPoints should have a crlDistributionPoint if specified > rspec ./spec/units/certificate_spec.rb:234 # > CertificateAuthority::Certificate X.509 V3 Extensions on Signed Certificates > CrlDistributionPoints should NOT have a crlDistributionPoint if one was not > specified > rspec ./spec/units/certificate_spec.rb:250 # > CertificateAuthority::Certificate X.509 V3 Extensions on Signed Certificates > CertificatePolicies should have a certificatePolicy if specified > rspec ./spec/units/certificate_spec.rb:287 # > CertificateAuthority::Certificate X.509 V3 Extensions on Signed Certificates > CertificatePolicies should NOT include a certificatePolicy if not specified > rspec ./spec/units/certificate_spec.rb:354 # > CertificateAuthority::Certificate Signing profile should be able to sign with > an optional policy hash > rspec ./spec/units/certificate_spec.rb:358 # > CertificateAuthority::Certificate Signing profile should support a default > signing digest of SHA512 > rspec ./spec/units/certificate_spec.rb:364 # > CertificateAuthority::Certificate Signing profile should support a > configurable digest algorithm > > [33m[Coveralls] Outside the CI environment, not sending data.[0m > Stopped processing SimpleCov as a previous error not related to SimpleCov has > been detected > /usr/bin/ruby3.0 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb --format documentation failed > mv ./.gem2deb.Gemfile.lock Gemfile.lock > ERROR: Test "ruby3.0" failed: The full build log is available from: http://qa-logs.debian.net/2022/02/12/ruby-certificate-authority_0.2.0~434c15cd-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---Source: ruby-certificate-authority Source-Version: 1.0.0-1 Done: Antonio Terceiro <terce...@debian.org> We believe that the bug you reported is fixed in the latest version of ruby-certificate-authority, 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 1005...@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 ruby-certificate-authority 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: Sun, 20 Feb 2022 19:24:24 -0300 Source: ruby-certificate-authority Architecture: source Version: 1.0.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team <pkg-ruby-extras-maintain...@lists.alioth.debian.org> Changed-By: Antonio Terceiro <terce...@debian.org> Closes: 1005448 Changes: ruby-certificate-authority (1.0.0-1) unstable; urgency=medium . * Team upload . [ Utkarsh Gupta ] * Add salsa-ci.yml . [ Debian Janitor ] * Bump debhelper from old 11 to 12. * Set debhelper-compat version in Build-Depends. * Set upstream metadata fields: Bug-Database, Bug-Submit. * Apply multi-arch hints. + ruby-certificate-authority: Add :any qualifier for ruby dependency. . [ Antonio Terceiro ] * debian/watch: point at github repository * New upstream version 1.0.0 - Drop patches applied upstream: + 0004-Let-ruby-find-certificate-authority-in-specs.patch + 003_fix_generated_csr - Replace debian/patches/002_disable_pkcs11_pkey_ref with a exclude_pattern setting in debian/ruby-tests.rake * debian/rules: install using Rubygems layout. Don't avoid installing rake task now that that will not interfere with the global namespace. * debian/upstream/metadata: refresh from template * debian/control: refresh from template - Build-Depends: + require debhelper-compat = 13, gem2deb >= 1 + add ruby-budler, pry to avoid having to patch corresponding require statements from spec/spec_helper.rb - Standards-Version: bump to 4.6.0 (no changes needed) - Add Rules-Require-Root: no - Depends: drop explicit ruby interepreter dependency in favor of ${ruby:Depends}. * Add patches: - 0001-Build-a-string-config-for-OpenSSL-Config-as-opposed-.patch: add fix for Ruby openssl 3.0.0 (Closes: #1005448) - 0002-gemspec-don-t-use-git-to-get-list-of-files.patch: drop git usage from gemspec. - 0003-gemspec-don-t-load-file-from-lib-explicitly.patch: fix loading the gemspec under autopkgtest (i.e. with lib/ moved out of the way). Checksums-Sha1: 0b4f0f15b46dd9422fe2a1f7d0b69e13b496a8e0 2251 ruby-certificate-authority_1.0.0-1.dsc 78d87c96868591319b60c1dff029110b9108f644 57104 ruby-certificate-authority_1.0.0.orig.tar.gz b2b198c3098ab8f1ca7b9c86b6a73b0d90e9140d 5700 ruby-certificate-authority_1.0.0-1.debian.tar.xz 7fae11ba37e809347f9d57671c0b860356b1998b 10533 ruby-certificate-authority_1.0.0-1_amd64.buildinfo Checksums-Sha256: a7595887f24b25785e2f23803666b42bed3a93af0ae1328f2928469b7bd6206b 2251 ruby-certificate-authority_1.0.0-1.dsc 9ce890b0f74c0fe04f38abd1c55d7ac8d997e8c9bf3f99ab1c850d6e128cb662 57104 ruby-certificate-authority_1.0.0.orig.tar.gz b0b8adf868091b6764cb348ec87b54b8059bf3a16813481f35eb68b407520bbf 5700 ruby-certificate-authority_1.0.0-1.debian.tar.xz ab02b7653fe3dc069ac335c5274273ed5155607f88e0f1ef978d47bc98dea40a 10533 ruby-certificate-authority_1.0.0-1_amd64.buildinfo Files: a64fa0a43000f2492a74f90d19b44ce1 2251 ruby optional ruby-certificate-authority_1.0.0-1.dsc 7d764bce53e2f3e3bb99a86035b1263a 57104 ruby optional ruby-certificate-authority_1.0.0.orig.tar.gz c4b10d27964127fb28a61854a8205660 5700 ruby optional ruby-certificate-authority_1.0.0-1.debian.tar.xz 45789a44a05396d38ffea6ae393c03b5 10533 ruby optional ruby-certificate-authority_1.0.0-1_amd64.buildinfo -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAmISwm0ACgkQ/A2xu81G C96H6xAAtwgfvIEQwCBKHYyp7zY+LJI0wxqffMIPtKb7wF29sW/J+88KBgIHra51 ml/D/GQwm6MTQfImNB8ftdDHb+5qQjkCXpBW6dJ6nLmGf4f3TFvF0Gz6ioLMbMNC ESFj0+LAas9BRX8oX8vf4Up/p19UoCnRN/3klIoTZkvYzzRvX+gknTHXom1XImHt LMmiXImBbb9+a2op/pSvyNNX55y4SCU/VmElJ8ehU7EhZMwIPSml94pX8cPli8Fd YJdyyBYIGXrZYThSkzDD6W7QFNwUJHpRfvNFufzQX/BWtwcdtIx7Q1pKmSBJxNuO iwFaGCPtn9YcNE6PotBtFtVwPvWp0OkvTA4gBFe0fIu4UksMPMUMRCMQ8lxbjcly rC261Fx3YcFK7rDR+j12R8ilgznP71aLdA4eJd++a7JuPt5AOgVPOlBTP92PTNoV RhucZ8qMmXUjU0H2ZcYk/RqlBsGwYAstHcCjWQGEBRqUe1mdXu3ZnR8eBEhKdL4T SA6neSBsk0+NKW5T/EN78deY6GwrE3JuXWxfazuAfKqx0Py6LepgfFYT7T2eZC8w 9HheG3ILhi30gVYUTBuw8QDBtiOOH+od71YiOGKjMcoQvwmTH0yRMuBJE1B7VWwv Mi60Lvvv1rVZmt4SDxqBFJ/hkjZgBbrFMKMsdPhQxEMiX2hspxo= =Pr/e -----END PGP SIGNATURE-----
--- End Message ---
