all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Vincent Legoll <vincent.legoll@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: 1.1.0rc1 available for test!
Date: Sun, 12 Apr 2020 08:43:28 +0200	[thread overview]
Message-ID: <CAEwRq=p9uyqS90=Xsp-ZaQ0n51CV8FRj2QztVJynC8Qc+anvqw@mail.gmail.com> (raw)
In-Reply-To: <87sgh9r75g.fsf@gnu.org>

Hello,

On Sun, Apr 12, 2020 at 12:26 AM Ludovic Courtès <ludo@gnu.org> wrote:
> Did you use ‘guix-install.sh’ (modified) or did you install it manually?

I used a modified guix-install.sh for the void testing (I'll submit
the modifications) but not for the others. I'll do future testing
with it, as it is the recommended way to setup guix on a foreign
distro.

BTW, how would I test that (modified guix-install + nix/local.mk) ?

I've modified guix-install to handle runit-based distros (for void
linux) and nix/local.mk, like in the sysv-init enablement Danny
submitted lately.

I've seen the rebuild instructions at the end of binary installation
page in the manual, but I couldn't make that take my local
modifications in account. I think there's some required steps
that are only made by the release make target.

I want to test, at least once before submitting my patch series
for review. Even if I think it would be nice-to-have for the 1.1.0...

> > (*) those tried to rebuild a lot of things locally at step 5,
> > so I stopped them. Maybe an operator error...
>
> Could be that substitutes were missing.

Yes, that's also possible, how would I check / ensure that ?

> > I'm still working on automating those tests though...
>
> Heh, we’ll have them for 1.2.  ;-)

Hopefully.

Thanks

-- 
Vincent Legoll

  reply	other threads:[~2020-04-12  6:43 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-09 20:51 1.1.0rc1 available for test! Ludovic Courtès
2020-04-09 21:33 ` Danny Milosavljevic
2020-04-10  1:56 ` pelzflorian (Florian Pelz)
2020-04-10 10:38   ` Ludovic Courtès
2020-04-10 12:06   ` Mathieu Othacehe
2020-04-10 14:35   ` pelzflorian (Florian Pelz)
2020-04-10 14:47     ` pelzflorian (Florian Pelz)
2020-04-13 18:12       ` pelzflorian (Florian Pelz)
2020-04-10  3:20 ` Vagrant Cascadian
2020-04-10 10:29   ` Ludovic Courtès
2020-04-10 11:24 ` Alex Sassmannshausen
2020-04-10 12:01   ` Mathieu Othacehe
2020-04-10 12:19     ` Alex Sassmannshausen
2020-04-10 12:07   ` Alex Sassmannshausen
2020-04-10 12:17     ` Mathieu Othacehe
2020-04-10 13:11       ` Alex Sassmannshausen
2020-04-10 13:53       ` Mathieu Othacehe
2020-04-10 14:19         ` Ludovic Courtès
2020-04-10 16:02           ` Alex Sassmannshausen
2020-04-10 15:42 ` Alex Sassmannshausen
2020-04-10 22:38   ` Ludovic Courtès
2020-04-11  9:11     ` alex sassmannshausen
2020-04-11 13:16       ` Amin Bandali
2020-04-11 13:48         ` Pierre Neidhardt
2020-04-10 15:45 ` Alex Sassmannshausen
2020-04-11 10:51 ` Vincent Legoll
2020-04-11 22:26   ` Ludovic Courtès
2020-04-12  6:43     ` Vincent Legoll [this message]
2020-04-13 10:50       ` Ludovic Courtès
2020-04-13 11:46         ` Vincent Legoll
2020-04-13 12:36         ` Vincent Legoll
2020-04-13 16:14         ` Vincent Legoll
2020-04-13 20:24           ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAEwRq=p9uyqS90=Xsp-ZaQ0n51CV8FRj2QztVJynC8Qc+anvqw@mail.gmail.com' \
    --to=vincent.legoll@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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.