<THFKA4>anyone got a link to an example config that uses wayland? ***Elon_Satoshi is now known as Copenhagen_Bram
***rvgn1 is now known as rvgn
***MinceR_ is now known as MinceR
<rvgn>civodul How the upcoming Guix versions going to be tagged? stable, non-stable, testing ...?? <civodul>rvgn: Guix remains very much "rolling release" style <civodul>so there won't be branches like you have in Debian <civodul>it turns out that the functional paradigm makes the the rolling release model affordable: we can test things very easily <civodul>it's much harder for a traditional (imperative) distro to make sure an upgrade somewhere doesn't break something elsewhere <rvgn>civodul No no understood that there will be no branches for guix system. But is it even for guix? Like when I do guix pull there will be new version each time right? <rvgn>Like once Guix 1.0 is released, and if you folks started to work on Guix 1.5 or something, will that Guix 1.5 tagged as beta until Guix 2.0? <rvgn>civodul Will there be a GUI front-end for Guix Package Management? <rvgn>civodul Never mind about the former. I got it now :) Please let me know about the GUI part. <civodul>rvgn: re beta tagging, no, i don't think so <civodul>as for the GUI, why not, i think it'd be nice if GNOME Software could use Guix as a backend <civodul>nobody has stepped up to work on that yet! <rvgn>civodul That's awesome to hear. <brendyyn>But will the way master is used changed? I kinda wish everything would first go to a testing branch for a short time before going to master. Then guix users can choose if they want to be a regular user or a tester. developers will generally put themselves on this testing branch by default allowing them to test other peoples patches with 0 effort. Currently testing requires going and getting peoples patches off <brendyyn>the mailing list and rebuilding, which is tedious. Currently, if things are still how they were a year ago, small contributions go Submitter -> one reviewer -> every guix user on the planet. And there have been occasions where master is broken in preventable ways because of this. Perhaps if it was like Submitter -> Reviewer -> testing (5 days) -> master, it would be more sensible. <civodul>brendyyn: if you've seen the automation work by cbaines_, that sort of goes in that direction ***cbaines_ is now known as cbaines
<cbaines>Yeah, although I've been looking at trying to automate the testing of individual patches, as I think that would avoid having to hold patches on a testing branch, and instead just merge them in to master. <cbaines>If the testing process for patches can get more rigorous, then hopefully things on master will break less often <brendyyn>I'd like for it to not just have awesome automated testing, but if patches can go into a testing branch very easily rather than sitting on the mailing list, then any user is only one guix command away from building and testing a given submittion <cbaines>I'm not quite sure where a testing branch comes in to it... but as part of the stuff I've been working on, I've been generating Git branches corresponding to series of patches sent to the mailing list <cbaines>brendyyn, are you talking about people testing patches by using Guix pull to get the changes on their local machine? <brendyyn>it would split guix users into two groups, normal users and testers <brendyyn>normal users would be a little bit behind the head except for urgent fixes <brendyyn>i think i have far too many packages to do that <brendyyn>it would be cool to make a spacemacs package <Blackbeard[m]>I have my-bindings.el, my-org.el, my-generic.el, my-lisp-programming.el <Blackbeard[m]>I didn't do it in one huge remove and installation of packages ***notnotdan` is now known as notnotdan
*civodul gets side-tracked and plays with self-referential records <roptat>is it possible to use wisp in guix configs? <civodul>but what rekado_ and zimoun reported makes me skeptical <kmicu>civodul: reported on IRC or on ML? Was that about wisp in general or issues specific to Guile integration? ***joehillen_ is now known as joehillen
<XWill>I need some help: i'd like to run Freecad from the appimage found on the website, i thought i have to use guix environment but i did not find a way to run this application. The same is true for all others programs distributed in binary format. What is the right way to do that? ***paroneayea is now known as dustyweb
<civodul>kmicu: no, rekado_ talked about the experience using Wisp in the GWL when we were at FOSDEM <civodul>there's a Flatplak package in Guix, but nothing for AppImage (what is it actually called?) <civodul>my recommendation would be not to run those big opaque binaries, though <XWill>thank you civodul, i will look for a flatpack package then. I'm not able to make a guix package for such a big thing. <civodul>hmm 'guix system docker-image' seem to produce a truncated tarball ***rekado_ is now known as rekado
<rekado>I would like to see wisp support in Guix, but I’d like it even more if Guile itself supported #lang declarations. <rekado>cuirass was disabled and stopped <rekado>in related news: we may get new servers for the build farm soon. All old servers are likely going to be replaced within the next few months. <lfam>The new libssh2 1.8.1 is broken :/ <lfam>From that thread, it also seems that 1.8.1 was "pulled" and "republished" with some changes so it's possible that our package will have the wrong hash... <lfam>I can look at this later <anadon>Is there a place I can throw my 2 cents for feature requests? <lfam>anadon: I recommend mailing it to <guix-devel@gnu.org> <anadon>lfam: Is that a filtered list I need to subscribe to first, or can I post directly to it? <lfam>anadon: It's an open list but your first message will be moderated, so it may take a little while to show up. As long as your mail doesn't get bounced you can be sure it will go through <Blackbeard[m]>GitHub - domtronn/spaceline-all-the-icons.el: A Spaceline Mode Line theme using All The Icons for Emacs <lfam>Blackbeard[m]: Yes, it is freely licensed so it's okay <lfam>You don't need to follow every recommendation in there. Especially The Perfect Setup... not everything is perfect :) <lfam>I just meant, don't get hung up on that stuff if it's too much, Blackbeard[m]. The important thing is to write and submit the patch. The Guix community will guide you as necessary <rekado>(specifications->manifest …) on a list of packages *sometimes* works and sometimes it doesn’t. <anadon>OK, email in. I'm way too overcomitted to do the coding (I'm sorry!) but I hope the brain time helps. <buffet>hey, hows guix with 32-bit hardware? do i have to compile everything myself, or no? <nckx>buffet: No, but there tend to be slightly more bugs/temporarily broken packages due to fewer testers. <buffet>nckx: time to become a tester then :^) <roptat>so I received my ssd and tried installing guix on it, but there's still something that's not working <roptat>guix doesn't seem to find the disk, I am still missing a module? <lfam>roptat: What do you mean that it doesn't seem to find the disk? The installer kernel doesn't see it? <roptat>I don't use the installer, I use a foreign distro to install on the ssd <roptat>so the error is at boot, I get the repl where I can run (find-files "/dev" "") and I don't see /dev/sda or anything like that <roptat>I only get /dev/mmcblk0, which is the sd card reader where the foreign distro is installed <lfam>How is the storage attached? <bavier>katco: it should probably be added as a new license <katco>darn! and the yak-shaving continues ;p <bavier>katco: it happens :), but adding a new license is trivial. <katco>yeah it doesn't actually look bad at all <bavier>katco: do other FSDG distro's distribute packages under this license? <bavier>oh, I see the cliki is part of debian <bavier>but the fsf.org/licenses page doesn't mention the LLGPL, might be nice to get a confirmation from licensing@fsf.org that it's legit <lfam>I'm testing a fix for the VLC / libssh2 issue <roptat>so, according to udevadm, I need something called sunxi-ahci, so I'm reinstalling the system again :/ <civodul>and still no useful hints from 'guix system'? <civodul>roptat: 'guix system' normally suggests modules to add to 'initrd-modules'. <roptat>mh... it was ahci_sunxi, not ahci-sunxi :( <roptat>so loading the right module made it find the ssd, which is great, but still no /dev/sda <roptat>[ 112.857606] ata1.00: ATA-11: Samsung SSD 860 EVO 500GB, RVT02B6Q, max UDMA/133 <civodul>you're doing the 'guix system init /' method? <roptat>almost, I init from the foreign system on the sd card, and I install to the ssd <roptat>so guix system init /etc/config.scm /mnt <rekado>civodul: good catch re the truncated docker images! <rekado>I had always been lucky in generating them — as far as I know :) <civodul>rekado: yeah it probably depends on various factors