From: Vagrant Cascadian <vagrant@reproducible-builds.org>
To: Leo Famulari <leo@famulari.name>
Cc: 34449@debbugs.gnu.org
Subject: [bug#34449] [PATCH] gnu: Add trydiffoscope.
Date: Wed, 13 Feb 2019 16:26:49 -0800 [thread overview]
Message-ID: <87ftsr5i5y.fsf@ponder> (raw)
In-Reply-To: <20190213235805.GA24134@jasmine.lan>
[-- Attachment #1: Type: text/plain, Size: 969 bytes --]
On 2019-02-13, Leo Famulari wrote:
> On Wed, Feb 13, 2019 at 01:43:13PM -0800, Vagrant Cascadian wrote:
>> I couldn't really think of a straightforward way to mention the
>> diffoscope package, but the attached patch updates the synopsis and
>> description to address the other mentioned issues.
>
> Okay, sometimes these non-code parts are actually the hardest! :)
Indeed.
> I pushed as commit 706460a35754a47bf832a40de4f22271e7088226 with the
> changes below.
Thanks!
> I found that the software didn't work without the requests module, and
I was surpised it worked without it for me (I had seen that it used
requests); could my user profile have somehow leaked python-requests
from some other package?
> that the man page was being installed to a location that is not
> idiomatic for Guix.
I wondered why it wasn't showing up in MANPATH... now I know, thanks!
/usr/share is a hard habit to break. :)
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2019-02-14 0:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 2:08 [bug#34449] [PATCH] gnu: Add trydiffoscope Vagrant Cascadian
2019-02-12 7:31 ` Julien Lepiller
2019-02-12 8:16 ` Vagrant Cascadian
2019-02-12 9:34 ` Julien Lepiller
2019-02-12 20:37 ` Leo Famulari
2019-02-13 8:05 ` Julien Lepiller
2019-02-13 21:43 ` Vagrant Cascadian
2019-02-13 23:58 ` bug#34449: " Leo Famulari
2019-02-14 0:26 ` Vagrant Cascadian [this message]
2019-02-14 0:32 ` [bug#34449] " Leo Famulari
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=87ftsr5i5y.fsf@ponder \
--to=vagrant@reproducible-builds.org \
--cc=34449@debbugs.gnu.org \
--cc=leo@famulari.name \
/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.