On 28/02/13 22:27, Thomas Kahle wrote:
> On 22:11 Thu 28 Feb 2013, Francois Bissey wrote:
>> This must be new patches. I "forked" the sage-on-gentoo" from the main
>> tree 7 days ago. At that time the difference was patches I added based
>> on the spkg shipped in sage (one backport from an unreleased version,
>> the other won't be merged because what it fixes is being revamped).
>
> Oh, my bad. The patches are in your version:
>
> # diff ~up/dev-python/ipython/ipython-0.13.1-r1.ebuild
> /var/lib/layman/sage-on-gentoo/dev-python/ipython/ipython-0.13.1-r1.ebuild
> 3c3
> < # $Header:
> /var/cvsroot/gentoo-x86/dev-python/ipython/ipython-0.13.1-r1.ebuild,v 1.1
> 2013/02/11 15:59:01 mgorny Exp $
> ---
>> # $Header: $
> 52a53,54
>> epatch "${FILESDIR}"/${PN}-history-backport.patch
>> epatch "${FILESDIR}"/prun_timeit_magics.patch
>
>
> OK. What I'm trying to say is: Your mask is irrelevant since the
> main-tree version is not masked and emerge want's to install it anyway,
> I think? If you intended to not unmask any python-1 ebuilds, then it
> failed.
>
Not all but you are right. The mask only applies to the content of the
overlay. That's by design. I don't like it but we either have to provide
keywording for the python-r1 dep or enforce ipython-0.13.1 exactly
which is about as bad.
Opinions Christopher?
Francois
