From: Jan Nieuwenhuizen <janneke@gnu.org>
To: 28484@debbugs.gnu.org
Subject: [bug#28484] Some steps and questions for Cuirass
Date: Sun, 17 Sep 2017 22:11:53 +0200 [thread overview]
Message-ID: <20170917201157.9802-1-janneke@gnu.org> (raw)
When Cuirass creates a new working directory from a guix.git clone, it tries
to build guix but fails like this
/gnu/store/jqs80jq4j9z06p2vb9f7djv9k7jmc3d4-profile/bin/msgmerge: cannot create output file "de.po": Permission denied
make[3]: *** [Makefile:255: de.po] Error 1
make[3]: *** Waiting for unfinished jobs....
...although that may be a feature?
Patch 1/3 fixes this build problem...however now Cuirass rebuilds *all* of
guix (.go files) for each update of guix.git that it tracks. When playing
with Cuirass to set it up, it's handy to only build `hello'. Rebuilding all
of guix for each commit even if it fast-forwards, do we need/want that?
Patch 2/3 allows to test with other packages than "hello" or everything by
using a spec like
((#:name . "guix")
(#:url . "git://git.savannah.gnu.org/guix.git")
(#:load-path . ".")
(#:file . "examples/gnu-system.scm")
(#:proc . hydra-jobs)
(#:arguments (subset . ("hello" "grep")))
(#:branch . "master"))
Because this build recipe and thus this feature belongs in the repository
we're building, I also added a patch (the last one) for Guix itself that
implements this.
Patch 3/3 is the one I'm least happy with. When building many more packages
than only `hello', Cuirass will not give any feedback until after everything
is built. The Emacs interface under M-x guix-hydra-latests-builds is very
nice, but polling for that less so.
As the comment in the file already says
;; Register the results in the database.
;; XXX: The 'build-derivations' call is blocking so we end updating the
;; database potentially long after things have been built.
we probably want feedback (or guix-hydra-latests-builds availability) per
package...but any ideas how to do that? We'd have to wrap/closure that into
building the derivations?
Greetings,
janneke
next reply other threads:[~2017-09-17 20:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-17 20:11 Jan Nieuwenhuizen [this message]
2017-09-17 20:11 ` [bug#28485] [PATCH 1/3] base: Make working copy writable Jan Nieuwenhuizen
[not found] ` <handler.28485.B.1505679193775.ack@debbugs.gnu.org>
2017-09-18 15:46 ` bug#28485: Acknowledgement ([PATCH 1/3] base: Make working copy writable.) Jan Nieuwenhuizen
2017-09-17 20:11 ` [bug#28486] [PATCH 2/3] gnu-system: Accept subset with list of package names Jan Nieuwenhuizen
[not found] ` <handler.28486.B.1505679194784.ack@debbugs.gnu.org>
2017-09-18 15:45 ` bug#28486: Acknowledgement ([PATCH 2/3] gnu-system: Accept subset with list of package names.) Jan Nieuwenhuizen
2017-09-17 20:11 ` [bug#28488] [PATCH 3/3] base: Show feedback when build has finished Jan Nieuwenhuizen
[not found] ` <handler.28488.B.1505679198802.ack@debbugs.gnu.org>
2017-09-18 15:48 ` bug#28488: Acknowledgement ([PATCH 3/3] base: Show feedback when build has finished.) Jan Nieuwenhuizen
2017-09-17 20:11 ` [bug#28487] [PATCH] cuirass: Add gnu-system build spec Jan Nieuwenhuizen
2017-09-26 8:18 ` Ludovic Courtès
2017-09-26 17:56 ` Jan Nieuwenhuizen
2017-09-26 18:05 ` Jan Nieuwenhuizen
2017-09-26 20:29 ` Ludovic Courtès
2017-09-27 18:55 ` Jan Nieuwenhuizen
2017-09-27 19:45 ` Ludovic Courtès
2017-09-27 20:32 ` Jan Nieuwenhuizen
2017-09-27 20:52 ` Jan Nieuwenhuizen
2017-09-28 8:26 ` Ludovic Courtès
2017-09-28 15:41 ` bug#28487: " Jan Nieuwenhuizen
2017-09-28 8:27 ` [bug#28487] " Ludovic Courtès
2017-09-28 16:04 ` Jan Nieuwenhuizen
2017-09-18 11:51 ` [bug#28484] Some steps and questions for Cuirass Mathieu Othacehe
2017-09-18 15:44 ` bug#28484: " Jan Nieuwenhuizen
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=20170917201157.9802-1-janneke@gnu.org \
--to=janneke@gnu.org \
--cc=28484@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.