Comment 0 for bug 1644364

Revision history for this message
Joshua Powers (powersj) wrote :

[Availability]
The package is currently in universe with no deltas with Debian.

[Rationale]
The package provides an interactive process viewer that is more complex and feature rich than top, while still being a text-mode application. The package is useful for system administrators all the way to general users to get a better idea of what is going on with their system.

[1] https://hisham.hm/htop/index.php

[Security]
There has been a single CVE [1] for htop back in 2008 around version 0.7 (now on 2.0.2). The source package comes with one binary package, which contains a single binary under /usr/bin.

[2] https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-5076

[Quality assurance]
There is no configuration required and no debconf questions asked by the package. The package currently is built and ran across all release architectures.

The package does have a debian/watch file [3].

There are a 14 bugs in the Ubuntu bug tracker [4] and 26 in the Debian bug tacker [5]. None of which are related to data corruption, system crashing, or other catastrophic issues.

[3] https://anonscm.debian.org/cgit/collab-maint/htop.git/tree/debian/watch
[4] https://bugs.launchpad.net/ubuntu/+source/htop
[5] https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no&src=htop

[Dependencies]
All three run time dependencies [6] are in main: libc6, libtinfo5, and libncursesw5

All build dependencies [7] are in main: debhelper, dh-autoreconf, dpkg-dev, libncurses5-dev, libncursesw5-dev, python-minimal

I am ignoring libhwloc-dev and libkvm-dev as build dependencies as libhwloc-dev is marked as 'not linux-any' and libkvm-dev is marked as 'kfreebsd-any'.

[6] http://packages.ubuntu.com/yakkety/htop
[7] http://packages.ubuntu.com/source/yakkety/htop

[Standards compliance]
The package has no major lintian [8] problems.

[8] https://<email address hidden>#htop

[Maintenance]
We can continue to keep this package synced directly with Debian. It is not a volatile package with many changes coming.

[Background information]
The general purpose and context of the package is explained in the package's debian/control file. This package has not had a different name in the past.