GNU bug report logs - #75518
Request for merging "core-packages-team" branch

Previous Next

Package: guix-patches;

Reported by: Janneke Nieuwenhuizen <janneke <at> gnu.org>

Date: Sun, 12 Jan 2025 15:33:01 UTC

Severity: normal

Done: Andreas Enge <andreas <at> enge.fr>

Full log


View this message in rfc822 format

From: yelninei <at> tutamail.com
To: Andreas Enge <andreas <at> enge.fr>
Cc: Greg Hogan <code <at> greghogan.com>, Ludovic Courtès <ludo <at> gnu.org>, Christopher Baines <mail <at> cbaines.net>, Z572 <zhengjunjie <at> iscas.ac.cn>, Liliana Marie Prikler <liliana.prikler <at> gmail.com>, Iyzsong <iyzsong <at> envs.net>, Rutherther <rutherther <at> ditigal.xyz>, Z572 <z572 <at> z572.online>, 75518 <75518 <at> debbugs.gnu.org>, Janneke Nieuwenhuizen <janneke <at> gnu.org>
Subject: [bug#75518] Request for merging "core-packages-team" branch
Date: Thu, 5 Jun 2025 16:14:17 +0200 (CEST)
Hello Andreas,


Jun 5, 2025, 09:49 by andreas <at> enge.fr:

> Am Mon, Jun 02, 2025 at 06:35:06PM +0200 schrieb Rutherther:
>
>> Andreas Enge <andreas <at> enge.fr> writes:
>> > I wonder if one "solution" would be to remove motif and its dependent
>> > packages?
>> I suppose. Is it fine to not follow the deprecation policy though? I am
>> really expecting just putting gcc-11 to native-inputs will fix it.
>>
>
> Okay, fine as well. If not, as this branch is concerned, I am getting
> desperate, and think that any approach to getting it merged would be
> good :)
>
> Concerning clisp, there is a fix for some test problem on master.
>
> I have rebased again on master, dropped the bash replacement and added the
> CPPFLAG to the bash package itself, and pushed.
>

It seems like the merge conflict I caused for hurd has been resolved incorrectly: hurd still has the "hurd-64bit.patch" that I removed when updating hurd for core-packages-team.

> It would be good to get this merged, the branch sends out strong
> core-updates vibes - we made the merge request almost five months ago!
> This is quite incompatible with our goal of making a release once per
> year, or maybe even twice.
> Also qt-team is waiting for the switch to gcc <at> 14.
>
> Are the remaining problems critical, or something that could be fixed
> later on master?
>
having every gcc that is not gcc-14 broken seems bad.

Here is where where the packages I reported come from:
clisp is blocking linux-libre
dtc and openbios are blocking grub
nvi is in %base-packages-interactive
python-pyelftools is blocking genimage
fakeroot is needed for system-disk-image

You cannot currently run guix system image gnu/system/examples/bare-bones.tmpl from core packages team.


> QA feels a bit slow right now, so I was about to suggest watching CI
> instead, but this gives me 504 errors...
>
> Andreas
>
Yelninei




This bug report was last modified 22 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.