From: Timothy Sample <samplet@ngyro.com>
To: 47027@debbugs.gnu.org
Subject: [bug#47027] Disarchive package
Date: Tue, 09 Mar 2021 14:37:31 -0500 [thread overview]
Message-ID: <87y2ewyv7o.fsf@ngyro.com> (raw)
Hi Guix,
These patches add Disarchive and one of its dependencies,
Guile-QuickCheck.
They are pretty straight forward, but I am a little shaky about using
“guile-3.0-latest”, so I would appreciate another pair of eyes. The
reason it’s there is because Disarchive opportunistically uses the SWH
code from Guix if it is available. If I use plain “guile-3.0”, I get
“incompatible bytecode” errors when restoring archives from SWH.
TIA!
-- Tim
next reply other threads:[~2021-03-09 20:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 19:37 Timothy Sample [this message]
2021-03-09 19:39 ` [bug#47027] [PATCH 1/2] gnu: Add guile-quickcheck Timothy Sample
2021-03-09 19:39 ` [bug#47027] [PATCH 2/2] gnu: Add disarchive Timothy Sample
2021-03-10 10:23 ` Leo Prikler
2021-03-11 22:17 ` [bug#47027] Disarchive package Ludovic Courtès
2021-03-11 22:43 ` Tobias Geerinckx-Rice via Guix-patches via
2021-03-12 3:06 ` Timothy Sample
2021-03-12 10:08 ` Leo Prikler
2021-03-12 16:45 ` Ludovic Courtès
2021-03-21 10:29 ` Ludovic Courtès
2021-03-21 11:10 ` Leo Prikler
2021-03-21 14:13 ` Timothy Sample
2021-03-21 14:59 ` Maxime Devos
2021-03-21 16:59 ` Ludovic Courtès
2021-03-23 4:45 ` bug#47027: " Timothy Sample
2021-03-23 11:01 ` [bug#47027] " Ludovic Courtès
2021-03-10 10:00 ` [bug#47027] [PATCH 1/2] gnu: Add guile-quickcheck Leo Prikler
2021-03-14 21:12 ` Maxime Devos
2021-03-17 20:52 ` [bug#47027] Disarchive package Ludovic Courtès
2021-03-17 21:58 ` bug#47221: Guile not in native-inputs when it should Maxime Devos
2021-03-18 7:18 ` Maxime Devos
2021-03-18 9:29 ` Maxime Devos
2021-03-18 14:01 ` Maxime Devos
2021-03-18 19:08 ` Maxime Devos
2021-03-20 21:45 ` bug#47221: [PATCH v2]: Correct some inputs / native-inputs issues with guile Maxime Devos
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=87y2ewyv7o.fsf@ngyro.com \
--to=samplet@ngyro.com \
--cc=47027@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.