All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12446] Buildroot fails to finish installing packages
Date: Mon, 06 Jan 2020 17:17:13 +0000	[thread overview]
Message-ID: <bug-12446-163-hDPR4iEvEX@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-12446-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=12446

--- Comment #6 from Yann E. MORIN <yann.morin.1998@free.fr> ---
> https://gist.github.com/RossComputerGuy/4d023304f3a33eeb02cc1a04a9d4e5bc

As I expected, that config file builds perfectly well in upstream
Buildroot.

> try it and you'll see that my issue occurs.

I am sorry, but you have still failed to provide a way to reproduce
your issue on upstream Buildroot, and thus I am no longer going to
spend any time on this build report.

Please, please, try on *your* side to reproduce with upstream
Buildroot. If you can't reproduce, it is a problem with the changes
you did in your fork.

Note that if you want to help update some components versions, you
can send patches to that effect, and we can then help iron out the
issues on the patches.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2020-01-06 17:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-05  2:01 [Buildroot] [Bug 12446] New: Buildroot fails to finish installing packages bugzilla at busybox.net
2020-01-05  2:01 ` [Buildroot] [Bug 12446] " bugzilla at busybox.net
2020-01-05  8:40 ` bugzilla at busybox.net
2020-01-05  8:40 ` bugzilla at busybox.net
2020-01-05 20:10 ` bugzilla at busybox.net
2020-01-05 20:34 ` bugzilla at busybox.net
2020-01-05 20:49 ` bugzilla at busybox.net
2020-01-05 21:01 ` bugzilla at busybox.net
2020-01-06 17:17 ` bugzilla at busybox.net [this message]
2020-01-10  7:57 ` bugzilla at busybox.net

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=bug-12446-163-hDPR4iEvEX@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --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.