[Python-modules-team] Bug#892436: pygame: Please use 'pkg-config' to find FreeType 2

[René Dudfield]

This was fixed, and will be in the next pygame release. Thanks again.
https://github.com/pygame/pygame/pull/442


On Tue, Apr 3, 2018 at 2:36 PM, René Dudfield <ren...@gmail.com> wrote:

> Thank you very much. That's very helpful.
>
> cheers,
>
> On Tue, Apr 3, 2018 at 2:08 PM, Hugh McMaster <hugh.mcmas...@outlook.com>
> wrote:
>
>> Hi René,
>>
>> Thanks for looking on this bug.
>>
>> On Tue, 3 Apr 2018 11:19:20 +0200, René Dudfield wrote:
>> > I wonder if you know how portable pkg-config is for this?
>> >
>> > Will using pkg-config work for getting config on older versions of
>> Debian?
>> >
>> > Or will we have to try and use both of the scripts? freetype-config for
>> > older, and pkg-config for newer?
>>
>> pkg-config has been part of Debian-based distros for many years.
>> The current release 0.29-4 is also part of Stretch, with Jessie using
>> 0.28-1.
>>
>> Also, freetype-config has been deprecated for many years, with pkg-config
>> being the preferred method of obtaining CFLAGS and libs for several years
>> now.
>>
>> In fact, freetype-config has been a wrapper for pkg-config since February
>> 2017.
>>
>> FreeType has also had pkg-config support since version 2.1.5 was released
>> in 2003, so
>> pkg-config support is comfortably available everywhere.
>>
>> In addition, freetype-config(1) has recommended developers use pkg-config
>> since March 2014.
>>
>> Hope that helps.
>>
>> Hugh
>
>
>
___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#892436: pygame: Please use 'pkg-config' to find FreeType 2

[René Dudfield]

Thank you very much. That's very helpful.

cheers,

On Tue, Apr 3, 2018 at 2:08 PM, Hugh McMaster <hugh.mcmas...@outlook.com>
wrote:

> Hi René,
>
> Thanks for looking on this bug.
>
> On Tue, 3 Apr 2018 11:19:20 +0200, René Dudfield wrote:
> > I wonder if you know how portable pkg-config is for this?
> >
> > Will using pkg-config work for getting config on older versions of
> Debian?
> >
> > Or will we have to try and use both of the scripts? freetype-config for
> > older, and pkg-config for newer?
>
> pkg-config has been part of Debian-based distros for many years.
> The current release 0.29-4 is also part of Stretch, with Jessie using
> 0.28-1.
>
> Also, freetype-config has been deprecated for many years, with pkg-config
> being the preferred method of obtaining CFLAGS and libs for several years
> now.
>
> In fact, freetype-config has been a wrapper for pkg-config since February
> 2017.
>
> FreeType has also had pkg-config support since version 2.1.5 was released
> in 2003, so
> pkg-config support is comfortably available everywhere.
>
> In addition, freetype-config(1) has recommended developers use pkg-config
> since March 2014.
>
> Hope that helps.
>
> Hugh
___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#892436: pygame: Please use 'pkg-config' to find FreeType 2

[René Dudfield]

Hello,

I wonder if you know how portable pkg-config is for this?

Will using pkg-config work for getting config on older versions of Debian?

Or will we have to try and use both of the scripts? freetype-config for
older, and pkg-config for newer?


best regards,



On Thu, 08 Mar 2018 22:52:30 +1100 hugh.mcmas...@outlook.com wrote:
> Source: pygame
> Severity: important
>
> Dear Maintainer,
>
> The next release of libfreetype6-dev will *not* ship
> `freetype-config', as the script has now been deprecated in favour of
> `pkg-config'.
>
> This is an upstream change:
>
> "Use of the `freetype-config' script to get compilation and
>
> linking options is deprecated since it doesn't support
>
> cross-compiling, among other deficiencies. Instead, you should
>
> use the `pkg-config' interface." [1]
>
> Please use `pkg-config' to detect the FreeType 2 headers and
> libraries in pygame.
>
> If this bug is not resolved prior to the release of FreeType 2.9.1,
> your package may FTBFS.
>
> Thank you
>
> [1]
> http://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/?id=b0
> a93839b52818abbfe9b4c8755b4aa0f5232063
>
>
___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#861252: pygame: FTBFS on ppc64el: some color-handling tests fail

[René Dudfield]

Hello,

I spent quite some hours debugging this on a ppc64le virtual machine.

tldr; it's a rare case in SDL1 on ppc64le, and I've skipped those tests on
this architecture for SDL1. Additionally there is a work around for users
of this architecture (don't do self blits, make a copy first).
https://github.com/pygame/pygame/pull/391/commits/9601fd1a2d1d359b811943d5d123096fabfad1a0

best,


https://github.com/pygame/pygame/issues/370#issuecomment-364625291

It looks like these fail inside SDL_BlitSurface.

Inside surface.c, this part... (line 3084 currently)

src = SDL_ConvertSurface (src, , SDL_SWSURFACE);
if (src) {
result = SDL_BlitSurface (src, srcrect, dst, dstrect);
SDL_FreeSurface (src);
}
If in the test, I add something like this around test/surface_test.py:2314

comp.blit(tmp.copy(), (0, 0))
It avoids the self blit error... but is still slightly wrong color value
(off by one in r). And of course, avoiding the self-blit is avoiding the
whole point of the test.

It's sort of a quite rare case, of needing to do a self blit using a
palette. That combined with the very low chance of updates for SDL1 on
ppc64le(upstream moved on years ago), I've skiped these tests on ppc64le
inside pygame on SDL1.



On Wed, 26 Apr 2017 10:49:21 -0400 "Aaron M. Ucko"  wrote:
> Source: pygame
> Version: 1.9.1release+dfsg-10+b2
> Severity: serious
> Justification: fails to build from source (but built successfully in the
past)
>
> The ppc64el build of pygame failed:
>
>   ==
>   FAIL: test_save_colorkey (pygame.tests.image_test.ImageModuleTest)
>   make sure the color key is not changed when saving.
>   --
>   Traceback (most recent call last):
> File
"/<>/pygame-1.9.3+dfsg/.pybuild/pythonX.Y_2.7/build/pygame/tests/image_test.py",
line 283, in test_save_colorkey
>   self.assertEqual(p1, s2.get_at((0,0)))
>   AssertionError: (23, 23, 23, 255) != (23, 23, 255, 23)
>
>   ==
>   FAIL: test_cross (pygame.tests.math_test.Vector2TypeTest)
>   [as per #861249]
>
>   ==
>   FAIL: test_blanket_alpha (pygame.tests.surface_test.SurfaceSelfBlitTest)
>   --
>   Traceback (most recent call last):
> File
"/<>/pygame-1.9.3+dfsg/.pybuild/pythonX.Y_2.7/build/pygame/tests/surface_test.py",
line 2331, in test_blanket_alpha
>   self._assert_same(surf, comp)
> File
"/<>/pygame-1.9.3+dfsg/.pybuild/pythonX.Y_2.7/build/pygame/tests/surface_test.py",
line 2252, in _assert_same
>   a.get_bitsize(
>   AssertionError: (255, 0, 0, 255) != (0, 255, 170, 255), bpp: 8
>
>   ==
>   FAIL: test_colorkey (pygame.tests.surface_test.SurfaceSelfBlitTest)
>   --
>   Traceback (most recent call last):
> File
"/<>/pygame-1.9.3+dfsg/.pybuild/pythonX.Y_2.7/build/pygame/tests/surface_test.py",
line 2311, in test_colorkey
>   self._assert_same(surf, comp)
> File
"/<>/pygame-1.9.3+dfsg/.pybuild/pythonX.Y_2.7/build/pygame/tests/surface_test.py",
line 2252, in _assert_same
>   a.get_bitsize(
>   AssertionError: (255, 0, 0, 255) != (0, 255, 0, 255), bpp: 8
>
> Could you please take a look?
>
> Thanks!
>
> -- System Information:
> Debian Release: 9.0
>   APT prefers testing
>   APT policy: (500, 'testing'), (500, 'stable'), (300, 'unstable')
> Architecture: amd64
>  (x86_64)
> Foreign Architectures: i386, x32
>
> Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
>
___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#861253: pygame: FTBFS (64-bit BE): BufferProxyLegacyTest.test_write fails

[René Dudfield]

Hello,

This has been fixed in the 1.9.3+ series.

I can't reproduce it on ppc64 with current git master of pygame.
cheers,


On Wed, 26 Apr 2017 10:53:09 -0400 "Aaron M. Ucko"  wrote:
> Source: pygame
> Version: 1.9.1release+dfsg-10+b2
> Severity: serious
> Justification: fails to build from source (but built successfully in the
past)
>
> Builds of pygame for 64-bit big-endian architectures (s390x and the
> non-release architectures ppc64 and sparc64) failed:
>
>   ERROR: test_write (pygame.tests.bufferproxy_test.BufferProxyLegacyTest)
>   --
>   Traceback (most recent call last):
> File
"/<>/pygame-1.9.3+dfsg/.pybuild/pythonX.Y_2.7/build/pygame/tests/bufferproxy_test.py",
line 469, in test_write
>   bp.write(data[:3], 2)
>   IndexError: 'offset' is out of range
>
> All of these architectures encountered additional test-suite errors,
> which I've already reported separately (#861249, #861250).
>
> Could you please take a look?
>
> Thanks!
>
> --
> Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
> http://www.mit.edu/~amu/ |
http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
>
>
___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#861249: FTBFS: math_test.Vector2TypeTest.test_cross fails

[René Dudfield]

Hello,

this has been fixed in pygame upstream here:
https://github.com/pygame/pygame/pull/391/commits/630b40ecd7be4ac5583d9ace0ad125190c6abf33

It will be part of the pygame 1.9.4 upstream release.

best regards,



On Sun, 21 May 2017 21:50:58 +0100 Edmund Grimley Evans <
edmund.grimley.ev...@gmail.com> wrote:
> On arm64 and at least one other architecture, the error says:
>
> -3.2862601528904633e-16 != 0
>
> It looks as though the test is computing (1.2 * 3.4 - 3.4 * 1.2).
>
> Now, the log to base 2 of (1.2 * 3.4) divided by 3.286e-16 is about
> 53.5. There are 52 bits in the mantissa of a 64-bit float, or 53
> including the implicit "1". So I would guess that the error comes from
> multiply and subtract being combined into a single operation, so that
> the error in computing 1.2 * 3.4 is revealed.
>
> If this is a real problem, perhaps "cross" could be implemented in a
> way that prevents multiply-subtract from being used. If it is not a
> real problem, then the test should be made less sensitive, perhaps by
> requiring the absolute value of the result to be less than 1e-12 or
> some other arbitrary epsilon.
>
>
___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#861250: pygame: FTBFS (big-endian): test_get_bounding_rect fails

[René Dudfield]

Hello,

this has been fixed in pygame upstream here:
https://github.com/pygame/pygame/pull/391/commits/a6ff02663e3564f7ebe3191d4e90bf0a20482386

It will be part of the pygame 1.9.4 upstream release.

best regards,


On Wed, 26 Apr 2017 10:43:40 -0400 "Aaron M. Ucko"  wrote:
> Source: pygame
> Version: 1.9.1release+dfsg-10+b2
> Severity: serious
> Justification: fails to build from source (but built successfully in the
past)
>
> Builds of pygame for big-endian architectures (mips, s390x, and the
> non-release architectures hppa, powerpc, ppc64, and sparc64) all failed:
>
>   FAIL: test_get_bounding_rect (pygame.tests.surface_test.SurfaceTypeTest)
>   --
>   Traceback (most recent call last):
> File
"/«BUILDDIR»/pygame-1.9.3+dfsg/.pybuild/pythonX.Y_2.7/build/pygame/tests/surface_test.py",
line 154, in test_get_bounding_rect
>   self.assertEqual(bound_rect.width, 0)
>   AssertionError: 1 != 0
>
> On most of these architectures (all but mips and hppa), there were
> additional test suite failures, which I'm reporting separately.  I
> presume the non-release architectures m68k and powerpcspe would have
> encountered the same error if those builds hadn't silently skipped the
> test suite altogether for some reason.
>
> Could you please take a look?
>
> Thanks!
>
> --
> Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
> http://www.mit.edu/~amu/ |
http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#861256: pygame: FTBFS on sh4: surface_test.AllTestCases times out

[René Dudfield]

Hello,

According to here: https://buildd.debian.org/status/package.php?p=pygame

It looks like this one has been built successfully now with the
1.9.3+dfsg-2 package on sh4.

best regards,


On Wed, 26 Apr 2017 10:59:25 -0400 "Aaron M. Ucko"  wrote:
> Source: pygame
> Version: 1.9.1release+dfsg-10+b2
> Severity: important
> Justification: fails to build from source (but built successfully in the
past)
>
> The sh4 build of pygame failed, per the log excerpt below, from
>
https://buildd.debian.org/status/fetch.php?pkg=pygame=sh4=1.9.3%2Bdfsg-2=1493197569=0
>
> Could you please take a look?
>
> Thanks!
>
> ERROR: all_tests_for (pygame.tests.surface_test.AllTestCases)
> --
> Traceback (most recent call last):
>   File "test/pygame.tests.surface_test.py", line 1, in all_tests_for
> subprocess completely failed with return code of "Process timed out
(time_out = 120 secs) and was successfully terminated"
> cmd:  ['/usr/bin/python3.5', '-m',
'pygame.tests.test_utils.test_runner', 'pygame.tests.surface_test',
'--exclude', 'opengl,interactive,subprocess_ignore,python3_ignore']
> test_env: [...]
> working_dir:  /tmp/tmpqaf65cf7
> return (first 10 and last 10 lines):
> WARNING: You are using the SDL disk writer audio driver!
>  Writing to file [sdlaudio.raw].
> WARNING: You are using the SDL disk writer audio driver!
>  Writing to file [sdlaudio.raw].
> WARNING: You are using the SDL disk writer audio driver!
>  Writing to file [sdlaudio.raw].
> WARNING: You are using the SDL disk writer audio driver!
>  Writing to file [sdlaudio.raw].
> WARNING: You are using the SDL disk writer audio driver!
>  Writing to file [sdlaudio.raw].
> ...
> WARNING: You are using the SDL disk writer audio driver!
>  Writing to file [sdlaudio.raw].
> WARNING: You are using the SDL disk writer audio driver!
>  Writing to file [sdlaudio.raw].
> WARNING: You are using the SDL disk writer audio driver!
>  Writing to file [sdlaudio.raw].
> /usr/lib/python3.5/runpy.py:125: RuntimeWarning:
'pygame.tests.test_utils.test_runner' found in sys.modules after import of
package 'pygame.tests.test_utils', but prior to execution of
'pygame.tests.test_utils.test_runner'; this may result in unpredictable
behaviour
>   warn(RuntimeWarning(msg))
> loading pygame.tests.surface_test
> <--!! TES
>
> --
> Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
> http://www.mit.edu/~amu/ |
http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
>
>
___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team