Re: [PATCH cuirass] doc: Fix evaluation hook URL example.

Hi, vicvbcun writes: > * doc/cuirass.texi (Invocation): Fix URL in the example of the push hook. > --- > doc/cuirass.texi | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/doc/cuirass.texi b/doc/cuirass.texi > index 69c58f7..00f00c1 100644 > --- a/doc/cuirass.texi > +++ b

Re: Enabling contribution through documentation

One elephant was already spoken about. Your message points toward another: the Guile documentation. The Guile documentation needs significant editing. This is a problem because Guix is forever bound to Guile. For every benefit Guix gains from Guile, it also suffers by inheriting its shortcomi

Re: Golang mudules to follow common grouping

Hi, I'm about to create golang-check and golang-build modules, which both are core and would be in used by others. As Maxim mentioned, the most time consumption task would be migrating copyrights header properly. On Sun, 15 Oct 2023, 22:25 Wilko Meyer, wrote: > > Hi, > > Sharlatan Hellseher wr

Re: How to send revision patches to old issues in DEBBUGS so Guix QA can look at them?

Hi, Andy Tai writes: > Maxim, I know about this. Problem is Guix QA does not look at old issues OK; sorry for the noise. It's an improvement that is desired in in QA, I see. -- Thanks, Maxim

Re: performance issue with TeX Live

Hi Emmanuel, Emmanuel Beffara writes: > De Maxim Cournoyer le 16/10/2023 à 15:46: >> My next question would be; how is this ls-R file produced in Guix? > > That I do not know, but I would assume mktexlsr is called at some point when > building the profile. > >> Does it matches the expectations o

Re: How to send revision patches to old issues in DEBBUGS so Guix QA can look at them?

Maxim, I know about this. Problem is Guix QA does not look at old issues On Mon, Oct 16, 2023 at 8:36 AM Maxim Cournoyer wrote: > > Hi Andy, > > Andy Tai writes: > > > Hi, per Chris's recent comments, Guix QA only looks at (a window of) > > recently created issues due to storage space limitatio

Re: [RFC]: Skipping rust crate tests by default

Hi Efraim, Efraim Flashner writes: > Currently for for rust crates we build the crates, run the tests, and > then in %output we only have the license files and a repackaged version > of the source. > > The build system goes: > unpack source > unpack crates > patch shebangs > patch checksums of t

Re: How to send revision patches to old issues in DEBBUGS so Guix QA can look at them?

Hi Andy, Andy Tai writes: > Hi, per Chris's recent comments, Guix QA only looks at (a window of) > recently created issues due to storage space limitations, which is > understandable. > > However, if I have update (package definition) patches to not very > recent issues, such as some stale issue

Re: performance issue with TeX Live

De Maxim Cournoyer le 16/10/2023 à 15:46: > My next question would be; how is this ls-R file produced in Guix? That I do not know, but I would assume mktexlsr is called at some point when building the profile. > Does it matches the expectations of upstream for producing such file? I don't know a

Re: performance issue with TeX Live

Hi, Emmanuel Beffara writes: > Hello, > > De Maxim Cournoyer le 14/10/2023 à 18:06: >> > I tried to explore this but I see no reason why the ls-R files would be >> > ignored and I don't know how to explore this further. I do want to >> > contribute >> > to a solution, because right now texlive

Re: performance issue with TeX Live

Hello, De Maxim Cournoyer le 14/10/2023 à 18:06: > > I tried to explore this but I see no reason why the ls-R files would be > > ignored and I don't know how to explore this further. I do want to > > contribute > > to a solution, because right now texlive is practically unusable in Guix. > > Hav