<nckx>This is HN we're talking about, so they probably think ‘relevance’ means ‘market share’ or something similarly stupid. No, of course I don't. I think it's the relevance of a trustworthy open system is increasing every year.
<brendyyn>anyone else find with duckduckgo when you search something, get the results page, go to a page, then press the back button, it takes you all the way to the ddg home page instead of the search results. and pressing forward again skips it too. its so annoying
<apteryx>brendyyn: that because you disable LibreJS
<apteryx>nothing Icecat can do about, unfortunately. It convinced me to give another try at LibreJS, though :-). It improved. Can be enabled/disabled without rebooting, whitelisting per domain with wildcards, etc.
<nckx>I wonder how Mark actually manages these updates. He must have some form of automation, or I question whether he's fully human.
<nckx>When he took some time off I basically maintained the linux-libre packages and it was… a lot of work. Very far from how I do things with my own kernels. I'd switch to a diffconfig in an instant if it were up to me.
<vagrantcish>right, i think i helped with one of those updates too
<raghavgururajan>"Errors found in `Notification` component 1:" (qrc:/ui/modules/Linphone/Notifications/NotificationReceivedFileMessage.qml:2:1: module "QtQuick.Layouts" is not installed, qrc:/ui/modules/Linphone/Notifications/NotificationReceivedFileMessage.qml:1:1: module "QtQuick" is not installed
<jayspeer>I'm getting ssl error  when using cargo from guix (foreign distribution ubuntu); is there an env var I should set? curl from guix resolves crates.io just fine
<ericst>Hello, I am trying to package supbackages from a git repository that countains a few... Is there a possiblitlity in the package definition to tell guix to run the build phases in a subdirectory ?
<rekado_>ericst: you can run any build phase again, but I recommend unbundling instead.
<rekado_>oh, it’s not a loop. It’s just generating different files.
<rekado_>but each time it has to load the same files, and that’s really slow
<rekado_>I wonder if the regular Emacs build does the same or if it compiles the files first.
<rekado_>something doesn’t seem to stick. It regenerates autoloads, for example, the same again and again, for each file that it tries to generate.
<zzappie>following yesterday and today's hot conversation on Hurd/Linux support I have a question. what does "kernel support burden" mean? I understand that there are many linux specific features like namespaces, /proc etc... But can they be abstracted? As an example I thought first - libvirt is basically a common API for many types of hypervisors which are very different. Can guix in theory be structured in a way that differnt kernels support
<mbakke>dutchie: I don't think so, would be a great Cuirass patch though
<mbakke>dutchie: I typically search for "<package-name> spec:guix-master" and go from there
<mbakke>jayspeer: not yet, but soon! civodul and others were trying really hard yesterday to add that functionality for the April 1st blog post, but in the end we had to cheat with a Debian base image.
<reepca>hmm, I've got a substitute download that's stuck partway through. That's the third time I've noticed that within the past day or so, but I also changed my router recently-ish. Netstat says it's in the ESTABLISHED state, and wireshark hasn't mentioned any traffic on that connection in the past 5 minutes or so. Have we changed up any of our downloading code recently?
<dutchie>ahh, ./bootstrap, that's the one, thansk civodul
<reepca>strace has it waiting on a recvfrom currently
<reepca>TCP connections should either be reset automatically or continue working if packets fail to make it through for a minute or so, right? The connection to the outside world is a bit spotty here, but it's certainly working now, so I'm wondering if it somehow ended up in a broken state?
<mbakke>in the next core-updates round I intend to inline the phases anyway so that Python can be changed at will.
<terpri_>J[m], i haven't heard of major upgrades in the coming months, but you've waited long enough to get the second-generation version of the cpus :) with some upgrades to hypervisor/ultravisor support iiuc
<mbakke>but copying all the phases is quite an ugly workaround for a not-so-big problem (rebuilding Python on i686 and x86_64).
<terpri_>might be considering how much bloat it would add to just add all the fs utils to %base-packages; people will often want to removable drives with random FSes, regardless of static filesystem configuration
<nckx>Any reason they can't install foofs-tools when they do? bricewge: No guidance, just: how?
<jonsger>terpri_: yes, LE should be simpler on userland. But LE is harder to bootstrap in Guix due to required versions of gcc and glibc in the bootstrap path...
<brendyyyn>btrfs is exotix? i thought it was the recommended default filesystem now
<joshuaBPMan>Hello guix!!!! Way to make an awesome announcement on the Guix blog! I've only read Phoronix's article about it....now I need to go digest the blog post. And paste it on my wall at home. And Read it every night.
<bricewge>nckx: Than plan was to extend the system-profile from file-system-service-type by tweaking file-system-packages (gnu system linux-initrd)
<nckx>This is a file system that can't even read from more than one drive at once. It's great for basic home use & hobbying & very specific things like they do at Facebook. I'd never recommend it as the default file system for a distribution.
<bricewge>nckx: Do you mean what I suggested can't work?
<brendyyyn>mbakke, ext4 doesnt even checksum anything right? seems silly to recommend it in 2020. what is the recommended one then?
<mbakke>brendyyyn: ext4 definitely! probably the most battle tested file system out there, maybe except for NTFS.
<brendyyyn>i thought it has no silent data corruption protection though?
<nckx>I think ZFS is the only reliable file system that does.
<alextee[m]>rekado: it looks like we'll have to deprecate the old zynaddsubfx UI. the program is essentially the same, however it uses the same LV2 URI for the plugin and the same URI for the old and for the new UI, and this causes many problems if we keep both. there is no need to keep the old zynaddsubfx because it's essentially the same program with a refreshed UI, and it exposes everythign the old UI did. so i guess i should create
<alextee[m]>a zynfusion package and somehow mark zynaddsubfx as deprecated?
<rekado>so that users won’t accidentally install both of them
<alextee[m]>that would be nice to have, im not sure why guix doesn't have that feature yet
<nckx>alextee[m]: You're making too many assumptions about hosts. AFAIK qjackctl doesn't use ‘URI‘s over here 😉
<waynedpj>ahoy all. just read the blog post about the move to GNU+Hurd and the phasing out Linux Libre. interesting news, just wondering if there is any background on the the decision, i.e. mailing list archive, IRC logs, blog post? a quick search did not turn up anything. thanks.
<alextee[m]>nckx: well, if you only use the binary, it would be fine, but if you use thet plugin, every host uses the lilv library to detect lv2 plugins, and that skips duplicated URIs
<andydarcyjewell>I've been using the --keep-failed option to test out what's happening with my problems with packaging Factor
<andydarcyjewell>Even with freshly grafted-in sources and boot image, I get the same problem, so I don't think it's any kind of patching that's causing it. Any suggestions where else to look, please?
<rekado>the error is reported by Factor, isn’t it? Can you build with debug symbols and run it in gdb?
<rekado>or even check with strace to see what it tries to do when it fails?
<andydarcyjewell>rekado: I can give it a go. Not used strace much, and never tried gdb. The error it's giving is that "Invalid header" one, but I think it's erroneous, because the exact same file works on a binary created the prescribed way.
<andydarcyjewell>I'm suspecting now that the error is more related to the way the code checks the header, rather than the header itself - that it is somehow misinterpreting it. Will re-acquiant myself with strace, and see what I find.
<mbakke>civodul: any thoughts on merging the GRUB localisation work mentioned above?
<rndd>hi everyone! i encountered an error after installing virt-manager "cannot connect to virtlogd: failed to connect soccket to /var/run/libvirt/virtlogd-sock: no such file or directory" and didn't find solution. Does anybody know a way out of this?
<rekado>dutchie: submitting this upstream could help
<civodul>i would mark it as "normal" or even "wishlist"
<rekado>dutchie: if you do please also note this for 40388
<raghavgururajan>rekado You are right. That should not be marked serious. I may have used wrong bug number.
<ngz>I have a packaging question. I packaged a set of two Emacs themes using Github repository. Now, upstream also released their two themes separately in ELPA. What is the best way forward? Keep updating set from Github? Package both themes from ELPA and deprecate Github source?
<nckx>I'd take that upstream patch, take a look at the file it patches. If it hasn't changed significantly, create a copy of it, insert that hunk of code manually, then diff your new copy with the old one to generate a patch that will work in (patches (search-patches …)).
<Gooberpatrol66>The April 1 Hurd image freezes at "start ext2fs: Hurd server bootstrap: ext2fs[device:hd0s2] exec"
<FennecCode>So... I kinda hate to ask this, but is dropping support for Linux-Libre in the next release an April fools joke, or is it genuine? I really can't tell. It's not a bad move, but it's a big commitment.
<civodul>Gooberpatrol66: did you use the QEMU command line given in the blog post?