Hi Markus,
On 12.01.2016 22:27, Markus Koschany wrote:
> I have uploaded the new revision a few minutes ago, so this bug should
> be closed very soon. The new upstream release requires a new, yet
> unpackaged, build-dependency and more work from our side but I will
> forward this patch upstream an
Am 12.01.2016 um 22:18 schrieb Andreas Cadhalpun:
> Hi Markus,
>
> On 11.01.2016 21:43, Markus Koschany wrote:
>> I am working on updating this package. This issue will hopefully be
>> fixed soon.
>
> Thanks!
>
> By the way, I had a quick look at the new upstream version and this
> bug doesn't s
Hi Markus,
On 11.01.2016 21:43, Markus Koschany wrote:
> I am working on updating this package. This issue will hopefully be
> fixed soon.
Thanks!
By the way, I had a quick look at the new upstream version and this
bug doesn't seem to be fixed there. So it would be great if you could
forward the
Hi,
On Fri, 8 Jan 2016 00:43:21 +0100 Andreas Cadhalpun
wrote:
> Dear Maintainer,
>
> the next version of FFmpeg is planned to be released this month
> (and it might be called 3.0 instead of 2.9).
>
> Since I haven't heard back from you during the past two month
> I'm wondering what the status
Dear Maintainer,
the next version of FFmpeg is planned to be released this month
(and it might be called 3.0 instead of 2.9).
Since I haven't heard back from you during the past two month
I'm wondering what the status of this bug is:
* Are you aware of the patch I provided?
* Do you plan an upl
Package: renpy
Version: 6.17.6-1.1
Severity: important
Tags: patch
User: pkg-multimedia-maintain...@lists.alioth.debian.org
Usertags: ffmpeg2.9
Dear Maintainer,
your package fails to build with the upcoming ffmpeg 2.9.
This bug will become release-critical at some point when the
ffmpeg2.9 transit
6 matches
Mail list logo
