bug#61364: core-updates branch needed multiple hacks to work

[Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>]

Am Mittwoch, dem 08.02.2023 um 09:57 +0100 schrieb Dr. Arne
Babenhauserheide:
> Hi,
> 
> I updated my Guix system to the core-updates branch because I need
> Mesa 22 and Linux 6 for my new CPU+graphics card.
Note that running core-updates is not recommended, because it is often
missing changes that hit master or staging first.  For instance, Linux
6 is on master right now (but Mesa 22 isn't).  In general, the workflow
for staging/core-updates is to first merge master into the branch, then
deal with the conflicts, then merge the branch onto master.  You can
skip the third step if you're not aiming to push the result to master.

> To get that to work required multiple hacks — mostly ignoring tests
> around missing OSErrors on sockets.
Needless to say, blindly ignoring tests is not a good idea.  Use the
without-tests transformation locally instead.  For CI on the other
hand, we should maximize the number of tests that can run reproducibly.

> I attached the patches I required in the hopes that they can help get
> the core-updates branch into the condition needed to release from it.
Please clean up your patches before submitting and try to follow the
Contribution Guidelines.  For instance, you have three patches in
sequence targeting the documentation of git.  Is it really necessary to
keep two failed attempts at fixing whatever issue this phase causes?

Cheers