On Sun, Mar 10, 2019 at 9:36 PM Carl Eugen Hoyos wrote:
> > What might work is disabling the avdevice outdev AND
> > moving 'ffplay' to its own binary package.
>
> Before suggesting this, I would prefer the OP to test. I
> still do not entirely believe that this fixes his issue.
>
>
There is a go
Processing control commands:
> tag -1 pending
Bug #923494 [ffmpeg] Please Recommend and dlopen libsdl2 rather than depending
on it
Added tag(s) pending.
--
923494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923494
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Please show the dependencies of (at least) libavutil and libavcodec
with your approach and maybe compare them to what sdl needs: While the
list may become smaller I wonder if it this would really solve the
described issue.
2019-03-12 13:25 GMT+01:00, Reinhard Tartler :
> In a headless installation that is used for transcoding and streaming,
> such dependencies, like on X11, wayland, etc. may not be desirable.
Funny that you mention X11 and wayland: Both are still dependencies
of FFmpeg after your patch, no?
On Sun, Mar 10, 2019, 14:18 Sam Hartman wrote:
> package: csound
> severity: important
> justification: Stretch regression with no work around without code
> changes
> version: 1:6.12.2~dfsg-3
> tags: patch, fixed-upstream, upstream
>
> Hi. In https://github.com/csound/csound/issues/1119
> I rep
On Tue, Mar 12, 2019 at 08:25:55AM -0400, Reinhard Tartler wrote:
> On Sun, Mar 10, 2019 at 9:36 PM Carl Eugen Hoyos wrote:
>
> > > What might work is disabling the avdevice outdev AND
> > > moving 'ffplay' to its own binary package.
> >
> > Before suggesting this, I would prefer the OP to test.
On Tue, Mar 12, 2019 at 08:25:55AM -0400, Reinhard Tartler wrote:
>Depends: libavcodec58 (= 7:4.1.1-2),
> libavdevice58 (= 7:4.1.1-2), libavfilter7 (= 7:4.1.1-2), libavformat58 (=
> 7:4.1.1-2), libavresample4 (= 7:4.1.1-2), libavutil56 (= 7:4.1.1-2), libc6
> (>= 2.14
2019-03-12 18:48 GMT+01:00, Josh Triplett :
> On Tue, Mar 12, 2019 at 08:25:55AM -0400, Reinhard Tartler wrote:
>> I think this should address the issue. Any objections to this approach?
>
> This would work perfectly for me, and I would then avoid installing
> ffplay on my servers.
I was expectin
On Tue, Mar 12, 2019 at 08:31:51PM +0100, Carl Eugen Hoyos wrote:
> 2019-03-12 18:48 GMT+01:00, Josh Triplett :
> > On Tue, Mar 12, 2019 at 08:25:55AM -0400, Reinhard Tartler wrote:
>
> >> I think this should address the issue. Any objections to this approach?
> >
> > This would work perfectly for
On Sun, Feb 10, 2019 at 07:48:12PM +0100, Moritz Muehlenhoff wrote:
> Source: gpac
> Severity: grave
> Tags: security
There's a 0.7.1 in NEW, but that won't be in time for buster, could you
please upload a targeted fix for the open issues for 0.5?
https://security-tracker.debian.org/tracker/sourc
On Tue, Mar 12, 2019 at 1:49 PM Josh Triplett wrote:
> On Tue, Mar 12, 2019 at 08:25:55AM -0400, Reinhard Tartler wrote:
> >Depends: libavcodec58 (= 7:4.1.1-2),
> > libavdevice58 (= 7:4.1.1-2), libavfilter7 (= 7:4.1.1-2), libavformat58 (=
> > 7:4.1.1-2), libavresam
On Tue, Mar 12, 2019 at 07:10:09PM -0400, Reinhard Tartler wrote:
> On Tue, Mar 12, 2019 at 1:49 PM Josh Triplett wrote:
>
> > On Tue, Mar 12, 2019 at 08:25:55AM -0400, Reinhard Tartler wrote:
> > >Depends: libavcodec58 (= 7:4.1.1-2),
> > > libavdevice58 (= 7:4.1.1
12 matches
Mail list logo