<johnabs>Hopefully easy question: my nmapplet icons are all look like "do not enter" traffic signs but without the words. I've installed other icon themes and tried using lxappearance to fix it, but no dice. Any tips on how I can fix this?
<johnabs>(p.s. same johnabs as the matrix one, but on my new, almost completely working, guix box :3 )
<gnucode>that's where I am currently trying to improve our current opensmtpd service.
<mohamed>Ok thanks @gnucode and @shcv, I will look at it. I need to add the dependencies both in the import package and in "native-input" ?
<shcv>mohamed: depends; `native-inputs` is for tools needed at build time but not runtime, like parser generators. Looking at other golang packages (in guix/gnu/packages/golang.scm) I think you probably want `propagated-inputs` for most of your libs, and `inputs` for testing frameworks etc.
<shcv[m]>unmatched-paren: I think I'm still having the issue where `guix pull` doesn't update the repo that `guix system reconfigure` is using. `which guix` is /home/shcv/.config/guix/current/bin/guix, and `guix --version` is "guix (GNU Guix) 0"... I have also tried guix home, which I thought might be interfering, but reconfiguring it didn't seem to change anything
<antipode>shcv: It's not about build-time vs runtime, e.g. header-only packages are only needed at build time, yet they need to be in inputs.
<antipode>It's about 'architecture it's built on' vs. 'architecture it will be run on'
<shcv>antipode: whoops; you're right, thanks for the correction. I think I abridged my message incorrectly and got inputs and native-inputs swapped.
<shcv>(was looking at docs for the definitions and and golang.scm for examples, so I should have no excuse...)
<PurpleSym>Do any Rust wizards know how I can resolve the following error during 'build? error: failed to get `anyhow` as a dependency of package `dolby_vision v2.0.0 (/tmp/guix-build-dovi-tool-1.5.7.drv-0/source/dolby_vision)`
<antipode>PurpleSym: Did you check that 'rust-anyhow' is in the inputs (actually #:cargo-inputs, I guess)?
<PurpleSym>antipode: Yeah, both rust-dolby-vision-2 and dovi-tool (which I am trying to build) have this dependency in #:cargo-inputs.
<PurpleSym>I also updated rust-anyhow to 1.0.65, because that’s what both require.
<old>Hey any way to tell `guix pack` to not include everything? For example when I bundle a package, the entire inputs are pulled as if they were propagated inputs.
<old>This results in having header files in the bundle when they are not needed for example
<antipode>old: IIUC, "guix pack" only pulls in references.
<antipode>Perhaps one of the things it refers to can be split up in separate outputs (e.g. with a separate "include" output).
<old>antipode: Right. It's one downside I found of it. The resulting bundle are enormous
<lilyp>that's the point – you get everything you need
<lilyp>guix packs are not that large compared to equivalent docker container or similar solutions
<old>My point being there's thing that are not needed. My program does not need header files of llvm at runtime
<old>They are large depending on what you put in it.
<old>I have a bundle that uses rocm-runtime, the resulting tar.gz is a few hundreds MB at least
<old>Ofc the header files are probably not going to downsize that much. But I'm sure there's other things that could be left from the bundle and reduce the size. Such as the entire coreutils translation in 60 languages
<antipode>old: What downside are you referring to?
<old>ofc if thing would benefit the community I would contribute to the main channel instead
<old>Yes that's my idea also. Just unpack, sweep things and pack again
<antipode>Though I expect there is something between 'status quo' and 'diet' that would be acceptable for upstream Guix, so I would propose to patch+send things for upstream Guix where feasible and unproblematic and leave other things for post-processing.
<pkill9>rekado: i noticed you mentione din the mailing list that gnome on wayland has problems for you, specificlaly you mentioned that it flickers with black screen, do you know what might be causing this?
<nckhexen>sneek: later tell antipode: We do, through litharge, which is a bot (oh! vile bots!) that remembers to unban the person. Unlike, say, me. That's as high-tech as it gets. That and prodding sneek's owner in #guile.