<orneb>Yes, I'm on Guix System thanks! Are you also familiar with this error that I get after starting Sway on tty1? [backend/session logind.c:511]User has no sessions [backend/session/logind.c:559] Couldn't find an active session or a greeter session
<vagrantc>you might need to add an elogind service?
<orneb>To run Sway I had to add export XDG_RUNTIME_DIR=“/.run/swaywm" to my .bashrc then mkdir -p $XDG_RUNTIME_DIR and chmod 0700 $XDG_RUNTIME_DIR, but I get those errors. Is this because no display manager is installed?
<Maya[m]1>i actually used home-sway-service-type from rde, i cant recommend it enough
<orneb>Thanks vagrant, I'll try with elogind and see what happens.
<vagrantc>i tried getting the smallest configuruation possible, as i was running it on a pinebook pro and aarch64 substitutes weren't generally available reliably
<orneb>:Maya I prefer not to run a display manager since I'm using an old laptop and it already takes a while to reach the login prompt despite having an SSD. 20s to unlock my luks drive, then I have to enter my passphrase a second time. I intend to enable the auto login for the user on tty1 as soon as I fix the Sway error. Was wondering if something like this were possible on Guix. https://wiki.archlinu
<vagrantc>orneb: i doubt that's possible, because the initrd is in the public store, so would be a security issue for anyone able to read the initrd
<vagrantc>i'm not sure how secrets are managed, but guix would have to get some more clever post-processing of files in /boot to make that possible... to avoid embedding the key in the store which is publicly readable by design
<vagrantc>e.g. append the key to the initrd when generating the files in /boot rather than just linking to the files in the store
<clever>vagrantc: on the nixos side of things, there is support to package up secrets when generating the /boot config files
<spaethnl>Unfortunately those bugs didn't help. I'm trying to get my network printer working. I've added the printer, but when I attempt to print a test page via the CUPS web admin interface I get "Unable to locate Printer "BRW4CEBBD851047.local".". My understanding is that I had to add avahi to the services, which I've done, but now I'm not sure what might still be wrong.
<spaethnl>Anyone know if there are additional things I need to configure to get CUPS to print to the network printer. My understanding is that even if it is able to discover it, that is different from being able to connect to it?
<jackhill>I think this channel tends to me most active in the European daytime, so if you don't get an answer, and you're able to, I might try then, or email email@example.com
<ncbfg36>Does anyone know of a good replacement for intel 7260 wifi card that works with linux-libre kernel? All I have laying around is an atheros card from a T500 thinkpad but it's the wrong size for this slot (T440p)
<Idliketointerjec>Hello, guix! When I upgrading packages without substitutes guix-daemon is breaking. Now it is trying to build rust-1.39.0 and later for sure, as befor it will show error: corrupt input from socket. So again I have to restart guix-daemon and then again it will break. Anyone could say what is the problem?
<Maya[m]1>orneb: i get that, i just know it works, yet this is a good reason not to use gdm
***wielaard is now known as mjw
<attila_lendvai>something needs to be done for a flatpak app to be able to open files in my home... some dbus or xdg magic, but i cannot find it in my notes. any help, even search keywords, would be appreciated!
<vivien>attila_lendvai, isn’t the job of portals to give access to files?
<attila_lendvai>vivien, yep, i'm honing in on it with searches. i think i must install xdg-desktop-portal-gtk and probably xdg-desktop-portal-wlr, too. but they are installed... :/
<unmatched-paren>because Cargo expects every input in the dependency tree to be in the registry at build time
<mbakke>I had one package complain that the requirements of rust-dlib (a #:cargo-input) was not satisfied; when I added an (inputs ...) field to rust-dlib with the same packages as #:cargo-inputs the build succeeded
<Cairn>I've added a quirk in /etc/libinput and when I run `libinput quirks list --data-dir /etc/libinput /dev/input/event17` it shows my modified value
<Cairn>When I remove the --data-dir flag though, it just shows the default. I can't find anywhere in the docs that suggests I would need to do anything to get my quirk applied other than add it to the dir, but I'm not sure how it's supposed to recognize it.
<Cairn>Is it just always watching /etc/libinput for changes? Seems bizarre
<q-posev>Hello everyone. I am packaging new library with Guix and encountered an issue. So the software has an Autotools build system in place, but the source code is generated, which means that the typical autogen.sh includes one additional line which parses the output of the `git tree command` and generates the Makefile.am file. Building from the source
<q-posev>code distribution works like a charm. However, when I attempt to build from the fixed Git commit, I noticed that actually there is no `.git` folder in the /gnu/store/......-checkout/ folder which is produced by Guix before the `unpack` phase. Because of that, my code generation fails. So my main question is: is it possible to force Guix to keep the
<q-posev>`.git` folder after cloning and checkouting my Github repository? I suppose that this might be a common use case since some programs include the Git hash info in their metadata, but I could not find anything on the web. Thank you in advance!
<nckx>Programmes that try to embed git hashes are just fixed not to do so.
<nckx>Not sure what you mean by ‘git tree command’, so can't give more specific guidance, but the thrust will always be ‘patch the build not to try to run git at build time, 's bad’.
<nckx>s/embed/sniff out/, because there's nothing stopping you from specifying a ‘commit’ in the Guix package and hard-coding it during the build. It's only the ‘let's run git assuming we're in a git repository’ that's not supported.
<q-posev>I see, thank you! We parse the output of the `git ls-tree --name-only -r` command to get a list of files to process since we do not want to hard-code it. Even if running git at build time is a bad practice, I was surprised that the `.git` folder is removed by Guix. Is there any practical reason for that?
<Cairn>Ok, package question. I see that my active libinput package has its own version of /etc/libinput: `/gnu/store/yfmgjhh5qhgni8i47p7yyy313sb2b9z4-libinput-1.19.2/etc/libinput/local-overrides.quirks`
<Cairn>It looks like libinput's only accessing this file.
<Cairn>So how, in my Guix configuration do I modify this file with my custom value?
<Cairn>I know I'm not supposed to touch /etc on its own, I can't get libinput to recognize the file even in ~/.local/share/libinput. So what's the guix method of adding the lines I want to /etc/libinput/local-overrides.quirks?
<antipode>Cairn: Doing a quick "git grep -F libinput", Guix does not make any libinput configuration files.
<antipode>So it looks like etc-service-type is your friend here.
<antipode>(Though possibly libinput is looking in /gnu/store/.../etc, as the etc directory has not been overriden in the libinput package definition)
<Cairn>Yes, it's looking in the /gnu/store/.../etc.
<Cairn>I can tell because it lists the directory when running `libinput quirks list --verbose`
<mbakke>since 'librsvg' is (now?) a staging-level package, I'm not sure 'librsvg-bootstrap' is necessary ... even though it clocks in at 3k dependents
<Cairn>And it doesn't list my temporarily created /etc/libinput/ file
<Cairn>Is that a packaging issue? Should libinput not include a /gnu/store/.../etc file?
<nckx>q-posev: I don't think it's reproducible, and it's generally huge compared to the source, and to any value it would bring — we've come this far without it… Those are just the first 3 possible reasons that popped into my head.
<tribals>I'm trying to use guix as a provider for cross-compilation toolchains. It is a big mess to get "right" toolchain, especially when cross-compiling for ARM, so I'm trying to make my life easier a bit, with help from Guix. I know that guix support cross-compiling "natively", meaning that any package can be built for supported target with ease. But I can't figure out: could this be used for getting a toolchain to build non-guix software?
<tribals>For example, if I need to cross-compile for arm (32-bit), could `gcc-toolchain` package be used?
<nckx>The test suite happens to grep for a hard-coded number, which differs from reality (pending investigation, but the actual values are correct so I suspect fs shenanigans). To neuter this check, I patch in the same regex I used to find that number, and because it's in a grep it all happens to work out.
<nckx>(At the risk of over-explaining the joke, but oh well.)
<lilyp>Oh, okay, so it does have an actual use case.
<shcv[m]>I'm also curious what the best way to declare a channel that optionally depends on local and public versions of another channel is. I was thinking I'd just put two versions ('public' and 'local') of the channel in the same repo
<shcv[m]>idea being, I'll have make each of my packages their own channel, to simplify development, and then have an additional 'meta channel' that merges all of the other ones to be easier for others to use
***spaethnl is now known as Guest1901
<shcv[m]>hmm. If I define a package in the same repo as the source, how should I reference the source files? if someone pulls the channel does it download everything in the repo? is that a bad idea?
<apteryx>is there an easy way to get the message ID from Gnus?
<apteryx>nckx: I just sent a trivial v2 for 56799 (2 lines changed)
***rgherdt__ is now known as rgherdt
<apteryx>I don't understand what the "file-append, output" is testing; is it possible to use file-append with specific outputs?
<Guest1901>I'm trying to get my network printer working. CUPS is able to discover the printer on the network for me to add, but after I've added it, when I attempt to print a test page via the CUPS web admin interface I get "Unable to locate Printer "BRW4CEBBD851047.local".". My understanding is that I had to add avahi to the services, which I've done, but now I'm not sure what might still be wrong. Anyone know what I addition
<spaethnl>Hmm, canceling and restarting does not fix it for me :/
<apteryx>I'm confused by the Vinagre VNC client connection window; there's a 'Host', fair enough. Then there's also 'Use host [ ] as a SSH tunnel'. If I put a host there, what do I put then in the main 'Host' field?
<shcv[m]>apteryx: it looks like file-append produces a record containing 'base and 'suffix that is then processed by the gexp expander in a way that uses the output. So, that test is to verify that the output appropriately affects the results
<shcv[m]>you can look at file-append-compiler and the surrounding code in guix/gexp.scm for more details
<apteryx>shcv[m]: thanks! isn't it invalid to use more than 2 arguments with file-append?
<apteryx>OK, no the signature is: (file-append base . suffix), so it captures whatever 2+ args into the suffix list
<shcv[m]>probably just an intermediate proxy that it connects to first, then tries to connect to the main host
<apteryx>these strings are then string-concatene'd in file-append-compiler... seems a dubious feature
<apteryx>I guess it could be useful if you were to format the string, but reckon 99% of examples in the source code only provide 2 arguments to file-append :-)
<shcv[m]>they aren't "just" concatenated - since each is a separate object, they could involve stuff that gets processed by the gexp compiler / expander
<shcv[m]>actually nvm, it looks like only base is expanded
<apteryx>I don't think so, 'suffix' is expected to be a list of strings, as mentioned in guix/gexp:666
<shcv[m]>how do I declare a package with local source?
<apteryx>OK, I'm connected to my remote machine via VNC, but I get a black screen. I was expecting to see my fancy SlIM login manager.
<apteryx>shcv[m]: you can use the git-checkout procedure for the source
<shcv[m]>the package reference says that any "file-like object" can be used in the source field, and it even mentions local-file, but I'm having trouble getting that to work. It sounds like it wants a single file, not a directory...
<apteryx>you could always use fetch-url with a local uri such as file:///home/src/your-project
<apteryx>but if you use git the <git-checkout> option is easier/better (from (guix git))