On Mon, Apr 12, 2021 at 09:47:45PM +0100, Christopher Baines wrote:
>
> Christopher Baines writes:
>
> > Mathieu Othacehe writes:
> >
> >>> One workaround, the one employed in the tests is to revert to the old
> >>> behaviour for the PostgreSQL service by setting socket-directory to #f.
> >>
>
Christopher Baines writes:
> Mathieu Othacehe writes:
>
>>> One workaround, the one employed in the tests is to revert to the old
>>> behaviour for the PostgreSQL service by setting socket-directory to #f.
>>
>> You're right, sorry about the breakage. As you noticed we are in an
>> in-between s
Mathieu Othacehe writes:
>> One workaround, the one employed in the tests is to revert to the old
>> behaviour for the PostgreSQL service by setting socket-directory to #f.
>
> You're right, sorry about the breakage. As you noticed we are in an
> in-between situation where the patch updating Pos
Hello Chris,
> One workaround, the one employed in the tests is to revert to the old
> behaviour for the PostgreSQL service by setting socket-directory to #f.
You're right, sorry about the breakage. As you noticed we are in an
in-between situation where the patch updating Postgresql package to
Hey,
When reconfiguring recently, I ran in to issues with the Guix Data
Service and probably the Patchwork service too.
Looking at the change, I think it's clear there's a problem, because
some system tests were changed, and I'm guessing they were changed so
that they passed [1].
1:
https://git
