Main Inclusion Report for jack-audio-connection-kit

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.

Requirements

1. Availability: [http://archive.ubuntu.com/ubuntu/pool/universe/j/jack-audio-connection-kit]; Available for all supported architectures.

2. Rationale:

   • Build dependency of the 'jack' alsa plugin (now disabled in libasound2-plugins)

3. Security:

   • No [http://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=jack CVE entries] known.

   • No [http://secunia.com/search/?search=jack Secunia history] known

   • Any binaries running as root or suid/sgid ? Any daemons?
   • Network activity: does it open any port ? Does it handle incoming network data ?
   • Any source code review performed ? (The approver will do a quick and shallow check.)

4. Quality assurance:

   • 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 ?

5. Standards compliance:

   • [http://www.pathname.com/fhs/ FHS], [http://www.de.debian.org/doc/debian-policy/ Debian Policy] compliance ?

   • [http://www.netfort.gr.jp/~dancer/column/libpkg-guide/libpkg-guide.html Debian library packaging guide] standards compliance ?

   • Packaging system (debhelper/cdbs/dbs) ? Patch system ? Any packaging oddities ?

6. Dependencies:

   • ...
   • Are these all in main ?

7. 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.
   • What do upstream call this software ? Has it had different names in the past ?

Reviewers

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

The author of this report should put their name here; reviewers will add comments etc. too