Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] Open bug overview: help wanted!
Date: Wed, 16 Jul 2014 14:18:44 -0300	[thread overview]
Message-ID: <53C6B3F4.6060101@zacarias.com.ar> (raw)
In-Reply-To: <CAAXf6LXxPunhd=VU2jXqRvE5rFmiApZM1FxaTvLWgHCTqC2e5A@mail.gmail.com>

On 07/16/2014 02:08 PM, Thomas De Schampheleire wrote:

> Thanks a lot for working on this.
> If Jeremy or you could respin the main patch, that'd be great. But I
> assume it can only be applied once all the package fixes are in?
> Are nano and statserial the only ones needing fixing?

statserial is a generic fix so it was applied yesterday by Thomas P.
nano depends on the ncursesw config knob - it can be applied but
technically it's a no-op until ncursesw is in so should be part of the
series or at least applied immediately after ncursesw.
allyespackageconfig was my test run and yes, there shouldn't be any
unpleasant surprises with the patches applied, just maybe a couple of
sneaked new/bumped packages since my test tree run and now but unlikely
given that only 2 packages "complained".
Of course i couldn't finish a similar run on static because that would
require to fix all static build failures :)
Regarding the respin we can wait for Jeremy, modify his patch or just do
an extra patch with the static fix - we still need the nano fix anyway.
I'd go with the 3rd option since it's pretty straightforward.
Regards.

  reply	other threads:[~2014-07-16 17:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-12 18:50 [Buildroot] Open bug overview: help wanted! Thomas De Schampheleire
2014-07-12 20:12 ` Gustavo Zacarias
2014-07-16 17:08   ` Thomas De Schampheleire
2014-07-16 17:18     ` Gustavo Zacarias [this message]
2014-07-16 18:33       ` Thomas De Schampheleire
2014-07-12 21:53 ` Yann E. MORIN
2014-07-13  1:54   ` Mike Zick
2014-07-13  9:05     ` Yann E. MORIN
2014-07-13 13:29       ` Mike Zick
2014-07-13 14:56         ` Yann E. MORIN
2014-07-16 18:32   ` Thomas De Schampheleire
2014-07-15 19:27 ` Károly Kasza
2014-07-15 20:12   ` Thomas Petazzoni
2014-07-19  9:58     ` Károly Kasza
2014-07-16 15:00   ` Johan Oudinet
2014-07-16  7:31 ` Thomas Petazzoni
2014-07-16 18:35   ` Thomas De Schampheleire

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=53C6B3F4.6060101@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox