From: dftxbs3e <dftxbs3e@free.fr>
To: 45374@debbugs.gnu.org
Subject: [bug#45374] [PATCH] gnu: udisks: Add dosfstools to PATH with wrapper.
Date: Tue, 22 Dec 2020 23:44:29 +0100 [thread overview]
Message-ID: <a275d3e7369e3129ec0524cb69b7b9aea3d35499.camel@free.fr> (raw)
In-Reply-To: <handler.45374.B.160867571524131.ack@debbugs.gnu.org>
[-- Attachment #1: Type: text/plain, Size: 197 bytes --]
Looks like there has already been some discussion about this:
https://issues.guix.gnu.org/41247
So what do we do?
Patch libblockdev to use full paths or give it to udisksd's
environment?
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2020-12-22 22:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-22 22:21 [bug#45374] [PATCH] gnu: udisks: Add dosfstools to PATH with wrapper John Doe
[not found] ` <handler.45374.B.160867571524131.ack@debbugs.gnu.org>
2020-12-22 22:44 ` dftxbs3e [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
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=a275d3e7369e3129ec0524cb69b7b9aea3d35499.camel@free.fr \
--to=dftxbs3e@free.fr \
--cc=45374@debbugs.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).