Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 498696 - sys-apps/portage-2.2.7: missing dev-python/pyxattr RDEPEND
Summary: sys-apps/portage-2.2.7: missing dev-python/pyxattr RDEPEND
Status: RESOLVED DUPLICATE of bug 498478
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Portage team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 427888
  Show dependency tree
 
Reported: 2014-01-20 15:05 UTC by Nikoli
Modified: 2014-01-20 18:35 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
patch, works for me (portage-2.2.8.ebuild.xattr.patch,1016 bytes, patch)
2014-01-20 15:05 UTC, Nikoli
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Nikoli 2014-01-20 15:05:44 UTC
Created attachment 368246 [details, diff]
patch, works for me

Several of my desktop systems have PYTHON_SINGLE_TARGET="python2_7" PYTHON_TARGETS="python2_7", but python-3.3 is required at build time for app-misc/media-player-info-21-r1.
After updating app-misc/media-player-info from version 17 to 21-r1 'emerge --depclean --with-bdeps=n -q' removed dev-python/pyxattr instead of dev-lang/python-3.3.3, because portage-2.2.7 and 2.2.8 ebuilds have this in RDEPEND:
xattr? ( kernel_linux? ( || ( >=dev-lang/python-3.3_pre20110902 dev-python/pyxattr ) ) )

My portage is compiled with python2 support only, so removing pyxattr is obviously wrong:
[ebuild   R    ] sys-apps/portage-2.2.7  USE="(ipc) python2 (xattr) -build -doc -epydoc (-pypy2_0) -python3 (-selinux)" LINGUAS="ru" PYTHON_TARGETS="python2_7 (-pypy2_0) -python2_6 -python3_2 -python3_3 (-python3_4)"

Attached patch works fine for me, but not using eapi5 makes deps huge.
Comment 1 Mike Gilbert gentoo-dev 2014-01-20 15:17:05 UTC
I attached a similar patch on bug 498478.
Comment 2 Mike Gilbert gentoo-dev 2014-01-20 18:35:08 UTC

*** This bug has been marked as a duplicate of bug 498478 ***