From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: 75092@debbugs.gnu.org
Cc: Christopher Baines <mail@cbaines.net>
Subject: bug#75092: Building ruby-puma fails
Date: Wed, 25 Dec 2024 20:04:05 +0100 [thread overview]
Message-ID: <dc6c1ced-4567-49b2-99ed-1457af87e277@crazy-compilers.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1386 bytes --]
Hi,
building ruby-puma fails:
Errors & Failures:
1) Failure:
TestPumaServerSSLWithCertPemAndKeyPem#test_server_ssl_with_cert_pem_and_key_pem
[/tmp/g
uix-build-ruby-puma-6.3.0.drv-0/source/test/test_puma_server_ssl.rb:543]:
Expected #<OpenSSL::SSL::SSLError: SSL_connect returned=1 errno=0
peeraddr=127.0.0.1:33
445 state=error: certificate verify failed (certificate has expired)> to
be nil.
2) Error:
TestIntegrationSSL#test_ssl_run_with_curl_client:
RuntimeError: "curl -s -v --show-error --cacert
/tmp/guix-build-ruby-puma-6.3.0.drv-0/s
ource/examples/puma/client-certs/ca.crt --cert
/tmp/guix-build-ruby-puma-6.3.0.drv-0/so
urce/examples/puma/client-certs/client.crt --key
/tmp/guix-build-ruby-puma-6.3.0.drv-0/
source/examples/puma/client-certs/client.key --tlsv1.2 --tls-max 1.2 -X
GET -k https://
localhost:37245" process failed: pid 892 exit 35
Refreshing the package failed since it now requires ruby 1.3:
/gnu/store/4vm6i8x42xxiqz5rm9qbfnzsfrxkqn9s-bundler-2.4.18/lib/ruby/vendor_ruby/gems/bu
ndler-2.4.18/lib/bundler/resolver.rb:304:in `raise_not_found!': Could
not find gem 'con
current-ruby (~> 1.3)' in locally installed gems. (Bundler::GemNotFound)
Any idea how to solve this?
--
Regards
Hartmut Goebel
| Hartmut Goebel |h.goebel@crazy-compilers.com |
|www.crazy-compilers.com | compilers which you thought are impossible |
[-- Attachment #2: Type: text/html, Size: 2836 bytes --]
reply other threads:[~2024-12-25 19:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=dc6c1ced-4567-49b2-99ed-1457af87e277@crazy-compilers.com \
--to=h.goebel@crazy-compilers.com \
--cc=75092@debbugs.gnu.org \
--cc=mail@cbaines.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).