<Michal_Atlas[m]><TristanCottam[m]> "Michal_Atlas: Are there any..." <- Unsure, most probably doesn't work for more internal things, like editing anything about the daemon itself, for other things it was sufficient to me.
<TristanCottam[m]>I got an error about a missing architecture, so I'm going the local channel route
<sughosha>Hi, I am trying to build zrythm, the same version that is still available in Guix (without pre-inst-env). It was getting built until I upgraded my recently. Here is the build log https://paste.debian.net/1279015/.
<gnucode>email@example.com seems to not be installable on power9...because inkscape fails to build...that's odd. I guess I will try a guix pull.
<ben-7549>Hi everyone. I am a new user of guix, and I quite like it. I’d like to participate and was wondering how to do. I saw that neovim is not at the latest version and I think it would be an easy first contribution. To do so, I should simply send a patch containing the version bump to firstname.lastname@example.org directly ?
<kaelyn> hardware decoding fails with the console message "[ffmpeg/video] h264: No support for codec h264 profile 100." and I've seen the error with h265 files as well (the regression would mean my media mini-pc will no longer be able to play 4K videos after upgrading).
<futurile>does anyone know how to run alacritty in a guix shell? I saw someone ask about it the other day so wondering if anyone has any success ...
<RavenJoad>futurile: "guix shell alacritty -- alacritty" does not work?
<podiki[m]>kaelyn: there was a report the other day of a driver missing from mesa as well, so we should get both of those for the mesa branch; I will build a branch locally to see if it works and then see about how to do that with savannah/cuirass
<podiki[m]>kaelyn: can reproduce the error but haven't tried with older mesa
<kaelyn>podiki[m]: sounds good, I'll see if I can find that report. I'm currently working on several patches for a mesa branch, including my existing patch for fixing the vulkan layer manifests, adding `VDPAU_DRIVER_PATH` as a native-search-path, updating to 23.0.3, and using gexps instead of quasiquote for the arguments.
<podiki[m]>maybe we should compare (I did once long ago) our mesa build options to some other places to see if we've missed something or something changed in recent versions
<kaelyn>For the hw decode issue I saw, it looks like mesa added a new video-codecs meson option with the default being an empty list. I checked the Arch and Debian package definitions, and both add "-Dvideo-codecs=vc1dec,h264dec,h264enc,h265dec,h265enc"
<kaelyn>(added in one of the 22.x releases, as the commit for the new option was from 2022)
<podiki[m]>very good, great; so we can do that on the mesa branch along with the driver that was missing (I think it was "crocus" if i recall)
<old>rekado: I did that by adding a phase before configure to call autoreconf
<kaelyn>I folded the VDPAU_DRIVER_PATH change and adding the -Dvideo-codecs into a single "fix hardware decoding" commit. Would the best way for me to contribute commits the mesa branch be to send it as a series to guix-patches (perhaps prefixed with "[PATCH mesa-branch]" or similar)?
<podiki[m]>yes, in light of an official policy I've been thinking that, [PATCH <branch>] or similar
<podiki[m]>in this case it'll be mostly us coordinating and is a limited number of patches, so not hard to gather I hope
<podiki[m]>thanks for working on this! (i'm often guilty of having a local version for myself and not finishing the polish/sending a patch)