<jackhill>do we do any cross-building on the build farm? I know we spend some effort trying to make the build systems support cross-building…
<contrapunctus>Tried cp'ing the Guix System image to a USB flash drive. Laptop detects the drive, offers it in the boot device menu, but selecting it for boot just takes me back to the startup screen ("press ESC for boot menu"). This laptop boots a Debian USB flash drive just fine. 🤔
<donotshake[m]>there's software like Yumi that use grub, which is a bootloader that has the ability to directly boot iso. For now I would keep it simple and dd, which will make sure the usb is setup properly.
<contrapunctus>donotshake[m]: oh lol - sounds like you missed this bit "Also tried dd as suggested in the manual, no difference." 🙂 cool, waiting for the Devuan ISO to download.
<donotshake[m]>Sorry, I did miss that. Could be a legacy / uefi boot situation.
<sturm>hi folks, I'm seeing "guix package: error: corrupt input while restoring archive from socket" when running `guix install`. Is that normal, or is it likely to be something at my end (bad hard drive, bad network etc)
<leoprikler>sounds similar to a bug, that should recently have been fixed
<sturm>thanks leoprikler, i'll try a guix pull and see how I go
<civodul>sturm: hey! the daemon is running and fine? anything in its log?
<sturm>civodul: hi! seems to be running ok as it in installing things ok generally well - just seems to intermittently fail when I give it my full manifest.scm to install. It may be a coincidence, but it seems to fail on a rust package
<sturm>I've just put on a stir-fry so I'll pop back in with more info in an hour or two :)
<civodul>there were a couple of interesting issues
<mothacehe>is it ok to patch doc/build.scm on 1.2.0 branch to fix manual generation?
<civodul>mothacehe: sure; what's the problem there, something with guile-lib?
<mothacehe>civodul: yes, doc/build.scm from 1.2.0 uses a modified guile-lib. When building the docs from a recent Guix, the 1.2.0 doc/build.scm inherits from the recent Guile-lib, causing a build failure.
<civodul>mothacehe: right; we discussed it a couple of times with lfam and apteryx
<lle-bout>civodul: hello! what do you think about getting an NLNet grant for community organizing in GNU Guix? I heard NLNet is becoming more keen to that.
<lle-bout>The people who want to do that need to show up, I know someone also who does it very well, Maxime, a friend
<lle-bout>He's already working on some NLNet project doing it right now actually, but that will come to an end at some point
<civodul>lle-bout: hi! what does "community organizing" mean?
<lle-bout>civodul: something similar to LibreMiami meetups
<lle-bout>I wouldnt know how to explain it with words necessarily
<efraim>I would image also something like our online guix meetup last novemberish
<lle-bout>Basically every time we had a meetup, including LibreMiami meetup ones, I felt like it was such a great learning experience for everyone, information flows through and all much better
<lle-bout>But I also think there's more to meetups in community organizing
<sturm>civodul: regarding the earlier "guix package: error: corrupt input while restoring archive from socket", haven't hit it again yet after a `guix pull`, `guix gc -d 1m` and `sudo guix system reconfigure`. Nothing interesting in guix-daemon.log, but here's the install output: https://paste.debian.net/hidden/e38206fc/
<lle-bout>I feel like to make GNU Guix development (or even just packaging) more accessible and inclusive, community organizing is a must
<efraim>I also attended a C++ meetup about using conan as a dependency manager for c++.
<nefix>Good morning! Is it possible to add nix packages to a operating-system definition?
<lle-bout>I don't know if any Outreachy or other initiatives actually paid off in terms of actual people feeling included and staying around now and the future in the GNU Guix project, maybe more regular GNU Guix meetups would help making it a pleasing experience and have people not give up early because nobody would be here to help or else, in some way, doing community organizing would be also that probably
<davidl>nefix: I don't think so, there is however a guix import nix <pkg> command, that could help you in defining your nix packages as guix packages which you could then use.
<davidl>lle-bout: are there any measurements with numbers for people using and staying around with Guix? Say number of substitute downloads etc.
<davidl>since mailing list archives and manual are pretty good resources for help these days, less ppl may show up in here for example.
<lle-bout>davidl: I don't know I have no visibility there, probably some statistics could be made on package popularity (by the way that would be a great way to focus our efforts on what people actually use), but then there's also the political question of whether it is OK to do such statistics or not
<davidl>lle-bout: I think nginx should be able to collect some data, which then could be anonymized and fed into maybe piwik/motomo for some good statistics.
<lle-bout>I think Matomo is not strictly necessary also not very fit for the use case, it's some PHP thing and that part is far from being packaged in GNU Guix I feel, probably some custom counters page in ci.guix.gnu.org would do the job
<davidl>lle-bout: ok. Matomo should be good at supporting both nginx logs and anonymization so thats why I thought be useful, but you probably know better.
<lle-bout>davidl: I don't know better I just felt that Matomo was too intrusive
<davidl>lle-bout: well its not really minimalist if thats a consideration.
<lle-bout>davidl: that also, but I felt even though it's Free Software and put forward as privacy-respecting, I think the actual implementation still tracks stuff in undesirable ways, I wouldnt feel great if it was used
<davidl>lle-bout: I think knowing how many downloads of substitutes you have in total (losing who requested them) could be a useful measure of overall use, and I believe you could still get data pinpointed to which package is being requested.
<lle-bout>davidl: agree but do we still need to get people's consent for that?
<davidl>lle-bout: no, so that's a bonus. Keeping track of how many times you serve substitutes is your info.
<lle-bout>davidl: for me that's all we would need but I don't know if we must still get consent for this
<civodul>lle-bout, efraim: i'm all for more meetings (on-line or not), indeed
<civodul>Guix Days so far were rather targeting insiders
<civodul>but having meetings explicitly reaching out to newcomers, like the LibreMiami meetups i suppose, would be great
<lle-bout>civodul: happy to learn that makes sense to you too!
<civodul>we "just" need a few volunteers for each meeting; we have machines with BBB ready to go
<zzappie>apteryx: jami is a great project but It newer worked for me and my friends. Did you have positive experience with it?
<civodul>i admit i haven't yet given Jami a try, but it sounds like you have a good point
<apteryx>heck, perhaps savannah could host such instances itself and have the savannah usernames registered through the new JAMS server (a way to manage users in a centralized way, such as via LDAP), although I'm not familiar with JAMS at this point.
<lle-bout>Having to *install* Jami might be a barrier for some newcomers, but also Jami has had connectivity issues due to it's P2P nature, nonetheless I acknowledge it's been getting better and better and it becomes a more dependable tool I believe
<zzappie>don't know but we use jami as paper post for fun. Messages usually delevered in a week. And sometimes lost :)
<cantillion>Do I need to go through specific steps to add non us locales into my guix-profile? I'm getting this kind of warning and I would like to fix it: "bash: warning: setlocale: LC_ALL: cannot change locale (de_DE.utf8)"
<raghavgururajan>civodul: Any chance "Unbound variable: %outputs" for librsvg, related to your patches?
<lle-bout>If I don't have people helping I feel like I will be burning out following the CVE feed if I have other things to do in parallel, if I follow the CVE feed I must not do anything else, be full time on it also not much other things other than contributing to GNU Guix
<maddo>lle-bout: will do, I plan to switch my main desktop to guix (which will require some reading to be perfectly honest as to while I understand guix doesn't want to support nonfree software, it is however required to run my own pc).
<lispmacs[work]>hi, I wanted to get qucs back into my profile, which was removed from Guix. I can do it with guix install and time-machine, but I prefer to use manifest files. Is there a way I could do that using channels and a manifest file? Or would I need to create a separate profile for it?
<leoprikler>you can always add some snippets to etc/snippets :)
<lispmacs[work]>hi, I'm trying to use the Inferiors example from setion 5.8 in the manual. However, my manifest file currently is of the form (specifications->manifest '("package1", "package2", ... , "package100")) whereas example uses packages->manifest instead. Could somebody tell me the easiest way to integrate my inferior package in this case?
<apteryx>the wrapper scripts make debugging with GDB a bit of a pain
<Frosku>Hey all, I've managed to get Guix up and running. Can someone help me to get a tor service running on startup? Right now it runs but only manually in terminal.
<Frosku>Apr 2 19:29:22 localhost shepherd: Service tor could not be started.
<lle-bout>leoprikler: I'll try, dont know much elisp
<apteryx>should --with-source apply recursively? E.g., guix build B --with-source=A=some-source.tar, where B depends on A, should rebuild B using the modified A? Currently it says a warning that the transformation has no effect and returns B unmodified
<Vongazi>Hello i am trying to build GNU IceCat, but it is taking a very long time, because it compiled 5 different versions of llvm and rust 1.19, rust 1.20, and now it is compiling rust 1.21, i don't understand why i need to build different versions of the same package just for IceCat to build?
<lfam>Vongazi: It sounds like you have chosen not to use binary substitutes for Guix, but to instead build everything from source. Is that correct?
<Vongazi>yes, the only binaries i installed were when doing guix system init, and guix pull
<lfam>So, you want to build every package from source?
<Telc[m]>on upgrading emacs to 27.2 I got """.guix-profile/share/emacs/27.1/lisp': No such file or directory"""
<Vongazi>i thought it would not take a long time, because i was running gentoo and compiling firefox takes around an hour, but now icecat has been building for 5 hours
<lfam>Vongazi: The more detailed answer is that IceCat depends on Rust. In Guix, Rust is bootstrapped by building a couple dozen versions of Rust. Each version is built using the previous version of Rust
<lfam>I would expect it to take a few days, if not a week
<apteryx>16 hours on a Ryzen 3900X on master / 8 hours on core-updates
<lfam>Unfortunately, the Rust project chose not to make Rust "bootstrappable" in any other way. I guess that Gentoo doesn't bootstrap Rust but instead use a binary blob
<lfam>Or, their version of Firefox is too old to depend on Rust. I don't know
<lfam>apteryx: Nice, did we improve the bootstrap chain on core-updates?
<apteryx>yes, it starts at 1.29 intead of 1.19, and the tests of intermediary rust packages are disabled
<lle-bout>It's the router from my ISP, they added a feature to create VMs on it somehow, and it runs on arm
<apteryx>I'm having an issue with Docker still; it won't build opensuse tumbleweed images to to some update missing from runc IIUC (they have some kind of syscall whitelist, and it needs to be updated for new syscalls used by the glibc in tumbleweed)
<lfam>That will be great lle-bout. I forgot, but we should also test installing in a VM
<lfam>That's amazing lle-bout. American ISPs do not offer hardware like that
<apteryx>it's not clear from this report what needs to be updated, but from experience it seems to resolve around having a recent containerd package (not sure if that includes runc on debian, I'm guessing so)
<apteryx>another bit that may be required to update could be libseccomp
<apteryx>actually I had already tried recent versions of containerd and runc, and it was not enough on Guix System the last time I tried (I still have the branch)