<PotentialUser-85>ryanprior: I am using git-fetch to download the tagged version "v0.95" from 2019 instead of the pypi url, since the version available on pypi is from 2015. I have the same problem (no setup.py found) with both versions.
<rekado>Zrythm looks very interesting. The ability to extend it with Guile means that I will *have* to see if I can switch from Ardour.
<ryanprior>Ooh that's cool software, thanks for working on a package for it!
<spudpnds>ryanprior: That's surprising, if I download it from MELPA it's just a bunch of emacs lisp. I'm not sure why guix is bringing in all this stuff.
<ryanprior>Well, for one thing, melpa is perfectly happy to let you install a non-functioning package that lacks its dependencies, while emacs packages installed via Guix come with their dependencies (and transitive dependencies)
<ryanprior>Incidentally, in this case, guix is also perfectly happy to let you install a non-functioning emacs-guix package because that package is just a mess in general
<ryanprior>But John Soo has been working on pulling it into shape so hopefully we'll be putting that parenthetical behind us soon :)
<spudpnds>ryanprior: I'm starting to get that feeling. I struggled a lot to get it to work on an ubuntu system where I'm running guix as a local user. So I thought I'd sping up a guix os box, and it's not any easier :)
<ryanprior>No, the truth about emacs-guix is it doesn't work
<spudpnds>Ok. I'll give up on it for now, and go back to learning scheme :)
<ryanprior>If you're hitting it over and over with a script, you should probably stop that and cache responses instead. If you're just doing it a few dozen times manually in a session, don't worry about it
<Gooberpatrol66>I generated an image with guix system disk-image, and when I boot it, ifconfig shows no network interfaces. I was just wondering if I am forgetting something.
<spudpnds>ryanprior: I see for a number of packages I install I end up with 'cups-2.3.3' as a depdencency. I've downloaded that when I installed emacs, I downloaded that when I installed tmux, I feel caching would be useful somewhere here.
<guixy_>Interesting... multiple machine learning algorithms can predict if source deviates from its build system's equivalent of download->config->make->make test->make install with 90% or greater accuracy. BernoulliNB gives 94% accuracy. MultinomialNB gives 91% accuracy. KNeighborsClassifier gives 95% accuracy. DecisionTreeClassifier gives 95% accuracy. I'm taking the floor for all of these.
<guixy_>When my results are ready and my grades are finalized, I'll let the guix community tear apart this project.
<ngz>Hmm, I packaged wob but I get a segmentation fault when I try it…
<kisaja[m]>those are pretty useless, and only bring vulnerabilitys
<MrtnDk[m]>kisaja There are different opinions on that, but I don't see how those apps would prevent your Guix installation from working. The problem might be something else. Maybe you can share what your problem is?
<kisaja[m]>it came preinstalled so i thought its essential
<OriansJ>kisaja[m]: the only essentials are a posix kernel and a scheme interpreter that can run guix (and MesCC, gash and gash-utils); everything else is a build dependency and a choice.
<db48x>sudo is generally considered essential, but it's not actually holding your system together
<OriansJ>oh and cryptsetup if you luks encrypted your drive
<OriansJ>guix-vits: the TV series breaking bad; main character Walter White started the whole thing because he learned he had lung cancer.
<fonz>leoprikler: guix describe doesn't seem to work here (guix describe: error: failed to determine origin) and doc says it produces a channel. but a manifest is a list of packages, not the same. no? sorry. new to guix.
<OriansJ>guix-vits: you might benefit more from a clone as it is literally C compilers and scheme from hex0
<leoprikler>fonz: sure, a manifest is different from a list of channels, but channels don't have a manifest in the same way, that profiles do
<fonz>leoprikler: That sounds what's I'm looking for. But profile-manifest doesn't exist in the documentation at http://guix.gnu.org/manual/en/guix.html. And it fails here: $ echo "(profile-manifest \"$HOME/.guix-profile\")" | guix repl
<leoprikler>Either way, Guix does not use the "shared" site and instead puts everything in site/EFFECTIVE_VERSION
<leoprikler>so guile3.0-artanis (which should be guile-artanis for consistent naming) would put its stuff in site/3.0 and if someone wanted to use guile 2.2, they'd install guile2.2-artanis, which puts its stuff in site/2.2
<euandreh>Using EFFECTIVE_VERSION as a variable on the package definition would make it easier for inheriting from the the existing artanis package, right?
<euandreh>so that I will create a guile3.0-artanis that inherits from artanis, and patch artanis to use EFFECTIVE_VERSION instead of 2.2
<atw>just wanted to share something I found on bug 43610 (the icecat 78 segfaulting one): I searched for the minimal part of my profile to delete and found that I can delete just the line user_pref("network.captive-portal-service.enabled", true); from prefs.js to avoid the segfault. As rekado_ says in the thread, this is a workaround, not a fix, but hopefully this gets us closer! I'll email this result too :)
<OriansJ>simonsouth: it would also apply to the GNU Guix 1.2.0 Binary and GNU Guix 1.2.0 Source tarballs; which perhaps are the more important piece of the equation because one should in theory be able to build the ISO from the guix install config
<simonsouth>OriansJ: I agree. GNU doesn't seem to offer any of their software via BitTorrent. Not sure why.
<OriansJ>I believe RMS even touched on that point when expressing the benefits of GPLv3
<cbaines>OriansJ, sure, but you can meet the terms of the license by just including the information on where to get the source. At least that's my reading of section 3c in GPLv2
<simonsouth>cbaines: So "make" on its own doesn't build the guile executable, but "make guile" afterwards does. I may just have to remember to do that for now.
<cbaines>Anyway, this is offtopic, and it's probably not useful to speculate
<simonsouth>Not sure why it doesn't work as-is for me, but then I can _never_ get the documentation to build successfully on my machine. I wonder if these things are related; maybe the build has never completed fully and I just never really noticed.
<simonsouth>cbaines: Yes, I believe so. Looks like the problem was that /bin/sh on my system pointed to dash rather than bash, which caused one of the early build steps that updates the documentation's PO files to fail.
<simonsouth>This failure "stuck" since the broken files wouldn't be updated again and wouldn't be removed by a "make distclean" or even a "git clean" without additional options.
<cbaines>simonsouth, OK, I'm not really sure what Guix should cope with as /bin/sh, maybe this is worth filing a bug about.
<simonsouth>After changing the /bin/sh symlink and starting a new build, everything seems to be going okay.
<simonsouth>Well, on this machine I'm hosting Guix on what I know is a rather broken Void "Linux" installation. It's probably safe to chalk it up to that.