Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 470278 - app-text/pelican-3.2 and above are python 3.2 compliant
Summary: app-text/pelican-3.2 and above are python 3.2 compliant
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Python Gentoo Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-18 20:06 UTC by Thibaud CANALE
Modified: 2013-05-29 06:16 UTC (History)
1 user (show)

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


Attachments
emerge --info (file_470278.txt,5.11 KB, text/plain)
2013-05-18 20:06 UTC, Thibaud CANALE
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Thibaud CANALE 2013-05-18 20:06:49 UTC
Created attachment 348622 [details]
emerge --info

Hello,

Based on info from http://blog.getpelican.com/pelican-3.2-released.html, app-text/pelican-3.2 and above are Python 3.2 compliant.
However, app-text/pelican-3.2's ebuild has PYTHON_COMPAT=( python2_7 ) option, and shouldn't.


Output of emerge when trying to emerge app-text/pelican-3.2
> # emerge -vat 'app-text/pelican'
> 
> These are the packages that would be merged, in reverse order:
>
> Calculating dependencies... done!
>
> emerge: there are no ebuilds built with USE flags to satisfy "dev-python/six[python_targets_python2_7(-)?,-python_single_target_python2_7(-)]".
> !!! One of the following packages is required to complete your request:
> - app-text/pelican-3.2::gentoo (Change USE: -python_targets_python2_7)
> (dependency required by "app-text/pelican-3.2" [ebuild])
> (dependency required by "pelican" [argument])

The temporaly solution is to write
=app-text/pelican-3.2   python_targets_python2_7
in /etc/portage/package.use

Best regards,


-- 
Thibaud CANALE
Comment 1 Thibaud CANALE 2013-05-18 23:37:40 UTC
Sorry, 2 mistakes:

> The temporaly solution is to write
> =app-text/pelican-3.2   python_targets_python2_7
> in /etc/portage/package.use

typo mistake:
=app-text/pelican-3.2   -python_targets_python2_7


And even with it, =app-text/pelican-3.2 is not emerging:

 * Messages for package app-text/pelican-3.2:

 * No Python implementation selected for the build. Please add one
 * of the following values to your PYTHON_TARGETS (in make.conf):
 *
 * python2_7
 * ERROR: app-text/pelican-3.2 failed (compile phase):
 *   No supported Python implementation in PYTHON_TARGETS.
 *
 * Call stack:
 *     ebuild.sh, line   93:  Called src_compile
 *   environment, line 3304:  Called distutils-r1_src_compile
 *   environment, line  890:  Called _distutils-r1_run_foreach_impl 'distutils-r1_python_compile'
 *   environment, line  219:  Called python_parallel_foreach_impl 'distutils-r1_run_phase' 'distutils-r1_python_compile'
 *   environment, line 3180:  Called _python_obtain_impls
 *   environment, line  579:  Called _python_validate_useflags
 *   environment, line  675:  Called die
 * The specific snippet of code:
 *       die "No supported Python implementation in PYTHON_TARGETS."

In fact, I don't have a solution, I even don't understand the reamson of this message when python2_7 is activeated when I am lokking in ebuild files:
> emerge: there are no ebuilds built with USE flags to satisfy "dev-python/six[python_targets_python2_7(-)?,-python_single_target_python2_7(-)]".

Thanks for your attention.


-- 
Thibaud CANALE
Comment 2 Ian Delaney (RETIRED) gentoo-dev 2013-05-29 06:16:02 UTC
  29 May 2013; Ian Delaney <idella4@gentoo.org> pelican-3.2.1.ebuild:
  add py3 support, fixes Bug #470278