<TaoHansen[m]>as a regular user, things are more difficult for me. as an example, from a USB session i was able to invoke `herd start ssh-daemon` without a problem, now as a regular user, `guix package -i openssh` followed by `herd start ssh-daemon` results in `ssh-daemon could not be found`. additionally, configuring anything in /etc/config.scm only results in changes, packages and services available to the root user. when i used
<TaoHansen[m]>NixOS, changes and packages and services were available to all users.
<TaoHansen[m]>how do i resolve whatever cognitive dissonance i'm experiencing here?
<TaoHansen[m]>what parts of the manual should i familiarize myself with? is there a config.scm that applies strictly to nonprivileged users?
<mb[m]2>Packages specified in config.scm are available to all users. Services must also be defined in config.scm, just installing the package won't work. The example I sent earlier should have an OpenSSH service defined.
<rekado>I’d like to hide all build output by default and only print something like “building… (phase 2/7)”
<rekado>this can be disabled with “--verbose”. By default all output would go to log files instead.
<ng0>when the log file location is displayed at the end of the build, that would be a very good idea
<rekado>Another thing I find annoying is that the daemon and guix client both print the same message, e.g a hash mismatch error.
<ng0>python.scm is large. I need to add buildbot and its dependencies, where the one I am working on right now is autobahn and its dependencies. cbor seems like a thing that belongs in serialization.scm ?
<mb[m]2>rekado: have you looked at the puri.sm laptops?
<mb[m]2>thomasd: will you look at disabling this test on 'master' for armhf (only)?
<jonsger>same here. if you have to pick one, I would recommend you to wait at least until begin of next year for the AMD Ryzen Mobile
<jonsger>I expect to see more power for the same money (like with Ryzen, Threadripper and Epyc + the reactions of Intel ^^)
<mb[m]2>Oh no, ceph CVEs. I may have to disable a lot of tests to build the later versions :/
<rekado>mb[m]2: I had not, because I was put off by the misleading advertisement during the crowdfunding campaign.
<rekado>mb[m]2: but looking at the laptops now, I think they might be good for an office purchase.
<rekado>I’m quite attached to the X200 keyboard and the laptop’s durability
<jonsger>rekado: yeah x230+ keyboard isn't as nice as the older ones :(
<thomasd>mb[m]2: Perhaps we should disable (skip) it for every architecture, no? Since it's failing/succeeding in an unpredictable manner (at least on x86_64), XFAIL is not the way to go (should have thought of that before).
<mb[m]2>Yes, but that will cause a lot of rebuilds. So we need a fix for armhf ASAP, then we can fix it properly on core-updates.