unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Vincent Legoll <vincent.legoll@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 40083@debbugs.gnu.org
Subject: [bug#40083] [PATCH] gnu: Add blktrace.
Date: Thu, 19 Mar 2020 16:05:07 +0100	[thread overview]
Message-ID: <CAEwRq=qkjehnTvDyqLw=UPiv6gCPBW2Gh15-zqxn2L9sGYK3-Q@mail.gmail.com> (raw)
In-Reply-To: <87a74c5tkk.fsf@gnu.org>

Hello,

On Thu, Mar 19, 2020 at 3:05 PM Ludovic Courtès <ludo@gnu.org> wrote:
> Vincent Legoll <vincent.legoll@gmail.com> skribis:
>
> > Dunno what to do about the packaged .py scripts, Should I patch the
> > shebang ? ("#! /usr/bin/env python") after adding python to inputs ?
>
> Just do something like this:

[something's missing here] ;-)

> and the .py files will be automatically patched.
>
> However, ‘bno_plot.py’ refers to /bin/rm and gnuplot, and these
> references should probably be replaced with absolute file names.
>
> Could you take a look and send an updated patch?

I already have that patched out, replacing that rm call with pure
python code, I'll resubmit a new version correcting all those glitches
later.

Now's time for a bit of sunlight to placebo-help fight covid...

-- 
Vincent Legoll

  reply	other threads:[~2020-03-19 15:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-15 20:52 [bug#40083] [PATCH] gnu: Add blktrace Vincent Legoll
2020-03-15 21:00 ` Vincent Legoll
2020-03-15 21:47   ` Vincent Legoll
2020-03-19 14:04     ` Ludovic Courtès
2020-03-19 15:05       ` Vincent Legoll [this message]
2020-03-19 15:48         ` Marius Bakke
2020-03-19 16:01           ` Vincent Legoll
2020-03-19 17:25             ` Vincent Legoll
2020-03-20 17:35               ` bug#40083: " Marius Bakke
2020-03-20 21:52 ` [bug#40083] cleanups submitted upstream Vincent Legoll

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='CAEwRq=qkjehnTvDyqLw=UPiv6gCPBW2Gh15-zqxn2L9sGYK3-Q@mail.gmail.com' \
    --to=vincent.legoll@gmail.com \
    --cc=40083@debbugs.gnu.org \
    --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).