Created attachment 439520 [details] Updated PyGame ebuild Updated ebuild for RnPy version 6.99.10 and also PyGame_SDL2 same version
Created attachment 439522 [details] RenPy 6.99.10 updated ebuild
Updated PyGame ebuild fails since S doesn't exist.
(In reply to Mr. Bones. from comment #2) > Updated PyGame ebuild fails since S doesn't exist. Oh, I'm terribly sorry - it's not even the right one. Replaced it.
Created attachment 439946 [details] Right EBUILD for pygame_sdl2
It's already 6.99.12 release of upstream. Is it so hard to just bump a version?
Created attachment 450238 [details, diff] multiabi patch for RenPy 6.99.12 (formatting changes from 6.99.10)
(In reply to Alex from comment #6) > Created attachment 450238 [details, diff] [details, diff] > multiabi patch for RenPy 6.99.12 (formatting changes from 6.99.10) Hi. The proxy maintainer of this ebuild is AWOL it seems. Would you be interested in taking over maintainership?
(In reply to Patrice Clement from comment #7) > Hi. The proxy maintainer of this ebuild is AWOL it seems. Would you be > interested in taking over maintainership? Well, I don't have much free time and required skills. I'm OK to write and propose my (sometimes ugly) ebuilds, but not ready to be a maintainer.
I don't understand which file is what here. I named your files like so in overlay: 1. "RenPy 6.99.10 updated ebuild" => "renpy-6.99.12.ebuild". 2. "Right EBUILD for pygame_sdl2" => "pygame_sdl2-6.99.12.ebuild" 3. "multiabi patch for RenPy 6.99.12 (formatting changes from 6.99.10)" => "renpy-6.99.12-multiple-abi.patch" And the patchs fails with renpy-6.99.12: checking file renpy.py Hunk #1 FAILED at 28. Hunk #2 succeeded at 156 (offset 2 lines). 1 out of 2 hunks FAILED checking file renpy/common.py checking file renpy/main.py Hunk #1 succeeded at 31 with fuzz 2 (offset 4 lines). Hunk #2 succeeded at 267 (offset -6 lines). Hunk #3 succeeded at 379 (offset 8 lines). patch program exited with status 1 What's wrong here?
(In reply to Pavel Volkov from comment #9) > What's wrong here? Sorry, but I can't reproduce your issue. Tried to rebuild RenPy and pygame_sdl2, no errors, went flawlessly. Please provide more information and complete build log.
(In reply to Alex from comment #10) > Sorry, but I can't reproduce your issue. Tried to rebuild RenPy and > pygame_sdl2, no errors, went flawlessly. Please provide more information and > complete build log. Exactly the same issue here, the patch does not apply against 6.99.12. Since the build does not even start, no build log can be included apart from: * Failed Patch: renpy-6.99.12-multiple-abi.patch ! * ( /usr/local/portage/local/games-engines/renpy/files/renpy-6.99.12-multiple-abi.patch ) * * Include in your bugreport the contents of: * * /var/tmp/portage/games-engines/renpy-6.99.12/temp/renpy-6.99.12-multiple-abi.patch.out The interesting part of "patch.out" was already shown. Maybe upstream did something ugly and modified their distfile? I have: $ md5sum /usr/portage/distfiles/renpy-6.99.12-source.tar.bz2 123826a194a6d2e23b948f5bfda5c46f And, just for reference, the patch which is also attached to this bug: $ md5sum /usr/local/portage/local/games-engines/renpy/files/renpy-6.99.12-multiple-abi.patch cc6fe39bb53946898165e8ddcde985f9
(In reply to Oliver Freyermuth from comment #11) > Maybe upstream did something ugly and modified their distfile? Nice catch, they are. I just wasn't expecting such dirty trick from them, they changed some source files. Sorry guys, patch now should be fixed. Tried to rebuild against "new" version of 6.99.12 with MD5 123826a194a6d2e23b948f5bfda5c46f, went smoothly.
Created attachment 462112 [details, diff] multiabi patch for RenPy 6.99.12 (rewritten from 6.99.12)
This is an important fix with the recent gst-plugins updates which all but force a ffmpeg upgrade - none of the old versions of renpy will build. I had to figure out how to create my own local repository to use these sample ebuilds, but they worked perfectly.
either this is finally fixed in the tree or this should be treecleaned
(In reply to Pacho Ramos from comment #15) > either this is finally fixed in the tree or this should be treecleaned No, it's not fixed, still unbuildable 6.99.6 in tree. And I can't understand why it's so hard to just bump package version. Well, better is to remove it than have broken version in tree I guess.
Fixed in commit 9a1bcce1539cf2b1107865cb5b77eb189ac3344c.
