From: Andrew Tropin <andrew@trop.in>
To: Declan Tsien <declantsien@riseup.net>, 60752-done@debbugs.gnu.org
Subject: bug#60752:
Date: Mon, 16 Jan 2023 21:22:11 +0400 [thread overview]
Message-ID: <87k01ml7i4.fsf@trop.in> (raw)
In-Reply-To: <87pmbhank4.fsf@riseup.net>
[-- Attachment #1: Type: text/plain, Size: 915 bytes --]
On 2023-01-14 09:54, Declan Tsien wrote:
> Started a new thread since the subject has changed
> https://issues.guix.gnu.org/60800
Let's keep the discussion in this thread, not to lose the context.
BTW, there is a retitle command for debbugs in case it necessary to
change the title of the bug.
From what I see wpa-supplicant requirement is not needed, as Bruno
mentioned, there are use cases, where connman can be used without
wpa-supplicant or wireless backend at all.
According to the documentation I was able to find, to enable iwd support
--wifi=iwd_agent should be added to connmand, so I applied the first
patch with a few adjustments: Completely removed wpa-supplicant
requirement, realigned the code. Unfortunately, I don't use connman and
can't easily check, Declan, could you please confirm that iwd is now
working correctly with connman?
--
Best regards,
Andrew Tropin
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2023-01-16 17:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <874jstc3zl.fsf@riseup.net>
2023-01-12 12:56 ` [bug#60752] [PATCH] services: connman: Add iwd backend support Declan Tsien
2023-01-12 14:12 ` Bruno Victal
2023-01-12 14:31 ` Declan Tsien
2023-01-12 14:53 ` Bruno Victal
2023-01-12 15:22 ` Declan Tsien
2023-01-14 1:17 ` [bug#60752] [Declan Tsien] Re: [bug#60752] [PATCH] services: connman: Add option to disable wpa-supplicant Declan Tsien
2023-01-14 1:54 ` bug#60752: Declan Tsien
2023-01-16 17:22 ` Andrew Tropin [this message]
2023-01-17 0:30 ` [bug#60752] Declan Tsien
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=87k01ml7i4.fsf@trop.in \
--to=andrew@trop.in \
--cc=60752-done@debbugs.gnu.org \
--cc=declantsien@riseup.net \
/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.