<lfam_>I think that "modern" and "clean" are hard to judge. I think we can assume the software is reliable. And keeping privacy in mind is hard to judge without a description of how it does that (for example, does it use the Signal protocol? OTR? PGP?)
<lfam_>It seems like every communication tool claims to keep our privacy in mind these days
<raghavgururajan>lfam_ I agree with the mordern. But the line about clean and privacy, it says it focuses, like in one-going work or objective.
<lfam_>What does it mean to be clean? They washed it with soap? :)
<vagrantc>i guess, for me, this will be "guix nights"
*vagrantc also failed to watch anything yet, but should resolve that later tonight
<kozo[m]>mothacehe Hey, I built the iso for guix PBP. I dd'ed it on to the microsd card but the PBP doesn't boot from it. When looking at lsblk, it's a single partition, there is no boot partition. Is there something I had to do?
<vagrantcish>there shouldn't be a boot partition for the pinebook-pro
<ryanprior>I have a few go packages I'm working on that have mutual dependencies, eg each depends on the other. This is not super uncommon in the go world - it basically means that any time you grab source code for one package, you also need the source code from the other. One package in practice, but with separate repositories and namespaces.
<ryanprior>My thought right now is to have an outer let- form that binds the origin of each package, and then in the package definitions, use those origins as inputs instead of using the actual packages.
<ryanprior>So given mutually dependent packages A and B, the package for A uses the origin for A as its source and the origin for B as its input, but doesn't actually depend on B; and vice-versa.
<ryanprior>Does that make sense? Is that abusing the Guile language features, or is that using them as intended? Is there a better cleverer or more idiomatic way of doing this?
*vagrantcish wonders how long efraim's talk is supposed to be ... seems to cut out at ~16 minutes when explaining vim
<lfam>We don't currently have that version packaged, although we do have 2.0.14 (I assume it's part of the same series and basically a collection of bug-fixes)
<lfam>We do use 2.0.9 as a "bootstrap" binary and it might be possible to launch it from the Git repo but that's not really a first-class use case
<chrislck>ok. I guess it'll be difficult to create a package locally to test 2.0.9?
<chrislck>(because 2.0.9 is the minimum supported guile for gnucash and /me wish to test a few @future things)
<lfam>I honestly don't know how difficult it would be. It's easier to make custom packages for Guix than for e.g. Debian, but that doesn't account for any difficutly that may be inherent to Guile 2.0.9 itself
<lfam>It might be possible to define a new package guile-2.0.9 that inherits from guile-2.0 and basically just changes the version and source hash
<nckx>For quick tests you could use guix time-machine with commit 78636f0b8ce0fa7c3483a378ef31832f38a3d19a but all other packages will be from 2016 as well.
<janneke>nckx: terrible tinycc details: tcc adds libtcc1.a at the very end of the linkage line; if nothing uses memmove before, but libtcc1.a does (because it was compiled by tcc and it emits "memmove"), then memmove is an unresolved symbol
<janneke>(adding an extra -lc just puts that in before libtcc1.a)
<janneke>also, libtcc1.a cannot come with its own "memmove", because then memmove is defined twice
<PotentialUser-86>Greetings ! I was wondering if there ever was a talk about creating a Guix wiki page, similar to the ArchLinux one ? And would there be any complications that I didn't think about other than just maintening the website ?
<zimoun>Thanks everybody for participating! I have learnt a lot and refill with new ideas and energy.
<eth01>nckx: awesome, thanks. I believe the dns issue was merely an intermittent issue, unable to replicate in UK and other core locations we operate from, but I agree there is an intermittent issue somewhere in our global infrastructure :)
<nckx>I'm in Belgium and got consistent (negative) results.
<raghavgururajan>In their presentation, I wonder what 'module system' and 'implicity' means.
<jonjitsu[m]>I'd like to install guix package manager/build system in an existing ubuntu system and I do not have enough disk space on / for the store. I was thinking of bind mounting a directory from another partition at /gnu and then running the setup script. Will this cause any issues?
<rekado_>(the chorus is the story of a contribution: sharing as others have shared, evaluating the patch, procrastinating on bugs… then countless recompilation in pure environments; and the first letters are always R E P L)
<lafrenierejm>What's the process for using packages provided by custom channels in `guix system reconfigure`? Trying `sudo -E guix system -L ~/etc/guix/system reconfigure ./etc/guix/system/desktop.scm` gives me "no code for module".
<cbaines>lafrenierejm, -L should come after reconfigure I believe
<brettgilio>Yes. cbaines is right lafrenierejm reconfigure is the command for system. Your syntax order is wrong
<civodul>yeah, they're not adults yet in that respect ;-)
<roptat>ok, I had a call with someone that manages fedora's weblate. We've set up something at https://translate.fedoraproject.org/projects/guix/ (not sure if you can see it) that temporarily uses a repository that I manage at framagit; hopefully we can migrate to the savannah repo as soon as it's accepted there, but discussions seem to have stalled...
<raghavgururajan>nckx: My first reaction on seeing "web-based" was "Oh boy!". I think it is better to have web-interface to a software, instead of making the software itself web-based.
<vagrantcish>what was crazy is i don't think i even changed the word order ... it was basically a reverse-order of what i got with: git log v1.1.0.. --author=vagrant --extended-regexp --grep='spelling|grammar|typo' --patch