From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>,
"Guix Devel" <guix-devel@gnu.org>,
"Mathieu Othacehe" <othacehe@gnu.org>
Subject: Re: ‘version-1.2.0’ branch created!
Date: Tue, 10 Nov 2020 14:32:40 +0100 [thread overview]
Message-ID: <CAJ3okZ0rU2iUN=XGwC=eKjLKOp1zgddG1kUnEgMP9W5aDB1QGw@mail.gmail.com> (raw)
In-Reply-To: <867dqyfy25.fsf@gmail.com>
Dear,
On Fri, 6 Nov 2020 at 13:52, zimoun <zimon.toutoune@gmail.com> wrote:
> > Thoughts? Patches? Ideas? :-)
>
> A lot of substitutes are still missing (for example R). Is it possible
> to trigger the builds?
I think Ludo tried to trigger a rebuild of all the r-* packages, see
[1]. However, "guix weather -c 15" still lists packages:
+ java-snappy which builds fine locally and Berlin reports
<https://ci.guix.gnu.org/log/mq1xagq5sn9mfhpfg7j2cn1dn4vsds72-java-snappy-1.1.7.5>
+ sbcl-zpb-ttf which builds fine locally and on Bayfront and I am not
able to find information
+ sbcl-cl-paths idem.
+ cl-ana.math-functions but I get a substitute; weird that weather
reports missing.
+sbcl-cl-aa builds fine
+ java-slf4j-simple builds fine
- python-pysam fails because of samtools.
where + means packages that should be rebuild on Berlin and - packages
that does not.
I think some IO issues lead to these missing substitutes and both Data
Services and ci.guix.gnu.org do not always report the correct status.
Well, or I am not sure to correctly understand.
However, it is not really an issue since the compilation is really
fast; I have not checked all the requirements though.
1: <http://issues.guix.gnu.org/44551>
All the best,
simon
next prev parent reply other threads:[~2020-11-10 13:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-06 10:15 ‘version-1.2.0’ branch created! Ludovic Courtès
2020-11-06 12:51 ` zimoun
2020-11-06 13:16 ` Julien Lepiller
2020-11-10 13:32 ` zimoun [this message]
2020-11-08 2:10 ` Oleg Pykhalov
2020-11-08 17:38 ` 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
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='CAJ3okZ0rU2iUN=XGwC=eKjLKOp1zgddG1kUnEgMP9W5aDB1QGw@mail.gmail.com' \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=othacehe@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 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).