On 09/03/18 16:13, Marc Espie wrote:
> On Mon, Sep 03, 2018 at 03:54:26PM +0200, Solene Rapenne wrote:
>> works on intel GPU
>>
>> I felt some audio delay of ~300ms in the game and in the menu, it's rather
>> annoying especially in this kind of game.
>
> Last time I got fretsonfire to work, it
On Mon, Sep 03, 2018 at 03:54:26PM +0200, Solene Rapenne wrote:
> works on intel GPU
>
> I felt some audio delay of ~300ms in the game and in the menu, it's rather
> annoying especially in this kind of game.
Last time I got fretsonfire to work, it was crap anyway. Most features
vital to Guitar
Brian Callahan wrote:
>
> On 08/31/18 04:38, Martijn van Duren wrote:
> > So here's an updated diff that's been tried and tested.
> > I placed a comment in both the Makefile and the DESCR so that both users
> > and future ports maintainers see that it might not work on every system.
> >
> > OK?
On 08/31/18 04:38, Martijn van Duren wrote:
So here's an updated diff that's been tried and tested.
I placed a comment in both the Makefile and the DESCR so that both users
and future ports maintainers see that it might not work on every system.
OK?
I can't directly test this myself as you
So here's an updated diff that's been tried and tested.
I placed a comment in both the Makefile and the DESCR so that both users
and future ports maintainers see that it might not work on every system.
OK?
martijn@
Index: Makefile
On Wed, 29 Aug 2018 01:01:38 +0200, Martijn van Duren
wrote:
> I agree that we should mention that radeon cards are known to cause
> issues, but I don't know the best place for them. Diff below places
> them in the Makefile, but maybe we want them somewhere where users
> can find them more
On 8/28/2018 7:01 PM, Martijn van Duren wrote:
> On 08/28/18 23:17, Brian Callahan wrote:
>> On 08/28/18 17:08, Martijn van Duren wrote:
>>> On 08/28/18 22:08, Daniel Dickman wrote:
> On Aug 28, 2018, at 3:19 PM, Klemens Nanni wrote:
>
>> On Tue, Aug 28, 2018 at 03:15:14PM -0400,
On 08/28/18 23:17, Brian Callahan wrote:
>
> On 08/28/18 17:08, Martijn van Duren wrote:
>> On 08/28/18 22:08, Daniel Dickman wrote:
>>>
On Aug 28, 2018, at 3:19 PM, Klemens Nanni wrote:
> On Tue, Aug 28, 2018 at 03:15:14PM -0400, Brian Callahan wrote:
> I removed the BROKEN
On 08/28/18 22:08, Daniel Dickman wrote:
>
>
>> On Aug 28, 2018, at 3:19 PM, Klemens Nanni wrote:
>>
>>> On Tue, Aug 28, 2018 at 03:15:14PM -0400, Brian Callahan wrote:
>>> I removed the BROKEN marker to see what would happen, and it turns out the
>>> code uses functions that from Py-Pillow
On 08/28/18 17:08, Martijn van Duren wrote:
On 08/28/18 22:08, Daniel Dickman wrote:
On Aug 28, 2018, at 3:19 PM, Klemens Nanni wrote:
On Tue, Aug 28, 2018 at 03:15:14PM -0400, Brian Callahan wrote:
I removed the BROKEN marker to see what would happen, and it turns out the
code uses
> On Aug 28, 2018, at 3:19 PM, Klemens Nanni wrote:
>
>> On Tue, Aug 28, 2018 at 03:15:14PM -0400, Brian Callahan wrote:
>> I removed the BROKEN marker to see what would happen, and it turns out the
>> code uses functions that from Py-Pillow that have since been removed. And
>> "fixing" it as
On Tue, Aug 28, 2018 at 03:15:14PM -0400, Brian Callahan wrote:
> I removed the BROKEN marker to see what would happen, and it turns out the
> code uses functions that from Py-Pillow that have since been removed. And
> "fixing" it as best I could ran into a different segfault (from pygame it
>
On 08/28/18 14:56, Daniel Jakots wrote:
Hi,
I don't know about our policy about ports that have been marked as
BROKEN for years. For instance,
$ cvs blame games/fretsonfire/Makefile:
1.12 (sthen06-Apr-14): BROKEN = fails at runtime "python2.7
in free(): error: modified
13 matches
Mail list logo
