Bug 563546 – repoman fails to resolve missing USE deps

• Status: RESOLVED FIXED
• Product: Portage Development

[Description Justin Lecher (RETIRED) 2015-10-20 08:39:57 UTC]

checkout f46845b4677bf3d4e820e2f01adb19dce8de36a5
and add pyhton3_5 to PYTHON_COMPAT in dev-python/ipython

repoman -vdx full

doesn't pick up the missing python3.5 support in the dependencies.

[Comment 1 Justin Lecher (RETIRED) 2015-10-20 08:40:58 UTC]

This happens with portage 2.2.23

[Comment 2 Justin Lecher (RETIRED) 2015-10-20 08:44:06 UTC]

emerge does pick it up.

[Comment 3 Zac Medico 2015-10-20 19:00:13 UTC]

(In reply to Justin Lecher from comment #0)
> checkout f46845b4677bf3d4e820e2f01adb19dce8de36a5

That commit is not in gentoo.git:

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f46845b4677bf3d4e820e2f01adb19dce8de36a5

> and add pyhton3_5 to PYTHON_COMPAT in dev-python/ipython
> 
> repoman -vdx full
> 
> doesn't pick up the missing python3.5 support in the dependencies.

The likely cause is this:

profiles/base/use.stable.mask:python_targets_python3_5

Because dev-python/ipython-3.2.1-r1 has stable keywords.

If I remove that setting from profiles/base/use.stable.mask, repoman complains loudly.

[Comment 4 Justin Lecher (RETIRED) 2015-10-20 19:33:46 UTC]

(In reply to Zac Medico from comment #3)
> (In reply to Justin Lecher from comment #0)
> > checkout f46845b4677bf3d4e820e2f01adb19dce8de36a5
> 
> That commit is not in gentoo.git:
> 
> https://gitweb.gentoo.org/repo/gentoo.git/commit/
> ?id=f46845b4677bf3d4e820e2f01adb19dce8de36a5

I am sorry. It's not yet committed.

Will comment once I hey everything finished.

[Comment 5 Justin Lecher (RETIRED) 2015-10-21 05:48:37 UTC]

(In reply to Zac Medico from comment #3)
> The likely cause is this:
> 
> profiles/base/use.stable.mask:python_targets_python3_5
> 
> Because dev-python/ipython-3.2.1-r1 has stable keywords.
> 
> If I remove that setting from profiles/base/use.stable.mask, repoman
> complains loudly.

But shouldn't repoman complain loudly for the ~arch case? I would be able to commit it in that stage but it would be broken when trying to emerge.

[Comment 6 Zac Medico 2015-10-21 06:52:51 UTC]

(In reply to Justin Lecher from comment #5)
> But shouldn't repoman complain loudly for the ~arch case? I would be able to
> commit it in that stage but it would be broken when trying to emerge.

That's true. We can trace the behavior to this line where the stable keyword is translated to a stable profile configuration:

https://gitweb.gentoo.org/proj/portage.git/tree/pym/repoman/scanner.py?h=v2.2.23#n389

So, repoman does not consider unstable ACCEPT_KEYWORDS when the ebuild has stable keywords.

[Comment 7 Zac Medico 2015-10-23 06:52:01 UTC]

I've started working on a patch in this branch:

https://github.com/zmedico/portage/tree/bug_563546

[Comment 8 Zac Medico 2015-10-25 23:38:16 UTC]

There's a working patch in the following branch:

https://github.com/zmedico/portage/tree/bug_563546

You can test it like this:

echo '=sys-apps/portage-9999 **' >> /etc/portage/package.accept_keywords
portage_LIVE_BRANCH=bug_563546 \
portage_LIVE_REPO=https://github.com/zmedico/portage.git \
emerge -1 =sys-apps/portage-9999

I've posted it for review here:

https://archives.gentoo.org/gentoo-portage-dev/message/c2b2e41933760a9e0326b06b8bf47586

[Comment 9 Zac Medico 2015-10-26 16:02:03 UTC]

This is in the master branch:

https://gitweb.gentoo.org/proj/portage.git/commit/?id=713611a67455d2f38b0b452d0eaed17fd68bd517

[Comment 10 Zac Medico 2016-03-14 02:54:33 UTC]

Fixed in 2.2.24.