<rekado>PurpleSym: the static pandoc is a bit hacky, but it’s necessary in order to dramatically cut the closure size for pandoc (and packages using it like rmarkdown).
<rekado>it uses package-closure to collect all transitive Haskell inputs
<rekado>that’s probably how it gets the wrong GHC somehow
<GNUtoo>hi, is it easy to build some go software locally in Guix?
<GNUtoo>I've a build failure with "guix build matterbridge --with-latest=matterbridge" and I don't really know how to fix it
<GNUtoo>ah scratch that, I meant with updating matterbridge to the lastest version within guix sources
<GNUtoo>The "guix build matterbridge --with-latest=matterbridge" somehow fails to download the tarball while the latter has a different error
<GNUtoo>I've some "go install [...] failed with stats 1, but not much clue about the cause
<GNUtoo>It says that though: "src/github.com/42wim/matterbridge/bridge/vk/vk.go:15:2: found import comments "github.com/SevereCloud/vksdk/v2/api" (account.go) and "github.com/SevereCloud/vksdk/api" (store.go) in /tmp/guix-build-matterbridge-1.22.3.drv-0/src/github.com/42wim/matterbridge/vendor/github.com/SevereCloud/vksdk/v2/api" but it doesn't tell if it's an error
<brettgilio>nckx what is the nick of the blake, the person who was looking for me yesterday?
<iskarian>GNUtoo, you may need to use an older version of Go
<PurpleSym>rekado_: “a bit hacky” is an understatement… I can build it now after filtering “ghc-next” as well, but the daemon reports: cycle detected in the references of `/gnu/store/a0wcf4bcw8xr24zwys0idah2gvbpprwj-pandoc-18.104.22.168' :/
<geex3>PotentialUser-35: looks like it uses "open --type luks" by default and u would need to copy and modify to --type luks2
<dissoc>is it possible to have sound working in a guix environment --container ?
<nckx>geex3, PotentialUser-35: Don't do that (yet)! You'll be on your own, at the very least, and it may well break boot.
<Kimapr[i]>hello, i'm trying to run some services in `guix environment` containers but i noticed that when killing the process (with `kill`'s default, SIGTERM), the processes inside the container continue running, which is not what i want. how do i make them terminate too?
<nckx>If you're aware of the risks (mainly to your free time :), you can convert LUKS1 to LUKS2 (and back) in-place as, long as it started life as 1.
<Kimapr[i]>looks like sending a SIGINT instead achieves the desired result
<efraim>unless you wanted (nix-system->gnu-triplet (%current-system))
<apapsch>hello, adherents of the Perfect Setup. I'm now trying to hook into geiser-guile mode to call geiser-mode-switch-to-repl-and-enter, but it feels like I'm missing something, as Geiser chapter 1.1 Modus operandi says "Every time you switch to a different file, you're switching namespaces automatically"
<apapsch>guix manual boasts about M-. (geiser-edit-symbol-at-point), but it doesn't work out of the box and the effort required to make it work seems quite counterintuitive
<attila_lendvai>so, while building, $out is pointing straight into a /gnu/store/somehash... directory, and the files are under the user:group of the builder. when the check phase runs, some files are unreadable for the app that i'm packaging (Idris2). i assume it's because they are chowned to root:root only in a later phase? but i don't see where. any hints how i can make sure everything in $out is readable?
<attila_lendvai>this may be because the files are installed by idris itself? when i ls -l the directory, permissions and user/group is all question marks
<attila_lendvai>hrm, or this is only an issue when i try to debug this after entering a --keep-failed state? and i'm looking at a different problem? but i cannot chown them, as the store is read only... any hints to look at?
<apapsch>attila_lendvai: ls -ln shows numeric uids
<attila_lendvai>apapsch, oh, i see now that the relevant directory doesn't have g+x on it
<apapsch>this is on guix system? Uids change when you reorder services in operating-system
<itd>Hi. Why does `guix system reconfigure` (re-)start some shepard services but not others? E.g., a change in `cuirass-configuration` does not restart cuirass, but the output mentions that `ntpd has been started`. Thanks.
<roptat>why do you think we're not? We're focused on core-updates right now, but that doesn't mean we can't use staging if it makes sense
<iskarian>Ah, so we are. It was last merged in february; I thought it was supposed to be a quicker-turnaround than core-updates
<GNUtoo>iskarian: btw, about matterbridge, I tried rm -rf vendor && go build on Parabola and it worked, so that looks promising, but I didn't find a way to partially remove one dependency from vendor/ and keep the other
<GNUtoo>As I could build github.com/SevereCloud/vksdk under Guix and that I still have issue after the substitute I was wondering if the way to go was to unvendor for that lib and step by step unvendor for more and more libs
<iskarian>it's a bit of a hack, but you could add a phase after 'setup-go-references which moves 'vendor' to a temporary location 'orig-vendor', then creates a directory union of 'orig-vendor' and $build-path/src in 'vendor'