From: Raghav Gururajan <raghavgururajan@disroot.org>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: 41025@debbugs.gnu.org
Subject: bug#41025: blueman does not start
Date: Sun, 3 May 2020 11:24:41 -0400 [thread overview]
Message-ID: <20200503112441.66903f8c.raghavgururajan@disroot.org> (raw)
In-Reply-To: <87v9leb2gx.fsf@ambrevar.xyz>
[-- Attachment #1: Type: text/plain, Size: 710 bytes --]
Hi Pierre!
> Thanks! Sadly your patch does not fix the issue for me.
>
> You can reproduce with
>
> --8<---------------cut here---------------start------------->8---
> ./pre-inst-env guix environment --pure --ad-hoc blueman -- blueman-tray
> --8<---------------cut here---------------end--------------->8---
>
> I had a quick look at the package definition: it's a
> glib-or-gtk-build-system but the package is in python, so you need to
> set the PYTHONPATH manually I think. Look at the other GNOME package
> written in Python, my guess is that it's the same thing.
Thanks! I was able to fix "gi" error. But "No module 'blueman', I could not
fix. Any ideas?
I have attached a new patch.
Regards,
RG.
[-- Attachment #2: 0004-gnu-blueman-Test-patch.patch --]
[-- Type: text/x-patch, Size: 6906 bytes --]
From 19cdddadcff5fa940c8e7e6ef1a31040a4412db5 Mon Sep 17 00:00:00 2001
From: Raghav Gururajan <raghavgururajan@disroot.org>
Date: Sun, 3 May 2020 11:21:48 -0400
Subject: [PATCH 4/4] gnu: blueman: Test patch.
* gnu/packages/networking.scm (blueman): Test patch.
---
gnu/packages/networking.scm | 119 +++++++++++++++++++++++++++++++++++-
1 file changed, 118 insertions(+), 1 deletion(-)
diff --git a/gnu/packages/networking.scm b/gnu/packages/networking.scm
index 94b521584f..b624149b23 100644
--- a/gnu/packages/networking.scm
+++ b/gnu/packages/networking.scm
@@ -143,7 +143,124 @@
"--enable-polkit"
"--disable-appindicator" ; Deprecated
"--with-systemdsystemunitdir=no" ; Not required
- "--with-systemduserunitdir=no"))) ; Not required
+ "--with-systemduserunitdir=no") ; Not required
+ #:phases
+ (modify-phases %standard-phases
+ ;; Python references are not being patched in patch-phase of build;
+ ;; despite using python-wrapper as input. So patching them manually.
+ (add-after 'unpack 'patch-python-references
+ (lambda* (#:key inputs #:allow-other-keys)
+ (substitute* "apps/blueman-adapters.in"
+ (("@PYTHON@") (string-append (assoc-ref inputs "python")
+ "/bin/python3.7")))
+ (substitute* "apps/blueman-applet.in"
+ (("@PYTHON@") (string-append (assoc-ref inputs "python")
+ "/bin/python3.7")))
+ (substitute* "apps/blueman-assistant.in"
+ (("@PYTHON@") (string-append (assoc-ref inputs "python")
+ "/bin/python3.7")))
+ (substitute* "apps/blueman-manager.in"
+ (("@PYTHON@") (string-append (assoc-ref inputs "python")
+ "/bin/python3.7")))
+ (substitute* "apps/blueman-mechanism.in"
+ (("@PYTHON@") (string-append (assoc-ref inputs "python")
+ "/bin/python3.7")))
+ (substitute* "apps/blueman-report.in"
+ (("@PYTHON@") (string-append (assoc-ref inputs "python")
+ "/bin/python3.7")))
+ (substitute* "apps/blueman-rfcomm-watcher.in"
+ (("@PYTHON@") (string-append (assoc-ref inputs "python")
+ "/bin/python3.7")))
+ (substitute* "apps/blueman-sendto.in"
+ (("@PYTHON@") (string-append (assoc-ref inputs "python")
+ "/bin/python3.7")))
+ (substitute* "apps/blueman-services.in"
+ (("@PYTHON@") (string-append (assoc-ref inputs "python")
+ "/bin/python3.7")))
+ (substitute* "apps/blueman-tray.in"
+ (("@PYTHON@") (string-append (assoc-ref inputs "python")
+ "/bin/python3.7")))
+ #t))
+ (add-after 'glib-or-gtk-wrap 'wrap-blueman-adapters
+ (lambda* (#:key outputs #:allow-other-keys)
+ (let
+ ((bm-adap
+ (string-append
+ (assoc-ref outputs "out") "/bin/blueman-adapters")))
+ (wrap-program bm-adap
+ `("PYTHONPATH" = (,(getenv "PYTHONPATH")))
+ `("GI_TYPELIB_PATH" = (,(getenv "GI_TYPELIB_PATH"))))
+ #t)))
+ (add-after 'glib-or-gtk-wrap 'wrap-blueman-applet
+ (lambda* (#:key outputs #:allow-other-keys)
+ (let
+ ((bm-app
+ (string-append
+ (assoc-ref outputs "out") "/bin/blueman-applet")))
+ (wrap-program bm-app
+ `("PYTHONPATH" = (,(getenv "PYTHONPATH")))
+ `("GI_TYPELIB_PATH" = (,(getenv "GI_TYPELIB_PATH"))))
+ #t)))
+ (add-after 'glib-or-gtk-wrap 'wrap-blueman-assistant
+ (lambda* (#:key outputs #:allow-other-keys)
+ (let
+ ((bm-ass
+ (string-append
+ (assoc-ref outputs "out") "/bin/blueman-assistant")))
+ (wrap-program bm-ass
+ `("PYTHONPATH" = (,(getenv "PYTHONPATH")))
+ `("GI_TYPELIB_PATH" = (,(getenv "GI_TYPELIB_PATH"))))
+ #t)))
+ (add-after 'glib-or-gtk-wrap 'wrap-blueman-manager
+ (lambda* (#:key outputs #:allow-other-keys)
+ (let
+ ((bm-man
+ (string-append
+ (assoc-ref outputs "out") "/bin/blueman-manager")))
+ (wrap-program bm-man
+ `("PYTHONPATH" = (,(getenv "PYTHONPATH")))
+ `("GI_TYPELIB_PATH" = (,(getenv "GI_TYPELIB_PATH"))))
+ #t)))
+ (add-after 'glib-or-gtk-wrap 'wrap-blueman-report
+ (lambda* (#:key outputs #:allow-other-keys)
+ (let
+ ((bm-rep
+ (string-append
+ (assoc-ref outputs "out") "/bin/blueman-report")))
+ (wrap-program bm-rep
+ `("PYTHONPATH" = (,(getenv "PYTHONPATH")))
+ `("GI_TYPELIB_PATH" = (,(getenv "GI_TYPELIB_PATH"))))
+ #t)))
+ (add-after 'glib-or-gtk-wrap 'wrap-blueman-sendto
+ (lambda* (#:key outputs #:allow-other-keys)
+ (let
+ ((bm-st
+ (string-append
+ (assoc-ref outputs "out") "/bin/blueman-sendto")))
+ (wrap-program bm-st
+ `("PYTHONPATH" = (,(getenv "PYTHONPATH")))
+ `("GI_TYPELIB_PATH" = (,(getenv "GI_TYPELIB_PATH"))))
+ #t)))
+ (add-after 'glib-or-gtk-wrap 'wrap-blueman-services
+ (lambda* (#:key outputs #:allow-other-keys)
+ (let
+ ((bm-serv
+ (string-append
+ (assoc-ref outputs "out") "/bin/blueman-services")))
+ (wrap-program bm-serv
+ `("PYTHONPATH" = (,(getenv "PYTHONPATH")))
+ `("GI_TYPELIB_PATH" = (,(getenv "GI_TYPELIB_PATH"))))
+ #t)))
+ (add-after 'glib-or-gtk-wrap 'wrap-blueman-tray
+ (lambda* (#:key outputs #:allow-other-keys)
+ (let
+ ((bm-tray
+ (string-append
+ (assoc-ref outputs "out") "/bin/blueman-tray")))
+ (wrap-program bm-tray
+ `("PYTHONPATH" = (,(getenv "PYTHONPATH")))
+ `("GI_TYPELIB_PATH" = (,(getenv "GI_TYPELIB_PATH"))))
+ #t))))))
(native-inputs
`(("cython" ,python-cython)
("glib:bin" ,glib "bin")
--
2.26.2
next prev parent reply other threads:[~2020-05-03 15:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-02 13:39 bug#41025: blueman does not start Pierre Neidhardt
2020-05-02 13:56 ` Raghav Gururajan
2020-05-02 18:45 ` Pierre Neidhardt
2020-05-03 15:24 ` Raghav Gururajan [this message]
2020-05-03 16:13 ` Pierre Neidhardt
2020-05-04 3:18 ` Raghav Gururajan
2020-05-04 8:47 ` Pierre Neidhardt
2020-05-04 9:11 ` Pierre Neidhardt
2020-05-09 6:29 ` Raghav Gururajan
2020-05-09 9:12 ` Pierre Neidhardt
2020-05-09 21:49 ` Raghav Gururajan
2020-05-09 22:03 ` Raghav Gururajan
2020-05-10 9:27 ` Pierre Neidhardt
2020-05-11 10:05 ` Raghav Gururajan
2020-05-14 17:16 ` Pierre Neidhardt
2020-05-14 23:37 ` Raghav Gururajan
2020-05-15 0:56 ` Raghav Gururajan
2020-05-15 9:52 ` Pierre Neidhardt
2020-05-10 21:29 ` Marius Bakke
2020-05-11 10:07 ` Raghav Gururajan
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=20200503112441.66903f8c.raghavgururajan@disroot.org \
--to=raghavgururajan@disroot.org \
--cc=41025@debbugs.gnu.org \
--cc=mail@ambrevar.xyz \
/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.