[gentoo-user] openshot-2.0.6.ebuild

[gentoo-user] openshot-2.0.6.ebuild

[James]

Howdy,

Looking at the openshot ebuild, I see::
EAPI=6
PYTHON_COMPAT=( python3_{4,5} )

among other interesting details.

So it should work with python 3.4 or 3.5, right?

I have this::
Installed versions:  2.7.10-r1  3.4.3-r1 
(examples gdbm ipv6 ncurses readline sqlite ssl threads tk wide-unicode xml
-berkdb -build -doc -hardened -wininst ELIBC="-uclibc")

Available Python interpreters:
  [1]   python2.7
  [2]   python3.4 *


currently I get this build failure message::

The ebuild selected to satisfy "=media-video/openshot-2.0.6" has unmet
requirements.
- media-video/openshot-2.0.6::gentoo USE="" ABI_X86="64"
PYTHON_SINGLE_TARGET="-python3_4 -python3_5" PYTHON_TARGETS="python3_4
-python3_5"

  The following REQUIRED_USE flag constraints are unsatisfied:
    exactly-one-of ( python_single_target_python3_4
python_single_target_python3_5 )

  The above constraints are a subset of the following complete expression:
    exactly-one-of ( python_single_target_python3_4
python_single_target_python3_5 ) python_single_target_python3_4? (
python_targets_python3_4 ) python_single_target_python3_5? (
python_targets_python3_5 )


So, I should not have to install python 3.5. But that's no big deal.
If I do install python 3.5, it'll have it's own slot and I should leave
python-3.4x as the default or can I set the default to 3.5x? Not sure what I
missed.


discussion or guidance is welcome,
James

Re: [gentoo-user] openshot-2.0.6.ebuild

[Dale]

James wrote:
> Howdy,
>
> Looking at the openshot ebuild, I see::
> EAPI=6
> PYTHON_COMPAT=( python3_{4,5} )
>
> among other interesting details.
>
> So it should work with python 3.4 or 3.5, right?
>
> I have this::
> Installed versions:  2.7.10-r1  3.4.3-r1 
> (examples gdbm ipv6 ncurses readline sqlite ssl threads tk wide-unicode xml
> -berkdb -build -doc -hardened -wininst ELIBC="-uclibc")
>
> Available Python interpreters:
>   [1]   python2.7
>   [2]   python3.4 *
>
>
> currently I get this build failure message::
>
> The ebuild selected to satisfy "=media-video/openshot-2.0.6" has unmet
> requirements.
> - media-video/openshot-2.0.6::gentoo USE="" ABI_X86="64"
> PYTHON_SINGLE_TARGET="-python3_4 -python3_5" PYTHON_TARGETS="python3_4
> -python3_5"
>
>   The following REQUIRED_USE flag constraints are unsatisfied:
>     exactly-one-of ( python_single_target_python3_4
> python_single_target_python3_5 )
>
>   The above constraints are a subset of the following complete expression:
>     exactly-one-of ( python_single_target_python3_4
> python_single_target_python3_5 ) python_single_target_python3_4? (
> python_targets_python3_4 ) python_single_target_python3_5? (
> python_targets_python3_5 )
>
>
> So, I should not have to install python 3.5. But that's no big deal.
> If I do install python 3.5, it'll have it's own slot and I should leave
> python-3.4x as the default or can I set the default to 3.5x? Not sure what I
> missed.
>
>
> discussion or guidance is welcome,
> James
>
>

I ran into this the other day.  My thinking, the Python 3 stuff is
coming so may as well go with something that should be around longer
than Python 2 since the package supports Python 3.  So, I did this in
package.use:

media-video/openshot python_single_target_python3_4

I have this available:

root@fireball / # eselect python list
Available Python interpreters:
  [1]   python2.7 *
  [2]   python3.4
root@fireball / #

I'm not sure if this has changed but I think it used to be recommended
not to set Python 3 stuff to active, at the time anyway.  That may have
changed.  I read that either here or on -dev a good while back.  May
want to see what others think on this or it could be that everything you
use works fine that way. 

Hope that helps.

Dale

:-)  :-) 

Re: [gentoo-user] openshot-2.0.6.ebuild

[Alan McKinnon]

On 24/03/2016 18:35, James wrote:
> Howdy,
> 
> Looking at the openshot ebuild, I see::
> EAPI=6
> PYTHON_COMPAT=( python3_{4,5} )
> 
> among other interesting details.
> 
> So it should work with python 3.4 or 3.5, right?

Not quite.

IIRC PYTHON_COMPAT is the old way
PYTHON*_TARGET_* is the new way

> 
> I have this::
> Installed versions:  2.7.10-r1  3.4.3-r1 
> (examples gdbm ipv6 ncurses readline sqlite ssl threads tk wide-unicode xml
> -berkdb -build -doc -hardened -wininst ELIBC="-uclibc")
> 
> Available Python interpreters:
>   [1]   python2.7
>   [2]   python3.4 *
> 
> 
> currently I get this build failure message::
> 
> The ebuild selected to satisfy "=media-video/openshot-2.0.6" has unmet
> requirements.
> - media-video/openshot-2.0.6::gentoo USE="" ABI_X86="64"
> PYTHON_SINGLE_TARGET="-python3_4 -python3_5" PYTHON_TARGETS="python3_4
> -python3_5"

There's your problem.
PYTHON_SINGLE_TARGET is not set but the ebuild requires it (see
following error)
> 
>   The following REQUIRED_USE flag constraints are unsatisfied:
>     exactly-one-of ( python_single_target_python3_4
> python_single_target_python3_5 )
> 
>   The above constraints are a subset of the following complete expression:
>     exactly-one-of ( python_single_target_python3_4
> python_single_target_python3_5 ) python_single_target_python3_4? (
> python_targets_python3_4 ) python_single_target_python3_5? (
> python_targets_python3_5 )
> 
> 
> So, I should not have to install python 3.5. But that's no big deal.
> If I do install python 3.5, it'll have it's own slot and I should leave
> python-3.4x as the default or can I set the default to 3.5x? Not sure what I
> missed.
> 
> 
> discussion or guidance is welcome,

Add PYTHON_SINGLE_TARGET="python3_4" to USE for this package.

This might be an ebuild bug (python packages should have all been fixed
by now), or maybe it's on your end.

What do you have for
emerge --info | grep PYTHON


-- 
Alan McKinnon
alan.mckinnon@gmail.com

Re: [gentoo-user] openshot-2.0.6.ebuild

[Peter Humphrey]

On Thursday 24 March 2016 11:54:03 Dale wrote:

> I'm not sure if this has changed but I think it used to be recommended
> not to set Python 3 stuff to active, at the time anyway.  That may have
> changed.  I read that either here or on -dev a good while back.  May
> want to see what others think on this or it could be that everything you
> use works fine that way.

I saw that too, and I've always been sure to eselect python to 2.7, but for 
a long time now the installation CD has come with 3.3 or 3.4 set, so I 
assume it's okay to eselect 3.4 nowadays.

-- 
Rgds
Peter

linux counter 5290, 1994/04/23

[gentoo-user] Re: openshot-2.0.6.ebuild

[James]

Alan McKinnon <alan.mckinnon <at> gmail.com> writes:

> What do you have for
> emerge --info | grep PYTHON


a ton of flags....    Here's the relevant part?::

 PYTHON_SINGLE_TARGET="python2_7" PYTHON_TARGETS="python2_7 python3_4"

 USE_PYTHON


I thought I read somewhere that this sort of bugger had been addressed
with EAPI-6, which the ebuild is? It could easily be me though, as
I have been noodling with python and ipython and  billions other
little python codes....so no telling what I've buggered up. Still
all of the other python  centric codes are happy, atm.

I'm getting ready to start working on (2) new python ebuilds::
turbogears-2 and dpark (a very cool "in-memory" python knockoff of
apache-spark):: so bear that in mind on any other recommendations.


???
James

[1] https://github.com/douban/dpark

[2] http://turbogears.org/

[gentoo-user] Re: openshot-2.0.6.ebuild

[»Q«]

On Thu, 24 Mar 2016 18:14:39 +0000 (UTC)
James <wireless@tampabay.rr.com> wrote:

> Alan McKinnon <alan.mckinnon <at> gmail.com> writes:
> 
> > What do you have for
> > emerge --info | grep PYTHON  
> 
> 
> a ton of flags....    Here's the relevant part?::
> 
>  PYTHON_SINGLE_TARGET="python2_7" PYTHON_TARGETS="python2_7 python3_4"

You have PYTHON_SINGLE_TARGET="python2_7" but the ebuild requires it to
be either python3_4 or python3_5.  You can set it in package.use with 

media-video/openshot python_single_target_python3_4

Re: [gentoo-user] openshot-2.0.6.ebuild

[Dale]

Peter Humphrey wrote:
> On Thursday 24 March 2016 11:54:03 Dale wrote:
>
>> I'm not sure if this has changed but I think it used to be recommended
>> not to set Python 3 stuff to active, at the time anyway.  That may have
>> changed.  I read that either here or on -dev a good while back.  May
>> want to see what others think on this or it could be that everything you
>> use works fine that way.
> I saw that too, and I've always been sure to eselect python to 2.7, but for 
> a long time now the installation CD has come with 3.3 or 3.4 set, so I 
> assume it's okay to eselect 3.4 nowadays.
>


Sounds like it is safe.  I can't recall when I read that but it has been
a good while.  I guess I missed the change.  Makes me wonder if it is
safe for me to switch over.  <thinking>

Dale

:-)  :-) 

Re: [gentoo-user] openshot-2.0.6.ebuild

[Alan McKinnon]

On 24/03/2016 19:19, Peter Humphrey wrote:
> On Thursday 24 March 2016 11:54:03 Dale wrote:
> 
>> I'm not sure if this has changed but I think it used to be recommended
>> not to set Python 3 stuff to active, at the time anyway.  That may have
>> changed.  I read that either here or on -dev a good while back.  May
>> want to see what others think on this or it could be that everything you
>> use works fine that way.
> 
> I saw that too, and I've always been sure to eselect python to 2.7, but for 
> a long time now the installation CD has come with 3.3 or 3.4 set, so I 
> assume it's okay to eselect 3.4 nowadays.
> 


It's probably not safe, python2 and python3 are basically different
languages, not really compatible. Out there in the wild, there are still
more python apps not migrated to use python3 than have been migrated.

A user has 2 choices:

- set python2 as default and configure packages that can use python3 to
use it
- set python3 as default and configure packages that requires python2 to
use it

Which method you use depends entirely on what packages you use.

-- 
Alan McKinnon
alan.mckinnon@gmail.com

Re: [gentoo-user] Re: openshot-2.0.6.ebuild

[Alan McKinnon]

On 24/03/2016 20:14, James wrote:
> Alan McKinnon <alan.mckinnon <at> gmail.com> writes:
> 
>> What do you have for
>> emerge --info | grep PYTHON
> 
> 
> a ton of flags....    Here's the relevant part?::
> 
>  PYTHON_SINGLE_TARGET="python2_7" PYTHON_TARGETS="python2_7 python3_4"
> 
>  USE_PYTHON
> 
> 
> I thought I read somewhere that this sort of bugger had been addressed
> with EAPI-6, which the ebuild is? It could easily be me though, as
> I have been noodling with python and ipython and  billions other
> little python codes....so no telling what I've buggered up. Still
> all of the other python  centric codes are happy, atm.


The solution is right there in the original output. The ebuild needs
3_4, you have 2_7. So set it in USE.


-- 
Alan McKinnon
alan.mckinnon@gmail.com

Re: [gentoo-user] openshot-2.0.6.ebuild

[Peter Humphrey]

On Friday 25 March 2016 10:03:34 Alan McKinnon wrote:
> On 24/03/2016 19:19, Peter Humphrey wrote:
> > On Thursday 24 March 2016 11:54:03 Dale wrote:
> >> I'm not sure if this has changed but I think it used to be recommended
> >> not to set Python 3 stuff to active, at the time anyway.  That may have
> >> changed.  I read that either here or on -dev a good while back.  May
> >> want to see what others think on this or it could be that everything
> >> you
> >> use works fine that way.
> > 
> > I saw that too, and I've always been sure to eselect python to 2.7, but
> > for a long time now the installation CD has come with 3.3 or 3.4 set,
> > so I assume it's okay to eselect 3.4 nowadays.
> 
> It's probably not safe, python2 and python3 are basically different
> languages, not really compatible. Out there in the wild, there are still
> more python apps not migrated to use python3 than have been migrated.
> 
> A user has 2 choices:
> 
> - set python2 as default and configure packages that can use python3 to
> use it
> - set python3 as default and configure packages that requires python2 to
> use it
> 
> Which method you use depends entirely on what packages you use.

But Gentoo has two python versions set: a python 2 and a python 3. I assume 
that ebuilds specify which version they need, so the default is rarely used.

In that case it won't matter which is set as default.

-- 
Rgds
Peter

linux counter 5290, 1994/04/23

Re: [gentoo-user] openshot-2.0.6.ebuild

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 1247 bytes --]

On Fri, 25 Mar 2016 09:40:07 +0000, Peter Humphrey wrote:

> > A user has 2 choices:
> > 
> > - set python2 as default and configure packages that can use python3
> > to use it
> > - set python3 as default and configure packages that requires python2
> > to use it
> > 
> > Which method you use depends entirely on what packages you use.  
> 
> But Gentoo has two python versions set: a python 2 and a python 3. I
> assume that ebuilds specify which version they need, so the default is
> rarely used.
> 
> In that case it won't matter which is set as default.

It's not the ebuilds, they are written n bash, it's the various scripts
you tun. If they specify the interpreter as python2 or python3,
everything is fine (you can eselect the default for each of these) but if
it just calls python, the script had better be written for the version
you have as default.

On the basis that all python3 scripts were written at a time when the
difference was known, but the same does not apply to all python2 scripts,
I prefer to leave the default at python2. That was everything should run,
no matter how old it is.


-- 
Neil Bothwick

It may be that your sole purpose in life is simply to serve as a
warning to others.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

[gentoo-user] Resolved : openshot-2.0.6.ebuild

[James]

Alan McKinnon <alan.mckinnon <at> gmail.com> writes:


> > Alan McKinnon <alan.mckinnon <at> gmail.com> writes:
> >> emerge --info | grep PYTHON

> >  PYTHON_SINGLE_TARGET="python2_7" PYTHON_TARGETS="python2_7 python3_4"
> >  USE_PYTHON

> The solution is right there in the original output. The ebuild needs
> 3_4, you have 2_7. So set it in USE.

So you are saying the first output of that env parse is the default setting?
I thought eselect set the priority::


# eselect python list
Available Python interpreters:
  [1]   python2.7
  [2]   python3.4 *


If that's not true where do I got to set the default to 3.4?

I.E. where is the best place to set that env varialble for python? Is it
a system default that is not address by eselect?

It was set up to python 3.4 by default, according to eselect. The openshot
(EAPI-6) ebuild did not pick this up, automatically, so I set these falgs
manually in  ::/etc/portage/package.use/package.use::

media-video/openshot python_single_target_python3_4 
dev-python/PyQt5	webkit gui widgets opengl network printsupport

I view python 2.x and deprecated, hence I never want to set it as
a default, ymmv. 

I guess it's a bug as I have not had problem with other python codes/ebuilds.
I'd need some verification on the status as a bug to file with bgo. 

thx for all the help and comments to everyone.
James

Re: [gentoo-user] Resolved : openshot-2.0.6.ebuild

[Alan McKinnon]

On 25/03/2016 17:09, James wrote:
> Alan McKinnon <alan.mckinnon <at> gmail.com> writes:
> 
> 
>>> Alan McKinnon <alan.mckinnon <at> gmail.com> writes:
>>>> emerge --info | grep PYTHON
> 
>>>  PYTHON_SINGLE_TARGET="python2_7" PYTHON_TARGETS="python2_7 python3_4"
>>>  USE_PYTHON
> 
>> The solution is right there in the original output. The ebuild needs
>> 3_4, you have 2_7. So set it in USE.
> 
> So you are saying the first output of that env parse is the default setting?
> I thought eselect set the priority::
> 
> 
> # eselect python list
> Available Python interpreters:
>   [1]   python2.7
>   [2]   python3.4 *
> 
> 
> If that's not true where do I got to set the default to 3.4?
> 
> I.E. where is the best place to set that env varialble for python? Is it
> a system default that is not address by eselect?
> 
> It was set up to python 3.4 by default, according to eselect. The openshot
> (EAPI-6) ebuild did not pick this up, automatically, so I set these falgs
> manually in  ::/etc/portage/package.use/package.use::
> 
> media-video/openshot python_single_target_python3_4 
> dev-python/PyQt5	webkit gui widgets opengl network printsupport
> 
> I view python 2.x and deprecated, hence I never want to set it as
> a default, ymmv. 
> 
> I guess it's a bug as I have not had problem with other python codes/ebuilds.
> I'd need some verification on the status as a bug to file with bgo. 

James,

You are being especially obtuse this time. Ate too many chocolate easter
eggs this weekend?

LOOK at the emerge output please (eselect python is a red herring), this
is what it says:

  The following REQUIRED_USE flag constraints are unsatisfied:
    exactly-one-of ( python_single_target_python3_4
python_single_target_python3_5 )

Clear as daylight. It says right there it needs PYTHON_SINGLE_TARGET to
be 1, and only 1, between 3.4 and 3.5.
You have it set as 2.7 per your emerge info.

Do what Q says 1 reply higher up in this sub-thread and your problem
will go away.

Here's what's happening:
When the ebuild installs a python package, it needs to determine what
python you will use and what goes in the python script shebang. This is
what PYTHON*TARGET does - it's really just a USE flag and emerge uses
that USE flag to figure out which python version to install against.

The flag is defined like any other flag - globally in make.conf or
per-package in package.use. The ebuild can and should assist by setting
it's own variables about what it can work with, but all of that is
undone when you override the ebuild with your own USE.

There is no bug here, your USE is set wrong by you.

eselect python: This handy gadget is a different thing from the above.
It determines what gets run when you type the command "python",
"python2" or "python3", because you can have lots of them. eselect
python tells Gentoo what is the global default. It has NOTHING to do
with installs.

The reason that all your other packages work and this one doesn't is
because so far that's the only one that has tripped over your
misconfigured USE.


-- 
Alan McKinnon
alan.mckinnon@gmail.com

[gentoo-user] Re: Resolved : openshot-2.0.6.ebuild

[»Q«]

On Fri, 25 Mar 2016 22:27:14 +0200
Alan McKinnon <alan.mckinnon@gmail.com> wrote:

>   The following REQUIRED_USE flag constraints are unsatisfied:
>     exactly-one-of ( python_single_target_python3_4
> python_single_target_python3_5 )
> 
> It says right there it needs PYTHON_SINGLE_TARGET
> to be 1, and only 1, between 3.4 and 3.5.
> You have it set as 2.7 per your emerge info.

> The reason that all your other packages work and this one doesn't is
> because so far that's the only one that has tripped over your
> misconfigured USE.

I also had PYTHON_SINGLE_TARGET set to 2.7 because the last time I
checked (which could be over a year ago) something I had was requiring
that.

This thread prompted me to change it to 3.4 and try a --pretend
update.  I've got seven packages to re-build, without any errors,
blockers, or other complaints from portage.

I mention it because some of my fellow USE="-*" lunatics may want to
give it a try and possibly preemptively avoid an eventual headache like
the one that hit James.

[gentoo-user] Re: Resolved : openshot-2.0.6.ebuild

[James]

Alan McKinnon <alan.mckinnon <at> gmail.com> writes:


> > # eselect python list
> >   [2]   python3.4 *

> You are being especially obtuse this time. Ate too many chocolate easter
> eggs this weekend?

That's the nicest way somebody has ever call me a moron, pig-headed
or just dense. sorry...


> LOOK at the emerge output please (eselect python is a red herring), this
> is what it says:

>   The following REQUIRED_USE flag constraints are unsatisfied:
>     exactly-one-of ( python_single_target_python3_4
> python_single_target_python3_5 )

> Clear as daylight. It says right there it needs PYTHON_SINGLE_TARGET to
> be 1, and only 1, between 3.4 and 3.5.
> You have it set as 2.7 per your emerge info.

Not intentionally.

> Do what Q says 1 reply higher up in this sub-thread and your problem
> will go away.

I got all of that.

> Here's what's happening:
> When the ebuild installs a python package, it needs to determine what
> python you will use and what goes in the python script shebang. This is
> what PYTHON*TARGET does - it's really just a USE flag and emerge uses
> that USE flag to figure out which python version to install against.

> The flag is defined like any other flag - globally in make.conf or
> per-package in package.use. The ebuild can and should assist by setting
> it's own variables about what it can work with, but all of that is
> undone when you override the ebuild with your own USE.

> There is no bug here, your USE is set wrong by default.

> eselect python: This handy gadget is a different thing from the above.
> It determines what gets run when you type the command "python",
> "python2" or "python3", because you can have lots of them. eselect
> python tells Gentoo what is the global default. It has NOTHING to do
> with installs.

Actually, I did not know this, seriously. I thought that setting eselect
python, was the master way of setting *everything* to the version of python
selected, including the relevant USE flags. I got it now. No worries. 


And yes I'm severely distracted with several other things. I'm only
interested in a variety of video codes, to run on gentoo  clusters
as custom frameworks, benchmarking and testing. I'm just now bothering 
to learn python.

Sorry for being so dense:: piss-poor assumption on my part.

James

Re: [gentoo-user] openshot-2.0.6.ebuild

[Peter Humphrey]

On Friday 25 March 2016 14:40:57 Neil Bothwick wrote:
> On Fri, 25 Mar 2016 09:40:07 +0000, Peter Humphrey wrote:
> > > A user has 2 choices:
> > > 
> > > - set python2 as default and configure packages that can use python3
> > > to use it
> > > - set python3 as default and configure packages that requires python2
> > > to use it
> > > 
> > > Which method you use depends entirely on what packages you use.
> > 
> > But Gentoo has two python versions set: a python 2 and a python 3. I
> > assume that ebuilds specify which version they need, so the default is
> > rarely used.
> > 
> > In that case it won't matter which is set as default.
> 
> It's not the ebuilds, they are written n bash, it's the various scripts
> you tun. If they specify the interpreter as python2 or python3,
> everything is fine (you can eselect the default for each of these) but if
> it just calls python, the script had better be written for the version
> you have as default.
> 
> On the basis that all python3 scripts were written at a time when the
> difference was known, but the same does not apply to all python2 scripts,
> I prefer to leave the default at python2. That was everything should run,
> no matter how old it is.

Hmm. I'll have to give that some thought.

-- 
Rgds
Peter

linux counter 5290, 1994/04/23