<nee`>sneek: later tell ng0 I fixed or worked around most of the problems I had with GNUSocial and got some patches merged upstream. I have do some more testing and then I'll send an update during the next week.
<efraim>guix build: error: build failed: a `armhf-linux' is required to build `/gnu/store/jzp3gjr3ln0j8cixpvpg7p0km3hyflic-Linux-PAM-1.3.0.tar.bz2.drv', but I am a `aarch64-linux'
<efraim>ludo made some changes for cross building before
<soundtoxin>str1ngs: I haven't got around to trying your deluge package yet. I am not sure how to use it.
<soundtoxin>Also, can someone tell me how I get an ssh server running? I've installed openssh and can do an outgoing ssh connection, but not sure of the process for getting the server working. If I try the thing from the install for getting one up, it doesn't work.
<str1ngs> soundtoxin just clone the repo and add it to GUIX_PACKAGE_PATH
<str1ngs>soundtoxin: add a openssh-service-type to services
<jrandall_>I managed to use `guix system vm-image` to build a qcow2 image that works on our openstack cloud, but to do this I found I had to change the `file-systems` declaration in the definition of `system-qemu-image` in `gnu/system/vm.scm` (it appears to be hard-coded to install to `/dev/sda1` whereas the virtio driver on openstack makes the root filesystem available at `/dev/vda1`). I thought I ought to be able to set that in the operating system de
<jrandall_>Oh, my earlier message got truncated - the end was: I thought I ought to be able to set that in the operating system declaration that I passed to `guix system` but file-system settings there seemed to be overridden by the definition of `system-qemu-image` in `vm.scm` - is that correct, or is there some other way I am supposed to override that setting?
<brendyn>Does anyone know if any of the latest nvidia cards like 1080ti work with nouveau at all?
<rekado>For the record: there *are* rules for this channel.
<rekado>for the whole project we abide by the code of conduct that is part of the Guix git repository.
<rekado>This channel is about Guix development within the context of the GNU system.
<mlin>amz3: How would I enable some of the modules on the polybar wiki? I forgot about that part
<rekado>it’s not a problem to veer slightly off topic for a while, but it’s good to get back on topic quickly, especially when it’s pointed out by someone else.
<rekado>on this channel we don’t want discussions about non-free software and how to get it to work in Guix.
<rekado>I don’t have the full logs of the discussion above, but talking about getting firefox to work is not off topic here.
<rekado>getting it to work through Nix on GuixSD is barely on topic, but I guess we had worse.
<rekado>to those using this channel as a log of what they are currently doing, even if it has very little to do with Guix: I’d like you to remember that we have many newcomers here, who may feel alienated by long monologues.
<catonano>"Keep the build tree of failed builds. Thus, if a build fails, its build tree is kept under /tmp, in a directory whose name is shown at the end of the build log. This is useful when debugging build issues. See Debugging Build Failures, for tips and tricks on how to debug build issues."