guix package path

Hi, I need help to understand why my GUIX_PACKAGE_PATH env variable is not working as expected. AFAIU, the variable is correctly set (to my local package channel): ~$ guix describe Generation 75 Dec 18 2022 20:53:08(current) nonguix e95e2b5 repository URL: https://gitla

Re: texlive-bin: Error: I can't find the format file pdflatex.fmt

Hi jgart, After using LaTeX recently too, I think you don't need texlive-bin, but rather texlive-base. You can use the example in the manual to bootstrap. Best, -- Josselin Poiret

Re: cirrus (was Re: Release progress, week 10)

Ludovic Courtès writes: > "pelzflorian (Florian Pelz)" skribis: >> That hold-up aside, maybe could you also tentatively add the cirrus >> initrd module to the 1.4.0 installation image? I suppose it won’t break >> anything, but it might help with bugs like >> .

Re: Release progress, week 10

Hi! zimoun skribis: > On Thu, 15 Dec 2022 at 17:38, Ludovic Courtès wrote: > >> If everything goes well, I plan to publish the release on Monday, 19th. >> Time to get to your instrument for a release song or whatever other >> performance you feel like making! :-) > > It reminds me the announce

Re: cirrus (was Re: Release progress, week 10)

Hi, "pelzflorian (Florian Pelz)" skribis: > Ludovic Courtès writes: >> There are currently two installer bugs that I think now have a valid fix: >> >> https://issues.guix.gnu.org/60010 >> https://issues.guix.gnu.org/59784 > > Sadly those are still not completely fixed… Both should be fixed

re: Drafting a Guix blog post on the FHS container

Sorry for (presumably) breaking threading; I came across this online and don't see a way to set my in-reply-to-email header properly. Anyways just thought I'd mention that I recently learned about this feature, and was able to use it to get a downloaded [Tor Browser Bundle] running with: ``

Re: Proof of Concept: Import Emacs' use-packaged packages into Guix' manifest.scm

Am Sonntag, dem 18.12.2022 um 01:54 + schrieb Mekeor Melire: > Nevertheless, for me, personally, it's pretty neat and handy to > use, because I don't need to maintain the list of emacs-packages > in two places. I also think that it could come pretty handy for > many others, at least in order