From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: [gentoo-portage-dev] [PATCH] repoman: filter out duplicate dependencies in error messages
Date: Mon, 4 Jan 2016 16:30:30 -0500 [thread overview]
Message-ID: <1451943030-20380-1-git-send-email-vapier@gentoo.org> (raw)
Some packages list the same atom multiple times (e.g. behind diff USE
flags). If one of them throws an error, we end up listing it more than
once, and the output can get verbose/useless.
---
pym/repoman/scanner.py | 13 +++++++++++--
1 file changed, 11 insertions(+), 2 deletions(-)
diff --git a/pym/repoman/scanner.py b/pym/repoman/scanner.py
index d1c10d7..94ada90 100644
--- a/pym/repoman/scanner.py
+++ b/pym/repoman/scanner.py
@@ -704,13 +704,22 @@ class Scanner(object):
# we have some unsolvable deps
# remove ! deps, which always show up as unsatisfiable
- atoms = [
+ all_atoms = [
str(atom.unevaluated_atom)
for atom in atoms if not atom.blocker]
# if we emptied out our list, continue:
- if not atoms:
+ if not all_atoms:
continue
+
+ # Filter out duplicates. We do this by hand (rather
+ # than use a set) so the order is stable and better
+ # matches the order that's in the ebuild itself.
+ atoms = []
+ for atom in all_atoms:
+ if atom not in atoms:
+ atoms.append(atom)
+
if self.options.output_style in ['column']:
self.qatracker.add_error(mykey,
"%s: %s: %s(%s) %s"
--
2.6.2
next reply other threads:[~2016-01-04 21:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-04 21:30 Mike Frysinger [this message]
2016-01-05 3:17 ` [gentoo-portage-dev] [PATCH] repoman: filter out duplicate dependencies in error messages Brian Dolbec
2016-01-05 9:43 ` Brian Dolbec
2016-01-15 18:22 ` Mike Frysinger
2016-01-05 5:36 ` Zac Medico
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=1451943030-20380-1-git-send-email-vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gentoo-portage-dev@lists.gentoo.org \
/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