MainInclusionReportJACK

Differences between revisions 7 and 8
⇤ ← Revision 7 as of 2008-08-06 16:23:32 →
Size: 3353
Editor: localhost
Comment: converted to 1.6 markup
← Revision 8 as of 2009-09-09 17:24:25 → ⇥
Size: 2684
Editor: 17
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
= Main Inclusion Report for jack-audio-connection-kit =

'''Note''': this is a work in progress: every individual remaining placeholder 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.		 = Main Inclusion Report for Jack-Audio-Connection-Kit (JACK)=

= Main Inclusion Report for Jack-Audio-Connection-Kit (JACK)=

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, see launchpad bugs 197957 and 84900)

    • ...

  3. Security:

    • No CVE entries known.

    • No Secunia history known

    • Only binaries in jackd, none of which are suid/sgid: realtime capabilities are nowadays granted to users/groups though /etc/security/limits.conf
    • jackd is of course a daemon, but is not automatically started on startup
    • jackd does not listen for network connections itself - it requires the installation of a separately available 'netjack' driver for this.
    • No source code review is performed that we know of.

  4. Quality assurance:

    • Jack needs some audio output device to connect to in order to start. This might fail if such a device is not available, or if another process is keeping a device occupied that does not support multiple concurrent connections.
    • Jack does not ask any debconf questions.

    • Debian bugs: only wishlist items are open right now.

    • Maintenance in Debian is calm

    • Upstream is calm

    • Upstream bug tracker: nothing particularly relevant or critical there either it seems

  5. Standards compliance:

  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 * Contributor: Arnout 'raboof' Engelen

MainInclusionReportJACK (last edited 2010-03-16 12:37:56 by 189)