<apteryx>I did find some strange things though... reconfiguring on very close configs, it seemed like the system generation didn't change; sometimes reconfiguring upon a working version of my config magically "enabled" a previous one which shouldn't have worked. It was all very confusing and I don't still understand what exactly was happening.
<mbakke>nckx: huh, I always prefer to purge bundled source code to guarantee that the system libs are used; make the source smaller (easier to audit); notice if the unbundling becomes ineffective in the future, etc
<mbakke>nckx: do you think we should run the ungoogled-chromium scripts in a phase instead of a snippet then?
<nckx>That makes it sound like I'm in the ‘snippets are only for FSDG issues’ camp. I'm not really. If you want to add a snippet & patch the Makefile to remove some assumptions about zlib/ and popt/, fine by me mbakke. 👍
<brendyyn>is there guix-vits how do you make .onion work on guixsd?
<mbakke>nckx: right, patching build scripts is no fun, especially when unnecessary... I thought it was an easy delete-file-recursively :-)
<guix-vits>brendyyn: i do that wrong: `tor --runasdaemon 1`, then a Web-browser's proxy settings.
<mbakke>raghavgururajan: looks like CMake fails to locate the bcunit input
<guix-vits>brendyyn: then browser is accepting the onion addresses as usual ones.
<brendyyn>would be good to have systemwide .onion support
<guix-vits>brendyyn: idk; i'd heard that anything "system-wide" with a tor is a SSEPA (Self-sustained-evil-pinnocio-approach). Like "make a strong wall between you strictly hidden and strictly puplic activities". For fan, there was some instructions on Tor's Wiki and Arch-Wiki.
<mbakke>rekado: OK, I'll do that, so that we don't have to introduce more modules in python-xyz when they get updated (I have patches to update them too, but it breaks all the users.. required for core-updates though).
***wxie1 is now known as wxie
<brendyyn>Hmm, I don't know if it is correct to wrap a program with prefix or =?
<brendyyn>prefix would mean it would also have the users PYTHONPATH appended, = wouldn't. But which is correct for a user application?
<rekado>“prefix” means that the environment variables that the user sets are augmented. With “=” they are overwritten.
<rekado>I encountered are a couple of problems with “prefix”, especially when using PYTHONPATH, as it doesn’t seem to be processed in order.
<brendyyn>rekado: Yeah I just investigated wrap-program and learnt that, but I don't think there is any guideline
<rekado>for a Python application I would probably pick = nowadays.
<rekado>(and I use wrap-script instead of wrap-program)
<brendyyn>nckx: I'm testing it. it looks like it involves rebuilding just about everything
<NieDzejkob>brendyyn: yeah, that's why we're talking about core-updates
<nckx>brendyyn: Yeah, that's the problem and why it isn't merged yet. It needs to go on core-updates. I naively thought (‘think’ is very much the wrong word here) only of wrap-scripts very few users, not the rebuild-the-world module that contains it.
<NieDzejkob>maybe we should break up (guix build utils) somehow?
<nckx>You can copy, past & fix your own wrap-script/brendynn to test, if that's worth anything now.
<nckx>brendyyn: It was. I guess nobody used it [in some specific way].
<nckx>raghavgururajan: Yep, I'm updating it as we speak.
<raingloom>sorry, i need some quick help. how the hecc do i mount a WebDAV file system? sftp finally works now, but gio tells me it needs glib-networking and i installed it and it still doesn't work :|
<brendyyn>mbakke: turns out my /etc/environment had load paths for 2.2 since i first set it up, so i set them to 3.0, now ive upgraded to a new error guix/ui.scm:1833:12: In procedure run-guix-command: In procedure =: Wrong type argument in position 1: #f
<apteryx>is /bin/sh visible in guix environment --container but not in the build side container?
<apteryx>Cause for emacs-elpy I'm debugging right now I can't see much input from the failure, it stops hard at: Searching for program: No such file or directory, /bin/sh, while I don't get this in guix environment --container
<apteryx>and of course it's explained in the manual in 7.1.4 Debugging Build Failures
<apteryx>I can do 'rm /bin/sh' in the container environment :-)
<nckx>And this is exactly why I think we shouldn't have an opt-out flag for tests: were are all lazy girlz and boiz and doggoz and if you're first instinct was ‘tests are failing, how do I disable them’ that doesn't bode well for the rest of us.
<joshuaBPMan>raghavgururajan: have you tried twinkle? it works well enough for me.
<nckx>raghavgururajan: #:tests? #f isn't a hack since it changes the hash (as it should). An untested package isn't ‘equivalent’ to a tested one. What folks fresh from other distros sometimes ask for is ‘guix build --skip-tests foo’ → /gnu/store/identicalhash-foo/, or a road straight to hell.
<lfam>(I don't know anything about locales unfortunately)
<lfam>Even 30 megabytes would be a tremendous improvement for us
<cbaines>I'm not sure, but if you download the package (you can click the small "all" link towards the bottom of the page I linked to), open control.tar.xz, and then some of the scripts like post-inst, it's calling things like locale-gen
<nckx>lfam: I dunno, you've volunteered. I was thinking of a nice (glibc-locales (list …)) procedure that returns a package.
<lfam>I like the idea nckx. Do you know the status of the effort towards parameterized packages? Can we use that work here?
<nckx>By the way, I *do* sympathise with people who want to keep their system small and relatively (urg) un-bloated. I'm one of those folks. But I don't think we're obligated to provide everyone's dream -minimal package to do so. That's the deal. You want custom, you learn.
<nckx>lfam: I haven't heard anything more about that at all, now that you mention it.
<lfam>I agree nckx. If it's big, it's big. But I don't want to leave any big gains on the table
<mbakke>hmf, I knew I should have delayed the far-reaching libjpeg-turbo and util-linux:lib changes on core-updates until it was 100% guaranteed ready to go, there are difficult merge conflicts with every merge now :/
<mbakke>I'm so used to these merges now that I don't really think twice about it... I could not have done them so swiftly if I did not read almost every commit on the master branch and make mental notes "this must be adjusted when merging to branch X".
<mbakke>by swiftly, I mean spending an hour checking just about everything I can think of :-/
<mbakke>the absolutely worst thing is finding a problem after making the commit (and pulling it for good measure), finding a problem, and having to start all over...
<sirgazil>Do you have to modify system configuration files somehow to be able to create virtual machine images with "guix system vm-image"? Because I'm getting this backtrace when I use my system config without change: