Re: working for wheezy-security until wheezy-lts starts
Brian May <firstname.lastname@example.org> writes:
>> 2. Spend some time on investigating what it takes to backport
>> libav from jessie to wheezy. 11.x is still supported by
>> libav upstream and we could share triage work for jessie/wheezy
>> going forwards. 0.8 has simply too much missing.
>> There will be a few applications which are going to break due to
>> API changes, possibly exclude some exotic ones from wheezy LTS
>> support and backport some fixes for important apps from jessie.
>> (Most of the changes are fairly straightforward, e.g. they renamed
>> lots of internal constants).
Am I suppose to mark anywhere that I am now working on libav???
Looks like this will be the first thing I need to "fix":
The following packages have unmet dependencies:
sbuild-build-depends-libav-dummy : Depends: libfreetype6-dev (>= 2.5.1) but 2.4.9-1.1+deb7u1 is to be installed
Depends: libgnutls28-dev but it is not installable
Depends: libopus-dev (>= 1.0.1) but it is not going to be installed
Will see if I can get it to build with what is available in wheezy.
Brian May <email@example.com>