bug#56799: (gnu services configuration) usage of *unspecified* is problematic

On 28-07-2022 06:55, b...@bokr.com wrote: Lots of systems are dealing with this issue, it seems, judging from [1]https://en.wikipedia.org/wiki/Bottom_type I don't think it's a bottom type -- *unspecified* _is_ a value, so if we assign a type to it, it is inhabited, and hence not a bottom type

bug#56805: guix import opam fails

angola10 via Bug reports for GNU Guix writes: > Hello, > > The following opam package import fails > > Command: `guix import opam -r mirage-crypto-pk` > > Output: > > ``` > > Starting download of /tmp/guix-file.ZERar3 > From > https://github.com/mirage/mirage-crypto/releases/download/v0.10.6/m

bug#56799: [PATCH v2] gexp: Handle *unspecified* as a gexp input.

Hi, Maxime Devos writes: > On 27-07-2022 22:20, Maxim Cournoyer wrote: > >> Fixes . >> >> * guix/gexp.scm (gexp->sexp)[*unspecified*]: Quote value when encountering >> it. > > I recommend writing a test case -- this patch does not actually do that. > > Instead

bug#56799: (gnu services configuration) usage of *unspecified* is problematic

Hi Maxime, Maxime Devos writes: [...] > I think it would be better to: > > * gradually move away from *unspecified* to (values) > * and this way, gradually change the meaning of *unspecified* from "an >unspecified value" to 'an atom you can do with as you want" > * after this, unspecifie

bug#56805: guix import opam fails

angola10 via Bug reports for GNU Guix writes: > Command: `guix import opam -r mirage-crypto-pk` Not a solution to this issue, but have a look at issue #49867 which contains patches to add mirage-crypto-pk. -pukkamustard > > Output: > > ``` > > Starting download of /tmp/guix-file.ZERar3 > Fro

bug#56799: (gnu services configuration) usage of *unspecified* is problematic

Hi Attila, [...] > i need to run now, and i'll be offline for a week or two. i can't look > the example in depth now, but my gut instinct says that it's a bug if > *unspecified* reaches any GExp machinery. I don't think it's reasonable to burden users with normalizing their G-exp input data, whe

bug#55113: [BUG] texlive-bin doesn't set $TEXMFCACHE properly

Sorry for the delay; I came down with the rona and was knocked out of commission for a while. Maxim Cournoyer writes: > Could you share your workload to demonstrate the problem (reproducer), > if it's not too complicated? texlive-bin sets GUIX_TEXMF; perhaps > TEXMFCACHE is derived from it in