libffado

Differences between revisions 1 and 23 (spanning 22 versions)
⇤ ← Revision 1 as of 2009-08-09 18:29:40 →
Size: 4011
Editor: conr-adsl-209-169-122-85
Comment:
← Revision 23 as of 2009-08-20 01:03:59 → ⇥
Size: 4899
Editor: d66-183-44-51
Comment: added a couple bits.
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
||<style="color:red"> In progress||
Line 4: Line 2:

'''Note''': when writing a report this template should be vigorously edited; as a rule of thumb, every individual point should be replaced with a description of the actual situation in the package in question. The purpose of the report is to convey information to the reviewer, so there is no problem with varying the text in the bullet items, or with adding additional information.

Please be informative, and in particular be thorough in investigating and explaining any weaknesses and problems with the package. The purpose of the report is to show to the reviewer that the package has been properly investigated, and to give the reviewer the information from that investigation, for their decision.
Line 11: Line 5:
 0. ''Availability:'' [[http://archive.ubuntu.com/ubuntu/pool/universe/s/sourcepackage]]; available for all supported architectures or some subset ?  0. ''Availability:'' [[http://archive.ubuntu.com/ubuntu/pool/universe/libf/libffado/]]; available for i386 and amd64 architectures.
Line 13: Line 7:
  * Why is this package needed? What feature(s) does it add? Does upstream expect it? Plain text description of expected use
  * Build dependency of ...
  * 		  * The libffado library provides support for FireWire based audio devices
  * libffado will allow Jackd into main, fixing Bugs [[https://bugs.launchpad.net/bugs/407841|#407841]], [[https://bugs.launchpad.net/bugs/152487|#152487]], [[https://bugs.launchpad.net/bugs/84900|#84900]], [[https://bugs.launchpad.net/bugs/109659|#109659]], [[https://bugs.launchpad.net/bugs/360590|#360590]]
Line 17: Line 10:
  * [[http://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=PRODUCT_NAME|CVE entries]]: ...
  * [[http://secunia.com/search/?search=PRODUCT_NAME|Secunia history]]: ...		   * [[http://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=libffado|CVE entries]]: '''none'''
  * [[http://secunia.com/search/?search=libffado|Secunia history]]: '''none'''
Line 20: Line 13:
  * Network activity: does it open any port ? Does it handle incoming network data ?
  * Does it directly (not through a library) process binary (video, audio, etc) or structured (PDF, etc) data ?
  * Any source code review performed ? (The approver will do a quick and shallow check.)		    * '''DO NOT KNOW'''
   * '''DO NOT KNOW'''
 * Network activity: does it open any port ? '''no'''
  * Does it handle incoming network data ? '''no'''
  * Does it directly (not through a library) process binary (video, audio, etc) or structured (PDF, etc) data ? '''no'''
Line 24: Line 19:
  * In what situations does the package not work out of the box without configuration ?
  * Does the package ask any debconf questions higher than priority 'medium' ?
  * [[http://bugs.debian.org/src:SOURCE_PACKAGE_NAME|Debian bugs]]: (mention any that are particularly relevant, and any showstoppers)
  * [[http://packages.qa.debian.org/S/SOURCE_PACKAGE_NAME.html|Maintenance in Debian]] is frenetic/vigorous/calm/dead ?
  * [[http://|Upstream]] is frenetic/vigorous/calm/dead ?
  * [[http://|Upstream bug tracker]]: (mention any particularly relevant or critical)
  * Hardware: Does this package deal with hardware and if so how exotic is it ?		   * In what situations does the package not work out of the box without configuration ? '''n/a'''
  * Does the package ask any debconf questions higher than priority 'medium' ? '''no'''
  * [[http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libffado|Debian bugs]]: (mention any that are particularly relevant, and any showstoppers) '''None found for libffado, libffado-dbus-server, libffado-mixer-qt4, libffado-tools, libffado-dev or libffado1'''
  * [[http://packages.qa.debian.org/libf/libffado.html|Maintenance in Debian]] is frenetic/vigorous/calm/dead ? '''Maintenances in Debian appears to be vigorous'''
  * [[http://subversion.ffado.org/|Upstream]] is frenetic/vigorous/calm/dead ? '''There appears to be vigorous activity upstream'''
  * [[http://subversion.ffado.org/report|Upstream bug tracker]]: (mention any particularly relevant or critical) '''no noticeably relevant or critical bugs'''
  * Hardware: Does this package deal with hardware and if so how exotic is it ? '''This package does deal with hardware, but none is exotic'''
Line 32: Line 27:
   * '''DO NOT KNOW'''
   * '''DO NOT KNOW'''
Line 33: Line 30:
  * User-visible strings are internationalized using standard gettext system ?
  * Package with translatable strings builds a PO template during package build ?
  * End-user applications ship a desktop file ?		   * User-visible strings are internationalized using standard gettext system ? '''n/a'''
  * Package with translatable strings builds a PO template during package build ? '''n/a'''
  * End-user applications ship a desktop file ? '''n/a'''
Line 38: Line 35:
   * Some Debian Policy concerns exist in this package. The diff.gz file shows direct alteration of the tarball contents without use of a patch system.
   * '''DO NOT KNOW'''
Line 39: Line 38:
   * CDBS packaging system
   * no patch system used
   * '''DO NOT KNOW'''
Line 40: Line 42:
  * ...
  * Are these all in main ?		    * '''libc6 (>= 2.4)'''
   * '''libexpat1 (>= 1.95.8)'''
   * '''libgcc1 (>= 1:4.1.1)'''
   * '''libglib2.0-0 (>= 2.12.0)'''
   * '''libglibmm-2.4-1c2a (>= 2.19.8)'''
   * '''libiec61883-0 (>= 1.2.0)'''
   * '''libraw1394-11'''
   * '''libsigc++-2.0-0c2a (>= 2.0.2)'''
   * '''libstdc++6 (>= 4.1.1)'''
   * '''libxml++2.6-2 (>= 2.24.0)'''
   * '''libxml2 (>= 2.6.27)'''
  * Are these all in main ? '''yes'''
Line 43: Line 55:
  * How much maintenance is this package likely to need ? (Simple packages may largely take care of themselves; complex packages will need dedicated developers paying attention to them.)
  * Who is responsible for monitoring the quality of this package and fixing its bugs ? Are they Ubuntu or Debian developers ?
  * Who is the package bug contact in Ubuntu? (Needs one if its a nontrivial package which does not fully maintain itself through Debian)		   * How much maintenance is this package likely to need ? (Simple packages may largely take care of themselves; complex packages will need dedicated developers paying attention to them.) '''Little maintenance should be required'''
  * Who is responsible for monitoring the quality of this package and fixing its bugs ? Are they Ubuntu or Debian developers ? '''Upstream (FFADO) developers along with Ubuntu developers'''
  * Who is the package bug contact in Ubuntu? (Needs one if its a nontrivial package which does not fully maintain itself through Debian) '''[[https://launchpad.net/~ubuntustudio-dev|Ubuntu Studio developers]]'''
Line 47: Line 59:
  * The general purpose and context of the package should be clear from the package's debian/control file. If it isn't then please explain.
  * What do upstream call this software ? Has it had different names in the past ?		   * The general purpose and context of the package should be clear from the package's debian/control file. If it isn't then please explain. '''It should already be clear'''
  * What do upstream call this software ? Has it had different names in the past ? '''Upstream calls this software FFADO (Free FireWire Audio Drivers). It was previously know as FreeBoB'''
Line 50: Line 62:
  * Are graphical applications translatable? Do they support gettext?   * Are graphical applications translatable? '''n/a'''
  * Do they support gettext? '''n/a''
Line 56: Line 70:
''The author of this report should put their name here; reviewers will add comments etc. too' ''Author: [[https://launchpad.net/~slavender|Scott Lavender]]''

Main Inclusion Report for libffado

Requirements

  1. Availability: http://archive.ubuntu.com/ubuntu/pool/universe/libf/libffado/; available for i386 and amd64 architectures.

  2. Rationale:

  3. Security:

    • CVE entries: none

    • Secunia history: none

    • Any binaries running as root or suid/sgid ? Any daemons ?

      • DO NOT KNOW

      • DO NOT KNOW

    • Network activity: does it open any port ? no

    • Does it handle incoming network data ? no

    • Does it directly (not through a library) process binary (video, audio, etc) or structured (PDF, etc) data ? no

  4. Quality assurance:

    • In what situations does the package not work out of the box without configuration ? n/a

    • Does the package ask any debconf questions higher than priority 'medium' ? no

    • Debian bugs: (mention any that are particularly relevant, and any showstoppers) None found for libffado, libffado-dbus-server, libffado-mixer-qt4, libffado-tools, libffado-dev or libffado1

    • Maintenance in Debian is frenetic/vigorous/calm/dead ? Maintenances in Debian appears to be vigorous

    • Upstream is frenetic/vigorous/calm/dead ? There appears to be vigorous activity upstream

    • Upstream bug tracker: (mention any particularly relevant or critical) no noticeably relevant or critical bugs

    • Hardware: Does this package deal with hardware and if so how exotic is it ? This package does deal with hardware, but none is exotic

    • Is there a test suite in the upstream source or packaging ? Is it enabled to run in the build ?

      • DO NOT KNOW

      • DO NOT KNOW

  5. UI standards:

    • User-visible strings are internationalized using standard gettext system ? n/a

    • Package with translatable strings builds a PO template during package build ? n/a

    • End-user applications ship a desktop file ? n/a

  6. Standards compliance:

    • FHS, Debian Policy compliance ?

      • Some Debian Policy concerns exist in this package. The diff.gz file shows direct alteration of the tarball contents without use of a patch system.

      • DO NOT KNOW

    • Packaging system (debhelper/cdbs/dbs) ? Patch system ? Any packaging oddities ?
      • CDBS packaging system
      • no patch system used

      • DO NOT KNOW

  7. Dependencies:

    • libc6 (>= 2.4)

    • libexpat1 (>= 1.95.8)

    • libgcc1 (>= 1:4.1.1)

    • libglib2.0-0 (>= 2.12.0)

    • libglibmm-2.4-1c2a (>= 2.19.8)

    • libiec61883-0 (>= 1.2.0)

    • libraw1394-11

    • libsigc++-2.0-0c2a (>= 2.0.2)

    • libstdc++6 (>= 4.1.1)

    • libxml++2.6-2 (>= 2.24.0)

    • libxml2 (>= 2.6.27)

    • Are these all in main ? yes

  8. Maintenance:

    • How much maintenance is this package likely to need ? (Simple packages may largely take care of themselves; complex packages will need dedicated developers paying attention to them.) Little maintenance should be required

    • Who is responsible for monitoring the quality of this package and fixing its bugs ? Are they Ubuntu or Debian developers ? Upstream (FFADO) developers along with Ubuntu developers

    • Who is the package bug contact in Ubuntu? (Needs one if its a nontrivial package which does not fully maintain itself through Debian) Ubuntu Studio developers

  9. Background information:

    • The general purpose and context of the package should be clear from the package's debian/control file. If it isn't then please explain. It should already be clear

    • What do upstream call this software ? Has it had different names in the past ? Upstream calls this software FFADO (Free FireWire Audio Drivers). It was previously know as FreeBoB

  10. Internationalization:

    • Are graphical applications translatable? n/a

    • Do they support gettext? n/a

Reviewers

MIR bug: https://launchpad.net/bugs/BUGNUMBER

Author: Scott Lavender

MainInclusionReport/libffado (last edited 2009-08-21 03:35:32 by conr-adsl-209-169-122-85)