unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 48224@debbugs.gnu.org,
	Vagrant Cascadian <vagrant@reproducible-builds.org>
Subject: [bug#48224] [PATCH 0/2] Avoid Bash wrapper in 'guix' package
Date: Wed, 05 May 2021 01:05:03 +0200	[thread overview]
Message-ID: <878s4uksm8.fsf_-_@gnu.org> (raw)
In-Reply-To: <09cee506693a26af13b7fbc318f7a09528161bbc.camel@telenet.be> (Maxime Devos's message of "Tue, 04 May 2021 21:21:24 +0200")

Hi,

Pushed to ‘master’ with followup commits to address the ‘guile2.2-guix’
issues you mentioned:

  dd3e4fe6e7 gnu: guile2.2-guix: Add missing dependencies.
  2238bd8ddc gnu: guile-lzlib: Add Guile 2.2 variant.
  2a9af22540 gnu: guile-zlib: Add Guile 2.2 variant.
  c3f20a6678 gnu: guix: Phases refer to #:system, #:target, and #:native-inputs.
  e42bfd236e gnu: guix: Avoid Bash wrapper.
  55f7cd701c gnu: guix: Add run-time dependency on Guile-Lib.

I’ll cherry-pick to ‘version-1.3.0’.

‘guile2.2-guix’ fails tests/swh.scm though, because (guix swh) relies on
#:verify-certificate?, which Guile 2.2 didn’t have.  I wonder how
Vagrant addressed that for Debian?

Thanks,
Ludo’.




  reply	other threads:[~2021-05-04 23:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-04 13:25 [bug#48224] [PATCH 0/2] Avoid Bash wrapper in 'guix' package Ludovic Courtès
2021-05-04 13:39 ` [bug#48224] [PATCH 1/2] gnu: guix: Avoid Bash wrapper Ludovic Courtès
2021-05-04 13:39   ` [bug#48224] [PATCH 2/2] gnu: guix: Phases refer to #:system and #:target Ludovic Courtès
2021-05-04 19:21     ` Maxime Devos
2021-05-04 23:05       ` Ludovic Courtès [this message]
2021-05-04 23:26         ` [bug#48224] [PATCH 0/2] Avoid Bash wrapper in 'guix' package Vagrant Cascadian
2021-05-09 21:56           ` Ludovic Courtès
2021-05-13  3:45             ` Vagrant Cascadian

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=878s4uksm8.fsf_-_@gnu.org \
    --to=ludo@gnu.org \
    --cc=48224@debbugs.gnu.org \
    --cc=maximedevos@telenet.be \
    --cc=vagrant@reproducible-builds.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 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).