On 2014-02-22 12:39:20, Andreas Cadhalpun wrote:
> Hi all,
>
> I have looked at the packaging provided by Antoine and it seems - no
> offense intended - a little bit messy.
Hehe, none taken. To my defense, I did that in about an hour, using
Marillat's packages... :)
> Thus I have started from scratch and packaged FFmpeg 2.1.3 [1] (see
> attached debian.tar.xz).
Awesome!
> I have taken care to avoid conflicts with libav as far as possible, but
> the development files have to conflict, as it is really no good idea to
> build against both ffmpeg and libav at the same time.
You mean the -dev libraries?
> The ffmpeg package does not provide qt-faststart to avoid a conflict
> with libav-tools.
Fair enough - there could be a qt-faststart binary package which could
conflict with libav-tools.
> The libraries are build with --enable-raise-major, which bumps the
> sonames by 100 to get i.e. libavcodec155, thus avoiding conflicts.
> Note that there is also --enable-incompatible-libav-abi that would allow
> packages build against libav to be used with the ffmpeg library, but
> upstream thinks this would not work the other way round as well. And I
> think there wouldn't be too much use for FFmpeg libraries that can only
> be used as a drop in replacement the libav ones, but not to compile
> programs.
Makes sense.
> As the libav development packages are called libavcodec-dev etc., FFmpeg
> has to use different names and I chose libavcodec-ffmpeg-dev and so on.
I guess that makes sense...
> I'm not sure if this package will build on every architecture, because I
> can't test that.
Maybe an upload to experimental could test that? :)
> Any build failures could probably be sorted out by disabling some
> features for some architectures, as I enabled as many features as
> possible for building on linux-amd64, as long as the result is still
> GPLv2 licensed. (Only four codecs are GPLv3.)
Makes sense as well.
> I fixed most of the lintian problems, but some remain:
>
> * E: debian-watch-file-pubkey-file-is-missing:
> This is a bug in lintian [2].
> * E: embedded-library: I don't understand this one:
> Does it complain about libavfilter embedding libavfilter?
> Seems like a bug in lintian.
Not sure about those.
> * W: manpage-has-errors-from-man:
> I don't know how to fix the manpages. Can someone help?
I had the manpage errors as well, I think we can ignore those for now.
> * I: no-symbols-control-file:
> If anyone wants to create one, feel free to do so.
>
> With this package, users can install either ffmpeg or libav-tools and
> developers can either depend on lib*-ffmpeg-dev or on lib*-dev and
> everyone should be happy.
That would be awesome.
> Adrian, do you agree that this is sane?
>
> If the security team is not willing to support both, they can ask the TC
> to decide which one to use, but this does not prevent an upload of FFmpeg.
I don't see why security would complain: as things stand there are
hundreds of security issues that have been fixed in ffmpeg (see the
Google audit) which have not been fixed in libav... It seems to me
ffmpeg is only more secure than libav at this point...
> I think this package is ready for upload, but I'm neither DD nor DM, so
> I can't do this.
I would be hesistant in doing so, considering the controversy, but if we
reach consensus here, i'd be happy to sponsor it.
> Rogério, Jackson are you willing to review my packaging and then
> upload/maintain it? I can help e.g. rebuilding reverse-dependencies for
> future transitions and similar stuff.
>
> In fact, If have rebuild the 109 reverse build-dependencies of src:libav
> simply exchanging lib*-dev with lib*-ffmpeg-dev and 59 build
> successfully, only 50 FTBFS (similarly many fail building with libav 10
> [3], probably due to the same reasons [4]).
> Most failures are due to missing AVCODEC_MAX_AUDIO_FRAME_SIZE and
> CodecID. Only two packages check for a version smaller than 100 and thus
> fail to configure.
>
> I hope FFmpeg will be back in Debian soon.
Good work, cheers!
A.
--
We have no friends but the mountains.
- Kurdish saying
Attachment:
pgpIGQOSXu8JH.pgp
Description: PGP signature