IRC channel logs
2025-08-17.log
back to list of logs
<Kabouik>I'm trying to install Emacs packages in a new profile with a manifest on aarch64 but it fails because there is an issue with the test phase on Emacs currently (at least for aarch64, see #1831). I managed to build Emacs fine with a transformation to skip tests, and tried to replicate the transaltions in the manifest with the other packages (https://0x0.st/Krwr.txt) but it fails with the same error I was having before the transformation: <Kabouik>So I've got two questions: (1) is my way of adding the transformation in the manifest incorrect? Or alternatively, do I need to add the transformation to all Emacs-related packages? <Kabouik>The building of Emacs on this machine literally takes hours so iterating is really difficult, I've been at it for a couple days. <firefly707>hello, I'm running into an issue where a service I'm trying to make is failing to build and giving me an empty log file. Is this a known thing to happen? <firefly707>oof. is there a known way to fix this/common causes? <untrusem>firefly707: if you can share the file in which you are defining the service, maybe something is wrong there <firefly707>I'll try to get a minimal example, then send it. In the meantime, how do I send a file in irc? <firefly707>well, I think I managed to make a minimal reproducible version. It seems like using trivial-build-system for a package and not including a source does it? <firefly707>seems like the issue is when I try to use mkdir in a gexp with a hard-coded string as input <firefly707>also found a way to make the package try to recursively make itself. Fun stuff <firefly707>oh wait, that's not the minimal, it's a useless version that doesn't crash. oops. (use-modules (guix gexp) <ColdSideOfPillow>should I use @acronym{} only once for something, or do I need to use it for every instance? <ColdSideOfPillow>to be clear, I'm referring to the usage of GNU TexInfo, for descriptions. <identity>ColdSideOfPillow: you generally need to introduce an acronym only once <ColdSideOfPillow>identity: Should I do something like "@acronym{FOO, For Other Objects} is awesome! I love @acronym{FOO}!" or "@acronym{FOO, For Other Objects} is awesome! I love FOO!" <ColdSideOfPillow>From the TexInfo manual, I understood that it is recommended to do the former <identity>ColdSideOfPillow: the guix manual seems to be inconsistent with that, you probably want to do the first one <Rutherther>identity: what section is inconsistent specifically? <ColdSide`>also is there no way to `--force-with-lease` in AGit? <identity>Rutherther: for example the transmission-daemon-service section uses one-argument @acronym for all the acronyms, like ‘@acronym{RPC}’, while (most?) other sections just write acronyms without @acronym, like ‘RPC’ <Rutherther>ColdSide': I think not, but I don't think it matters as the author is the only one that can do changes, aren't they? <identity>some even write the meaning of the acronym in ()s, like ‘mail transfer agent (MTA)’ <Rutherther>identity: oh, right, I thought you were saying instructions in the manual are inconsistent with that, not the manual source, yeah, seems to be the case <csantosb>Hum ... we need new labels in Codeberg after the new teams landed, right ? Who takes care of that ? <ekaitz>csantosb: i think hako organized the previous set of rules <BunniesRCute>i have been trying to build the systemcrafters guix iso on my cachyos computer and it tries to compile the linux kernel and runs out of storage apparently and crashes. idk how it runs out of space because i made /tmp/ have 20G but idk if its trying to build it inside tmp, it may be trying to build inside /gnu/store/ which should be inside my root partition which is very big and not filled at <BunniesRCute>if i try to use the old iso, the ssl certs are incorrect <luca>What I do is set TMPDIR to some other folder (/var/guix-tmp) if I need to build something big <BunniesRCute>luca: just export the environment variable TMPDIR? and then run the build iso script? <luca>Set it in the environment of guix-daemon <BunniesRCute>can i just download the binary instead of building the kernel? idk how to do that because its all in the build iso script <luca>I don't know enough about cachyos to answer. I'd assume it's something with systemd like `systemctl edit guix-daemon`. And set it to _somewhere else_ that is not a tmpfs. I set it to /var/guix-tmp, you set it to wherever you want <BunniesRCute>luca: ooooooo!!!! tysm! ya ill try to download an iso from there instead of systemcrafters script! <Kabouik>I'm struggling with an Emacs + emacs-packages manifest on aarch4. I have to disable thhe test phase for emacs because it is broken on aarch64 right now, but every time I list an emacs-package in the same manifest, the same error occurs again. I tried disabling tests on them too but that didn't help. What is it I am missing? <ieure>Kabouik, emacs is an input to all the emacs-* packages, you need to use package-mapping to rewrite them to take your Emacs with tests disabled. <Kabouik>Thanks ieure. Is there some documentation on how to do that in a manifest somewhere? <ieure>Kabouik, Yes, it's in the Guix manual (guix)Writing Manifests. <ieure>Kabouik, It covers manifests with package variants. It doesn't cover package-mapping. <ieure>Kabouik, See `with-full-emacs' in (atomized packages emacs), that's the transform applied to all the Emacs packages. You want a function which provides your Emacs with tests disabled. <Kabouik>That seems to go far beyond my knowledge of Scheme, I'm struggling <Kabouik>That seems to go far beyond my knowledge of Scheme, I'm struggling <ieure>Kabouik, What part are you struggling with? <Kabouik>It's difficult for me to distinguish which parts would e relevant from my case here from those that are part of your home environment setup but unrelated to package mapping. As I can't clearly read basic Guile, it's hard to even have basic understanding of what is happening there. <Kabouik>As far as I understand, you have a custom Emacs package definition in atomized/packages/emacs and then import it <ieure>Kabouik, Not quite. `with-full-emacs' replaces the emacs in the package inputs with the full emacs (it's usually emacs-minimal). You want that transformation function, but to replace it with your Emacs which has tests disabled. <ieure>Kabouik, Then you need to apply that transformation function to all the packages in your manifest. The stuff in profiles.scm is close to what you need, but it works on a home-environment. <Kabouik>Well I can't even find the correct manifest, this one is bogus of course, it's the result of further tests but refers to a function that no longer is defined. Doing all that on a phone (the aarch64 machhine in question) while on the go doesn't help managing m files and trialgsf in a sane way. <gerogaga>Hello, how can I install a package I have defined via inheritance in my custom channel? Do I need to give it a separate name? It's specifically boost 1.88, but I can't install it via a simple guix install boost@1.88. <none>Hi everyone, the ISO file provided on the website seems very old (released 3 years ago). Can we still use it? Also, the latest images are just build outputs. Is there any signed version of the latest image available? <identity>none: you can definitely use the old ISO and just upgrade to latest <none>identity: thanks for the reply, let me try that. <untrusem>so it builds, but I think it pull from the git repo i have defined in .guix-channel what I want to use the local directory <Aurora_v_kosmose>Huh, hadn't realized that the way Guix has handled Java projects using insane build systems like maven & gradle is to just... ignore them and use/generate ant configs instead. <Aurora_v_kosmose>That does sound considerably less laborious than making some sort of sense out of them. <fractal>oh my, there's a maven build system but only one package uses it. java-jmh <Aurora_v_kosmose>Much of handling maven would be neutralizing the undesirable behavior it has.