Main Inclusion Report for libelf

Requirements

1. Availability: universe; available for all supported architectures or some subset? all

2. Rationale:

   • Why is this package needed? This package is a build-dep of prelink

   • Build dependency of prelink

3. Security:

   • no CVE entries

   • no Secunia history

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

   • 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 ? yes: ELF binaries are parsed

   • Any source code review performed ? yes, did a quick check

4. Quality assurance:

   • In what situations does the package not work out of the box without configuration ? works out of the box

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

   • Debian bugs: nothing serious

   • Maintenance in Debian is calm

   • Upstream is active

   • Upstream bug tracker: could not be found

   • 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 ? no Is it enabled to run in the build ?

5. UI standards: not a GUI application

   • User-visible strings are internationalized using standard gettext system ? yes

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

   • End-user applications ship a desktop file ? no

6. Standards compliance:

   • FHS, Debian Policy compliance ? yes

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

7. Dependencies:

   • gettext, debhelper (>= 4)

   • Are these all in main ? yes

8. Maintenance:

   • How much maintenance is this package likely to need ? very little (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 ? ubuntu security team Are they Ubuntu or Debian developers ? yes

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

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.

   • What do upstream call this software ? libelf Has it had different names in the past ? no

10. Internationalization:

    • Are graphical applications translatable? Do they support gettext? N/A

Reviewers

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

KeesCook