Hi Roland,

On Tue, Jun 12, 2018 at 10:40:18AM +0200, Roland Fehrenbacher wrote:
>     A> Hi folks, when I tried to fix this bug I realised that new
>     A> upstream versions are out.  I downloaded the latest one and
>     A> imported it into Git[1].  Since I don't know the software I would
>     A> like to ask you about your reasons you might have to stick to
>     A> version 1.4.  There are some patches to fix and may be some tests
>     A> to do which I can't.  So may be if I do not hear from you I'd
>     A> probably only go with the restriction of architectures to
>     A> amd64/i386 to fix #897239.
> please restrict again to amd64/i386 for now.

OK, so I will do this for the currently available version in Debian.

> I hope I will get around
> building the new version in time before the next freeze.

This would be really nice.  At least I'll upload with a working watch
file which will remember us that some work needs to be done.

> The big
> advantage of the newer versions 2.x + is support for GPUs. To support
> that will be quite a lot of effort though.

I can not be of any help here since I have no idea about this program.
I'd be very happy if you (or one of the other Uploaders) would take over
this effort.  It would be a shame if we would ship outdated software
with Buster.

> Given that we'll have to
> build against the non-free nvidia stuff for GPU support, will this
> require the package to move to non-free as well (at least the GPU variants)?

Packages with free softeare depending from packages in non-free need
to go to contrib.  It would be great if those parts that do not need
the non-free components could stay in main, thought.
Kind regards



Reply via email to