From: "宋文武 via Bug reports for GNU Guix" <bug-guix@gnu.org>
To: Zheng Junjie <zhengjunjie@iscas.ac.cn>
Cc: 72346-done@debbugs.gnu.org
Subject: bug#72346: dbus session daemon fail to start kdeconnectd
Date: Wed, 31 Jul 2024 07:58:14 +0800 [thread overview]
Message-ID: <87wml277qh.fsf@envs.net> (raw)
In-Reply-To: <87plqvzbm4.fsf@iscas.ac.cn> (Zheng Junjie's message of "Tue, 30 Jul 2024 13:34:43 +0800")
Zheng Junjie <zhengjunjie@iscas.ac.cn> writes:
> [...]
> Subject: [PATCH] gnu: kdeconnect: Fix dbus autostart.
>
> * gnu/packages/kde.scm (kdeconnect)[phases]: Add fix-dbus-autostart phase.
>
> Change-Id: I27ac61e41f15f9ff2de658fbd04633820f5e0966
> ---
> gnu/packages/kde.scm | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/gnu/packages/kde.scm b/gnu/packages/kde.scm
> index 59f3b1052b..0e51e3e230 100644
> --- a/gnu/packages/kde.scm
> +++ b/gnu/packages/kde.scm
> @@ -1326,6 +1326,12 @@ (define-public kdeconnect
> "-DKDE_INSTALL_LIBEXECDIR=libexec"
> ;; So kdeconnect.so isn't installed to lib/plugins
> "-DPLUGIN_INSTALL_DIR=lib/qt6/plugins")
> + #:phases #~(modify-phases %standard-phases
> + (add-after 'unpack 'fix-dbus-autostart
> + (lambda _
> + (substitute* "daemon/org.kde.kdeconnect.service.in"
> + (("kdeconnectd")
> + (string-append #$output "/bin/kdeconnectd"))))))
> #:tests? #f)) ; tests fail hard in our build environment
> (native-inputs
> (list extra-cmake-modules
>
> base-commit: fdc6274de5b1d617fcabb3f3af9d2c0dd2a6520d
> prerequisite-patch-id: 9429d31c7fc951f1c90d8df0d4c1d5655f38287f
> prerequisite-patch-id: 8aba1f6e2d202562de36cf70cb0cb0a4eaa76de7
Pushed to master, thank you!
prev parent reply other threads:[~2024-07-30 23:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-29 3:11 bug#72346: dbus session daemon fail to start kdeconnectd 宋文武 via Bug reports for GNU Guix
2024-07-30 5:34 ` Zheng Junjie
2024-07-30 23:58 ` 宋文武 via Bug reports for GNU Guix [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wml277qh.fsf@envs.net \
--to=bug-guix@gnu.org \
--cc=72346-done@debbugs.gnu.org \
--cc=iyzsong@envs.net \
--cc=zhengjunjie@iscas.ac.cn \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.