Main Inclusion Report for libcap2

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/libc/libcap2; available for all supported architectures.

2. Rationale:

   • Build dependency of bind9
   • replacement for libcap

3. Security:

   • CVE entries: none

   • Secunia history: none

   • Any binaries running as root or suid/sgid ? Any daemons ? none
   • Network activity: does it open any port ? 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
   • Any source code review performed ? no

4. Quality assurance:

   • In what situations does the package not work out of the box without configuration ? none known
   • Does the package ask any debconf questions higher than priority 'medium' ? no

   • Debian bugs: 489477 - we'll want 2.10-2 or later

   • Maintenance in Debian is frenetic/vigorous/calm/dead ? calm

   • http://www.eu.kernel.org/pub/linux/libs/security/linux-privs/libcap2/ is frenetic/vigorous/calm/dead ? calm

   • Upstream bug tracker: (mention any particularly relevant or critical) unknown

   • Hardware: Does this package deal with hardware and if so how exotic is it ? no
   • Is there a test suite in the upstream source or packaging ? Is it enabled to run in the build ? no

5. Standards compliance:

   • FHS, Debian Policy compliance ? yes

   • Debian library packaging guide standards compliance ? yes

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

6. Dependencies:

   • cdbs, debhelper (>= 5), libattr1-dev, quilt

   • Are these all in main ? yes

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://launchpad.net/bugs/BUGNUMBER

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