<adanska>happy gnome user, but was just curious: cinnamon exists as a package in guix, but there is no desktop-service associated with it. did someone just not have enough time to make it a full desktop-service and left the package in the repo in case someone else wanted to put the time in?
<lilyp>do we have a quick procedure to remove multiple configure flags?
<lilyp>adanska: more or less; we don't like removing packages that build, but cinnamon is quite outdated
<lilyp>someone would have to update it and also make a service
<adanska>fair enough! just saw the file as i was compiling guix and it piqued my curiosity :)
<adanska>isaneran: yeah, it will help a lot with packaging too, sometimes i feel getting the environment correct is not as nice and ergonomic as id like, probably because im not using the guix tooling proplerly :p
<isaneran>yeah takes a little while to learn I think
<isaneran>I have the same feeling but the more I learn to use new features it starts to click together better
<isaneran>but I also have some weird habits that are probably compensating for things there are a better way to do
<isaneran>for example when I am making a package and I depend on some other package and don't know what module to import, I use guix edit to find the file and scroll up to the module definition or guess it from the file name haha
<adanska>yeah for sure. before i really knew how to leverage guix shell i was just updating file in my local guix repo and doing ./pre-inst-env guix build whatever
<isaneran>I know I can also use the package-spec->package thing but I feel like it's more robust to depend on the package object directly
<adanska>theres less to think about (and more to bite you in the backside later, fwiw)
<isaneran>yeah I guess I can see what you mean adanska
<isaneran>like if I were to put a new person on debian I can just tell them to run update and upgrade once in a while and don't install packages outside of debian repo and they hopefully won't shoot themselves in the foot
<isaneran>but I guess here I have to tell them to run guix pull, guix upgrade, guix system reconfigure, oh and once in a while remember to delete package generations and system generations and run guix gc cuz you'll accumulate harddrive space
<isaneran>you get amazing benefits for learning all that for sure though
<isaneran>especially for someone a bit less technical
<adanska>in that respect guix is pretty user friendly, but gets complex as soon as you want to do anything that modifies your system outside what guix provides for you
<isaneran>however we should be able to solve that with a beginner friendly GUI for basic guix tasks
<isaneran>for a person who just wants to run it and install programs and keep their system up to date basically
<adanska>in that respect it makes the 'hacking' aspect of a linux distro a little harder. you need to consider a lot more before you can update an etc file somewhere or modify a service
<adanska>if theres one thing i wish there were more tutorials and blog posts about, it would be guix services. the naming is confusing and writing them requires a lot of knowledge about the whole guix setup
<adanska>one of my projects at the moment is writing a home-onedrive-service-type, and that is proving to be a far greater undertaking than i was bargaining for
<isaneran>tried to update postgresql to version 16 but can't figure it out haha
<isaneran>or at least it wasn't as simple as updating the version number and hash
<isaneran>another thing that would help a lot would probably be an easier graphical frontend for info manuals
<isaneran>if it comes installed with the default gnome system as an application called Guix Manual or something that just invokes that graphical reader with the guix manual open
<isaneran>hmm emacs-guix's guix-edit doesn't find files from other channels like guix edit does
<isaneran>maybe having a flag to get `guix edit' to print the path and line number etc would make it easier to get full parity? Though I dunno how emacs guix works, seems to use a guile repl and stuff so maybe that wouldn't help
<lilyp>the ironic thing here is that yelp should be able to find info and man files but doesn't tell you how
<efraim>it seems after stopping the qemu-binfmt service suddenly its much harder to cross-compile rust apps
<civodul>heh, were they *really* being cross-compiled? :-)
<efraim>more of once I turned off qemu emulation I wasn't able to run all the scripts, so I think it was more native than I had planned for
<efraim>in an interesting turn 'rust-sysroot-for-<arch>' is probably the same regardless of starting architecture, so in theory it could be #:target #f and I wonder if it could be used as an input for rust itself
<phf>Hello #guix! I've implemented enough of gnu/packages/elixir.scm, guix/build-system/mix.scm, guix/build/mix-build-system.scm for things like `guix shell -C elixir -f elixir-jason.scm -- elixir -e "import Jason"' to work as expected.
<phf>where `guix import hexpm jason > elixir-jason.scm' for the most part.
<phf>The objective is to have mix-build-system included in Guix. At what point should I bother the developement list with my patches ?
<lilyp>I mean, if it works for some projects, you could start writing an RFC patch, if not an actual one
<phf>right now, I'm looking at elixir packages that depend on C extensions and the likes, not only Elixir code.
<phf>lilyp: Ok, I will look at `RFC patch' then, thanks.
<lilyp>if there are any caveats to be aware of, you should just state them in your cover letter; probably others interested in elixir will be happy to chime in
<isaneran>hmm this might be a bit too hard for me at this point
<isaneran>I decided to just try and get it building first and not worry about the symlinks thing for now but it can't find icu4c and I saw another database had a workaround for that in its arguments, but I don't wanna write the arguments straight in the package since I don't want to override the one from the parent package
<isaneran>also, postgres is mission critical software for a lot of people, so I don't think I can be the one who submits the patch to get it to version 16 haha
<aldum>I'm really hoping for a proper 3rd party ThinkPad-style keyboard
<snape>"We’re continuing to invest in open source firmware development, with the goal of replacing other proprietary firmware we’re currently stuck with in the future too."
<janneke>snape: thanks, pretty interesting to follow that
<rekado>FYI: the guix-science channel now has a bazel-6 package. If someone would like to package a more recent version of Tensorflow by building it with Bazel in Guix, feel free to try this in guix-science.
<oriansj>snape: all bios are slow at doing the crypto stuff because the bootloader did not create an optimized crypt module
<oriansj>and probably because of the hardware limits on x86 in real-mode;
<PotentialUser-69>I've just installed the fontawesome package to get icon support in waybar. but i'm only getting about 2/3rd's of the icons appearing anyone have any idea what would cause this?
<bjc>i had the same problem, and it's not even guix specific. so i stopped using font-awesome and just use normal unicode stuff
<bjc>building infrastructure around the private use area is definitely a choice
<oriansj>guix has python-esptool but no ability to compile or assemble ESP32 binaries from source code
<snape>ACTION is eager to read the new "Software Development" chapter in the docs
<PotentialUser-57>Hi! I want to reinstall guix system. Can I just delete the 'gnu' folder from the disk?
<mirai>civodul: could you weight in on #62056? I'm wondering whether it makes sense for (erase-current-line …) to have an extra parameter instead (i.e. using (parameterize …) to set its newline behavior)
<mirai>instead of duplicating the definition of (erase-current-line …) everywhere
<civodul>ACTION considers redirecting civodul to ChatGPT or M-x doctor
<civodul>seriously though, i’ll take a look when i can!
<jaeme>PotentialUser-57: yeah just delete the /gnu directory and remove the guix-daemon.service assuming you are on a foreign distro with systemd
<bovid-19>Hello guix! How can I restart the audio system? I could not see any service that looks like it is responsible for it. I need to restart it because it shows the HDMI audio channel as unavailable. I assume restarting the right service would help because reconfiguring the system did. But it seems like a bit of overkill just to avoid a restart of the
<sneek>bovid-19, nckx says: ‘guix refresh -u’ more or less (but mostly more) assumes you're running it as ‘./pre-inst-env guix refresh -u’ in a writable Git checkout. The error message could be clearer.
<podiki>bovid-19: if you are using pulse audio I think you can just kill the process and it will get restarted by the next audio request. otherwise you can restart it from e.g. the pulseaudio tray icon if you use that
<bovid-19>podiki: thank you. I have currently disabled pulseaudio in my configuration. Restarting it did not always help. But I just checked and pulseaudio is actually a running process. Killing it did not help. There are a couple of other things that don't seem normal with my system. I probably should just try and reinstall it.
<podiki>Well you'd need to know what the audio system is if you are going to restart it or figure out what's wrong. If you share your system config someone can help look (I'm away now)
<apteryx>hm, where was that change-id patch I've sent
<luke-jr>still looking for a way to run a script in the chroot post-unpack (to abort if there's any ELFs)
<apteryx>our aarch64 machines on berlin are overwhelmed
<podiki>how do you show closed bugs in debbugs? i answered the prompt about showing archived bugs and also set debbugs-gnu-suppress-closed to nil as well
<podiki>but still don't see closed bugs on guix-patches
<podiki>well you can just go to the direct bug number at least with debbugs-gnu-bugs
<boo_>Hi! I've configured a couple of services for a user on one of my headless systems. The services work well but I would like for them to automatically start on bootup. Is there any way I can get a user's Shepherd daemon to start without having to manually login as that user? loginctl enable-linger <user> doesn't seem to work as it would on systemd
<podiki>for renaming in this case (two packages with same name) can't use a deprecation? or how do we handle that?
<lilyp>boo_ you could start it as a shepherd service maybe?
<boo_>lilyp: Do you mean running the user's shepherd daemon as a service?
<boo_>I've looked around the code and documentation and it seems reasonable that I could run the user's home shepherd as a service of system shepherd, the problem is that I don't know how to specify whose home shepherd to run. Any pointers?
<civodul>hmm i thought Cuirass commit 5e3e49c351f94a63dbea004333a1ac1fe4f43982 would give us 404 to begin with
<civodul>“selected 2453352 build logs to remove” <- builds logs more than 9 month old on berlin