GNU bug report logs -
#75751
Request for merging "python-team" branch
Previous Next
Reported by: Ricardo Wurmus <rekado <at> elephly.net>
Date: Wed, 22 Jan 2025 09:10:03 UTC
Severity: normal
Done: Sharlatan Hellseher <sharlatanus <at> gmail.com>
Bug is archived. No further changes may be made.
Full log
Message #77 received at 75751 <at> debbugs.gnu.org (full text, mbox):
On 2025-03-26 09:51, Christopher Baines wrote:
> Sharlatan Hellseher <sharlatanus <at> gmail.com> writes:
>
>> Hi Ricardo,
>>
>> I can contribute some time, please share your WIPs or
>> I can take a list from data service
>
> Thanks for volunteering, unfortunately I can't commit any time in the
> next couple of weeks.
>
> QA is still super fragile, but looking at python-team currently it has
> at least mostly built the branch, and while the information still isn't
> as clear as it could be, QA is highlighting at least some of the broken
> packages (at least 35 python-... things I think).
>
> Ideally these broken packages would be fixed before merging, but the
> current situation is still an improvement over the state of previous
> branch merges.
The issue is that Python development is not as well structured as those
of other languages. I noticed for instance that almost all failing
packages in bioinformatics and astronomy are packages that are simply
not developped anymore. We could remove them or maybe move them to
guix-past, but the effort for making them build again is not bearable in
Guix. That still means we're going to remove at least 15 packages just
because they don't build.
guix-past with an older version of python sounds good to me, but I don't
know if we have a policy on that.
--
Best regards,
Nicolas Graves
This bug report was last modified 86 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.