From: Ivan Vilata i Balaguer <ivan@selidor.net>
To: Ivan Vilata i Balaguer <ivan@selidor.net>
Cc: 63280@debbugs.gnu.org
Subject: bug#63280: encfs: Fails to build (test segfaults)
Date: Sat, 20 May 2023 12:33:04 +0200 [thread overview]
Message-ID: <ZGih4PeSRdmZFzpN@sax> (raw)
In-Reply-To: <ZGdneUZDj5XE6W+a@sax>
[-- Attachment #1: Type: text/plain, Size: 934 bytes --]
Ivan Vilata i Balaguer (2023-05-19 14:11:37 +0200) wrote:
> […] I copied the definition of the `encfs` package to another file,
> changed `(inputs (list attr fuse openssl tinyxml2))` to `(inputs (list attr
> fuse openssl-1.1 tinyxml2))` (i.e. `openssl -> openssl-1.1`), and the built
> succeeded and tests passed.
>
> Please note that
> <https://github.com/vgough/encfs/issues/600#issuecomment-950026929> points out
> that, around 3 years after the release of EncFS v1.9.5 (the version used in
> Guix), OpenSSL v3 was still very recent, so EncFS may have never been
> thoroughly tested with it anyway.
>
> Maybe reverting to its dependency to OpenSSL v1.1 would be a good choice
> (esp. since v1.1 still receives fixes).
I sent a patch doing that: <https://issues.guix.gnu.org/63593>
(Is it better to send the patch as a reply to this thread?)
Thanks!
--
Ivan Vilata i Balaguer -- https://elvil.net/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2023-05-20 10:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 16:46 bug#63280: encfs: Fails to build (test segfaults) Ivan Vilata i Balaguer
2023-05-19 11:40 ` Ivan Vilata i Balaguer
2023-05-19 12:11 ` Ivan Vilata i Balaguer
2023-05-20 10:33 ` Ivan Vilata i Balaguer [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZGih4PeSRdmZFzpN@sax \
--to=ivan@selidor.net \
--cc=63280@debbugs.gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.