Am 11.01.2012 01:19, schrieb Carl Eugen Hoyos:
libav is just one of several FFmpeg forks, all forks share several security
issues and many known bugs and regressions not present in FFmpeg, see the FFmpeg
bug tracker for details
Schily?!
;)
___
pkg-m
Hans-Christoph Steiner at.or.at> writes:
> >> I'm not really convinced by 'avtools' and 'avutils', as both seem
> >> pretty generic to me. 'libav' was chosen to follow the name change of
> >> the project 'ffmpeg'->'libav'.
> >
> > To clarify:
> > There was no name change, the FFmpeg project is a
On Jan 10, 2012, at 7:19 PM, Carl Eugen Hoyos wrote:
> Reinhard Tartler gmail.com> writes:
>
>> I'm not really convinced by 'avtools' and 'avutils', as both seem
>> pretty generic to me. 'libav' was chosen to follow the name change of
>> the project 'ffmpeg'->'libav'.
>
> To clarify:
> There w
Reinhard Tartler gmail.com> writes:
> I'm not really convinced by 'avtools' and 'avutils', as both seem
> pretty generic to me. 'libav' was chosen to follow the name change of
> the project 'ffmpeg'->'libav'.
To clarify:
There was no name change, the FFmpeg project is active with no name change
On Mon, Jan 9, 2012 at 10:01 AM, IOhannes m zmoelnig wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 2012-01-07 21:47, Paul Gevers wrote:
>>>
>>> It was specifically design for migration purposes. Still, you might
>>> want to update the dependencies for your package and update it t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-01-07 21:47, Paul Gevers wrote:
>>
>> It was specifically design for migration purposes. Still, you might
>> want to update the dependencies for your package and update it to use
>> '/usr/bin/avconf' instead of '/usr/bin/ffmpeg'.
>
> If I unde
> '/usr/bin/avconf' instead of '/usr/bin/ffmpeg'.
s/avconf/avconv/ that is. ;)
___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maint
>>> Then let's go with 'libav-tools', unless someone objects that is.
>>
>> Just to be sure, we are talking about the binaries here right? As the
>> source name seems fine with me and is no problem, right? I don't think
>> users would understand this name any better than ffmpeg, but I think the
>>
On Sat, Jan 7, 2012 at 9:04 PM, Paul Gevers wrote:
>> Then let's go with 'libav-tools', unless someone objects that is.
>
> Just to be sure, we are talking about the binaries here right? As the
> source name seems fine with me and is no problem, right? I don't think
> users would understand this n
> Then let's go with 'libav-tools', unless someone objects that is.
Just to be sure, we are talking about the binaries here right? As the
source name seems fine with me and is no problem, right? I don't think
users would understand this name any better than ffmpeg, but I think the
lib start might
On Sat, Jan 7, 2012 at 7:47 PM, Guillem Jover wrote:
> On Sat, 2012-01-07 at 19:03:23 +0100, Reinhard Tartler wrote:
>> On Sat, Jan 7, 2012 at 6:39 PM, Guillem Jover wrote:
>> > Package: libav
>> > Version: 4:0.8~beta1-2
>> > Severity: wishlist
>
>> > There's now a libav binary package in experim
On Sat, 2012-01-07 at 19:03:23 +0100, Reinhard Tartler wrote:
> On Sat, Jan 7, 2012 at 6:39 PM, Guillem Jover wrote:
> > Package: libav
> > Version: 4:0.8~beta1-2
> > Severity: wishlist
> > There's now a libav binary package in experimental, which ffmpeg
> > transitions to (due to the upstream ch
On Sat, Jan 7, 2012 at 6:39 PM, Guillem Jover wrote:
> Package: libav
> Version: 4:0.8~beta1-2
> Severity: wishlist
>
> Hi!
>
> There's now a libav binary package in experimental, which ffmpeg
> transitions to (due to the upstream change). The thing is that I
> initially got pretty confused by the
Package: libav
Version: 4:0.8~beta1-2
Severity: wishlist
Hi!
There's now a libav binary package in experimental, which ffmpeg
transitions to (due to the upstream change). The thing is that I
initially got pretty confused by the name, and on a quick glance
thought it was a metapackage for the shar
14 matches
Mail list logo
