public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/portage:master commit in: lib/portage/dep/
Date: Sun, 10 Dec 2023 22:01:55 +0000 (UTC)	[thread overview]
Message-ID: <1702245708.ee127db438307c133fcf650c148ed594ceb68591.sam@gentoo> (raw)

commit:     ee127db438307c133fcf650c148ed594ceb68591
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Mon Sep  4 17:40:06 2023 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun Dec 10 22:01:48 2023 +0000
URL:        https://gitweb.gentoo.org/proj/portage.git/commit/?id=ee127db4

dep: add comment to _eval_deps wrt binding slot deps in any-of || ( ... )

Bug: https://bugs.gentoo.org/455904
Bug: https://bugs.gentoo.org/489458
Bug: https://bugs.gentoo.org/586238
Signed-off-by: Sam James <sam <AT> gentoo.org>

 lib/portage/dep/_slot_operator.py | 1 +
 1 file changed, 1 insertion(+)

diff --git a/lib/portage/dep/_slot_operator.py b/lib/portage/dep/_slot_operator.py
index 82dd7d66c9..d3f506450f 100644
--- a/lib/portage/dep/_slot_operator.py
+++ b/lib/portage/dep/_slot_operator.py
@@ -91,6 +91,7 @@ def _eval_deps(dep_struct, vardbs):
     # and B installed should record subslot on A only since the package is
     # supposed to link against that anyway, and we have no guarantee that B
     # has matching ABI.
+    # See bug #455904, bug #489458, bug #586238.
 
     for i, x in enumerate(dep_struct):
         if isinstance(x, list):


             reply	other threads:[~2023-12-10 22:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-10 22:01 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-06-29  8:19 [gentoo-commits] proj/portage:master commit in: lib/portage/dep/ Sam James
2022-03-15  2:52 Matt Turner
2020-11-28 20:37 Zac Medico
2020-08-06  7:02 Zac Medico
2020-08-03 19:30 Zac Medico
2020-03-03  6:29 Zac Medico
2019-10-23 17:03 Zac Medico
2019-05-11 20:45 Zac Medico
2019-05-04 21:09 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=1702245708.ee127db438307c133fcf650c148ed594ceb68591.sam@gentoo \
    --to=sam@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-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