Bug 481242 – =dev-python/networkx-1.6 tries to install on python 3.2 even it does not support it - *** Error compiling '/usr/lib64/python3.2/site-packages/networkx/external/decorator/_decorator.py'...

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Yichao Zhou 2013-08-16 03:06:19 UTC]

Created attachment 356144 [details]
emerge --info

Some package still relies on networkx-1.6.  Emerge with networkx-1.7 successes.

See attachments for install log.

[Comment 1 Yichao Zhou 2013-08-16 03:07:03 UTC]

Created attachment 356146 [details]
emerge networkx-1.6

[Comment 2 Yichao Zhou 2013-08-17 16:39:03 UTC]

The mistake is very obvious.

# Dependency on any version of Python 2 or 3, which is at least 2.6.*.
PYTHON_DEPEND="*:2.6"

You shoud change it to
PYTHON_DEPEND="2::2.6"

See http://www.gentoo.org/proj/en/Python/developersguide.xml.

The whole networkx series has such problem.

[Comment 3 Michał Górny 2013-08-17 18:29:25 UTC]

> Yichao Zhou <[e-mail]> changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                  CC|                            |[e-mail]

And why are you CC-ing me? Just FYI:

1. users don't CC developers themselves, bug-wranglers assign bugs for them,

2. bug-wranglers have already assigned this bug correctly and there is no reason that you should override their decisions,

3. if you read the changelog entry instead of dumb searching for e-mails, you'd notice that my only contribution to this ebuild was a dependency update,

4. I'm on python@ so no need to mail me twice.

And for the ebuild, please name that package. I don't see one in the tree. If we're going to do anything about -1.6, it would be backporting the 1.7-r2 ebuild.

The guide you are referring to along with python.eclass is highly deprecated and almost nobody wants to mess with it.

[Comment 4 Yichao Zhou 2013-08-18 05:45:24 UTC]

> 1. users don't CC developers themselves, bug-wranglers assign bugs for them,
> 
> 2. bug-wranglers have already assigned this bug correctly and there is no
> reason that you should override their decisions,
> 
> 3. if you read the changelog entry instead of dumb searching for e-mails,
> you'd notice that my only contribution to this ebuild was a dependency
> update,
> 
> 4. I'm on python@ so no need to mail me twice.

Sorry I shouldn't do that.

> And for the ebuild, please name that package. I don't see one in the tree.
> If we're going to do anything about -1.6, it would be backporting the 1.7-r2
> ebuild.

Title is clear:  =dev-python/networkx-1.6.   I'm pretty sure that it is on the tree, at least for yesterday unless it is removed today.  Networkx-1.7-r2 is using python-r1.eclass.  So it does not has such problem.  But networkx-1.7{,r1} is affected.

> The guide you are referring to along with python.eclass is highly deprecated
> and almost nobody wants to mess with it.

This ebuild is very old.  And it just has some typo on it which make it not installable.  Replacing "*" with "2" is quite easy, unless you tell me why it is wrong.  How can you call this ``mess with it''??

Problem is simple, networkx-1.6 doesn't support python3.  But it is masked as  it could in the ebuild.

[Comment 5 Michał Górny 2013-08-18 07:51:50 UTC]

1.7-r2 is around since April. Please check what exactly pulls in -1.6 because all in-tree deps are unversioned. If it's not really required indeed, we'll just drop the old ebuilds.

[Comment 6 François Bissey 2013-08-18 09:40:21 UTC]

Not needed in tree. It is needed in the sage-on-gentoo overlay. A slight change in API means that 1.7 breaks things in sage.
I am happy to adopt 1.6 in the overlay if you want to get rid of it in the main tree.

[Comment 7 Michał Górny 2013-08-18 10:32:22 UTC]

(In reply to Francois Bissey from comment #6)
> Not needed in tree. It is needed in the sage-on-gentoo overlay. A slight
> change in API means that 1.7 breaks things in sage.
> I am happy to adopt 1.6 in the overlay if you want to get rid of it in the
> main tree.

Ok, thanks. I just need to know that. I'll fix -1.7-r2 first, then do a -1.6-r1.

[Comment 8 Michał Górny 2013-08-18 10:42:53 UTC]

I've just committed -r1 that should be free of the bug.