IRC channel logs


back to list of logs

<civodul>rekado: nice lyrics that you have here!
<civodul>vagrantc: the hack that was used to copy the kernel and initrd is at
<apteryx>rekado: cool lyrics!
***Xenguy_ is now known as Xenguy
<alethkit>jpoiret: Turns out the error was a missing channel for a module imported in the service file, but the error message gave no indication of that until I copied the definition over
<alethkit>So I guess the error UX could do with some work
***user3456_ is now known as user3456
<atka>hello, is there a way to autoformat a .scm file in vanilla emacs, indentation and such? I think nckx mentioned something when I asked about a guix/guile style guide a couple weeks back.
<sneek>atka, you have 1 message!
<sneek>atka, vagrantc says: some SBCs are very roughly supported in guix ... there's no list that I know of
<atka>vagrantc: thanks, I was watching "GNU Guix as an alternative to the Yocto Project" from fosdem 2020, and Mathieu Othacehe said something along the lines of 15 boards supported and I was curious as to what they might be. pine a64 lts was the example in the talk.
<atka>and I guess what does "supported" mean as well
<vagrantc>yes, the degree of support varies quite a bit
<vagrantc>but i really should watch that talk!
<vagrantc>in the middle of trying to upgrade u-boot and ... updating some old systems
<vagrantc>i can find it well enough, just a matter of setting aside the time ... long backlog of talks :)
<atka>ok, np, relatively short, 25 minutes
<vagrantc>i was running guix on the pinebook pro for a while, though only on usb-dongle ethernet/wifi
<vagrantc>working on rockpro64 and rock64 at the moment ... also had older pinebook working too
<vagrantc>many of the pine64 boards work ok-ish if you don't mind missing some features
<atka>oh that's good to know, I don't mind missing out on bt/wifi
<vagrantc>i've at least once in the past 4 years tested booting on most of the boards that have u-boot packages in guix
<vagrantc>the armhf port is languishing though... arm64 is getting there.
<vagrantc>er, aarch64, sorry. :)
<kitty1>vagrantc: Guix or Guix System? very curious how much its working on a pinebook pro now ; its kinda a shame the pinebooks arent designed more around libre distros lmao
<kitty1>and their phones, it would be super cool for mobile guix someday :P
<anadon>Evening all.  More packaging questions.
<anadon>So, I have my changes in a branch off of master, added a version and moved both to have some versioning information in repo.  However, the version that the daemon keeps referring to, and thus every it is ignoring my changes in favor of what it remembers from the install/master.  `./pre-install-env` doesn't appear to be doing what I would expect
<anadon>it to do here according to the manual.  What am I missing?
***iyzsong-www is now known as iyzsong-w
<anadon>I'm a doofus.  `make`.
<philofosser>Hey, y'all, does anyone know of a substitute server which has guile-emacs?
<philofosser>Going to make that switch now that I'm getting more into guile, but the source build is failing, and I figured I'd check before I start troubleshooting in earnest.
<drakonis>its not exactly in a highly usable state though
<drakonis>and i think it is based on a rather old version of emacs
<philofosser>My understanding is that the majority of the issues were with interoperating the scheme and elisp datatypes.
<philofosser>Are there other issues?
<drakonis>threading and such
<drakonis>also its guile as in guile the vm beneath guile scheme
<philofosser>Well that is the reason why I wanted to get into it.
<drakonis>i think it is based on emacs 24?
<philofosser>Thanks for the heads up.
<philofosser>Any other hot tips to keep in mind?
<drakonis>hmm, its an emacs version from 2014
<drakonis>but please do check that post
<philofosser>Giving it a read now.
<vagrantc>kitty1: i was running guix system on the pinebook pro for a while ...
<kitty1>ayy niice
<kitty1>what are the features that would be missing? how hard is it to get it to like it?
<vagrantc>it's a bit limited because anything that requires rust (most web browsers) basically isn't available on aarch64
<vagrantc>i never tried wifi, but with a usb ethernet dongle it worked fine ... the pinebook pro usb-c dock worked fine
<kitty1>as in rust the programming language or a dependency named rust? I didn't know rust was used that much in web browsers already if thats the case huh
<vagrantc>which has ethernet
<kitty1>ngl, as long as it can run EWW or W3M im fine, I only use web browsers for like, wikipedia ngl
<vagrantc>yeah, rust the programming language
<vagrantc>sometimes substitutes are hard to come by (e.g. notably linux-libre) and it can take a long time to build locally
<kitty1>ah yeah, I imagine it would take a long time to build on one of those haha
<vagrantc>e.g. right now linux-libre 5.17.1 isn't available as a substitute, but the slightly older 5.17 is
<vagrantc>i'm running another OS on it right now, though as guix is a bit rough for me as a primary OS
<vagrantc>but NVMe was working, so it at least had reasonble disk speeds
<vagrantc>used sway as a GUI environment; didn't bother with a login manager or whatever
<anadon>I was to have a package have multiple versions, and to have a base name which references the latest version by default like gcc does.  How do I do that?  I'm adding utfcpp v3, and currently there is v2 which has the name `utfcpp`.
<anadon>~I'm dumb~
<apteryx>has the revised texlive imported landed? the example in the manual doesn't work: guix import texlive fontspec
<apteryx>must be wip-texlive-importer
<apteryx>nope. that's next to nothing from 2019
<apteryx>oh, apologies, there's a parser for the tldp file, which is interesting
<atka>hi guix, how does one find out which module defines which package?
<kitty1>uhhh I think guix edit {package} is a way? I personally just use the emacs-guix package for that haha
<atka>I'll have to try that, still getting used to emacs so I don't have any extensions yet
<kitty1>ah yeah thats valid, GNU emacs by default kinda sucks but once you figure out configuring it and what are good packages or not it gets really good uwu; havent tried other emacs distros so cant comment on them
<atka>guix edit works well btw, thanks
<atka>yeah I'm going from anti-gnu to full-gnu :)
<atka>vim/musl to guix/emacs
<kitty1>uwu nice that its working for you
<kitty1>yeah vim has the massive benefit that its defaults are good, but having a lisp interpreter is very interesting and nice; I just wish it was using scheme instead of elisp and had a bit of a more welcoming community like guix does to help get over that initial barrier haha
<atka>well isn't there a guile emacs in the works?
<kitty1>I think I've heard about that? hope its still getting progress
<atka>I think there was some chatter about its current state earlier in the day if you care to check the logs
<kitty1>oh? might have to find that
***alMalsamo is now known as littlebobeep
<the_tubular>Hey atka :)
<atka>hello hello
<atka>how's it going?
<the_tubular>Here's a dumber way, search your package using :
<the_tubular>Click on it and there's a link to it's module
<the_tubular>Pretty good, what about you ?
<atka>had a pretty miserable week but back in the land of the living
<atka>thanks for the tip, works well
<the_tubular>Yeah, I've been slacking off the last few days :/
<rekado>apteryx: you need the subversion package for the importer to do anything
<rekado>the pyyaml branch was built mostly successfully on
<rekado>so quick!
<littlebobeep>Is there any reason a lot of the C binaries from GNU project have been rewritten in Scheme, but guix-daemon is still C++ binary (or am I missing something?)
<iyzsong-w>i'd like to, but haven't found time and courage to do it (rewrite guix-daemon in guile)...
<littlebobeep>iyzsong-w: Yeah that sounds like me
<iyzsong-w>we're not alone :)
<civodul>Hello Guix!
<civodul>a good writeup by roptat & co. on bootstrapping OCaml:
<civodul>featuring the camlboot implementation in Guile! \o/
<iyzsong-w>look very interesting, thx!
<unmatched-paren>atka: wasn't the guile emacs a temporary GSoC project that's basically abandoned now? that's what i heard...
<unmatched-paren>this is the guile emacs repo last commit is in 2015...
<abrenon>hello guix
<abrenon>why not: "o)" ? ^^
<rekado>unmatched-paren: guile emacs is part guile, part emacs. You won’t find it all in the emacs repo. It has also been rebased a couple of times.
<rekado>here’s a more recent version: and
<unmatched-paren>rekado: ah, okay. that was the repo linked in the emacs wiki.
<unmatched-paren>intriguin! it might even tempt me to go back to emacs :)
<littlebobeep>unmatched-paren: Have you looked at Edwin in MIT/GNU Scheme package?
*unmatched-paren guix shell edwin
<unmatched-paren>sorry, not guix shell edwin
*unmatched-paren guix shell mit-scheme
<unmatched-paren>bash: edwin: command not found
<unmatched-paren>btw, is there a way i can make guix shell use fish instead of bash?
<etopal>Isn't it just your user's shell to change?
<unmatched-paren>i'm worried that if i change it for my user it'll mess up guix
<unmatched-paren>i was told that you shouldn't change it from bash
<unmatched-paren>since then you can't source some important setup scripts
<unmatched-paren>i use fish by making it the default shell in the terminal emulator, but of course that doesn't work for guix shell
<etopal>aren't the scripts using the bash shebang?
<etopal>well, I've yet to change my own shell
<unmatched-paren>well, they're sourced, not run (afaik); pretty sure you can't source bash scripts from fish
<littlebobeep>unmatched-paren: does this work: mit-scheme --edit
<etopal>unmatched-paren "." and "source" aren't the same, right?
<unmatched-paren>they are the same
<unmatched-paren>except . is POSIX, source is a GNU extension
***iyzsong-www is now known as iyzsong-w
<tschilptschilp23>abrenon: I guess it's waving instead of smiling ;) hello!
<abrenon>yep, it is waving alright, but I thought a ')' could be an arm just as much as a '/' can, and I thought it would be funny for our unbalanced friend
<unmatched-paren>oh, ha, i get it now! i didn't realize that you were making a reference to my nickname :P
<unmatched-paren>not sure how i didn't catch that
<abrenon>but now, tschilptschilp23's comment make me realize that pretty much all smileys contain unmatched parentheses ^^
*unmatched-paren now really wants to make an emoticon esolang for some reason...
*abrenon will stick to japanese-style emoji (^▽^)
<unmatched-paren> !!!
<unmatched-paren>it exists!
<abrenon>ahahha that's wonderful ^^
<AIM[m]>Do I need to co fig sfuff for zsh?
<AIM[m]>Like do I install it and eveything works fine outta box?
<unmatched-paren>AIM[m]: you should probably use `guix home` for shell configuration, but yes, it should work ootb
<unmatched-paren>(the guix home services for shells usually set up some guix-related things)
<cehteh>^^ reminds me that i want to implement an alternative packed binary encoding better than base64: emoji256 encode things like 👍💩🤮😂
<cehteh>maybe next year 1.4. :D
<AIM[m]>unmatched-paren: Oh yeah, I did read on it
<AIM[m]>Unfortunately my guix home ain't working for some reason
<AIM[m]>I did copy the example config at the end and even that didn't work idky
<unmatched-paren>hm, are you using guix system?
<unmatched-paren>i've heard that some people are having trouble getting it to work on foreign distros
<AIM[m]><unmatched-paren> "hm, are you using guix system?" <- Yep
<AIM[m]>I run guix sd
<unmatched-paren>ok... did you run `guix home import ~/.guix-profile` and then `guix home reconfigure ~/.config/guix/home-configuration.scm`? pretty sure that's how you get it set up
<AIM[m]>I did the container one
<AIM[m]>guix home container /pathtoschemefile
<unmatched-paren>well, `guix home reconfigure` should in this case be safe
<unmatched-paren>oh, btw
<unmatched-paren>i needed to add `export PATH=$PATH:$HOME/.guix-home/bin` to my .bash_profile; for some reason it didn't do that automatically
<AIM[m]>read only filesystem error for guix home import command
<unmatched-paren>`guix home import` generates a `guix home` file that exactly corresponds to your profile
<unmatched-paren>it's `guix home import ~/.config/guix`, sorry
<AIM[m]>Where dya keep the scheme file btw
<AIM[m]>Like in home dir???
<AIM[m]>the scheme file for guix home*
<unmatched-paren>the scheme file gets generated in the directory you give it
<unmatched-paren>so `guix home import DIR` generates `DIR/home-configuration.scm`
<AIM[m]>Lemme try
<unmatched-paren>and that home-configuration should contain all your packages
<AIM[m]>Now it works
<AIM[m]>Atleast import did
<unmatched-paren>now, you'll probably need to add that PATH thing to your bash_profile
<unmatched-paren>and log out, then log back in
<unmatched-paren>(after home reconfiguring)
<AIM[m]>Path thing?
<unmatched-paren>export PATH=$PATH:$HOME/.guix-home/bin
<unmatched-paren>and maybe also `export PATH=$PATH:$HOME/.guix-home/sbin`
<unmatched-paren>once you've done that and logged out, try `guix remove`ing one of your packages
<unmatched-paren>it should still be accessible, just in your .guix-home instead of .guix-profile
<unmatched-paren>i've completely replaced my .guix-profile with .guix-home
<civodul>i sent a v2 regarding manifest exports:
<civodul>so instead of "guix manifest", it's now "guix shell --export-manifest"
<unmatched-paren>civodul: will this allow us to export our .guix-profile into a manifest?
<jpoiret>unmatched-paren: shouldn't it be something like `. ~/.guix-home/profile/etc/profile` or something similar?
<unmatched-paren>oh, yeah
<unmatched-paren>AIM[m]: sorry, it's actually `export PATH=$HOME/.guix-home/profile/bin`
<jpoiret>no, i mean, shouldn't you rather source the profile activation script instead of trying to replicate it?
*tschilptschilp23 needs to learn more about emojis
<jpoiret>otherwise you're gonna be missing a lot of env variables
<unmatched-paren>okay, sorry AIM[m], you should do what jpoiret said
<unmatched-paren>sneek: later tell jgart: first package merged from paren to guixrus!
<unmatched-paren>sneek: botsnack
***dgcampea-2 is now known as dgcampea
<mekeor[m]>hi guix! let me answer your questions! :D
<allana>Hi guix! quick question (I hope) -- if I have a project guix.scm and I pass that around to other users, say to continuous integration machine running a version of guix that is many versions behind, is there a common way to specify the version/inferior of guix that I am using within (or alongside) my guix.scm?
<jpoiret>you'd be able to do that using inferiors, yes :), otherwise you can provide a channels.scm file alongside it and do `guix time-machine -C channels.scm -- guix shell`
<jpoiret>ehrm sorry, `guix time-machine -C channels.scm -- shell`
<AIM[m]><unmatched-paren> "AIM: sorry, it's actually `..." <- Wait, it won't automatically add it?
<AIM[m]><jpoiret> "no, i mean, shouldn't you rather..." <- Where is it?
<jpoiret>i don't use guix home so i'm not sure about the specifics, but if it's anything like guix system then ~/.guix-home should contain a profile somewhere, and then it's /etc/profile in there
<AIM[m]>Just source it then?
<AIM[m]>Should I add it to .bash_profile
<allana>jpoiret: thanks!
<AIM[m]>Then again do the home-config generation?
<jpoiret>well, ideally you should even do `GUIX_PROFILE=~/.guix-home/..../profile; . $GUIX_PROFILE/etc/profile; unset GUIX_PROFILE`
<unmatched-paren>no, reconfiguring after that isn't necessary
<unmatched-paren>the correct location is `~/.guix-home/profile/etc/profile` on my machine
<jpoiret>that way the env variables will be cleaner (ie contain ~/.guix-home/.../profile instead of /gnu/store/xxxxxx-profile/)
<unmatched-paren>so just source that
<jpoiret>that also means that when reconfiguring, you often will not even need to logout->login since the env vars will still be good (compared to the absolute paths to a specific generation)
<allana>jpoiret: about inferiors in a guix.scm for a software package, do you know of any examples in the wild? I would love to have a look.
<jpoiret>unfortunately not
<allana>okay thanks :-)
<AIM[m]>So how is guix-home different from guix-profile
<AIM[m]>Is it like guix-profile but with home configs in it?
<jpoiret>well, they're 100% separate
<jpoiret>the profile that your home config generates will be there
<unmatched-paren>.guix-profile is where all your `guix package ...` packages will be
<unmatched-paren>so when you call `guix install` you get a new package in `.guix-profile/`
<AIM[m]>So all `guix install` stuff should go into guix-profile itself?
<unmatched-paren>guix home is superior to a simple manifest because it allows you to declare services as well as packages
<unmatched-paren>one of the services is `home-files-service-type`, which allows you to cram all your dotfiles in your home configuration
<unmatched-paren>AIM[m]: exactly
<unmatched-paren>currently, there are very few home services (you can see them using `guix home search`) but it's quite easy to add more
<unmatched-paren>home services can be used in place of system services when the service doesn't require root access
<tschilptschilp23>does anyone know, why this happens? As an explanation, I'm just trying to integrate manifests into my setup -- one benefical thing for how I work would be to use them as a ~guix weather~ safety-net, before I reconfigure. But if I avoid using a file for that, but rather a sed-extraction of the relevant parts, I get informed about 'unknown packages'. What's happening there?
<GNUverkty[m]>Hello, I think the package zrythm is broken on latest guix.
<jpoiret>looks like you forgot to cut the end of the line
<jpoiret>it's searching for `"libusb"))`
<AIM[m]>So do I keep the source profile thing inside home-configure.scm
<jpoiret>GNUverkty[m]: how are you trying to use it?
<jpoiret>eg. how did you install it
<jpoiret>AIM[m]: you can (and should!)
<GNUverkty[m]>jpoiret: It was installed as part of my guix home configuration.
<AIM[m]>source ~/.guix-home/profile/etc/profile
<jpoiret>ideally, all of your config files (.bashrc included) should be specified by home-configure.scm
<unmatched-paren>you can control your bash_profile from home-configuration.scm
<tschilptschilp23>jpoiret: thanks, piping to file does this for me automatically?
<jpoiret>GNUverkty[m]: is GDK_PIXBUF_MODULE_FILE set?
<jpoiret>are you properly sourcing the guix-home profile's /etc/profile?
<GNUverkty[m]>jpoiret: No, GDK_PIXBUF_MODULE_FILE is not set but other applications work just fine.
<GNUverkty[m]>I also sourced ~/.guix-home/profile/etc/profile just to be sure and I got the same result.
<AIM[m]>GNUverkty[m]: Okay so now I'll first have to reconfigure home it then source it
<allana>Any guile experts here than can help me debug a problem? Might need to share a paste. But basically, I have a working guix.scm, and I am trying to use inferiors so that I can "pin" versions used by my project's guix.scm. I get what seems to be a mysterious error: error: mlet: unbound variable -- followed by a "hint: Did you forget `(use-modules (guix monads))'?"
<allana>First thing was just to add a use-module directive to see if it worked... it did not, and it repeated the same error
<allana>Also there is no "mlet" in my guix.scm
<jpoiret>GNUverkty[m]: that env variable not being set seems to be the cause. Is it not set by the file you mentioned?
<jpoiret>allana: i think you'll need to share a paste, yes :) along with the full error backtrace
<AIM[m]>warning: cannot determine provenance for current system
<GNUverkty[m]>jpoiret: Nope, it's not setting it in the profile.
<jpoiret>that's weird. Let me check why
<GNUverkty[m]>I can try setting a temporary value to see if that fixes the problem. Any idea what it should be?
<jpoiret>i suspect that that env variable is treated specifically
<rekado>AIM[m]: I reconfigured guix home for the first time yesterday and got the same message.
<rekado>does guix home support the definition of separate profiles?
<rekado>I’d like my emacs profile to be managed with guix home as well
<GNUverkty[m]>AIM[m]: I have gotten this warning before, it is harmless.
<jpoiret>GNUverkty[m]: you could try GDK_PIXBUF_MODULE_FILE=~/.guix-home/profile/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache
<AIM[m]>GNUverkty[m]: Thank you
<AIM[m]>Thank you unmatched-paren: jpoiret: as well
<GNUverkty[m]>jpoiret: Looks like that fixed it, but now it says I need to install breeze-icons.
<GNUverkty[m]>Why isn't this variable set in the first place?
*attila_lendvai has just filed an extension to match-record:
<jpoiret>GNUverkty[m]: i'm investigating that
<GNUverkty[m]>rekado: What exactly do you mean by 'different profiles'?
<tschilptschilp23>allana: the use-module directive should go to the most upper part, where the ~#:use-modules [...]~ are
<allana>tschilptschilp23: Thanks for the response! which use-module are you referring to? I did try to add guix monads, but that didn't lead to an outcome
<tschilptschilp23>I cannot see it in your paste though!
<allana>My assumption is that the hint was just wrong :-/
<tschilptschilp23>something like ~#:use-module (guix monads)~
<jpoiret>by the way, there's a %guix-channel variable (i think that's its name) in (guix channels) that you can inherit
<GNUverkty[m]>jpoiret: Looks like zrythm is working without problems after setting the variable and installing breeze-icons.
<allana>The idea is that I want to pass this guix scm (along with some other source files) to a CI system that is running an old version of guix and have it build from whatever version of guix that I have blessed
<tschilptschilp23>allana: OK, then I better shut up ;)
<jpoiret>i think using time-machine will be better in general, inferiors are used when you want to mix-and-match versions
<jpoiret>but there seems to be a bug here
<allana>tschilptschilp23: No worries, I am such a beginner, your advice was completely appropriate. Thanks
<GNUverkty[m]>Ok, zrythm is not working fine at all. I'm getting bombarded with non-fatal errors.
<tschilptschilp23>allana: it's just that it happens to be confusing to me having to specify the modules in a config, while things like ~guix install PACKAGE~ just don't really care about this. But I do not have a single clue about CI! Happy though, if my scheme-jabbering can help every now and then
<jpoiret>GNUverkty[m]: looks like gdk-pixbuf would need to be propagated
<jpoiret>what a nightmare
<jpoiret>it's entirely possible that many packages forget to propagate gdk-pixbuf because 95% of users already have it propagated in their profile for some other reason
<allana>jpoiret: first time using guix time-machine, and it fits my use case. Should I file a bug about my issue though?
<jpoiret>are you trying to use an old guix?
<jpoiret>allana ☝️
<jpoiret>it's possible that the issue comes from the inferior itself, rather than your code
<apteryx>rekado: is there anything I can do to help with the PXE infra effort?
<apteryx>PXE boot*
<AIM[m]>Is configuring ~/.profile same as ~/.bash_profile ?
<jpoiret>there's a difference between the two, but i don't remember the specifics. You should check bash's man page
<AIM[m]>How do I config bash_profile in guix home
<AIM[m]>I can't edit the already existing one for some reason
<AIM[m]>The ~/.bash_profile can't be edited. It says read only file.
<jpoiret>everything that's generated by guix home is read-only (because it resides in the store)
<jpoiret>just like for system generations
<rekado>apteryx: I’ll ask my colleagues about how to upload an image to the PXE server
<jpoiret>your guix-home.scm file is the unique source of truth for those files
<rekado>once that’s done I guess we just need to see if it works at all
<rekado>if it works all that’s needed is to change the boot order so that network booting comes before the disks
<AIM[m]>So how do I add `source ~/.guix-home/profile/etc/profile` to the guix home config bash_profile
<AIM[m]>I did the reconfig home stuff and now Idk how to add the source thing....
<AIM[m]>I need to add it right? To make the guix home work?
<AIM[m]>It's like I did reconfigure with whatever I had in the generated thing, now I'm afraid to logout. Idk it might break stuff?
<jpoiret>i think you'll need to read to get a better idea of how guix home works
<jpoiret>as well as
<AIM[m]>The thing is that it already has a list of files
<AIM[m]>In bash profile
<AIM[m]> (list (local-file
<AIM[m]> "/home/aim/.config/guix/.bash_profile"
<AIM[m]> "bash_profile")))
<AIM[m]>am I supposed to remove them?
<AIM[m]>What does the files do?
<civodul>AIM[m]: what that means is that Guix Home takes the contents of "/home/aim/.config/guix/.bash_profile" and concatenates them with its own bit, leading to ~/.bash_profile when "guix home reconfigure" completes
<AIM[m]>I thought it'd automatically add the source stuff then
<AIM[m]><AIM[m]> "So how do I add `source ~/.guix..." <- Like this source stuff
<allana>jpoiret: Sorry, was away and didn't mark myself as away. I am actually trying to use guix time-machine to access the future! I have a custom continuous integration system and it runs an old version of guix. It's also ephemeral, meaning that it's frozen at an earlier version of guix for each invocation.
<jpoiret>how old is that guix version?
<allana>Not sure. It's actually whatever is packaged with ubuntu 21.04
<allana>But in my case, I just want to make sure my package variant builds. It requires a new-ish package called "libxcrypt".
<AIM[m]>Do I actually need to do this thing?
<AIM[m]>source ~/.guix-home/profile/etc/profile
<AIM[m]>No automation for this?
<jpoiret>seems that it's 1.2.0-4, so maybe the inferior code from back then has some issues
<allana>jpoiret: I was testing it on my workstation, which has the newest guix :-/
<jpoiret>ah. weird then
<jpoiret>if you can find the time for a bug report then, feel free. i don't see anything immediately wrong with it, but i've never used inferiors myself
<attila_lendvai>there's no npm importer yet, right? and thusly, packaging nodejs stuff is a real pain...
<allana>jpoiret: thanks! I plan to file a bug report when I get the chance, which may take a day or two :-)
<singpolyma>attila_lendvai: i have a script that I use, but it's not an importer for sure
<singpolyma>There's not a standard format for npm sources, so full automation is tricky
<attila_lendvai>singpolyma, do you think i could make it work locally with a reasonable amount of effort? if so, can you please send a link to it?
<singpolyma>It's not amazing, but my speed with it is much more than it was with just copy paste I find
<attila_lendvai>singpolyma, thanks! i'll try
<singpolyma>What package are you targeting right now?
<attila_lendvai>ultimately but it seems to be a nasy web of dependencies...
<singpolyma>Make sure you peek in guixrus for any deps not in guix. I have several hundred npm packages there maybe there's some small overlap
<attila_lendvai>singpolyma, oooh, thanks! i'm sure there'll be an overlap
<singpolyma>attila_lendvai: if you don't want to package babel you can probably get away with using esbuild and an es6 target. node in guix can run that no problem
<singpolyma>That'll cut all the babel and probably webpack deps
<attila_lendvai>singpolyma, that's chineese to me, but i'm taking notes
<singpolyma>I have typescript but an old version. If the tsconfig isn't too crazy you can use esbuild for that too
<singpolyma>Look in guixrus for examples of swapping in esbuild feel free to ask me about any of them I wrote most of those packages
<attila_lendvai>singpolyma, for now i have managed to put together a simple guix.scm file, and i can build it in `guix shell`, i.e. using npm to fetch the dependencies
<attila_lendvai>singpolyma, will do, thank you!
<singpolyma>esbuild is a tool that can replace 70% of webpack, babel, rollup, typescript, and similar tools. Sometimes it manages to be the 70% you need and it saves packaging all those
<singpolyma>I mean, I'd love to package babel, but it's a lot if all I want is grunt for example
<mhj[m]>Good day Guix. Have y'all heard of distrobox? It's like a container rootless overlay solution like Fedora's toolbox for Fedora Silverblue. So for instance, say you have binary in some directory like SMT dot sh, and it plays a game for you or something. In normal guix obviously you couldn't run it because it expects a standard filesystem, but with the overlay, and after entering the distrobox container environment, you could run it like normal. It's
<mhj[m]>not packaged for Guix, but for NixOS, but the only way to get it to run in NixOS is if you're on the unstable channel and enable rootless Docker. WIth Guix, I enabled the Nix service, installed Distrobox, I had mount root rshared and from then I could use distrobox as normal. I think it'd be a great addition to Guix and it's licensed GPLv3.
<jpoiret>great! one more container system!
<rekado>apteryx: I have no idea what I’m doing. We’re now using cobbler and it needs me to define a whole bunch of things instead of just letting me upload the installer image.
<rekado>I hope I did that right.
<rekado>but I doubt it
<rekado>you can try rebooting the server and see if you get a menu to select a distro
<rekado>there should be an entry for Guix_System_1.3.0
<apteryx>OK! thank you!
<vldn>hi :)
<vldn>libvirtd could not be started?
<vldn>some one has the same problem? or am i missing sth
<AIM[m]>Do I need to install zsh using packages or will it auto install it when I specify it as default shell?
<AIM[m]>In thr config.scm file
<wdkrnls>Dear guix, how do you go about deleting profiles?
<wdkrnls>I couldn't find any reference to such an operation in `guix package`.
<wdkrnls>I tried to just `rm -rf` but it told me the files were read only.
<civodul>wdkrnls: you can delete old generations of profiles with 'guix package -d XYZ' or 'guix gc -d XYZ'
<civodul>the actual profile can be removed with 'rm'
<sneek>wb vagrantc
<civodul>cbaines: hi! just noticed that bordeaux.guix recompresses tarballs, as in:
***the-porcupirate is now known as porcupirate
<wdkrnls>civodul: thanks, after reading what you wrote I did notice that profiles in my home directory were links to another link which pointed to the store. So then I deleted those two links and then removed the profile object from the store with guix gc.
***Server sets mode: +Ccntz
<xigua>apteryx: I don't think so I just installed something like 30 seconds ago
<xigua>Oh my bad, like 20 minutes late, I read 38 as 58
<anadon>Can I get a bump on #54630?
***civodul` is now known as civodul
<atuin>I added an inferior in a operative-system definition and now i can not use guix at all
<atuin>it just keeps forking the guix command in some kind of loop
<atuin>a simple guix pull keeps creating guix childs
<atuin>infinite connections to the guix daemon
<user_oreloznog>ouf! :/
<atuin>any idea how to solve that issue?
<civodul>atuin: could you share that OS config?
<atuin>sure, one sec
<atuin>but first i created teh inferior using the repl to test it
<atuin>maybe the definition of the inferior is wrong
<atuin>but it worked in the repl
<atuin>i could find packages from it
<atuin>seems that commenting the inferior lines, guix pull works again
<atuin>i'm really confused how the inferior works
<atuin>mmmmm when i comment out those lines in the system definition i can just copy paste them in the repl and the work
<atuin>`(lookup-inferior-packages linux-compat-inferior "linux-libre" "5.16.14")`
<viivien>I wish guix build would keep all failed built derivations when passed -K, including everything that’s built dynamically with run-with-store
<atuin>that works
<atuin>seems that it's the `lookup-inferior-packages` the function looping
<atuin>civodul: interesting ... i changed os into (os) and i call it when generating the os like this: `guix system reconfigure -e '((@ (atuin systems leibniz) os))'`
<atuin>that worked, no more loop
<atuin>could it be a recursive evaluation when doing the lookup?
<civodul>atuin: at first sight the config LGTM
<atuin>now i can run guix pull, guix shell and guix system without problems
<atuin>seems that i needed to avoid the evaluation of the lookup
<civodul>note that inferior-for-channels takes a bit of time the first time; it's akin to "guix time-machine"
<atuin>yeah, i realized that but it's cached later seems
<atuin>my problem was the lookup-inferior-packages entering a loop
<atuin>probably becasue guix first evaluates whatever is in GUIX_PACKAGES_PATH (where my inferior definition was)
<atuin> `readlink -f /var/guix/profiles/system-171-link/kernel/bzImage` -> `/gnu/store/1shy73077i3im91i4lv9bamifm4w29q1-linux-libre-5.16.14/bzImage`
<atuin>so it worked and i got the kernel from the inferior
<atuin>interesting feature the inferiors
<AIM[m]>Okay, guix home is just effin amazing
***the-porcupirate is now known as porcupirate
<sneek>wb unmatched-paren
<atka>sneek: botsnack
<unmatched-paren>it appears as if ocaml-odoc is failing its tests, so a few ocaml packages won't build
<Kolev>How do I get Haunt's blog builder to comply with my existing URI scheme?
<Cassio>How do I install nodejs packages globally in Guix?