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

Bug #879434 reported by Matthias Klose
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
faad2 (Ubuntu)
Won't Fix
High
Unassigned
Precise
Won't Fix
High
Unassigned
liboggz (Ubuntu)
Expired
High
Unassigned
Precise
Expired
High
Unassigned

Bug Description

mutagen introduces b-d's on faad2 and liboggz; either MIR's are needed, or the dependencies need to be dropped.

CVE References

Matthias Klose (doko)
Changed in faad2 (Ubuntu):
importance: Undecided → High
milestone: none → precise-alpha-1
status: New → Confirmed
Changed in liboggz (Ubuntu):
importance: Undecided → High
milestone: none → precise-alpha-1
status: New → Confirmed
Michael Terry (mterry)
Changed in liboggz (Ubuntu Precise):
assignee: nobody → Jamie Strandboge (jdstrand)
Changed in faad2 (Ubuntu Precise):
assignee: nobody → Jamie Strandboge (jdstrand)
Revision history for this message
Matthias Klose (doko) wrote :

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

Dave Walker (davewalker)
Changed in faad2 (Ubuntu):
milestone: precise-alpha-1 → precise-alpha-2
Changed in liboggz (Ubuntu):
milestone: precise-alpha-1 → precise-alpha-2
Revision history for this message
Jamie Strandboge (jdstrand) wrote :

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.

Changed in faad2 (Ubuntu Precise):
status: Confirmed → Won't Fix
assignee: Jamie Strandboge (jdstrand) → nobody
Changed in faad2 (Ubuntu):
assignee: Jamie Strandboge (jdstrand) → nobody
Revision history for this message
Jamie Strandboge (jdstrand) wrote :

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.

Revision history for this message
Jamie Strandboge (jdstrand) wrote :

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.

Changed in liboggz (Ubuntu Precise):
assignee: Jamie Strandboge (jdstrand) → nobody
status: Confirmed → Incomplete
Changed in faad2 (Ubuntu):
status: Confirmed → Won't Fix
milestone: precise-alpha-2 → none
Martin Pitt (pitti)
Changed in liboggz (Ubuntu):
milestone: precise-alpha-2 → ubuntu-12.04-beta-1
Martin Pitt (pitti)
Changed in liboggz (Ubuntu):
milestone: ubuntu-12.04-beta-1 → ubuntu-12.04-beta-2
Revision history for this message
Martin Pitt (pitti) wrote :

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.

Changed in liboggz (Ubuntu Precise):
milestone: ubuntu-12.04-beta-2 → none
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in liboggz (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in liboggz (Ubuntu Precise):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.