<Gooberpatrol66>nckx i want to enclose the command, like: bash -c 'sleep 30 && wg-quick up config'
<nisa>Any other distro you can recommend that is 1. rolling release (at least somewhat, I tend to be in need of quite new package versions) 2. not arch 3. "good" for guix package manager 4. runs mainline linux kernel ?
<Gooberpatrol66>the double quotes get filtered out by the invoke function somehow
<daviid>vagrantc: right, and i won't work to make guile-gnome work using guile-3.0, rather invite those interested to use guile-gi or g-golf
<nckx>I don't think you're misunderstanding Scheme, I think you're misunderstanding bash. As I said, the exact same code pasted into bash causes the exact same ‘unexpected EOF’ error — Scheme was never involved.
<nckx>Ugh, ‘call a’ above should've been ‘call foo’. Sorry.
<nckx>But the point is that "'" in Scheme is just a single-character string and the string is an apostrophe. There is no magic. No exceptions to the rules.
<Gooberpatrol66>is scheme bound to bash on an abstract level? i was expecting it to just dump the contents of the double quotes into a command line.
<nckx>My way of thinking/explaining is clearly doing no good but confusing you further so I'll stop wasting your time. TL;DR you're overthinking or thinking invoke is somehow magic. It's not. It follows the same rules as any other Scheme code. (invoke "bash" "-c" "echo hello; echo 'how are you'; echo etc."). ☺
<atka>hey guix, rule of thumb when to use (cons vs (append for system configuration? I see them used interchangeably a lot between configs and examples. can someone recommend "best practices"?
***rekado_ is now known as rekado
<nckx>It's purely a matter of taste. ‘Append’ is considered more ‘general’ and ‘friendly’ or ‘familiar’ to new users by some. cons is a bit less flexible (adding a second list means refactoring) and old-school.
<barra>Okay, I may be missing something: I'm using emacs-next, but I can't seem to get emacs packages from guix to use the newer version of emacs. Can I do this, because I want to use EXWM on emacs 28.
<atka>nckx: thanks for the info, I suppose the same is true for indentation style? does the quix project have a style guide I can reference?
<barra>I'd reckon the GNU style is a good place to start, although I am pulling that one out of me arse
<barra>Simplified my question: How can I get Emacs packages from guix to use the Emacs-next package?
<nouun>Is there a way to automatically package required Rust dependencies when trying to package a Rust program?
<nouun>It seems rather inefficient manually packaging the several hundred recursive dependencies for something I'm trying to package.
<barra>whattaya mean! it's perfectly efficient to package thousands of dependencies
<atka>yeah, I need to figure out which variable is unbound, keeps failing
<nckx>I didn't mean to imply you were wrong, barra. I'm not even familiar enough with the GNU style to know. The most important distinction in Guix is to use a ‘functional style’, which isn't really related to spaces v. tabs (oh: use spaces, always spaces :). the_tubular: See ‘guix refresh -l openssl@VERSION’, because there are 2. That's why openssl fixes are grafted, so we don't have to rebuild >7000 packages. Bye bye for real now.
<jts>I'm trying to package an ocaml library and for some reason it is failing because it cannot copy files to the store during the install phase. Does anyone know if there's a work-around for this (using the gnu-make build system)?
<gnoo>it's probably trying to copy to /etc or somewhere else during install, see if you can patch the makefile to point to it's location in the store
<apteryx>One thing I'm ambiguous about is if a TODO in the maintenance repo is really the right place to track this kind of thing (why maintenance vs actual guix repo? who gets to add new entries to the list?)
<apteryx>other than that concern, it seems reasonable to me, so I'll commit it for now, and we can build upon that, thanks for the reminder
<apteryx>rekado: hi! I experimented a lot with iDRAC, enough to render the node 129 unbootable ^^'
<apteryx>but it seems it would boot even with the controller in RAID mode for this Btrfs RAID1c3 root file system (it doesn't because I forgot to adjust the swap field)
<WesterWest>Hi, I have a quick question, is there a way to access fields of some object?
<WesterWest>I have defined the `operating-system` as `(define name (operating-system (services ...))` and I want to access the services field and copy append something to it
<WesterWest>I know that I can use `(inherit name)` but that will only overwrite it, I want to get the value and append to it `(add-to-list (service ...) (name.services))` or something similiar (don't know the exact syntax. I need to know, if there's a way to do something like the `.` in that example, working like in C-like languages
<apteryx>rekado: guix deploy: error: failed to deploy hydra-guix-125: SSH connection to '126.96.36.199' failed: No route to host; is this known?
<apteryx>oh, but 125 is berlin, so I don't want to do this anyway :-|
<jpoiret>sneek, later tell WesterWest: each field of a record has a corresponding procedure to access the corresponding value, here it would be `operating-system-user-services` (you can look up the definition of the operating-system record in gnu/system.scm)
<jpoiret>"our computer's users may only interact with it by manually shorting transistors and reading the result with a voltmeter"
<barra>"our computer's users may only interact with the computer by manually evaluating their machine code using pen and paper and this 200,000,000 page specification dictating our massive instruction set, while the sysadmin gets to play solitare"
<lilyp>our computer's users may only interact with the computer through this simulation of Magic the Gathering
<barra>to interact with the computer of the free, thou must first answer my riddles three
<jpoiret>barra: spectre mitigation irl: "do *not* cheat on your neighbor!"
<barra>lilyp: i love that it's a *simulation* of mtc
<apteryx>it seems to be related to something the rpcbind-service-type does
<Guest1>I've been trying to install guix by downloading the .iso, using `dd` to put it on a USB drive and then booting into the drive. Everything goes fine until I get to the end of the graphical installer (after setting up users and choosing the target drive to install onto) - and then the installer just loops round back to the start (asking me for a
<Guest1>language for the installation). Does anyone have any suggestions how I should proceed?
<jpoiret>Guest1: did you get the latest or stable installer?
<Guest1>I don't have the faintest clue why it's not working. I've started again a few times (download the image again, dd again etc) - but I always get the same outcome.
<jpoiret>you're running into a bug someone else has reported previously, although only on IRC i think. i'm not sure it's fixed in the latest version, but it might be interesting to get something more detailed
<Guest1>Fab, thanks. I'll give that a go, see how I get on.
<jpoiret>are you familiar with gdb? if it's what i'm thinking of, the installer is segfaulting, probably because we're doing something nasty with the C parted library, and it would help to have a backtrace
<Guest1>Happy to try and get a backtrace, but I might need some help with how to do that. My gdb is very rusty.
<jpoiret>oh, mine as well, but it'll just be a simple backtrace
<jpoiret>the more annoying thing will be to find the guile executable to pass to gdb
<apteryx>I think the problem with rpcbind-service-type was that it's shepherd service was not bound at the top level; hence it could be folded into multiple objects, causing the error
<florhizome[m]>I‘m trying to package some go stuff but I get an error message that „some deprecated features are used“ and I should set „GUILE_WARN_DEPRECATED“ to detailed but doing that before the build phase does nothing.
<robin>hmm, if i start using core-updates, will i miss smaller commits that land in master?
*robin was just about to report the pam unix_chkpwd bug, which was fixed last month but only in core-updates
<robin>"This branch is not expected to be buildable or usable until late in its development process." ah, so i'm not really supposed to use it. guess i'll have to cherry-pick the patch or something (or wait a few months)
<robin>it could probably be made into a graft, actually
<apteryx>your last bet could be going with a manual install (it's not as bad as it seems)
<apteryx>it used to be the only way to install Guix System; simply follow the manual (available tty2; Alt-Control-F2 while installing)
<Guest1>I'm just reading through the install docs now. I'll give it a go. My worry is that I leave the system in an unusable state, and I have to revert to another blank slate OS without having any benefit.
<alethkit>Now to figure out how Guix deals with font paths without fontconfig
<apteryx>uh, "rpc.idmapd: -c is deprecated and may be removed in the future. See idmapd(8)"
<alethkit>Does guix have an equivalent of "/run/current-system/sw/share/X11/fonts" in Nix?
<alethkit>(I'm referring to Guix System, not Guix on a foreign distribution)
<alethkit>Although now that I think of it, the same problem might take place on foreign Guix
<jpoiret>alethkit: wdym? we do use fontconfig internally iiuc
<jpoiret>also we do have /run/current-system/profile/share/fonts
<alethkit>jpoiret: The terminal emulator I'm trying to package explicitly avoids using fontconfig and loads fonts directly
<alethkit>And I don't seem to have the fonts folder on my current profile, oddly enough.
<jpoiret>well, if you don't have anything graphical installed in your system proflie, then there won't be anything there I reckon
<jpoiret>while fontconfig is arguably a mess, it's still the standard way to find fonts on linux
<apteryx>haha, my earlier problem with "more than one target service of type 'shepherd-root'" ended up being caused by inheriting an OS and extending its service field with (cons (new-service ...) (operating-system-services base-os)); I had to use 'operating-system-user-services' instead.
<alethkit>jpoiret: I know, but the developer explicitly rejects the use of fontconfig
<alethkit>And I currently do have a window manager set up
<vagrantc>civodul: would require a change of workflow, probably ... e.g. build all the files in a temporary directory, and then generate an image out of that directory
<vagrantc>looks like guix is following an old debian packaging repository for genext2fs ...
<florhizome[m]>> <@florhizom:matrix.org> I‘m trying to package some go stuff but I get an error message that „some deprecated features are used“ and I should set „GUILE_WARN_DEPRECATED“ to detailed but doing that before the build phase does nothing.