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
On Sat, May 29, 2021 at 09:50:36PM -0700, Vagrant Cascadian wrote:
> When it generates a tarball, all the various packages independently try
> to recreate the source tarball; so you have at least fours jobs
> ("linux-libre", "linux-libre-arm64-generic", "linux-libre-headers",
> "linux-libre-bpf") a
On 2021-05-01, Leo Famulari wrote:
> On Sat, May 01, 2021 at 06:45:32PM -0700, Vagrant Cascadian wrote:
>> Pragmatically speaking, on slower platforms this is a huge resource
>> overhead. So much so that ci.guix.gnu.org *usually* times out when
>> generating the linux-libre aarch64 tarballs:
>>
>>
On May 6, 2021, Maxim Cournoyer wrote:
> Alexandre Oliva writes:
>> recipes as to the possibilities of getting to the GNU Linux-libre
>> sources from it, how to verify signatures, etc
> I for one have not seen them. Would you mind making them available
> somewhere? I'd be interested in havi
On Thu, May 06, 2021 at 01:10:45AM -0300, Alexandre Oliva wrote:
> I have heard about early format changes, but since Linux itself has used
> git archive to generate tarballs on the fly, and published digital
> signatures based on archives generated this way, I presume an
> expectation that changes
Hello,
Alexandre Oliva writes:
[...]
> Back when we made the switch, I wrote extensive documentation and
> recipes as to the possibilities of getting to the GNU Linux-libre
> sources from it, how to verify signatures, etc. It was to be assessed
> by then maintainers of Guix recipes to build GN
On May 3, 2021, Leo Famulari wrote:
> Is the tarball generation "stable" across Git releases? Or is it
> subject to change? We had this issue with Git archive creation in the
> past.
I have heard about early format changes, but since Linux itself has used
git archive to generate tarballs on the
On Mon, May 03, 2021 at 01:39:54PM -0300, Alexandre Oliva wrote:
> You don't have to clone anything. If all you want is a tarball, use
> 'git archive --remote'.
Thanks, I didn't know about this feature. Is the tarball generation
"stable" across Git releases? Or is it subject to change? We had thi
Hello, Leo,
On May 1, 2021, Leo Famulari wrote:
> it's not "source code" in the GNU sense, which is the "preferred form
> of the work for making changes in it":
That's not accurate. Linux-libre sources, whether obtained from a git
repository or from a tarball, are just as suitable for kernel
On Sat, May 01, 2021 at 10:45:22PM -0400, Leo Famulari wrote:
> The immediate solution is for me to make sure the tarballs have built
> before committing the updates. I already do this for x86_64 and I can
> start doing it for aarch64 too.
Well, this is easier said than done, currently.
I was abl
On Sun, May 02, 2021 at 06:26:15PM -0400, Leo Famulari wrote:
> In the meantime, can we make a 'kernel-updates' Cuirass job again, that
> would build a kernel-updates branch on Savannah?
Mistake: I'd want to call the branch wip-kernel-updates, so that it's
rebaseable.
> We had one recently for a
On Sun, May 02, 2021 at 11:08:49PM +0200, Ludovic Courtès wrote:
> For packages we can add a ‘max-silent-time’ property, but there’s
> nothing like this for origins.
Oh, right.
> I wonder if there’s a way we could address it in (gnu ci).
>
> Thoughts?
In the meantime, can we make a 'kernel-upda
Leo Famulari skribis:
> On Sat, May 01, 2021 at 10:45:22PM -0400, Leo Famulari wrote:
>> The immediate solution is for me to make sure the tarballs have built
>> before committing the updates. I already do this for x86_64 and I can
>> start doing it for aarch64 too.
>
> I started building the cur
On Sat, May 01, 2021 at 10:45:22PM -0400, Leo Famulari wrote:
> The immediate solution is for me to make sure the tarballs have built
> before committing the updates. I already do this for x86_64 and I can
> start doing it for aarch64 too.
I started building the current derivations "by hand" on th
On Sat, May 01, 2021 at 06:45:32PM -0700, Vagrant Cascadian wrote:
> Pragmatically speaking, on slower platforms this is a huge resource
> overhead. So much so that ci.guix.gnu.org *usually* times out when
> generating the linux-libre aarch64 tarballs:
>
>
> https://ci.guix.gnu.org/search?query
So, for better or worse, I do a lot with guix on aarch64 platforms and
sometimes even armhf ones. And these platforms are... often...
quite... slow...
The way guix does updates of linux-libre sources by downloading upstream
linux tarballs and applying the linux-libre deblobbing and related
scrip
16 matches
Mail list logo
