From: "Wamm K. D." <jaft.r@outlook.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 55518-done@debbugs.gnu.org, jackhill@jackhill.us
Subject: [bug#55518] [PATCH] gnu: Add python-gatt.
Date: Sun, 29 May 2022 21:52:10 -0500 [thread overview]
Message-ID: <BY5PR07MB70298ABC211ACCCA0D2EFB9699DD9@BY5PR07MB7029.namprd07.prod.outlook.com> (raw)
In-Reply-To: <87wne6bpms.fsf_-_@gnu.org> ("Ludovic Courtès"'s message of "Fri, 27 May 2022 18:02:45 -0400")
On Fri. (May 27, 2022) at 06:02:45 PM -04, Ludovic Courtès <ludo@gnu.org> wrote:
> Hi,
>
> I added a commit log and applied with the changes below, as suggested by
> Tobias (for the description).
…ah; heh, that was definitely not how I'd read his suggestion. I thought
~@acronym~ was used in every case, with the full acronym spelled out
only in first case, so thought I'd gotten it right in my last
patch. Sorry about that.
> The inputs are propagated because, for instance, the code reads:
>
> try:
> import dbus
> import dbus.mainloop.glib
> except ImportError:
> import sys
> print("Module 'dbus' not found")
> print("Please run: sudo apt-get install python3-dbus")
> print("See also: https://github.com/getsenic/gatt-python#installing-gatt-sdk-for-python")
> sys.exit(1)
>
> Thus, if you install python-gatt in a profile, python-dbus should be
> propagated as well so it “just works”.
Mmm; O. K. That makes sense. Thanks a ton for explaining, Ludo; it's
super appreciated.
next prev parent reply other threads:[~2022-05-30 2:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <11>
2022-05-19 6:05 ` [bug#55518] [PATCH] gnu: Add python-gatt Wamm K. D
2022-05-19 13:24 ` Tobias Geerinckx-Rice via Guix-patches via
2022-05-22 6:44 ` Jaft
2022-05-27 22:02 ` bug#55518: " Ludovic Courtès
2022-05-30 2:52 ` Wamm K. D. [this message]
2022-05-19 5:24 [bug#55518] " Wamm K. D
2022-05-19 5:46 ` Jack Hill
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BY5PR07MB70298ABC211ACCCA0D2EFB9699DD9@BY5PR07MB7029.namprd07.prod.outlook.com \
--to=jaft.r@outlook.com \
--cc=55518-done@debbugs.gnu.org \
--cc=jackhill@jackhill.us \
--cc=ludo@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).