RabbitmqMIR

Requirements

  1. Availability: http://archive.ubuntu.com/ubuntu/pool/universe/r/rabbitmsq-server; available for all supported architectures.

  2. Rationale:

    • Apart of the canonical Application support spec.
  3. Security:

    • No CVE entries.

    • No Secunia history.

    • No binaries running as root or suid/sgid. Daemons are started through running erlang.
    • Opens up 5673. Due to the nature of rabbit-mq it handles incoming data.
    • It directly (not through a library) process binary (video, audio, etc) or structured (PDF, etc) data.
    • No source code review performed.
  4. Quality assurance:

    • The situations where rabbitmq server does not start out of the box is that it might not be configured for the users network.
    • No debconf questions asked.
    • Debian bugs

    • Maintenance in Debian is vigorous.

    • Upstream is vigorous.

    • No upstream bug tracker, it looks like bugs are reported through the
    • No special hardware is required.
    • No testsuite included.
  5. Standards compliance:

    • FHS and Debian Policy compliant.

    • Uses cdbs but has debhelper as a build dependency.
  6. Dependencies:

    • cdbs - in main
    • debhelper (>= 5) - in main

    • erlang-dev - in main
    • python-simplejson - in main
    • erlang-base | erlang-base-hipe - not in main
    • erlang-ssl - not in main
    • erlang-os-mon - not in main
    • erlang-mnesia - not in main
    • adduser - in main
    • logrotate - in main
  7. Maintenance:

* Since there are no ubuntu changes the package can just be synced from debian. The ubuntu server team will be responsible for the maintaing the package in Ubuntu

Reviewers

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

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

RabbitmqMIR (last edited 2009-08-12 15:27:00 by CPE0006258ec6c1-CM000a73655d0e)