From: Mathieu Othacehe <othacehe@gnu.org>
To: Leo Famulari <leo@famulari.name>
Cc: Vagrant Cascadian <vagrant@debian.org>, guix-devel <guix-devel@gnu.org>
Subject: Re: linux-libre source tarballs
Date: Mon, 31 May 2021 21:57:36 +0200 [thread overview]
Message-ID: <874kei4qxb.fsf@gnu.org> (raw)
In-Reply-To: <YLRbHPRsjah9+fQo@jasmine.lan> (Leo Famulari's message of "Sun, 30 May 2021 23:42:20 -0400")
Hello,
>> Not knowing exactly how ci.guix.gnu.org works, would it make sense to
>> create a tarball package instead of the ... computed origin(?) tarball,
>> so it could be better represented in the package dependency graph, and
>> the various linux-libre-* packages can wait till it is available rather
>> than all trying to recreate the same thing?
>
> If I understand correctly, this was recently fixed in Cuirass:
>
> https://git.savannah.gnu.org/cgit/guix/guix-cuirass.git/commit/?id=d1a95e8b33b454a45bda506a22a8b9d9d2c8b16e
With the recent Cuirass commits, the notion of build dependencies have
been introduced. If you have a look to this page:
https://ci.guix.gnu.org/build/497096/details, you will see that the
"git" build won't start until all the other builds it depends are
successfully completed (xmlto, subversion, tk ...).
The problem with linux-libre and a few other packages is that some of
the derivations they depend do not correspond to proper packages that
are identified and built by Cuirass. You will see here:
https://ci.guix.gnu.org/build/512266/details that linux-libre has no
build dependencies.
If we could translate the computed origin method into a package, I think
it could solve this issue. I also noticed a similar issue with
ublock-origin and the make-chromium-extension method.
Thanks,
Mathieu
next prev parent reply other threads:[~2021-05-31 19:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-02 1:45 linux-libre source tarballs Vagrant Cascadian
2021-05-02 2:45 ` Leo Famulari
2021-05-02 4:42 ` Leo Famulari
2021-05-02 21:08 ` Ludovic Courtès
2021-05-02 22:26 ` Leo Famulari
2021-05-02 22:38 ` Leo Famulari
2021-05-03 15:44 ` linux-libre source tarballs (disable "deblob-check"?) Leo Famulari
2021-05-03 16:39 ` linux-libre source tarballs Alexandre Oliva
2021-05-03 17:13 ` Leo Famulari
2021-05-06 4:10 ` Alexandre Oliva
2021-05-06 21:23 ` Leo Famulari
2021-05-06 20:30 ` Maxim Cournoyer
2021-05-09 3:27 ` Alexandre Oliva
2021-05-30 4:50 ` Vagrant Cascadian
2021-05-31 3:42 ` Leo Famulari
2021-05-31 19:57 ` Mathieu Othacehe [this message]
2021-08-01 20:45 ` source tarballs potentially built for each derivation Vagrant Cascadian
2021-08-01 21:04 ` Vagrant Cascadian
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=874kei4qxb.fsf@gnu.org \
--to=othacehe@gnu.org \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
--cc=vagrant@debian.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).