Hi, =dev-python/fonttools-4.0.1 lacks support for Python 2.7. When it was stabilized (bug 699756) it causes a dependency conflict with several packages, including: * dev-python/booleanOperations * dev-python/defcon * dev-python/nototools * dev-python/ufoLib These packages should be revised to depend on <=dev-python/fonttools-3.44.0 More info can be seen at this forum thread: https://forums.gentoo.org/viewtopic-p-8393630.html Reproducible: Always
This rather sounds like you have misconfigured your PYTHON_TARGETS.
(In reply to Andreas Sturmlechner from comment #1) > This rather sounds like you have misconfigured your PYTHON_TARGETS. I ran into the same issue after it stabilized
I ran into the issue long ago in unstable myself, I should probably have considered filling a report back then but my solution was just to mask the newer fonttools until packages which depends on >=dev-python/fonttools-3.36.0 despite supporting _only_ python2.7 stop trying to get the >=4 version that doesn't support it (see nototools/noto-emoji and likely others). I guess it's more specifically be a bug with those packages rather than fonttools.
If what you are talking about is the paste seen in the forum thread, that is not a bug.
(In reply to Andreas Sturmlechner from comment #4) > If what you are talking about is the paste seen in the forum thread, that is > not a bug. Yeah, basically Gentoo ends up in a state where world updates report the listed dependency conflict if you install noto-emoji on stable. If it's not a bug then this should be able to be closed.
Got the same issue. Should be easily fixed in the package ebuilds, right?
I think the actual "bug" is that the whole dependency conflict messages is going to make people come here. Is there no more elegant way to handle this without having users either manually mask it (like I did, so I personally don't mind) or keep seeing this conflict message likely for months every time they try to update?
(In reply to Guido Kroon from comment #6) > Got the same issue. Should be easily fixed in the package ebuilds, right? No, you can't magically invent python3 support in the code.
... shouldn't fonttols-4 be slotted then vs fonttools-3?
I'm now having several pages of conflicts due to dev-python/setuptools. I do see there was a commit (nototools) that states "More updates to make Python 3 compatible" that isn't in the latest package, no idea if that means it's working yet or not (maybe working enough? no idea) But they haven't had a new release with that commit yet :/
Version removed. If you can repro with the current, feel free to reopen.
