Bug#871223: [871223] neverball: Strange squares instead of stars in the goals point

2019-05-17 Thread Qwerty Chouskie
Turns out the Debian package isn't packaging all the assets: 
https://github.com/Neverball/neverball/issues/170#issuecomment-493550779

Can someone look into why these PNGs aren't getting into the package?

-QwertyChouskie

On 4/5/19 8:22 AM, Markus Koschany wrote:
> On Wed, 20 Mar 2019 17:50:39 + Qwerty Chouskie
>  wrote:
>> After much research at
>> https://github.com/Neverball/neverball/issues/170, it seems this issue
>> only affects the Debian package for some reason, likely a weird compiler
>> bug or such.  Anyways, the solution seems to be a rebuild of the
>> package.  No changes are needed, just re-compiling seems to fix the
>> issue.  If a maintainer can do this, the bug can be closed.
> Just for the record: A rebuild doesn't change anything. I don't believe
> that is a compiler bug. More likely it is related to libgl1-mesa-glx
> [libgl1].
>
>
>


Bug#871223: [871223] neverball: Strange squares instead of stars in the goals point

2019-04-05 Thread Markus Koschany
On Wed, 20 Mar 2019 17:50:39 + Qwerty Chouskie
 wrote:
> After much research at 
> https://github.com/Neverball/neverball/issues/170, it seems this issue 
> only affects the Debian package for some reason, likely a weird compiler 
> bug or such.  Anyways, the solution seems to be a rebuild of the 
> package.  No changes are needed, just re-compiling seems to fix the 
> issue.  If a maintainer can do this, the bug can be closed.

Just for the record: A rebuild doesn't change anything. I don't believe
that is a compiler bug. More likely it is related to libgl1-mesa-glx
[libgl1].





signature.asc
Description: OpenPGP digital signature


Bug#871223: [871223] neverball: Strange squares instead of stars in the goals point

2019-03-20 Thread Qwerty Chouskie
After much research at 
https://github.com/Neverball/neverball/issues/170, it seems this issue 
only affects the Debian package for some reason, likely a weird compiler 
bug or such.  Anyways, the solution seems to be a rebuild of the 
package.  No changes are needed, just re-compiling seems to fix the 
issue.  If a maintainer can do this, the bug can be closed.