unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Jean-Pierre De Jesus Diaz via Bug reports for GNU Guix <bug-guix@gnu.org>
To: "Ludovic Courtès" <ludovic.courtes@inria.fr>
Cc: 68474@debbugs.gnu.org
Subject: bug#68474: [Guix-Past]: openssl@1.0.2u does not pass tests
Date: Wed, 31 Jan 2024 13:07:02 +0000	[thread overview]
Message-ID: <CAG1gdUrYCU7N0y2aL3TXjMu7e__EFsbrJFEMyeZ+Xs_x8cAhwg@mail.gmail.com> (raw)
In-Reply-To: <878r46k9w0.fsf@gnu.org>

Hi,

On Tue, Jan 30, 2024 at 5:29 PM Ludovic Courtès
<ludovic.courtes@inria.fr> wrote:
>
> Hi,
>
> Jean-Pierre De Jesus Diaz <jean@foundationdevices.com> skribis:
>
> > And the from the error file that the test writes:
> >
> > $ cat /tmp/guix-build-openssl-1.0.2u.drv-0/openssl-1.0.2u/test/cms.err
> > Verification failure
> > 140737353281920:error:21075075:PKCS7 routines:PKCS7_verify:certificate
> > verify error:pk7_smime.c:335:Verify error:certificate has expired
>
> This is a typically “time trap”.  Options are: use libfaketime to run
> “make check”, change the certificates so they don’t expire, or skip
> those tests.
>
> Would you like to give it a try?
>
> Thanks,
> Ludo’.

I'll give it a try to use libfaketime to keep tests enabled.

Thanks,

-- 
Jean-Pierre De Jesus DIAZ
Foundation Devices, Inc.




  reply	other threads:[~2024-01-31 13:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-15 15:05 bug#68474: [Guix-Past]: openssl@1.0.2u does not pass tests Jean-Pierre De Jesus Diaz via Bug reports for GNU Guix
2024-01-30 17:29 ` Ludovic Courtès
2024-01-31 13:07   ` Jean-Pierre De Jesus Diaz via Bug reports for GNU Guix [this message]
2024-01-31 14:20 ` bug#68474: [PATCH] tls: Fix openssl-1.0 check phase Jean-Pierre De Jesus DIAZ via Bug reports for GNU Guix
2024-02-02  0:07   ` Ludovic Courtès

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=CAG1gdUrYCU7N0y2aL3TXjMu7e__EFsbrJFEMyeZ+Xs_x8cAhwg@mail.gmail.com \
    --to=bug-guix@gnu.org \
    --cc=68474@debbugs.gnu.org \
    --cc=jean@foundationdevices.com \
    --cc=ludovic.courtes@inria.fr \
    /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).