From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12246] New: host-policycoreutils-graph-depends fails
Date: Sat, 21 Sep 2019 14:16:23 +0000 [thread overview]
Message-ID: <bug-12246-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=12246
Bug ID: 12246
Summary: host-policycoreutils-graph-depends fails
Product: buildroot
Version: 2019.08
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: thomas.petazzoni at free-electrons.com
CC: buildroot at uclibc.org
Target Milestone: ---
$ make host-policycoreutils-graph-depends
Getting dependency tree...
Traceback (most recent call last):
File "/home/thomas/projets/buildroot/support/scripts/graph-depends", line
357, in <module>
sys.exit(main())
File "/home/thomas/projets/buildroot/support/scripts/graph-depends", line
341, in main
dict_deps = remove_extra_deps(dict_deps, rootpkg, args.transitive,
arrow_dir)
File "/home/thomas/projets/buildroot/support/scripts/graph-depends", line
170, in remove_extra_deps
if d not in deps[rootpkg]:
KeyError: 'host-policycoreutils'
make[1]: *** [package/policycoreutils/policycoreutils.mk:100:
host-policycoreutils-graph-depends] Error 1
make: *** [Makefile:84: _all] Error 2
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2019-09-21 14:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-21 14:16 bugzilla at busybox.net [this message]
2019-09-21 14:16 ` [Buildroot] [Bug 12246] host-policycoreutils-graph-depends fails bugzilla at busybox.net
2019-09-21 15:18 ` bugzilla at busybox.net
2019-09-21 15:58 ` bugzilla at busybox.net
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@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.