Drat, I should have used X-Debbugs-CC to CC Guix-Devel, etc., rather
than the regular CC line, in my previous mail.
The Debbugs address for this bug is 75...@debbugs.gnu.org. Please send
any replies there.
Hi Guix,
First of all, please spare me a few paragraphs to explain why I'm CC'ing
guix-devel on this bug report (I promise it's a good reason this time!).
Introduction
As has been mentioned many, MANY times on these lists, patch review is
erratic in Guix, and patches can be neglecte
Ricardo Wurmus writes:
> Hi,
>
> I've spent the last weeks whipping the python-team branch into shape,
> but I'm running out of steam. There are still a number of failures, and
> I'm about to lose motivation to continue fixing the remaining build
> failures.
Thank you for the work!
> Here are
Attila Lendvai writes:
>> > this patch failed to get any attention in two weeks
>>
>>
>> Two weeks isn't a long time in free software projects. A more common
>> time frame would be between one year and eighteen months.
>
>
> ...and with such a delay most patches bitrot beyond recognition, then
>
> > this patch failed to get any attention in two weeks
>
>
> Two weeks isn't a long time in free software projects. A more common
> time frame would be between one year and eighteen months.
...and with such a delay most patches bitrot beyond recognition, then after one
too many burdensome rebas
Hi,
I've spent the last weeks whipping the python-team branch into shape,
but I'm running out of steam. There are still a number of failures, and
I'm about to lose motivation to continue fixing the remaining build
failures.
Here are some of the failures that may be of interest:
ansible
pyth
