Re: pygame: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" --system=custom --test-args "/usr/bin/xvfb-run {interpreter} -m pygame.tests.__main__ --exclude opengl" returned
On Wed, 23 Mar 2022, Hugh McMaster wrote: On Wed, 23 Mar 2022 at 02:37, Andreas Tille wrote: Hi, Am Wed, Mar 23, 2022 at 12:19:40AM +1100 schrieb Hugh McMaster: > On Mon, 28 Feb 2022 at 16:40, Hugh McMaster wrote: > > > I did some testing and found that pygame 2.1.0 is the first recent > > version not affected by the FreeType test issue. > > > > I'll keep digging, but I'd strongly suggest migrating to the most > > recent upstream version as soon as possible, as I had no problems > > building it. > > > Any progress on packaging the latest version of pygame? > > The current package will be removed from testing next week. If you ask me lets push pygame 2.1.0 and remove anything that does not work with this version from testing (it would be removed from there anyway). I know its not good style but stagnation in the status quo is also no good solution. Agreed. pygame 1.9.6 is now almost 3 years old. Since there were no objections, and pygame is already slated to be kicked out of testing, plus given that pygame 2 is advertised as largely backward compatible, I went and did a cursory check on most of pygame's rdeps and found they seemed to work fine with pygame 2. I just went ahead and uploaded the new pygame. Let me know if anyone notices any problems. Scott
Re: pygame: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" --system=custom --test-args "/usr/bin/xvfb-run {interpreter} -m pygame.tests.__main__ --exclude opengl" returned
On Wed, 23 Mar 2022 at 02:37, Andreas Tille wrote: > Hi, > > Am Wed, Mar 23, 2022 at 12:19:40AM +1100 schrieb Hugh McMaster: > > On Mon, 28 Feb 2022 at 16:40, Hugh McMaster wrote: > > > > > I did some testing and found that pygame 2.1.0 is the first recent > > > version not affected by the FreeType test issue. > > > > > > I'll keep digging, but I'd strongly suggest migrating to the most > > > recent upstream version as soon as possible, as I had no problems > > > building it. > > > > > > Any progress on packaging the latest version of pygame? > > > > The current package will be removed from testing next week. > > If you ask me lets push pygame 2.1.0 and remove anything that does not > work with this version from testing (it would be removed from there > anyway). I know its not good style but stagnation in the status quo > is also no good solution. Agreed. pygame 1.9.6 is now almost 3 years old. >
Re: pygame: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" --system=custom --test-args "/usr/bin/xvfb-run {interpreter} -m pygame.tests.__main__ --exclude opengl" returned
Hi, Am Wed, Mar 23, 2022 at 12:19:40AM +1100 schrieb Hugh McMaster: > On Mon, 28 Feb 2022 at 16:40, Hugh McMaster wrote: > > > I did some testing and found that pygame 2.1.0 is the first recent > > version not affected by the FreeType test issue. > > > > I'll keep digging, but I'd strongly suggest migrating to the most > > recent upstream version as soon as possible, as I had no problems > > building it. > > > Any progress on packaging the latest version of pygame? > > The current package will be removed from testing next week. If you ask me lets push pygame 2.1.0 and remove anything that does not work with this version from testing (it would be removed from there anyway). I know its not good style but stagnation in the status quo is also no good solution. Kind regards Andreas. -- http://fam-tille.de
Re: pygame: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" --system=custom --test-args "/usr/bin/xvfb-run {interpreter} -m pygame.tests.__main__ --exclude opengl" returned
On Mon, 28 Feb 2022 at 16:40, Hugh McMaster wrote: > I did some testing and found that pygame 2.1.0 is the first recent > version not affected by the FreeType test issue. > > I'll keep digging, but I'd strongly suggest migrating to the most > recent upstream version as soon as possible, as I had no problems > building it. Any progress on packaging the latest version of pygame? The current package will be removed from testing next week. >
Re: pygame: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" --system=custom --test-args "/usr/bin/xvfb-run {interpreter} -m pygame.tests.__main__ --exclude opengl" returned
Hi Marcin,
On Sat, 26 Feb 2022 at 20:47, Marcin Owsiany wrote:
>
> Dnia Tue, Feb 22, 2022 at 08:57:25AM +0100, Andreas Tille napisał(a):
> > I had a look into this issue since a Debian Med package received a
> > testing removal warning. I can confirm the build fails with
> >
> >Segmentation fault
> >
> > in the build time test suite.
>
> Just out of curiosity I ran the tests during build under GDB (simply
> inserting "gdb --args" right before the "{interpreter}" in the
> overrite_dh_auto_test rule in debian/rules).
>
> It seems like the segfault is in the freetype library, when loading a font,
> rather than in pygame (though I guess the root cause could be pygame passing
> garbage to freetype? - I have zero knowledge about the API).
>
> Cc-ing Hugh in case he can provide some hints about what might be going on
> here.
>
> This does not change the fact that it would be great to move to pygame2 :-)
This test failure occurs in the ftfont test, which is an alternative
for the older SDL font API.
The cause does seem to be a change in FreeType 2.11.1, as the tests
pass with FreeType 2.11.0. Unfortunately, I can't see any relevant
changes easily. I suspect pygame might be dereferencing a NULL pointer
somewhere.
I did some testing and found that pygame 2.1.0 is the first recent
version not affected by the FreeType test issue.
I'll keep digging, but I'd strongly suggest migrating to the most
recent upstream version as soon as possible, as I had no problems
building it.
Hugh
Re: pygame: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" --system=custom --test-args "/usr/bin/xvfb-run {interpreter} -m pygame.tests.__main__ --exclude opengl" returned
Dnia Tue, Feb 22, 2022 at 08:57:25AM +0100, Andreas Tille napisał(a):
> I had a look into this issue since a Debian Med package received a
> testing removal warning. I can confirm the build fails with
>
>Segmentation fault
>
> in the build time test suite.
Just out of curiosity I ran the tests during build under GDB (simply
inserting "gdb --args" right before the "{interpreter}" in the
overrite_dh_auto_test rule in debian/rules).
It seems like the segfault is in the freetype library, when loading a font,
rather than in pygame (though I guess the root cause could be pygame passing
garbage to freetype? - I have zero knowledge about the API).
Cc-ing Hugh in case he can provide some hints about what might be going on here.
This does not change the fact that it would be great to move to pygame2 :-)
loading pygame.tests.freetype_test
loading pygame.tests.ftfont_test
Thread 1 "python3.10" received signal SIGSEGV, Segmentation fault.
0x7fde9aeb34e3 in FT_Done_Face (face=0x7fde96aa04d8) at
./src/base/ftobjs.c:2836
2836./src/base/ftobjs.c: No such file or directory.
(gdb) bt full
#0 0x7fde9aeb34e3 in FT_Done_Face (face=0x7fde96aa04d8) at
./src/base/ftobjs.c:2836
error = 35
driver =
memory =
node =
#1 0x7fde9af11479 in ftc_face_node_done (ftcnode=0x1fce450,
ftcmanager=) at ./src/cache/ftcmanag.c:272
node = 0x1fce450
manager =
#2 0x7fde9af11872 in FTC_MruList_New (list=0x1ec9928, key=0x7fde970bb200,
anode=anode@entry=0x7ffce3eb1bc0) at ./src/cache/ftcmru.c:281
error = 1
node = 0x1fce450
memory = 0x1e70c40
#3 0x7fde9af12bbf in FTC_Manager_LookupFace (manager=,
face_id=face_id@entry=0x7fde970bb200, aface=aface@entry=0x7ffce3eb1be0) at
./src/cache/ftcmanag.c:324
_pfirst =
_compare = 0x7fde9af102d0
_first =
_node =
error = 0
mrunode = 0x7fde9ca14638
#4 0x7fde982a5228 in _PGFT_GetFont (ft=ft@entry=0x20bc470,
fontobj=fontobj@entry=0x7fde970bb1f0) at src_c/freetype/ft_wrap.c:321
error =
font = 0x0
#5 0x7fde982a550c in init (ft=ft@entry=0x20bc470,
fontobj=fontobj@entry=0x7fde970bb1f0) at src_c/freetype/ft_wrap.c:386
font =
#6 0x7fde982a58be in _PGFT_TryLoadFont_Filename (ft=ft@entry=0x20bc470,
fontobj=fontobj@entry=0x7fde970bb1f0, filename=,
font_index=) at src_c/freetype/ft_wrap.c:442
filename_alloc =
file_len =
#7 0x7fde9829d3d0 in _ftfont_init (self=0x7fde970bb1f0, args=, kwds=) at src_c/_freetype.c:823
kwlist = {0x7fde982a7bb3 "file", 0x7fde982a7cca "size", 0x7fde982a75cc
"font_index", 0x7fde982a777c "resolution", 0x7fde982a75d7 "ucs4", 0x0}
file = 0x7fde96f44d30
original_file = 0x7fde96f2a240
font_index = 0
face_size = {x = 1280, y = 0}
ucs4 = 0
resolution = 0
size = 0
height = 0
width = 0
x_ppem = 0
y_ppem = 0
rval = -1
source =
ft = 0x20bc470
#8 0x00599823 in ()
#9 0x00531efb in _PyObject_MakeTpCall ()
#10 0x0052c946 in _PyEval_EvalFrameDefault ()
#11 0x0053105a in _PyObject_FastCallDictTstate ()
#12 0x005446ab in ()
#13 0x00532228 in ()
#14 0x00549149 in PyObject_Call ()
#15 0x00528a93 in _PyEval_EvalFrameDefault ()
#16 0x0053b7ff in _PyFunction_Vectorcall ()
#17 0x00526ca7 in _PyEval_EvalFrameDefault ()
#18 0x0053b7ff in _PyFunction_Vectorcall ()
--Type for more, q to quit, c to continue without paging--c
#19 0x00526ca7 in _PyEval_EvalFrameDefault ()
#20 0x0054884c in ()
#21 0x00526aba in _PyEval_EvalFrameDefault ()
#22 0x0053b7ff in _PyFunction_Vectorcall ()
#23 0x00526ca7 in _PyEval_EvalFrameDefault ()
#24 0x0053b7ff in _PyFunction_Vectorcall ()
#25 0x0054893a in ()
#26 0x00528a93 in _PyEval_EvalFrameDefault ()
#27 0x0053105a in _PyObject_FastCallDictTstate ()
#28 0x005459b9 in _PyObject_Call_Prepend ()
#29 0x005c2c33 in ()
#30 0x00531efb in _PyObject_MakeTpCall ()
#31 0x0052b9ee in _PyEval_EvalFrameDefault ()
#32 0x0053b7ff in _PyFunction_Vectorcall ()
#33 0x0054893a in ()
#34 0x00528a93 in _PyEval_EvalFrameDefault ()
#35 0x0053105a in _PyObject_FastCallDictTstate ()
#36 0x005459b9 in _PyObject_Call_Prepend ()
#37 0x005c2c33 in ()
#38 0x00531efb in _PyObject_MakeTpCall ()
#39 0x0052b9ee in _PyEval_EvalFrameDefault ()
#40 0x0053b7ff in _PyFunction_Vectorcall ()
#41 0x0054893a in ()
#42 0x00528a93 in _PyEval_EvalFrameDefault ()
#43 0x0053105a in _PyObject_FastCallDictTstate ()
#44 0x005459b9 in _PyObject_Call_Prepend ()
#45 0x005c2c33 in ()
#46 0x00531efb in _PyObject_MakeTpCall ()
#47 0x0052b9ee in _PyEval_EvalFrameDefault ()
#48
Re: pygame: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" --system=custom --test-args "/usr/bin/xvfb-run {interpreter} -m pygame.tests.__main__ --exclude opengl" returned
Hi Stefano, Am Wed, Feb 23, 2022 at 01:56:11AM + schrieb Stefano Rivera: > Hi Andreas (2022.02.22_07:57:25_+) > > I've put all developers mentioned as Uploader in CC. Given that the > > last non-team upload was two years ago which might have lead to the > > situation that following upstream changes is stalled it would be great > > if you confirm that you intend to continue working on this package. > > I think it's high time to get pygame 2 into Debian. There's probably > some transition required, and maybe some rev-deps will need to be > removed, but pygame 1.9 isn't supportable forever. Missing myself the slightest insight into pygame I'd say we should start rather sooner than later. > I've done some of the recent uploads, kicking the can down the road, but > they're getting harder and harder. Definitely. And thanks for keeping it alife so far. Kind regards Andreas. -- http://fam-tille.de
Re: pygame: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" --system=custom --test-args "/usr/bin/xvfb-run {interpreter} -m pygame.tests.__main__ --exclude opengl" returned
Hi Andreas (2022.02.22_07:57:25_+) > I've put all developers mentioned as Uploader in CC. Given that the > last non-team upload was two years ago which might have lead to the > situation that following upstream changes is stalled it would be great > if you confirm that you intend to continue working on this package. I think it's high time to get pygame 2 into Debian. There's probably some transition required, and maybe some rev-deps will need to be removed, but pygame 1.9 isn't supportable forever. I've done some of the recent uploads, kicking the can down the road, but they're getting harder and harder. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Re: pygame: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" --system=custom --test-args "/usr/bin/xvfb-run {interpreter} -m pygame.tests.__main__ --exclude opengl" returned
Control: tags -1 confirmed Hi, I had a look into this issue since a Debian Med package received a testing removal warning. I can confirm the build fails with Segmentation fault in the build time test suite. I realised that this package is lagging quite a bit behind upstream and my personal approach would be to do an upgrade to latest upstream. However, the package has a number of dependencies which I have no idea about and thus I'm hesitating to go on with this idea which takes probably some time to review all the patches. So for the moment I've just commited the changes of lintian-brush (= made myself Debian Janitor ;-) ) I've put all developers mentioned as Uploader in CC. Given that the last non-team upload was two years ago which might have lead to the situation that following upstream changes is stalled it would be great if you confirm that you intend to continue working on this package. Kind regards Andreas. -- http://fam-tille.de
