<rekado>Tsutsukakushi: I don't remember, but it misbehaved for too long that I decided not to demo pinfo during the course. I cannot be more specific, I'm afraid. Could have been the particular version I used, or settings on the machine.
<vinben>Is the boot process for an installed GuixSD system documented? I have worked out how to change an installation config but not a running config.
<anonymiss>when the shebang is #!/usr/bin/env python2.7 and it produces the following error: bash: ./bitmessagemain.py: /usr/bin/env: bad interpreter: No such file or directory , is this related to python2.7 not in the guix-profile, or /usr/bin/env being problemativ to guix?
<mark_weaver>anonymiss: there's no /usr/bin/env in guix, and it would defeat the features of guix if it were relied upon.
<mark_weaver>we rewrite such shebangs to refer directly to /gnu/store/.../bin/python
<anonymiss>hm. I see. so much for just using pybitmessage from git checkout before I write a package.
<anonymiss>can you name a python package definition which does rewrite shebangs?
<mark_weaver>it's mostly handled automatically by the 'patch-source-shebangs' and 'patch-shebangs' phases, which are part of the 'gnu-build-system' by default. 'python-build-system' is derived from 'gnu-build-system' and inherits those phases.
<mark_weaver>every once in a while, the default phases fail to find them all and we need to do something else
<mark_weaver>in cases where the default phases fail to get them all, (guix build utils) includes a 'patch-shebang' procedure. (guix build utils) is available by default to all build code.
<anonymiss>I would like to do this now.. But I want to work on subtitles now, and the next 2 days I drive around the state because it's holidays, so I won't have time to apply this and also to test new patch additions for gnunet-gtk wip
<anonymiss>I don't know much about hydra, or the build process on it. But with late gentoo packages I wrote, I started to grab github hosted sources not by branches or snapshots, but by commits the snapshots were created from, to be sure that it actually is the package I wanted and not something somebody pushed my way. does hydra take care of something comparable too, or is grabbing things from git(s) to checkout and build not possible in the
<mark_weaver>it's okay, I'll just get another one used. they're pretty cheap
<mark_weaver>anonymiss: hydra just uses guix to build the packages, there's no special magic there that's not available to you. we prefer to use upstream tarball releases where available, but guix supports using VCS checkouts as well.
<jgay>marxistvegan, it is your own fault, you brought the joke a little too far when you locked davexunit out on the fire escape and jammed the ladder so he couldn't climb down ... he was stuck out there the entire night!
<jgay>maybe if you hadn't done that, davexunit would still be working with us :-P
<marxistvegan>jgay: would've been better if I left him in the 4 feet of snow on the roof last year
<fhmgufs>Maybe I should ask civodul (writer of the script) when he's back.
<jgay>marxistvegan, well we can always invite him over for lunch sometime in April, "hey davexunit, come check out this new solar array panel we installed, it uses gnu remotecontrol to control defroster so they run all winter!" ... that'll totally be enough to get him up there
<jgay>sorry I meant february ... geez, I hope not April :-)