bug#72284: kdeconnect-app fails to start

宋文武 via Bug reports for GNU Guix writes: > Hello, since the update to 24.05.2, 'kdeconnect-app' fails with: > > QQmlApplicationEngine failed to load component > qrc:/qt/qml/org/kde/kdeconnect/app/Main.qml:49:13: Type QQC2.ToolBar > unavailable > qrc:/qt/qml/org/kde/desktop/ToolBar.qml: Type Glob

bug#72284: kdeconnect-app fails to start

Hello, since the update to 24.05.2, 'kdeconnect-app' fails with: QQmlApplicationEngine failed to load component qrc:/qt/qml/org/kde/kdeconnect/app/Main.qml:49:13: Type QQC2.ToolBar unavailable qrc:/qt/qml/org/kde/desktop/ToolBar.qml: Type GlobalSonnetSettings unavailable qrc:/qt/qml/org/kde/deskto

bug#72040: [core-updates] Boost bug / breaks libreoffice [was libetonyek link failure]

On Thu, Jul 11, 2024 at 04:23:09PM -0400, Leo Famulari wrote: > Subject: [PATCH] WIP: Boost: Fix a bug that breaks libetonyek. > > This fixes > > * gnu/packages/patches/boost-fix-duplicate-definitions-bug.patch: New file. > * gnu/local.mk (dist_patch_DATA): Add

bug#71918: [DOCUMENTATION] the suggested key import method for `guix refresh` doesn't work

Hi, Attila Lendvai skribis: > i was trying to: > > $ ./pre-inst-env guix refresh --update dropbear > > but the key is not imported, because "no user ID". apparently some keyservers > drop the user id for privacy reasons. Yes, that’s the case of keys.openpgp.org, unless the user explicitly cons

bug#72061: Discrepancy when running ‘guix pull’ from different machines

HI Simon, > Could you share the channels.scm file? Attached. > Because the mention of ’guix-science’ means third-party channels, I > guess. And maybe there is something tricky when mixing different > specific pinned channels. I thought about that as well, but the behavior should still be the s

bug#72277: home-shepherd is flooding tty

Hi, Today I connected to my laptop running guix home over ssh as the first session and got greeted with a lot of shepherd logs from the on-first-login script from guix-home starting the user shepherd: Starting service root... Service root started. Service root running with value #t. Service

bug#72257: Non-English manuals for 1.4.0 are unavailable

The easiest resolution would be to generally use an old 1.4.0 guix package in with-extensions, because the modules from a guix@1.4.0 still should work fine even for the latest devel manual (I have not tested, but autonomous guix/self.scm ignores the changed Makefile). Regards, Florian

bug#72061: Discrepancy when running ‘guix pull’ from different machines

Hi Konrad, On Wed, 24 Jul 2024 at 10:05, Konrad Hinsen wrote: >guix time-machine --channels=channels.scm -- shell --container --network > --manifest=manifest.scm -- jupyter lab >guix-science/build-system/node.scm:119:2: error: #{ > %make-build-system-procedure/abi-check}#: unbound vari

bug#72257: Non-English manuals for 1.4.0 are unavailable

"pelzflorian (Florian Pelz)" writes: > The old manual as referred to in maintenance.git in > hydra/modules/sysadmin/web.scm was expected to build with the > guix/self.scm of old guix.git; it should not try to use po4a.cfg. The issue seems to be, maintenance.git in hydra/modules/sysadmin/web.scm u

bug#72271: GNOME Secrets won’t open

The GNOME Secrets app packaged with Guix—as ‘secrets’—isn’t able to launch (its graphical app). I get the following trace from trying to launch it from the terminal, which hints that it hasn’t been packaged with everything it needs: > Traceback (most recent call last): > File > "/gnu/store/vqi0

bug#72257: Non-English manuals for 1.4.0 are unavailable

Hello all, I do not understand why these old manuals are built with po4a.cfg. Why does it not use old guix 1.4.0 to build old manual 1.4.0? po4a.cfg was added to guix.git in early June 2024 in commits starting from commit 2d4af5247057505956e841d396ec78af9f769837 Author: gemmaro Date: Sun Apr

bug#72061: Discrepancy when running ‘guix pull’ from different machines

Hi everyone, Jumping in with a possibly related problem reported by a participant of the Reproducible Research MOOC. He gets an error when running an example from one of our exercises: guix time-machine --channels=channels.scm -- shell --container --network --manifest=manifest.scm -- jupyter