Bug 379791 – dev-python/pypy-1.7 version bump

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Ilya Osadchiy 2011-08-18 21:21:14 UTC]

pypy-1.6 was released. It has different download location, and perhaps patches need to be adapted.

http://morepypy.blogspot.com/2011/08/pypy-16-kickass-panda.html

Reproducible: Didn't try

[Comment 1 Ilya Osadchiy 2011-08-18 22:04:47 UTC]

Created attachment 283829 [details]
pypy-1.6.ebuild

Fixed download location etc.
Compiles and works for me, but as lots of QA warnings => patch needs improvement

[Comment 2 Ilya Osadchiy 2011-08-19 11:22:53 UTC]

Created attachment 283889 [details]
pypy-1.6.patch

The patch that I used.

[Comment 3 Queria Sa-Tas 2011-08-20 20:22:49 UTC]

I'm on x86 and it fails with:

 * Cannot find $EPATCH_SOURCE!  Value for $EPATCH_SOURCE is:
 * 
 *   /usr/local/portage/dev-python/pypy/files/pypy-1.6-x86.patch
 *   ( pypy-1.6-x86.patch )

in src_prepare() there is:
 40     epatch "${FILESDIR}/${P}.patch"
 41     use x86 && epatch "${FILESDIR}/${P}-x86.patch"

Did i missed something?

[Comment 4 Ilya Osadchiy 2011-08-24 19:47:43 UTC]

(In reply to comment #3)
> I'm on x86 and it fails with:
> 
>  * Cannot find $EPATCH_SOURCE!  Value for $EPATCH_SOURCE is:
>  * 
>  *   /usr/local/portage/dev-python/pypy/files/pypy-1.6-x86.patch
>  *   ( pypy-1.6-x86.patch )
> 
> Did i missed something?

There is pypy-1.5-x86.patch in trunk, I think it should work (if you just rename it to 1.6), but I can't be sure cause I only have x64

[Comment 5 Johan Bergström 2011-11-21 16:05:33 UTC]

Should we perhaps look at 1.7 now?

[Comment 6 Dirkjan Ochtman (RETIRED) 2011-11-21 16:22:55 UTC]

Definitely.

[Comment 7 Ilya Osadchiy 2011-11-26 20:07:43 UTC]

Created attachment 293883 [details]
pypy-1.7.ebuild

This ebuild worked for me as pypy-1.7. (On amd64).
It's same as previously posted pypy-1.6, with fix of bug 383063.

[Comment 8 Ilya Osadchiy 2011-11-26 20:09:06 UTC]

Created attachment 293885 [details, diff]
pypy-1.7-no-pdb.patch

Patch to use with pypy-1.7.ebuild

[Comment 9 Dirkjan Ochtman (RETIRED) 2011-11-30 08:50:20 UTC]

I've put 1.7 in the tree. Please test!

[Comment 10 Dirkjan Ochtman (RETIRED) 2011-11-30 08:53:22 UTC]

BTW, I don't think I have the x86 patch, maybe someone can test that?

[Comment 11 piotr.staroszczyk 2011-11-30 11:37:55 UTC]

(In reply to comment #9)
> I've put 1.7 in the tree. Please test!

>>> Compiling source in /var/tmp/portage/dev-python/pypy-1.7/work/pypy-pypy-release-1.7 ...
python2.7 ./pypy-pypy-release-1.7/pypy/translator/goal/translate.py -Ojit ./pypy-pypy-release-1.7/pypy/translator/goal/targetpypystandalone.py --withmod-bz2 --withmod-_minimal_curses --withoutmod-pyexpat --withmod-_ssl
python2.7: can't open file './pypy-pypy-release-1.7/pypy/translator/goal/translate.py': [Errno 2] No such file or directory
 * ERROR: dev-python/pypy-1.7 failed (compile phase):
 *   compile error
 *
 * Call stack:
 *     ebuild.sh, line  56:  Called src_compile
 *   environment, line 5219:  Called die
 * The specific snippet of code:
 *       ${translate_cmd} || die "compile error"

[Comment 12 Dirkjan Ochtman (RETIRED) 2011-11-30 11:43:19 UTC]

Ah yeah, sorry about that. Should be better now.

[Comment 13 piotr.staroszczyk 2011-11-30 16:00:11 UTC]

Created attachment 294347 [details]
error in compiling

[Comment 14 piotr.staroszczyk 2011-11-30 16:01:10 UTC]

It`s probably bug in pypy but i`ve uploaded build log.

[Comment 15 Dirkjan Ochtman (RETIRED) 2011-11-30 16:17:54 UTC]

Yeah, you should probably report that upstream.