MainInclusionReportPowerman
Main Inclusion Report for powerman
Requirements
Availability: http://archive.ubuntu.com/ubuntu/pool/universe/p/powerman; available for i386, amd64.
Rationale:
- Build dependency of nut
- Powerman allows to manage a wide range of Power Distribution Units (PDUs). Through it, NUT can offer its standardised layers (API, namespace, ...) and tools to manage both PDUs and UPSs
Security:
CVE entries: None
Secunia history: None
- All the framework is working with the "powerman" user. This change (not running as root) was part of the initial Debianisation
- Network activity: powermand opens the port 10101/tcp to receive client queries.
- No binary or structured data processed.
A source code review has been performed by the Debian Developer (ArnaudQuette).
Quality assurance:
- In what situations does the package not work out of the box without configuration ?
- All the profiles are in complain mode by default. Powerman need to be told what device(s) are present.
- Does the package ask any debconf questions higher than priority 'medium' ? No
http://bugs.debian.org/src:powerman:
- Powerman is currently still blocked in the Debian new queue:
Maintenance in Debian is vigorous (but still waiting the initial inclusion!).
Upstream is vigorous.
Upstream bug tracker: no bug currently.
- Hardware: this package adds support for Power Distribution Units (PDUs), which are common devices in Data Centers.
- An upstream test suite is available using "make check" for non regression testing.
- This feature is not used during the build stage.
- In what situations does the package not work out of the box without configuration ?
Standards compliance:
FHS, Debian Policy compliance ? Yes
Debian library packaging guide standards compliance ? Yes
- Packaging system (debhelper/cdbs/dbs) ? debhelper + cdbs
Dependencies:
- in universe:
- genders: can be disabled by removing the Build-Depends in debian/control and --with-genders from DEB_CONFIGURE_EXTRA_FLAGS in debian/rules! but it's an interesting feature (MIR for Genders?!)
- in main:
- libwrap0-dev
- libcurl4-gnutls-dev
- libncurses5-dev
- in universe:
Maintenance:
- How much maintenance is this package likely to need ? Simple
- Who is responsible for monitoring the quality of this package and fixing its bugs ? upstream developer and Debian developer.
Background information:
this point is part of the Improved Power Management blueprint, which will help the Server Team
- What do upstream call this software ? powerman
Reviewers
MIR bug: https://launchpad.net/bugs/337226
Author: ArnaudQuette
MainInclusionReportPowerman (last edited 2009-03-03 14:04:20 by 195)