<zacchae[m]>So, I tried making a minimal arm64 image (without syncthing), and it crashed saying that the most likely problem is that the disk ran out of space when it was building linux-libre. The disk in question is 32 GB so I doubt that. However, when I check it with fdisk, it says the two partitions are each <5GB. Is fdisk not reliable for a failed image write, or do I need to specify something in order for the entire disk to be used?
<sneek>Welcome back zacchae[m], you have 1 message!
<sneek>zacchae[m], iskarian says: I think efraim is also working on go cross-compilation :)
<zacchae[m]>iskarian: oh neat, though if I understand correctly, I should be able to install syncthing on the arm device so long as I make the image raw-efi and volitile
<GNUtoo>apteryx: thanks a lot, I'll try as soon as the current compilation finishes
*GNUtoo tried the unquote at another place before, like ,(%current-target-system) if I recall well
<vldn>what is the best way to submit version bumps with little adjustments to the package?
<muradm>bost: source tree of guix, as it was mentioned, if you did ever run "guix pull" in your vm, it is literally pulling the source tree of guix also
<muradm>so ~/.cache/guix/checkouts/....../ where dots is a long directory name, mine is ~/.cache/guix/checkouts/pjmkglp4t7znuugeurpurzikxq3tnlaywmisyr27shj7apsnalwq/
<bost>muradm: I meant the explanation in the manual is too vague.
<slyfox>does './pre-inst-env guix build --check my-package' do what you need?
<muradm>that is where you can find source tree of guix which used by "guix ...." commands by default
<bost>muradm: It'd be great to add there: "Run `find ~/.cache/guix/checkouts -name install.scm` to find the install.scm"
<muradm>slyfox: yeah, --check started building, thanks, let's see how it finishes
<GNUtoo>Nice, maybe the manual needs to be updated for adding --check
<muradm>bost: that file you need to find for you reference, normally your *.scm files should be prepared and managed by you i think, at least this is my understanding
*GNUtoo probably didn't pay enough attention when sending patches as he just checked if the 2 "builds" were the same, not what it did before
<muradm>once you get used to "look at guix source" that questions will be gone :)
<muradm>bost: i.e. just look in install.scm but have your own my-install.scm based on install.scm for instance, because if you will want to change/customize something, you won't be able to do it on ~/.cache/guix/checkouts/...
<muradm>also after "guix pull" whatever is under checkout may/will change without your control
<muradm>so once you used "gnu/system/install.scm" next time it might be different thing
<muradm>just keep in mind that every system you seed with guix, you need a scheme file for it under your control, since it is your system
<muradm>be it installation media, your laptop, cloud server or whatever
<muradm>that is how guix works, you declare your system in my-system1.scm and then ask guix to make it
<muradm>in some or another way depending on what is inside my-system1.scm
<vldn>mhh is there a possibility to add reallife examples to the docpages, or some additional info that is not bound to a function programmatically?
<apfel>hi there, ci.guix.gnu.org seems to be down, i know there is some mastadon status overview, but i cant find it right now. I just want to know what is going on and when it will be up again.
<muradm>also having issue with accessing ci.guix.gnu.org
<bost>muradm: Oh this is crazy. It doesn't work against a simple copy of the install.scm. `guix system image -t iso9660 install.scm` returns 'guix system: error: failed to load 'install.scm': No such file or directory'. It seems like the install.scm must be inside a git repository. E.g. `cd ~/.cache/guix/checkouts/<...>; guix system image -t iso9660 gnu/system/install.scm`
<podiki[m]>and it picks up things I've pulled, like when adding a package I needed in system
<iskarian>efraim, do you think it makes sense to keep the Go "tests" output? It includes toolchain tests, but it's not actually usable unless you create a directory union with "out" and "tests" and then set GOROOT to that union directory.
<Zambyte>Hi, I'm trying to set up cgit, but I'm not quite sure how I can "overload" values from %cgit-configuration-nginx, I'm pretty new to lisp in general :D This is what I have so far if anyone can help: https://dpaste.com/DE9AATBMJ
<iskarian>Zambyte, you can do (nginx-server-configuration (inherit %cgit-configuration-nginx) ...) where ... are the values you want to override
<Zambyte>Hm, this is what I get when I try to do that: guix system: error: Invalid value for field nginx: #<<nginx-server-configuration> listen: ("80" "443 ssl") server-name: ("git.mysite.tld") root: #<package email@example.com gnu/packages/version-control.scm:914 7f92f5de38c0> locations: (#<<nginx-location-configuration> uri: "@cgit" body: ("fastcgi_param SCRIPT_FILENAME $document_root/lib/cgit/cgit.cgi;" "fastcgi_param