All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] python-setuptools: forkbump and add workaround for shebang
Date: Mon, 06 May 2013 08:07:52 -0300	[thread overview]
Message-ID: <51878F08.2030804@zacarias.com.ar> (raw)
In-Reply-To: <87a9o8lfy6.fsf@dell.be.48ers.dk>

On 05/06/2013 04:34 AM, Peter Korsgaard wrote:

> Did this ever get tested? Thomas, could you send your ack / Gustavo,
> could you send a v2 fixing the issues pointed out by Arnout?

It's partially solved for lava-test since it's pulling other
dependencies by itself - that should probably be solved via new
buildroot python packages since it's doing so because they're not found,
and it's not nice when a package starts downloading stuff at
build/install time.
Yes, a V2 is forthcoming addressing Arnout's comments and a few more
fixes/improvements.
You shouldn't have committed the fixes to python-bottle and
python-serial since they both depend on the patch to this package,
they'll probably fail now.
Regards.

  reply	other threads:[~2013-05-06 11:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-13 16:56 [Buildroot] [PATCH 1/3] python-setuptools: forkbump and add workaround for shebang Gustavo Zacarias
2013-04-13 16:56 ` [Buildroot] [PATCH 2/3] python-bottle: bump version and fix shebang Gustavo Zacarias
2013-05-06  7:34   ` Peter Korsgaard
2013-04-13 16:56 ` [Buildroot] [PATCH 3/3] python-serial: " Gustavo Zacarias
2013-05-06  7:35   ` Peter Korsgaard
2013-05-06 11:08     ` Gustavo Zacarias
2013-05-06 11:27       ` Peter Korsgaard
2013-04-16  6:27 ` [Buildroot] [PATCH 1/3] python-setuptools: forkbump and add workaround for shebang Arnout Vandecappelle
2013-04-16 10:17   ` Gustavo Zacarias
2013-05-06  7:34     ` Peter Korsgaard
2013-05-06 11:07       ` Gustavo Zacarias [this message]
2013-05-06 11:30         ` Peter Korsgaard
2013-05-06 11:34           ` Gustavo Zacarias

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=51878F08.2030804@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --cc=buildroot@busybox.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. 
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.