<dftxbs3e>Ludo stated what we discussed earlier, but we still don't have the bandwidth to maintain unbundled deps (GNU Guix isnt well equipped to handle micro-dependencies philosophy)
<lfam>Maintaining the dependencies wasn't my limitation in the past. The current problem is that syncthing requires newer Go (at least it seems that way) and newer Go doesn't work with our build system
<dftxbs3e>lfam, oh.. the patch worked fine for me with current go.
<lfam>The next step will be to use your patch, I think
<lfam>I am optimistic about the future of Go in Guix. There are people contributing who really know about it. All that I know I learned just for packaging, and that's left me with a lot of gaps in my knowledge
<dftxbs3e>When I am able to write GNU Guile's Scheme proficiently I'll sure be contributing in a better way.
<pkill9>a dependency requires a newer version of a package that the main package requires, and rust seems only to want to choose one D:
<dongcarl>dftxbs3e: Hi, I'm trying to get the powerpc64le toolchain working on my very custom manifest... I'm building the cross-glibc with xgcc=gcc-7, but I'm still getting the notorious "binary128 floating point type (GCC >= 6.2) is required on powerpc64le." thing...
<pkill9>Why would Signal desktop use electron if it's a security-focused application..
<dftxbs3e>pkill9, I believe requirements and practicality fight each other
***iyzsong-- is now known as iyzsong-w
<pkill9>why do i need to reboot in order for mcron service to use new cronjobs after reconfigure? restarting mcron doesn't do anything
<wonko_the_sane>Speaking of Signal does it still make the arbitrary demand of linking to a phone number? And does it still lack any facilities for key management and revocation etc? (I think Signal is great, much respect for Moxie Marlinspike,et al)
<ryanprior>Signal has been working on easing the phone number restriction but have not rolled out any option to sign up without a phone number yet. I'm not sure what you mean about key revocation. You can choose to "reset the secure session" with any contact, which negotiates a new key between you two.
<ryanprior>There is a fork of Signal that does not require phone numbers, I forget what it's called.
<sturm>Anyone know how to enable outgoing network access for virtual machines in Gnome Boxes on Guix System?
<wonko_the_sane>ryanprior: thanks. In terms of revocation I've desired the ability to revoke a long term key in certain situations with signal. Also wanted to migrate preserving the same key or rotate to a new long term key within already established encrypted channels rather than needing to rebootstrap meatspace fingerprint verification
<ryanprior>They are working on the migration story but they're taking it slow. Meanwhile Keybase has had a great migration story for years, but the Keybase team has been occupied adding encryption features to Zoom.
<ss2>I sense we will approach another level of abstraction: I'm running a windows programme through wine, that is running through guix, on a foreign system. The host's wine fails to load the windows programme.
<leoprikler>raghavgururajan: I think it's '(("FOO_CONFIG_PATH" . "/path/to/bar"))
<PotentialUser-10>I see some weird character sequence when i run guix package commands: looks like "]8;;" I've not had problems getting colored output from guix thus far, it only happens when I run for example 'guix package --list-generations'
<civodul>if it "officially" supports ppc64le, you can tweak guix.m4 so --with-courage is no longer needed
<marusich>it would be nice to have a "binary guix" like the kind you can download from the website, but I'm not sure what the next steps are to get there
<civodul>you'll still need to "make update-guix-package" after that
<civodul>these are the two steps i guess (assuming everything builds fine), and the third step is "make guix-binary.powerpc4le-linux.tar.xz"
<civodul>also... we need ppc64 machines for the build farm :-)
<marusich>so the steps would be (1) make changes to guix.m4 etc. so we "officially" support ppc64le, (2) run make update-guix-package (and commit the changes I guess), then (3) make guix-binary.powerpc64le-linux.tar.xz. All of those are required, in that order?
<marusich>I mean, this is just curiosity. I'll do the 3 steps you described, since it doesn't seem like much
<civodul>there are two options: (1) add --with-courage to the 'guix' package so you can run ./pre-inst-env guix build guix, or (2) use "make update-guix-package" after you've made --with-courage unnecessary
<marusich>I'm sure a few things won't work. At least it's easier/faster to debug build problems now, than to try to debug bootstrap binaries (such slow turnaround time)
<civodul>yeah i guess you may encounter build issues
<marusich>By the way, is it intended that all gcc versions in (gnu packages gcc) use #:tests? #f?
<marusich>I noticed that gcc-final, which inherits from one of those, also disables the tests. I wanted to enable them, but I found that it didn't quite work (maybe a bug?), although many tests did pass.
<civodul>it's a choice that was made at the very beginning, but we could/should revisit it
<marusich>I was kind of paranoid about my gcc-final not being tested
<cbaines>Unfortunately, I think a different problem was introduced first, then this problem introduced, then the first different problem was fixed, so I didn't have any luck tracking back to when this specific issue was introduced
<civodul>cbaines: the "tar.gz" extension on the directory looks fishy, too.
<cbaines>yeah, I changed that locally, but it didn't have any effect
<civodul>i may have to do with recent patch-and-repack changes
<cbaines>I think I checked the file permissions with guile-ssh on master, and they matched
<PotentialUser-10>In case it helps someone else, the only guix installed terminal I could find that supports displaying (and clicking!) on hyperlinks output in the result of the 'guix package -l' (list generations) command is *terminology*
<civodul>PotentialUser-10: the command above gives the same results: links are ignored
<civodul>the escape sequences are swallowed though (as with current master)
<civodul>i'm pretty sure i've seen links in GNOME Terminal though
<PotentialUser-10>civodul: terminology is the only one where clicking on the link actually worked, and opened thunar for me. I'll stick with that. The xfce4-terminal and gnome-terminal build options probably are missing a configure flag setting, it's above my pay grade.
<rekado_>this bytecode incompatibility is unfortunate. My system Guix has a slightly different Guile version than the one I got with ‘guix pull’
***rekado_ is now known as rekado
<piemont>Hello, my Guile initrd is failing to mount my LVM volumes despite messages on the console saying that the volume group had been found. Any tips on how to debug the initrd from the Guile REPL? For instance how can I "ls /dev"?
<efraim>I'm getting errors with getaddrinfo in the initrd: In procedure getaddrinfo: Servname not supported for ai_socktype
<piemont>NieDzejkob: thanks! Its strange, the vol group is there under /dev/mapper, but attempting to mount any LVM volume fails with "No such device", even if specifying it with "/dev/dm-<num>". Mounting a non-LVM FAT partition works fine though.
<piemont>Hmm is there an easy way to get dmesg output in the Guile REPL in the initrd? Or do I have to use ice-9's popen?
<apteryx>any idea why guile-ssh is completely broken on core-updates? All the tests fail. Perhaps the openssh version?
<rekado>piemont: is the disk containing your shell not available?
<piemont>redako: Only the initramfs filesystem is available, my root is an LVM lv. Unfortunately only util-linux-libs are in the initramfs so I cannot run dmesg to find out why the mounting fails
<civodul>rekado: it's stored in the ELF by (system vm assembler), but i'm not sure how to extract it
<euandreh>How can I set a package description to the content of a file in the tarball?
<rekado>I’m in a pure environment, ran ‘make clean-go’, rebootstrapped the build system, reconfigured, confirmed that guile 3.0.5 is used, ran ‘make’, and still ‘./pre-inst-env guix build foo’ says ‘WARNING: loading compiled file /home/rekado/dev/gx/branches/master/guix/ui.go failed…’
<euandreh>I started writing code to re-download the tarball, add the file to the store, etc., but it felt as a bad workaround
<euandreh>I couldn't find any examples of this on the repo, also
<rekado>the package description should be a plain string
<euandreh>rekado: I agree on sticking to plain strings on the Guix repo, but I'm still interested in doing this for a custom channel
<benoitj>I have a question around how guix handles .so lookups. I'm using qutebrowser, and it does not see libasound_module_pcm.so* unless I export a LD_LIBRARY_PATH pointing to the modules folder in my .bash_profile. Is this normal?
<rekado>and now ‘make’ complains: error: failed to load 'gnu/packages/cran.scm': No such file or directory
<civodul>i would not do that unless we have evidence that this is a problem for a number of packages
<cbaines>civodul, apteryx on this subject, I've tested reverting cfcead2e515c0dae02127e5a76496463898be6b6, and I get the same error when building guile-ssh
<apteryx>civodul: I don't think it'll change a thing except for the handful of packages that needed an aditional phase.
<apteryx>civodul: also, it's annoying that --keep-failed builds sources are read-only, for hacking purposes
<civodul>dunno i'm more concerned about unexpected consequences
<terpri>is there consensus about adapting descriptions from other free package-management systems, e.g. debian's package descriptions? (mid:firstname.lastname@example.org reminded me of the question)
<civodul>also extra i/o (think chromium :-)), dangling symlinks that cause the phase to fail altogether, things like that
<piemont>After some more digging, neither "xfs" nor "btrfs" is in /proc/filesystems in my initrd
<terpri>i'm not sure if the typical debian description of just a few sentences (e.g. "Firefox ESR is a powerful, extensible web browser with support for modern web application technologies.") is even copyrightable, or if debian specifies a license for them in case they care
<apteryx>civodul: I guess we can wait and see? If there's a problem with it we'll find out soon.
<civodul>my general approach for these things is to opt for very focused changes, defensive programming, and parameters
<terpri>(it's a minor thing compared to just writing a new description but it would be nifty to have an "insert-debian-description" command to autofill the initial synopsis/description for common packages...)
<civodul>terpri: "guix import" usually provides something
<apteryx>cbaines: the file name thing was just that; the file name
<cbaines>part of me thinks that if a branch ends up like this, it would be better to declare patch debt bankruptcy, rename the branch to core-updates-broken, and start again from master
<apteryx>civodul: weird, no? Something going from Guile 3.0.4 to 3.0.5 caused the guile-ssh test suite to return #t instead of 'pass
<piemont>Is it possible to "guix system reconfigure" a guix installation from the livecd or is it required to run "guix system init" and therefore redownload all the packages again? Simple chrooting means guix cannot access the daemon socket.
<cbaines>apteryx, that commit is on master... so it can't be individually causing the failure
<apteryx>civodul: yes, I think the change in behavior was caused by this commit you mentioned
<PotentialUser-84>Is there a package for Guix that contains the haskell 'stack' command? I'm not sure how to search guix packages for 'command named xyz'.
<PotentialUser-84>'guix search' searches by package name and description, not command names
<lispmacs[work]>I added a udev rule to my system configuration for (non-root) access to the USBasp microcontroller. Seems like the rule should be available to guix as a whole, but am wondering what the path forward would be on that. Would the rule get added to some udev rules file in guix repository, or would a package need to be created?
<pkill9>back when i was obsessed with qutebrowser, it was like my dream for it to be in guix, and eventually it came true
<pkill9>especially as i was new to guile and it seemed insurmountable to create a package for it
<lispmacs[work]>I added a udev rule to my system configuration for (non-root) access to the USBasp microcontroller programmer. Seems like the rule should be available to guix as a whole, but am wondering what the path forward would be on that. Would the rule get added to some udev rules file in guix repository, or would a package need to be created?
<apteryx>cbaines: I've made a patch for guile-ssh; will commit shortly
<Ikosit>Hi, i want to package pulseeffects. Pulseeffects needs some search-paths set at runtime to the limiter, compressor, etc. . So i wonder how it is possible to get the path of the plugins (lsp-plugin, calf,…) in the search-path definition since %build-inputs is only bound in the arguments section of the package definition. My current pd: https://paste.debian.net/1184068
***sneek_ is now known as sneek
<apteryx>I'm curious; why do "./pre-inst-env guix environment -n -m manifest.scm" vs "guix time-machine -C channels.scm -- environment -n -m manifest.scm" don't produce the same output?
<apteryx>where channels.scm contains the exact same commit as the one used in Guix source checkout
<mjw>civodul, but seriously, I just tried and here it goes from 14.4 MB/s to 7.3 MB/s but never seems to drop lower.
<civodul>apteryx: we'd have to check the specifics
<lfam>I usually get very fast downloads but, occasionally, they are measured in KB/s
<abcdw>My friend building a package and getting a warning on patch-shebang phase: "no binary for interpreter `python' found in $PATH". Which is kinda expected, because python package has only python3 binary, but not python. How to workaround it?
<apteryx>civodul: perhaps that's expected when working from a non guix-pulled Guix (e.g., from the checkout directly), as it doesn't live in the store. The time-machine command wants to create the /gnu/store/kabcc4kamc1jli6gqksd9iip1jfr6cw3-guix-3299530c4.drv derivation for the Guix commit; the rest must depend on it and thus differ? (thinking out loud).
<civodul>no no, as a way to minimize the impact of the change to what we were addressing
<apteryx>well, if we just wanted to minimize the impact of the change we could add a make-files-writable phase to guile-ssh. The goal here was to be able to rely on the fact that the unpack phases make files writable, in my view.
<pkill9>ngz: well when i changed the inputs rust basically tried to choose only one
<civodul>apteryx: in general i think it's safer to not change the resulting of extracting a tarball; build results can be brittle
<vagrantc>i gave a talk about my solar setup a while back which was admittedly mostly focused on the various electronic bits, but i rambled on a lot about the efficiencies of growing some sunchoke plants which provided shade and food and way more solar efficient
<lfam>Woodworking is a skill that develops quite slowly, but it does develop. A friend of mine does luxury cabinetry and it took him about 5 years of full-time work to get there
<lfam>And, he had done basic woodwork since childhood