<euandreh>In Nix if a file returns an attribute set, I can pick which one to build with 'nix-build file.nix -A my-attribute'. Is there a way to do the same with Guix? Like 'guix build -f file.scm -A my-variable'?
<roptat>no, file.scm must return a package or a list of packages, you can't select which one to build
<roptat>what you can do is make it a module, load it and build exactly the package you want with guix build my-package
***sneek_ is now known as sneek
<euandreh>hmm, so I would have a bunch of '(define-public my-variable ...)' in the module, and build it
<euandreh>All I have to do is have a top-level define-module?
<lfam>You can see the list of outputs with `guix show git`
<lfam>Most packages only have one, but sometimes it's worth it to split things up
<PotentialUser-54>Hello! I just installed Guix system and chose the xfce4 option on graphics install menu. I would like to change the "Applications" menu in xfce to Whisker menu. I've already installed package "xfce4-whiskermenu-plugin" using "guix install", but it's not showing up in the "Add New Itemsmenu in xfce4. Any help is appreciated.
<blendergeek>lfam: Thank you! I didn't know that packages have multiple outputs and until today I didn't know how to install the other outputs!
<mroh>PotentailUser-54: that plugin does indeed look broken: ~/.guix-profile/bin/xfce4-popup-whiskermenu: line 47: /gnu/store/clmv25gbfjrajvh8bsnhfj3w86kry004-xfce4-whiskermenu-plugin-2.4.6/bin/xfce4-panel: No such file or directory
<olivuser>I've got two unrelated questions: first, does someone else have the problem that profile generation takes like foreeeeeever (I'm talking like 1-2 hours) after installing or upgrading? For me, it has come to the point where the progress bar doesnt move for like an eternity. `top` doesnt show any significant activity
<olivuser>second, does anyone here use exwm as their main wm and is willing to share his/her sys-config (specifically the part relating to exwm obviously) :)
<civodul>olivuser: maybe it's taking forever because it's building a package?
<olivuser>civodul, I dont understand. Because I know that if a package is building, the build process is indicated somehow. But I am talking about the very last process when installing a package, after xdg stuff has happened. Crudely translated, the process is called "Profile with XY packages is created". How is that related to a build process? Am I missing something?
<civodul>olivuser: oh ok, so it's specifically the "Profile with X packages" phase that's taking 1-2 hours?
<leoprikler>olivuser: all the packages that you've just built are collected (via symlinks usually) into one big directory
<civodul>it's an i/o-intensive phase for sure, but 1-2 hours seems one or two orders of magnitude more than what i see
<civodul>time taken is roughly proportional to the number of files in the union of all the packages in that profile
<olivuser>civodul, yes, and I've come to the conclusion that it might be hanging at some point, even though the rest of the computer works fine (its not clogged). And `top` doesnt show any significant activity either
<olivuser>one thing which might have caused this is that I have at some point -- annoyed by the time taken by the process -- interrupted it.
<olivuser>also, I have ~150 packages, which might also be a factor. Then again, for about half an hour, the progress indicator has not changed whatsoever
<olivuser>is there a way to show whats going on "under the hood"?
<civodul>olivuser: interrupting is fine, it's transactional :-)
<cbaines>sendmail: this program must be setgid smtpq
<cbaines>Meh, now I need to go find the old opensmtpd store item that isn't broken
<roptat>ok, I think I understand better what happened yesterday
<roptat>want to hear a good story? I want to cross-compile android for the arm-linux-androideabi architecture, but can't build a gcc cross-compiler, because it needs the bionic libc, which can only be built by a cross-compiler for that architecture...
<roptat>also, it's built with soong, there's no other build system for it
<roptat>so, let's try and get the simpler targets working... I have another issue when trying --target=i686-linux-gnu: "fatal error: 'gnu/stubs-32.h' file not found"
<roptat>which is very similar to the error I would get with gcc -m32
<roptat>recall that I use clang, which is supposed to be able to cross-compile to a number of architectures, I use clang --target=i686-linux-gnu, and I use the standard cross packages in the build environment
<roptat>but when building clang, we hard-code the path to the libc, which is specific to one architecture; clang can't use it properly
<nckx>cbaines: We can fix that properly after http://issues.guix.gnu.org/44700. Currently, programmes can only be setuid root. For now you can manually create a setuid copy of smtp* instead of using an older version, or at least make sure that [the way you use] your old version isn't affected by the 2020 CVEs.
<kisaja[m]>how come kaddressbook doesn't have many buttons features when installed in guix, but manual says it does?
<chrislck>ooh the famous sashachua is in emacsconf
<leoprikler>Which license would you propose for a guix.scm build file? [à la "Build it with Guix"] I'd like to apply the GNU All-Permissive license or similar.
<mizukota[m]>is there documentation about the "raw" image type? How should file-systems and bootloader configuration look like for that? Should I use dd to write it? will it be read-only when I boot it or is it fully working system suitable for anything?
<mizukota[m]>I want to make .img and write it to usb device and boot it. I'm sure when creating disk image you should set filesystems and bootloader to something that is expected by disk image creation script
<chrislck>Question: a malicious guix package can destroy my system?
<constfun>hello, new guix system user here, how can I install 'devel' headers and such for a package? looking for ncurses-devel in particular
<roptat>in most cases, it's available in the package itself, there's no "devel" separate package
<ngz>When building a package, I get the following error during the boostrap phase: "error: possibly undefined macro: AC_MSG_ERROR". Does that ring a bell somehow? I think I already encountered it.
<roptat>mh... using i686-linux-gnu as a triplet might have been a mistake
<civodul>ngz: that's weird because AC_MSG_ERROR is part of Autoconf
<civodul>perhaps there's a stale aclocal.m4 in there or something?
<ngz>civodul: Ah. I may try to clean up the build directory beforehand. It's worth a shot. Thank you.
<ngz>civodul: but there's a "aclocal --force" in the bootstrap sequence. Shouldn't it take care of that?
<ngz>OK, nevermind. It was a missing pkg-config in the native inputs…
<civodul>ngz: in general, "autoreconf -vfi" is what you need to run :-)
<civodul>the 'bootstrap' phase of gnu-build-system does that
<constfun>roptat: thank you, i have ncurses installed, but `make menuconfig` for the linux kernel still complains about missing ncurses-devel packages, yet i do see headers and dll in ~/.guix-profile/include, C_INCLUDE_PATH env var seems to be correct as well...
<chrislck>cbaines: thx w/o gnomecanvas gtk-2 conflict still appears:(
<roptat>constfun, do you also have LIBRARY_PATH correctly set?
<constfun>roptat: it seems I do, .guix-profile/lib ncurses is in there as well
<roptat>maybe you could strace the process to try and understand why it claims libncurses is not there?
<constfun>roptat: duh, i should read the full error message, I didn't have pkg-config installed, thank you for the help!
<mroh>constfun: in a (vanilla) kernel tree, try something like `guix environment bash --ad-hoc gcc-toolchain bison ncurses pkg-config coreutils gawk flex -- make menuconfig` I think, you also have to hack the shebang of scripts/ld-version.sh to something like "#!/gnu/store/alfmgg03i759f8ppzkbbad82lbdpv22h-gawk-5.0.1/bin/awk -f".
<cbaines>civodul, I did have a thought recently, while trying to get Cuirass and the Guix Build Coordinator to work together is a bit odd, maybe the least worse way to do it is to get the coordinator to act like the guix-daemon, and Cuirass can talk to it that way
<lfam>I made some good progress on getting ready for QEMU 5.2.0, which will use Meson / ninja to build. However, there is at least one stumbling block — the ./configure step is not considered valid when building starts, so it re-configures at the beginning of the build phase, printing this message: "config-host.mak is out-of-date, running configure"
<lfam>Is this familiar to anyone? Our QEMU package uses a custom configure phase and it seems to still be needed, but I guess it is missing something now
<luis-felipe>For example, running "guix upgrade rygel starfighter" results in the error "guix upgrade: error: starfighter: parámetro no conocido", while using "guix package --upgrade" with the same packages works.
<civodul>i wish we had a high-level way to define cross-compilation targets and the various quirks to use for each
<civodul>luis-felipe: in English it's "extranous argument" (wrong translation)?
<roptat>there, adding cross-ld-wrapper did the trick :)
<luis-felipe>civodul: I'll report it then. As for the translation, It could be translated as "Argumento extraño/desconocido". But in Spanish argument and parameter are frequently used as synonyms (I don't).
<apteryx>How can I get a font registered in the build environment?
<luis-felipe>civodul: "desconocido" is "unknown", so if the error message is suppossed to tell the user that guix upgrade doesn't know what the given argument is, then using "desconocido" would be fine.
<apteryx>I tried setting HOME then running the usual 'fc-cache -rv', with DejaVu Sans installed, but fc-match "DejaVu Sans" still reports 'n019003l.pfb: "Nimbus Sans L" "Regular"'
<Mayt>Hello! I'm currently looking for the list of packages in %base-package, I can't find it anywhere :/
<philipper905>The error I get is `Math formula deleted: Insufficient symbol fonts.`
<davidl>is there any quick and easy way to "dump" a package definition to file?
<davidl>say you are working on a package in a REPL, can you do something similar to what in other languages would have been package.dump() or dump(mypackage)?
<davidl>what Im really looking for is a way to replace github or gitlab CI workflow, with cuirass by having a channel in the cuirass specification that is continuously updated by a monitoring script that updates the commit and hash of a few packages and commits and pushes it to the channel.
<mbakke>civodul: I think D-Bus follows an even/odd release cycle like GNOME (i.e. the 1.13 branch is "unstable")
<philipper905>hmm, it seems I only get the error in pdflatex when the package ulem is included
***efraim is now known as efraim1
***efraim1 is now known as efraim
***efraim is now known as efraim1
***efraim1 is now known as efraim
<philipper905>Is there a way to get more helpful/verbose error messages from pdflatex?
<mbakke>civodul: I haven't really understood the mechanics yet, but there are several cases where adding a different GCC as a native-input leads to having to remove the default/implicit GCC from CPLUS_INCLUDE_PATH to avoid "include_next" errors and similar
<mbakke>'qt-4' and 'android-libutils' are two examples
<mbakke>civodul: I'll start hacking on core-updates in the next few weeks, let's see how it goes :-)
<mbakke>the weather on 'staging' is looking pretty good, I think I'll go ahead and merge shortly
<mbakke>civodul: have you thought about elfutils and enabling the debuginfo server at all?
<mbakke>I kind of dropped the ball on mjw back in #38803, but it sounds like a nice feature to have.
<mbakke>I have a patch somewhere to update to the latest elfutils (without the extra dependencies), and will try to make GCC use it for starters.
<pineapples>civodul: Hi! Thanks! On an unrelated note (I need to get this off my chest, I hope you don't mind): I've got to say that I've really got hooked up on the project, to the point where I'm trying to conform to the project's rules when writing personal configuration-related code even though it will be of no use to Guix. This is unheard for me, especially given the fact that I'm a mere user with no technical background whatsoever. An
<pineapples>yway, thanks everyone involved for your hard work!
<mbakke>pineapples: thanks for the kind words! Guix can be contagious, even its high standards and courteous community. :-)
<mbakke>cbaines: ooh, excellent. I'll check out the non-green items there.
<kisaja[m]>it says the former main developer is now patching OpenPrint fork of cups
<kisaja[m]>this fork is just following cups, not being a separate program
<mbakke>kisaja: Thanks for the heads-up. I heard about that fork and expect that Guix switches to it on the next rebuild cycle.
<mbakke>cbaines: that page is really useful! Can confirm most of the listed problems. Investigating...
<cbaines>mbakke, great :) I'm quite happy to investigate some failures too, just let me know what you're looking in to so we don't investigate the same thing
<sys2>hello guix! I'm trying to workaround this bug: https://issues.guix.info/44559, but am unsure how. I can't `guix pull --without-tests=gnutls`, but I can `guix build xyz --without-tests=gnutls` (but pull tries to build gnutls 3.6.12 directly). Oddly, `guix build email@example.com --without-tests=gnutls` builds firstname.lastname@example.org. Does anyone know how I can update?
<lle-bout>civodul: I am afraid the reproducibility issues might prevent powerpc64le-linux-gnu port to be merged at all, I am afraid not many people have looked at reproducibility of powerpc64le-linux-gnu binaries in general and that my skills with build tools are not extensive enough to solve them
<lle-bout>Debian doesnt even test reproducibility of their ppc64el binaries