Main Inclusion Report for saxonb

Requirements

1. Availability: http://archive.ubuntu.com/ubuntu/pool/universe/s/saxonb; available for all supported architectures or some subset ? yes, all

2. Rationale:

   • Build dependency of openoffice.org

3. Security:

   • CVE entries: none

   • Secunia history: none

   • Any binaries running as root or suid/sgid ? Any daemons ? no, no
   • Network activity: does it open any port ? Does it handle incoming network data ? no, no
   • Does it directly (not through a library) process binary (video, audio, etc) or structured (PDF, etc) data ? yes
   • Any source code review performed ? no

4. Quality assurance:

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

   • Debian bugs: none

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

   • Upstream is frenetic/vigorous/calm/dead ? calm

   • Upstream bug tracker: none

   • 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, no

5. UI standards:

   • User-visible strings are internationalized using standard gettext system ? no
   • Package with translatable strings builds a PO template during package build ? no
   • End-user applications ship a desktop file ? no

6. 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, simple-patchsys, no

7. Dependencies:

   • java-gcj-compat | java1-runtime | java2-runtime, libdom4j-java, libjdom1-java, libxom-java
   • Are these all in main ? no, libdom4j-java, libjdom1-java, libxom-java

8. Maintenance:

   • How much maintenance is this package likely to need ? not much, its a sync

   • Who is responsible for monitoring the quality of this package and fixing its bugs ? Are they Ubuntu or Debian developers ? Debian Java Maintainers <pkg-java-maintainers@lists.alioth.debian.org>, Michael Koch <konqueror@gmx.de>

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 ? Has it had different names in the past ? saxon

10. Internationalization:

    • Are graphical applications translatable? Do they support gettext? no

Reviewers

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

ChrisCheney