[MIR] mutagen introduces b-d's on faad2 and liboggz

according to bug 885858 the b-d on faad could be dropped

Based on 885858: "The faad depedency can be removed IMO, it's only used for the test suite." I would prefer not to pull in another audio encoder into main if we can at all avoid it-- these are often fast moving and hard to maintain.

Please adjust the test suite to disable the faad test.

Better yet, drop faad2 to a Suggests and simply have the test suite fail gracefully if the binary isn't there. This will allow people to install faad2 for testing of security updates, SRUs, etc.

Availability: Package is in universe

Rationale: needed for mutagen

Security: One CVE (CVE-2009-3377) and it was fixed in a timely fashion with minimal effort

QA:
- library
- no debconf questions
- no important outstanding Debian or Ubuntu bugs
- package is in sync with Debian and well maintained (though not many updates
- package ships a test suite which is enabled in the build
- package uses a debian/watch file

UI Standards: N/A

Dependencies: all main

Standards compliance: lintian clean for source. errors from lintian on the binary: liboggz2-dev
E: liboggz2-dev: non-empty-dependency_libs-in-la-file usr/lib/liboggz.la
lintian -i *.deb says this may cause problems with multi-arch

Maintenance: should be trivial if in sync from Debian. The above lintian change should be pushed to Debian

Extended security checks: not required

Bottom line: once the lintian error is addressed (must be sent to Debian as well! :) this package is acceptable for main inclusion.

This was fixed a while ago already:

mutagen (1.20-1ubuntu1) precise; urgency=low

  * debian/control: Drop unnecessary faad and oggz-tools build dependencies,
    they are in universe.

 -- Martin Pitt <email address hidden> Tue, 13 Dec 2011 12:49:42 +0100

So this is not a release blocker.

[Expired for liboggz (Ubuntu) because there has been no activity for 60 days.]

[Expired for liboggz (Ubuntu Precise) because there has been no activity for 60 days.]