<kristofer>I am trying to create a package with guile-lib and guile as inputs. when I build the package it cannot find htmlprag and when I create an environment it appears guile-lib is not included in it. I'm not sure what I am doing wrong
<rekado_>mb[m]1: the key is part of the guix-maintenance repo for now. For the next release we may add the key for berlin to the default set.
<rekado_>before that I need to attach the new glusterfs storage to the new head node, though. Haven’t been able to make time for that yet.
<civodul>ACTION fearlessly runs 'guix pull' on the Olimex A20
<vagrantc>ACTION wonders what time unit would be appropriate to measure that in
<benny>is there a way to see why something is considered for an upgrade when I run guix package -u? I've reported the (what I believe to be bug) about python-wrapper but I sometimes see a list of packages that all keep their version number
<taohansen>i have a few usability issues. they're papercuts for me and i'd like to confirm they are in fact bugs before submitted on the bug tracker.
<taohansen>1. to use any fuse-based filesystems i have to manually `modprobe fuse` after startup.
<taohansen>2. pulseaudio does not always start on-demand requiring me to launch it myself which i've set in my .xsession. personally i'd like if it was just firmly integrated into GuixSD rather than the provisional and responsive loading it appears to do presently.
<taohansen>i know it's Poettering software but man i'd really like to see that hatefest end.
<roptat>taohansen: for 1, there's a list of modules in the operating system declaration
<taohansen>3. basically GuixSD assumes a system that is not HiDPI. this in my opinion should be responsive by default. as it is, SLiM is tiny and unreadable, TTYs are tiny and unreadable, and .Xresources entries fix everything but the tiny cursor, which appears to be hardcoded. whatever the case, i and others cannot fix this issue.
<taohansen>we are entering very rapidly the HiDPI future. let's get it by the balls?
<ng0>often features are missing because of the usual reasons: no one noticed it. no one bothered to report. it's complex to work on (I've stuck myself into that field of work…). someone needs to do it.
<taohansen>by ".Xresources entries fix everything" i mean everything inside a window manager, not TTYs and SLiM
<roptat>taohansen: you can add modules in the initrd field of the operating-system, there's an example in the manual
<ng0>like for HiDPI, I'm still stuck with old laptops and a small 1080p television/monitor combination for finacial reasons
<taohansen>ng0: yeah, i totally understand. i'm just making these things clear before i go ahead and put them on the bug tracker
<ng0>more specific examples would maybe help in the documentation, if something already (partial) addresses these issues
<mb[m]1>Tao Hansen: Have you tried SDDM instead of SLiM for HiDPI support?
<mb[m]1>I've seen a configuration option for it, but not sure if it's tweakable atm.
<taohansen>mb: haven't no, i'd be interested if it doesn't pull in half of KDE with it?
<ng0>we need to achieve the following: Firefox based browser must accept a path/union in the store for the plugins. adjust one or two values in the extensions to make them accept the differing path. I'll take a look if I have pushed my work somewhere