unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Luis Felipe <luis.felipe.la@protonmail.com>
To: Maxime Devos <maximedevos@telenet.be>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Packaging: Need some help replacing a check phase
Date: Mon, 26 Dec 2022 20:31:48 +0000	[thread overview]
Message-ID: <3RuUGTIlxX8mWl6Z_C6yJtqVjzQ-fM8SEYPFNxLleWYP248AO-cxVXybDgM-_5tGaRAUoxHWxo3rz_rSCC0tdc2a6IsUhAWyUqHk9uHdYg8=@protonmail.com> (raw)
In-Reply-To: <3278892e-2264-3b56-33ef-4e94e9de1c4a@telenet.be>


[-- Attachment #1.1: Type: text/plain, Size: 710 bytes --]

Hi Maxime,

On Monday, December 26th, 2022 at 19:04, Maxime Devos <maximedevos@telenet.be> wrote:

> 

> On 26-12-2022 17:15, Luis Felipe wrote:
> 

> > Hi,
> > 

> > I'm packaging a Guile software but the package fails to build when I try to replace the check phase, and I can't see what I'm doing wrong.
> 

> As mentioned by Kaelyn, guile-build-system doesn't have a check phase to
> replace. The patch series at https://issues.guix.gnu.org/58365 adds
> support for tests to guile-build-system; you could apply those patches
> and then replace a phase (and maybe replace 'guile-test-driver' by
> 'guile-proba' for autodiscovery).

Thanks for working on that, Maxime, I had no idea. 


[-- Attachment #1.2: publickey - luis.felipe.la@protonmail.com - 0x12DE1598.asc --]
[-- Type: application/pgp-keys, Size: 1722 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 509 bytes --]

      reply	other threads:[~2022-12-26 20:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-26 16:15 Packaging: Need some help replacing a check phase Luis Felipe
2022-12-26 18:22 ` Kaelyn
2022-12-26 19:54   ` Luis Felipe
2022-12-26 19:04 ` Maxime Devos
2022-12-26 20:31   ` Luis Felipe [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

  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='3RuUGTIlxX8mWl6Z_C6yJtqVjzQ-fM8SEYPFNxLleWYP248AO-cxVXybDgM-_5tGaRAUoxHWxo3rz_rSCC0tdc2a6IsUhAWyUqHk9uHdYg8=@protonmail.com' \
    --to=luis.felipe.la@protonmail.com \
    --cc=guix-devel@gnu.org \
    --cc=maximedevos@telenet.be \
    /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).