On workflows and GWL

On Mon, Feb 04, 2019 at 07:14:23PM +0100, zna...@tutanota.com wrote: >Cool story from Ricardo Wurmus! >[1]https://fosdem.org/2019/schedule/event/guixinfra/ > >"The concept of the workflow is the expansion of the idea of >pipeline." We discussed workflows and I suppose we should c

Re: On workflows and GWL

Oh, missed that. There is a mailing list! http://lists.gnu.org/archive/html/gwl-devel/ On Tue, Feb 05, 2019 at 09:36:24AM +0100, Pjotr Prins wrote: > We discussed workflows and I suppose we should continue the > discussion. What would be the best mailing list - Guix, guix-hpc or a > new one?

Re: Video documentation repository

Hi Ludo, On Tue, 05 Feb 2019 00:02:20 +0100 Ludovic Courtès wrote: > Great initiative! I can’t create it myself but I’ve filed a support > request: (the Savannah > hackers usually respond within a couple of days.) Thank you for filing the request.

New Danish PO file for 'guix-packages' (version 0.16.0)

Hello, gentle maintainer. This is a message from the Translation Project robot. A revised PO file for textual domain 'guix-packages' has been submitted by the Danish team of translators. The file is available at: https://translationproject.org/latest/guix-packages/da.po (We can arrange thi

Re: Policy to remove obsolete packages

On Mon, 04 Feb 2019 23:52:47 +0100 Ludovic Courtès wrote: > (Note that, IIUC, in openSuSE a package can be broken and yet remain > installable by users, because the last binary that was produced is > still around.) We have guix pull --commit=..., inferiors, channels and time-travel, so there ar

Re: Policy to remove obsolete packages

On Tue, 5 Feb 2019 00:47:42 +0100 zimoun wrote: > To me the question is more about how to automatically detect that a > patch breaks another package than a policy to remove a broken package. > > I mean if we are able to automatically detect 6 months later that a > package is broken, why are we n

Re: FOSDEM 2019: Thank you!

On Mon, 4 Feb 2019 07:13:47 +0100 Pjotr Prins wrote: > Thank you everyone for this great FOSDEM with the GNU Guix days: it > was just great to see everyone and all the interactions! I feel much > inspired to try GNU Hurd, new Guix features, the new Guile build > system and even Racket (oops). It

Re: Rust 1.19 fails to build on i686 on ‘staging’

Chris and I compared what gets sent by the parent on i686 (where it breaks) vs on x86_64 (where it doesn't break): There are no differences. The next step will be to find out what the child process does with the data. I suspect that the child processes' input deserializer is broken. For referenc

Re: maven build system - new insights

Am 01.02.19 um 00:33 schrieb Ricardo Wurmus: > Hartmut Goebel writes: >> The drawback of this approach is: This only works within the >> build-system. Since within a normal environment or profile, there will >> be no such unison repo. Thus for every day's work, users will still >> download artifac

Questions related to packaging go-bitmask-vpn

Hi Today I took a stab at packaging the new go-bitmask-vpn The go-files are not in the pkg-root and the go-build-system therefore fails with: "starting phase `build' can't load package: package 0xacab.org/leap/bitmask-vpn: no Go files in /tmp/guix-build-go-bitmask-vpn-0.19.1.drv-0/src/0xacab

Re: On workflows and GWL

Pjotr Prins writes: > Oh, missed that. There is a mailing list! > > http://lists.gnu.org/archive/html/gwl-devel/ Yup, the gwl-devel mailing list is the place where GWL action happens. I’m looking forward to discussing the semantics of a CWL export with you there! :) -- Ricardo

Removing ocaml-4.01?

Hi Ben, During Fosdem we were discussing a security issue affecting ocaml-4.01. It seems that the only user of this version of ocaml is pplacer, which has been failing to build consistently since quite some time now. Since nobody complained, I suppose nobody uses that package and I'd like to

New Danish PO file for 'guix' (version 0.16.0)

Hello, gentle maintainer. This is a message from the Translation Project robot. A revised PO file for textual domain 'guix' has been submitted by the Danish team of translators. The file is available at: https://translationproject.org/latest/guix/da.po (We can arrange things so that in the

Re: [shepherd] 01/01: service: Don't raise error when stopping an already stopped service.

Hello! rek...@elephly.net (Ricardo Wurmus) skribis: > +# Stopping a stopped service should be a no-op. > +out=$($herd stop test) > +test $? > +test -z "$out" A really minor issue, but I’d suggest writing it like this: $herd stop test out="`$herd stop test`" test -z "$out" The reasoning i

libgtk3-nocsd and LD_PRELOAD (Was: bug#33861: Problem building sources for guile-bash)

Hi Ludo, On Sat, 19 Jan 2019 11:21:56 +0100 Ludovic Courtès wrote: > Björn Höfling skribis: > > > $ guix build -S guile-bash > > ERROR: ld.so: object 'libgtk3-nocsd.so.0' from LD_PRELOAD cannot be > > preloaded (cannot open shared object file): ignored. > > Plus, warranty void if you fiddle

Re: Policy to remove obsolete packages

Bjrn Hfling transcribed 846 bytes: > On Mon, 04 Feb 2019 23:52:47 +0100 > Ludovic Courtès wrote: > > > > (Note that, IIUC, in openSuSE a package can be broken and yet remain > > installable by users, because the last binary that was produced is > > still around.) > > We have guix pull --commit=

Re: Policy to remove obsolete packages

n...@n0.is skrev: (5 februari 2019 22:31:53 CET) >Bjrn Hfling transcribed 846 bytes: >> On Mon, 04 Feb 2019 23:52:47 +0100 >> Ludovic Courtès wrote: >> >> >> > (Note that, IIUC, in openSuSE a package can be broken and yet >remain >> > installable by users, because the last binary that was produc

Re: Policy to remove obsolete packages

swedebugia transcribed 6.9K bytes: > n...@n0.is skrev: (5 februari 2019 22:31:53 CET) > >Bjrn Hfling transcribed 846 bytes: > >> On Mon, 04 Feb 2019 23:52:47 +0100 > >> Ludovic Courtès wrote: > >> > >> > >> > (Note that, IIUC, in openSuSE a package can be broken and yet > >remain > >> > installa