From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11416] New: check-uniq-files staging issue
Date: Mon, 22 Oct 2018 07:22:48 +0000 [thread overview]
Message-ID: <bug-11416-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=11416
Bug ID: 11416
Summary: check-uniq-files staging issue
Product: buildroot
Version: 2018.02.4
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: jpcartal at free.fr
CC: buildroot at uclibc.org
Target Milestone: ---
Lots of false positive are happening for files located in staging directory
when building, even when building from scratch e.g. :
Warning: staging file "./usr/lib/libnl-route-3.la" is touched by more than one
package: [u'libnl', u'json-c', u'ncurses', u'readline', u'lvm2', u'popt',
u'util-linux', u'cryptsetup', u'expat', u'dbus', u'e2fsprogs', u'kmod',
u'eudev', u'libpng', u'freetype', u'libopenssl', u'ffmpeg', u'giflib',
u'graphite2', u'icu', u'libffi', u'pcre', u'libglib2', u'harfbuzz',
u'jpeg-turbo', u'json-glib', u'libcap', u'libcurl', u'libexif', u'libmng',
u'libnspr', u'sqlite', u'libnss', u'libogg', u'pciutils', u'tremor', u'webp',
u'wpa_supplicant', u'CUnit']
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2018-10-22 7:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-22 7:22 bugzilla at busybox.net [this message]
2018-10-22 7:33 ` [Buildroot] [Bug 11416] check-uniq-files staging issue bugzilla at busybox.net
2019-02-15 22:06 ` bugzilla at busybox.net
2019-11-29 13:08 ` 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-11416-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox