Hello,
As a new-new Guix user, I did find the review process or the time
it takes really long.
Maybe I've tackle too complex updates[0], I don't know but I don't
have a clear path how to push it.
As a dev, I am not super used to the email-patches workflow, I am
more used to the pull-request
Hello,
Is there anyone working on updating the docker packages to 20.x I believe Guix
ships with 19.x this is EOL if I remember it’s EOL. If someone working on it I
will be happy to help.
Thanks
Sent from my internet monolith
am sure we will have a few
dependencies to fix
It will be good to work together to fix them.
Thanks
[0] https://issues.guix.gnu.org/55210
On Thu, Apr 21, 2022 at 10:58 AM Katherine Cox-Buday <
cox.katherin...@gmail.com> wrote:
> Pier-Hugues Pellerin writes:
>
> > We should pr
.18. and
go-1.17.
- Move go to go-1.18 in another branch
- Remove 1.16?
WDYT? I am not super familiar with the scheme but this seems like a good
exercise.
Thanks
On Wed, Apr 20, 2022 at 7:43 PM Pier-Hugues Pellerin wrote:
> That sound great and great timing I was working on that as you se
to 1.18.
This will allow merging things right away to add support for go 1.18 and
also allow Ludovic to create the branch and rebuild.
Thanks
On Wed, Apr 20, 2022 at 7:36 PM Katherine Cox-Buday <
cox.katherin...@gmail.com> wrote:
> >>> Pier-Hugues Pellerin writes:
> >
Hello,
Is that a new behaviour? I’ve recently updated go to package to 1.17.8.
Sent from my portable monolith.
Ph
> On Apr 16, 2022, at 12:09 PM, jgart wrote:
>
> Hi Guixers,
>
> go libraries do not work in a guix shell.
>
> Some user experience reports:
>
> 2022-04-13 23:40:32Go work
use 1.18 sooner?
2. Move to the default Go to 1.18 with (define-public go go-1.17) and
create the testing branch from that?
Thanks for the `refresh` tips.
On Sun, Apr 10, 2022 at 4:45 PM Ludovic Courtès wrote:
> Hi,
>
> Pier-Hugues Pellerin skribis:
>
> > I am trying to updat
Hello,
I am trying to update Go to 1.18, I do have a *working* patch that defines
a package that inherits from 1.17 and that adjusts the inputs. However, I
have a few questions:
1. Is inheriting the way to do that? The package's build system appears to
be the same from 1.17.
2. How can I rebuild