Your message dated Sun, 11 Feb 2018 16:52:37 +0000
with message-id <e1ekurl-0002do...@fasolo.debian.org>
and subject line Bug#888148: fixed in ruby-certificate-authority 
0.2.0~434c15cd-1
has caused the Debian Bug report #888148,
regarding ruby-certificate-authority: FTBFS on ruby2.5: CSR varies?
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.)


-- 
888148: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888148
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-certificate-authority
Version: 0.2.0~6dd483bf-2
Severity: important
User: debian-r...@lists.debian.org
Usertags: ruby2.5

Dear Maintainer,

This package fails to build against ruby2.5. Soon, there will
be a transition to ruby2.5, and this package will FTBFS in sid.

There may be some details on the wiki about common problems:
https://wiki.debian.org/Teams/Ruby/Ruby25Transition

Build log excerpt:


Failures:

  1) CertificateAuthority::SigningRequest Generating CSRs should generate a CSR
     Failure/Error: expect(@csr.to_pem).to eq(expected)

       expected: "-----BEGIN CERTIFICATE 
REQUEST-----\nMIIBUTCBuwIBADAUMRIwEAYDVQQDDAlsb2NhbGhvc3QwgZ8wDQYJKoZIhvcNAQE...YfwPc8CxclIYt1+HyCmBndXIDvGR0JO8/lEdSObZQYHV197hWOay\nreDW940=\n-----END
 CERTIFICATE REQUEST-----\n"
            got: "-----BEGIN CERTIFICATE 
REQUEST-----\nMIIBUzCBvQIBADAUMRIwEAYDVQQDDAlsb2NhbGhvc3QwgZ8wDQYJKoZIhvcNAQE...N1uYQ1mpmN/LtseP8PkP7S3MzJK1SSdI7929EhWfJo4Zrm0+\ngPav58ePPg==\n-----END
 CERTIFICATE REQUEST-----\n"

       (compared using ==)

       Diff:

       @@ -1,11 +1,11 @@
        -----BEGIN CERTIFICATE REQUEST-----
       -MIIBUTCBuwIBADAUMRIwEAYDVQQDDAlsb2NhbGhvc3QwgZ8wDQYJKoZIhvcNAQEB
       +MIIBUzCBvQIBADAUMRIwEAYDVQQDDAlsb2NhbGhvc3QwgZ8wDQYJKoZIhvcNAQEB
        BQADgY0AMIGJAoGBALGIZV9Gt/3QIea9dr5dhYTibstnWyVzpzEhjIiBm5DlPwB6
        pRqRvJhjjAxRHaBnikM+z9Yazx9brqrbeqYdKvVtDodovzOdsPtQv8iKLKJbwjXW
        ituuGKYjHUDrTqqLz/SBBz4fznWDNS6x3nGAo/Zf6g/FjHdUbd2mSwuc0rUjAgMB
       -AAEwDQYJKoZIhvcNAQENBQADgYEAZWLXHmJJyHz+9AdWUJ3U3pLHR/ghA1f3Ihyu
       -2PuYvwqfnGfGTA8DUnQx7l7J6ATIn76SBadmOquBBbbuhJG05WfKZt0oqCAPdsIa
       -XBlLOqVQmWR7YfwPc8CxclIYt1+HyCmBndXIDvGR0JO8/lEdSObZQYHV197hWOay
       -reDW940=
       +AAGgADANBgkqhkiG9w0BAQ0FAAOBgQANCCSnS9L5tUZrtysGF+uP+eSc6O76jRbL
       +9XueRH57ZIddHm/z3xK/01IjyKVlLK7azlL187K1JZwBCwREhodBRULoQJGumhRT
       +qh9RuoJtuzEmviAYN1uYQ1mpmN/LtseP8PkP7S3MzJK1SSdI7929EhWfJo4Zrm0+
       +gPav58ePPg==
        -----END CERTIFICATE REQUEST-----
     # ./spec/units/signing_request_spec.rb:137:in `block (3 levels) in <top 
(required)>'

Finished in 2.15 seconds (files took 0.57521 seconds to load)
196 examples, 1 failure, 3 pending

Failed examples:

rspec ./spec/units/signing_request_spec.rb:124 # 
CertificateAuthority::SigningRequest Generating CSRs should generate a CSR

[Coveralls] Outside the CI environment, not sending data.
/usr/bin/ruby2.5 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format 
documentation failed
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install 
/build/ruby-certificate-authority-0.2.0\~6dd483bf/debian/ruby-certificate-authority
 returned exit code 1
debian/rules:6: recipe for target 'binary' failed
make: *** [binary] Error 1
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

Full build log:
https://rbuild.fau.xxx/2018-01-23/ruby-certificate-authority.log

Please fix it!

Cheers,
Chris.

--- End Message ---
--- Begin Message ---
Source: ruby-certificate-authority
Source-Version: 0.2.0~434c15cd-1

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 888...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sebastien Badia <sba...@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: SHA512

Format: 1.8
Date: Sun, 11 Feb 2018 16:48:34 +0100
Source: ruby-certificate-authority
Binary: ruby-certificate-authority
Architecture: source
Version: 0.2.0~434c15cd-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 
<pkg-ruby-extras-maintain...@lists.alioth.debian.org>
Changed-By: Sebastien Badia <sba...@debian.org>
Description:
 ruby-certificate-authority - tool to manage the core functions outlined in 
RFC-3280 for PKI
Closes: 888148
Changes:
 ruby-certificate-authority (0.2.0~434c15cd-1) unstable; urgency=medium
 .
   * New upstream version 0.2.0~434c15cd
   * d/patches:
     + Remove upgrade-spec-to-rspec3 patch (applied upstream)
     + Refresh others patches (new upstream)
     + Fix CSR spec tests with Ruby 2.5.x (Closes: #888148)
   * d/compat: Bump compat version to 11
   * d/watch: Bump to version 4 and use HTTPS for URI
   * d/copyright: Update copyritght years and use HTTPS for URI
   * d/control:
     + Use my Debian email address
     + Use salsa.debian.org in Vcs-* fields
     + Bump to Standards-Version 4.1.3 (no changes needed)
     + Remove activemodel dependency (already removed from B-D by bdeb690)
Checksums-Sha1:
 cdae28bfec2a476692cb1d93f42b7f0328bdc0c7 2287 
ruby-certificate-authority_0.2.0~434c15cd-1.dsc
 006d5eb371e089ac41f857ddc46dfaead3336600 57426 
ruby-certificate-authority_0.2.0~434c15cd.orig.tar.gz
 e9303db4a8c9d7f16c5a21f689a909ae3ffd49e4 4596 
ruby-certificate-authority_0.2.0~434c15cd-1.debian.tar.xz
 44f2382acd6bb1acb1f042b7cd4ce946fd7d5d1c 6894 
ruby-certificate-authority_0.2.0~434c15cd-1_source.buildinfo
Checksums-Sha256:
 1bb6dda346ba97f1cbb578a5761930cb4bb4b63bd66403fd7ed4c84e764e7910 2287 
ruby-certificate-authority_0.2.0~434c15cd-1.dsc
 0515dd2a07296e255bf33f8ab4edd91de9fc23ace8be02180d969ba0fc936bb9 57426 
ruby-certificate-authority_0.2.0~434c15cd.orig.tar.gz
 9443fca11aa9f1331112be2c87b5c4ff78ae6809d15dbed0401e2ac9e02b7959 4596 
ruby-certificate-authority_0.2.0~434c15cd-1.debian.tar.xz
 0702360f167bb3b6642111678ad860da3af514c18599300e83654a8aab5c70b2 6894 
ruby-certificate-authority_0.2.0~434c15cd-1_source.buildinfo
Files:
 8cea566e6f3fb36980aa4a386e71978a 2287 ruby optional 
ruby-certificate-authority_0.2.0~434c15cd-1.dsc
 0b4db62fbc72a8b396f48f2cbb2651df 57426 ruby optional 
ruby-certificate-authority_0.2.0~434c15cd.orig.tar.gz
 0eaf245e525054ec14cc1c9dcc100eea 4596 ruby optional 
ruby-certificate-authority_0.2.0~434c15cd-1.debian.tar.xz
 776368705009381fae3cac4e0bf5ea22 6894 ruby optional 
ruby-certificate-authority_0.2.0~434c15cd-1_source.buildinfo

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

iQIzBAEBCgAdFiEEfkPprL9yerPPCIUzhxbORhSkUtgFAlqAbjQACgkQhxbORhSk
UtiofQ/9FAhBdseYgXkHPHH3nPvYiZsB4aiz+bmolGp/p8ux3AibKAjLQomioPEc
5gXUVHKThgWHAcg34UlcZTz1FeAlde2lcYDpga+XlkXaOgNb6dopNvSioQAAVIbY
WRZBuWs62InK8FDBiLaHBMPzEf6SjH/YQTJhZbMEKInRojS60oBJqSZFa0bPnMRa
fT7THhUJkSRBUi8J8RMy16KhRli3I1p7V8xYH6ZjkacjrDLBAy3jTa4+b0ASWxWa
jeDLlveQtmFRGWAiDPK+zQlEIiop6Yh93Z5bw25ZSo8rKgOHLPbc2+GmCXLOiwtD
5zwiKhcubbY+jJh7VphpYnfFVbohwpt5CciFaUdNw/it4oykorKaCttxVkUoPahT
0T2PGZ4Ol1baO9j1f9ZJt1P13FS7I3tHWRDbvdmYOD4QovpVybtLyAulRmdzthut
JiEVNnn1N+MmgVC5Jh/WVw5tEiFKwuJv7iO6MxtPdluZKHd1eZzTEf89F8GThZJ8
vZw3wlY5Y9Hd0NBCuLHgsyzbAJ89OclouXq9364Cd+cfaYdlf8IHTQYuO235tAAj
y5tdtY98QE07v2vlaVAxxnblitxES5Fh//uatrClEcHmkziSHy+aH03h5KLKt5Uf
8kXz02NVg1+lBu38q5G2rn+Gx2t+DDV3QGexJIFf6qqIaqmNf58=
=BS2H
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to