From: Jan Nieuwenhuizen <janneke@gnu.org>
To: Vivien Kraus <vivien@planete-kraus.eu>
Cc: 37403@debbugs.gnu.org
Subject: bug#37403: Cannot 'guix guix build --target=x86_64-w64-mingw32 perl'
Date: Sun, 15 Sep 2019 14:16:45 +0200 [thread overview]
Message-ID: <87v9ttah5e.fsf@gnu.org> (raw)
In-Reply-To: <875zlulri8.fsf@planete-kraus.eu> (Vivien Kraus's message of "Sat, 14 Sep 2019 19:25:19 +0200")
Vivien Kraus writes:
>> Are you using the core-updates-next branch?
>
> No,
Ah. In that case it's a `know bug' that is being worked on.
> how do I do that?
I looked into core-updates-next and at the moment it does not seem to be
in a really usable state, in other words: work in progress.
Theoretically one might do `guix pull --branch=<branch-name>'. However,
branches other than master and version-1.0.x are generally not suited
for general use. See `14.6 Submitting Patches'
(https://guix.gnu.org/manual/en/html_node/Submitting-Patches.html).
Using a developer branch like core-updates-next is usually done by
working on a clone of the Guix Git archive. See `14.1 Building from
Git' (https://guix.gnu.org/manual/en/html_node/Building-from-Git.html).
Greetings,
janneke
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
next prev parent reply other threads:[~2019-09-15 12:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-14 7:53 bug#37403: Cannot 'guix guix build --target=x86_64-w64-mingw32 perl' Vivien Kraus
2019-09-14 11:16 ` P via Bug reports for GNU Guix
2019-09-14 11:28 ` Vivien Kraus
2019-09-14 11:59 ` Danny Milosavljevic
2019-09-14 12:23 ` Danny Milosavljevic
2019-09-14 17:24 ` Vivien Kraus
2019-09-14 13:16 ` Jan Nieuwenhuizen
2019-09-14 17:25 ` Vivien Kraus
2019-09-15 12:16 ` Jan Nieuwenhuizen [this message]
2020-03-25 19:49 ` Mathieu Othacehe
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=87v9ttah5e.fsf@gnu.org \
--to=janneke@gnu.org \
--cc=37403@debbugs.gnu.org \
--cc=vivien@planete-kraus.eu \
/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).