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 12246] host-policycoreutils-graph-depends fails
Date: Sat, 21 Sep 2019 15:58:07 +0000	[thread overview]
Message-ID: <bug-12246-163-vBKVKyAp1W@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-12246-163@https.bugs.busybox.net/>

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

--- Comment #2 from Yann E. MORIN <yann.morin.1998@free.fr> ---
(In reply to Thomas Petazzoni from comment #0)
As you already found, the issue is because the package is not enabled (it is a
host package without a config.in option), and is also not in the dependency
chain of any other package.

The proposal I have is to add a check to graph-depends, that checks that the
requested root package is indeed enabled, and if not, inform the user rather
than spew a traceback.

(In reply to Arnout Vandecappelle from comment #1)
> circular dependencies are no longer handles properly by graph-depends
Yes they are:
https://git.buildroot.org/buildroot/tree/support/scripts/graph-depends#n133 and
https://git.buildroot.org/buildroot/tree/support/scripts/graph-depends#n337

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

  parent reply	other threads:[~2019-09-21 15:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-21 14:16 [Buildroot] [Bug 12246] New: host-policycoreutils-graph-depends fails bugzilla at busybox.net
2019-09-21 14:16 ` [Buildroot] [Bug 12246] " bugzilla at busybox.net
2019-09-21 15:18 ` bugzilla at busybox.net
2019-09-21 15:58 ` bugzilla at busybox.net [this message]
2019-09-21 16:13 ` bugzilla at busybox.net
2024-06-15 14:51 ` bugzilla

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-12246-163-vBKVKyAp1W@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.