Comment 1 for bug 382692

1. Availability:
  - available in universe for all archs
2. Rationale:
  - python-sphinx 0.6.1 (build-)depends on it and several other packages are already in depwait on python-sphinx >= 0.6. It's the successor of python-jinja which is already in main.
3. Security:
  - no CVE entries found
  - no Secunia history found
  - no binaries at all (only a python module)
4. Quality assurance:
  - no debconf questions
  - there is a FTBFS bug open on jinja2 in the Debian BTS, but it looks more like a bug in python-sphinx 0.6.1 itself than jinja2
  - jinja2 is maintained by the Debian Python Modules Team
  - upstream seems to be active (last commit is 4 weeks old)
  - the source code contains a test suite but is doesn't seem to be run during build (at least it's not visible in the build log)
5. UI standards: n/a
6. Standards compliance:
  - package is linitian clean (2 warnings)
  - it's packaged with debhelper and quilt for patch management
7. Dependencies:
  - all (build-)dependencies are in main
8. Maintenance:
  - not much maintance is to be expected (only a merge in the future due to Ubuntu changes)