<nckx>Just that anything not required to build Guile won't be worked on/maintained by the (small but not that small) Guix community, that's another extra weight on 1 person's shoulders, and that goes for everything. Even submitting patches upstream to Guix to make it more portable — and defending them — could probably be a full-time job.
<OriansJ>nckx: so I guess we should encourage more people to start making guix better in other distros; so that in the end we win the hearts and minds of the other distros to help us
<nckx>Not to say Guix would break portability on purpose, but stuff bit rots, and we churn hard. Example: Guix/Hurd 😛
<nckx>OriansJ: That is a positive message I can get behind.
<OriansJ>small changes today make major waves of changes in the future
<ober>thanks for the info. interested on both fronts.
<OriansJ>I guess that is the thing that I never understood; when you tell someone going back in time and making a small change will have major impacts, people believe you but when you say the same thing about now; they act like such changes are impossible.
<ober>is there much "guile only" flavored scheme in guix?
<nckx>(Another example closer to home: Guix/i686. Breaks all the time. Just because so few people use/test it.)
<pkill9>it's trying to build my local channel i think, which i added to the load path using the "add-to-load-path" guile function
<au>Hello everyone, Guix newb here. I've got a minor problem. I'm using Guix as a package manager in my Trisquel system. It works great, but when I install an application, it doesn't show up in the list of programs in my start menu. I can run it via terminal, which is fine, but how do I go about making it show up in the start menu or as a desktop icon?
<pkill9>au: you probably need to add ~/.guix-profile/share to your XDG_DATA_DIRS environment variable in either /etc/profile or ~/.profile (as long as your display manager sources it, it should source both those i think)
<pkill9>well, it won't recognise the tilde i don't think, so use $HOME/.guix-profile/share instead
<Gamayun>Hmm... I'm trying to package qtpass. When running qmake, qmake tries to run 'lupdate-qt5' and 'lrelease-qt5', which we have packaged as just 'lupdate' and 'lrelease' as part of qttools. I'd imagine this would affect anything using qtlinguist, but I can't anything in the package definitions addressing it...
<bavier`>Gamayun: does the configuration honor the "QMAKE_LRELEASE" environment variable?
<Gamayun>bavier`: Doesn't seem so. Setting it didn't make any difference.
<mbakke>rekado: Did you find time to look into the glibc 2.29/python thing?
<kmicu>“European Processor Initiative will deliver key technologies to the new European HPC [High-Performance Computing] strategic plan for an independent and innovative European high-performance computing and data ecosystem,” just put Guix on it already!
<civodul>rain: it's not in the manual, but it means you need to recompile :-)
<jonsger>civodul: guix package: error: build failed: opening directory `/gnu/store/p5q59xqmhwg60y2437fnny76nw7l6gbz-module-import': Permission denied while installing something, but in the docker container it has more permissions then on my normal computer...
<playX>In arch linux I just installed python-neovim package
<roptat>playX, oh I have a package definition for that, I need to push it!
<roptat>if you can wait, I'll do that this evening
<AndreasL>I try to use guix under Xubuntu 18.04 but having problems with non ASCII caracters
<roptat>I don't have access to my private key right now
<g_bor[m]>To be more clear, the build tries to download the source from a git repository, which fails. I guess I could simply do a native input origin, and be done with it... But it seems like it would be great to have a package to reference...
<leungbk>`gtags --skip-unreadable --skip-symlink` <-- is this the correct way of generating gtags for the guix repo? when calling this from the project root, it seems like the .scm files are skipped over.
<nckx>str1ngs: Resign yourself to using a hardware clip, you'll thank yourself later. No bricking. Required to run ME-cleaner anyway. Once flashed, you can just use flashrom anyway, or disable that for bonus securiteez pointz.
<roptat>gnu/packages/ibus.scm tells you the name of the file where the variable is defined, then you replace / with spaces and remove the .scm, put parenthesis around that, and that's the module name you need to include
<nckx>quiliro: Guix does not provide a magical GRUB entry for that, no.
<quiliro>what happens if i boot grub with the ''single' parameter on the kernel line?
<roptat>probably nothing special, unless the shepherd supports run levels
<nckx>quiliro: Probably nothing. Single user mode is an old SystemV thing, which itself is just a hack upon runlevels (‘1’), but doesn't really describe what it does. I think systemd emulates it with a target. Shepherd doesn't.
<quiliro>or put another way, how can i modify a non acccessible version of the system without running its X11?
<nckx>Probably not. So your computer freezes completely?
<quiliro>rather: how can i modify a non acccessible version of the system so it does not run its X11?
<janas>I was playing around with the mpd service to try and figure out the pulseaudio bug, and I realized that for some reason when the service is started from herd it fails to connect to pulseaudio, but when I start the daemon from my terminal (same user, same binary, same config) it connects to pulseaudio successfully. I have no idea what could be going on, I'd appreciate any ideas people have.
<quiliro>but it does not freeze on the previous version of system reconfigure
<recj>wow do i really have to add every single gnu packages if it has a lot of dependencies ?
<nckx>quiliro: Can't you edit your system.scm from that generation? You can still get Xorg.0.log.old and /var/log/messages from there, too.
<roptat>that's why some files have so many #:use-module at the beginning
<quiliro>janas: herd is managed by root....did you start mpd as a normal user?
<nckx>janas: My guess would be that the system mpd tries to talk DBUS to the user's pulseaudio and fails, or otherwise can't find it, but I don't quite understand why that would happen. I think rekado_ (sorry for pinging if not) uses mpd.
<quiliro>maybe if i update guix with guix pull and redo the reconfig
<nckx>I have my kernel set to log panics to the (EFI variable) storage at /sys/fs/pstore, which is super handy (you can read dmesg from a crashed kernel!) but I don't know if the Guix kernel can do that.
<janas>nckx: Thanks for the info, I'll try to file a bug report tonight
<nckx>quiliro: Didn't know if you meant janas_ or me ☺ I haven't seen it, no.
<nckx>quiliro: So your problem isn't that you changed your configuration file and X broke, but that you updated (guix pull && guix system reconfigure or whatever) and your old configuration no longer works?
<nckx>So editing your configuration won't work, is that what you mean?
*nckx 's having a very hard time concentrating at the moment, sorry.
<quiliro>nckx: i had a working installation....formated and reinstalled...1.0.1 screwed everything ...even the boot usb did not have good video
<quiliro>so i installed manually a barebones config
<nckx>janas: You could try running mpd from a terminal as your user, I don't know off-hand if it has a --verbose or --debug option.
<quiliro>then reconfigured with a light-desktop config
<nckx>quiliro: If you can't extract anything useful from the log files I mentioned above because the kernel dies before they can be flushed to disc, this is what I use & described above: https://lwn.net/Articles/434821/
<nckx>(Why? I don't know. We call BIND ‘isc-bind’ to avoid shadowing Guile's ‘bind’ procedure, but there doesn't seem to be a ‘make’. Maybe there is, maybe there's another reason, maybe there's not.)
<nckx>quiliro: As much as I don't mind ‘helping’ you here, I don't think I'm of much help. I don't use GDM, and I never have. I still think a bug report with relevant excerpts of your logs will have the best chance of finding someone who does.
<nckx>quiliro: It will avoid xorg staring at all, even at reboot, if that's what you want (is that want you want?). You'll get a non-graphical system that will probably boot just fine, but there won't be a ‘herd start xorg’ or anything. There's unfortunately no way yet to add ‘disabled-by-default’ services in an OPERATING-SYSTEM, or I missed it being added.
<nckx>bzp: Installing tango-icon-theme gives me Tango as a new Icon choice (quelle surprise), I don't know the names of any ‘full’ theme. But the paths seem to be set up to search in all the right places.
<nckx>I assume GTK supports themes somewhere in ~/ too if you want to use an unpackaged one.