IRC channel logs


back to list of logs

<sughosha>Hi all! Could someone look into this patch? <>
<peanuts>"[PATCH v4 0/7] gnu: Add yabridgectl."
<sughosha> <>
<peanuts>"[PATCH 0/7] Add some themes and extensions for KDE Plasma."
<mekeor>ACTION hates this bot
<nckx>mekeor: Why?
<mekeor>nckx: i prefer bots that only talk when explicitely asked to do so. even if it shall deliver URL-details without being asked, it could at least avoid mentioning the link again
<nckx>futurile: Not looping as in circular, but a few propagated-inputs can ossify a profile so almost everything has to be updated in lockstep. Sometimes there's no other reasonable way to make things work. Often there is.
<nckx>mekeor: Yeah, not echoing the links seems like an easy fix. It doesn't check whether the original message already contained it.
<KE0VVT>Where can I look at others' Guix Home configurations?
<voroskoi>adding (udev-rules-service 'light light) to my services does not append the udev rules
<voroskoi>shall I wrap it to something?
<attila_lendvai>is it ok to add this-package in its own native-inputs? doesn't it introduce bootstraping related headaches? (
<peanuts>"guix.git - GNU Guix and GNU Guix System"
<voroskoi>oh, it works, but i do not see the file in /run/current-system/lib/udev/rules.d
<voroskoi>how does this work?
<Lumine>Good morning #guix
<futurile>Morning Lumine
<jpoiret>attila_lendvai: that's only for cross-compilation so it's fine
<Lumine>It seems `guix gc' borked my icecat the same way as described here:
<peanuts>"bug#61914: IceCat does not start with en_GB.utf8 locale"
<Lumine>What worked was creating a new profile in icecat
<tux1c>has anybody successfully built guix for 32bit raspberry boards?
<tux1c>i'm using the raspberry-pi-64.tmpl and adjusting it for arm-linux-gnueabihf, and gawk fails on the test phase, i wonder if anybody has had any similar experiences..
<voroskoi>after installing git:send-email i still get "git: 'send-email' is not a git command" error
<lizog>hello guix, i was trying to cross compile a system image for aarch64 on a x86_64 machine, but when trying to build gawk-mesboot it fails. i noticed on guix-patches someone asked about the same question several days ago but got no reply:
<peanuts>"aarch64 system cross compilation + pinebook pro image broken?"
<lizog>i think cross-compiling a system image shouldn't trigger the bootstrap?
<bonmlp>How can I run an sshd server in my guix system? I guix installed openssh but herd start ssh-daemon says that service doesn't exist.
<voroskoi>bonmlp: configure the service, something like this:
<peanuts>"Using the Configuration System (GNU Guix Reference Manual)"
<bonmlp>Do I have to write a whole config.scm from scratch?
<voroskoi>bonmlp: the config for the current system is /run/current-system/configuraion
<voroskoi>you can edit that file, put it anywhere (it is a good thing to keep it version controlled)
<voroskoi>and sudo guix system reconfigure my-config.scm to reconfigure the whole system
<bonmlp>voroskoi: I copied that file to /etc/config.scm and ran guix system reconfigure /etc/config.scm but it errors out while looking for a channel from a git repo under /home/ludo which doesn't exist.
<bonmlp>Actually, should I do that reconfig as root or as an unprivileged user?
<voroskoi>if you forgot sudo it will report symlinking issues, so you need root, but Your problem is something else
<voroskoi>paste the config.scm somewhere, so I can take a look
<bonmlp>voroskoi: I'm going to try from scratch.
<tux1c>lizog: i have the exact same issue with 32bit arm system configuration, gawk-mesboot fails on the configuration stage :/
<nckx>voroskoi: Did you install git:send-email into the same profile as git? That's a requirement. While you can 'stack' different profiles (e.g., your system profile bleeds through your user profile), packages in different profiles don't 'interact' as closely.
<gcarlos8>Hi guys, how can I install a 32-bit package on a x86_64 system?
<gcarlos8>nckx: what's the diff of --system and --target?
<nckx>gcarlos8: --target=i686-linux-gnu cross-compiles: it uses an x86-64 'cross' GCC to build an i686 binary. --system=i686-linux (note the slightly different argument) actually uses an i686 GCC to build an i686 binary.
<nckx>Cross-compiling is often more of an adventure.
<nckx>Sometimes you want adventure, or you need it. Sometimes you don't.
<nckx>(Also, many things don't support cross-compilation 'yet'.)
<mirai>never imagined that writing a commit message in changelog format would take nearly 1h30m
<gcarlos8>nckx: thx!
<gcarlos8>how do I declare packages with --system in scm?
<alxsim>In the cargo-build-system, any way to stop cargo trying to fetch dependencies from git and use instead defined packages from guix? It's trying to do "Updating git repository ``"
<peanuts>"GitHub - typst/self-replace: Utility library that helps to implement processes that replace themselves"
<mrh57>is there a way on wayland to get laptop screen to lock (say with swaylock) on lid close -> sleep?
<mrh57>also more generally: how to find documentation on the configuration options for a given service?
<mirai>mrh57: the guix manual usually has them
<mrh57>that's true. elogind-service should probably be updated at some point since it's deprecated
<mirai>? is that still mentioned in it?
<ieure>Is there some way to tell the guix command to output plain text? My $TERM is set to "dumb", but `guix describe` / `guix system describe` have a bunch of escape sequences in the output, so it looks like trash.
<Guest89>dave@host /mnt$ sudo mount /dev/sdg /mnt
<Guest89>mount: /mnt: wrong fs type, bad option, bad superblock on /dev/sdg, missing codepage or
<Guest89>helper program, or other error.
<Guest89>I am trying to mount my usb stick.
<Guest89>does guix need a special file system?
<ieure>Guest89, No. You probably need to mount /dev/sdg1
<ieure>/dev/sdg is the file representing the whole device, you usually have a partition table with a partition containing the filesystem. That should be /dev/sdg1 (but might be something different, depending on the way the drive is partitioned.)
<Guest89>ieure you  are right. It works now . Thank you
<ieure>Glad to help!