Purpose
The purpose of this page is to demonstrate that sh meets the architecture recertification criteria for lenny.
If some of these requirements are irrelevant or implausible for the port, please add a waiver request indicating why and how this isn't a problem for the arch in bold.
Availability
The architecture is publicly available without NDAs via:
Developer machines
The following machines are available to developers:
foo.debian.org - maintained by ..., connectivity via two tin cans and some string.
Port maintainers
The Debian port is maintained by the following developers, who actively work on architecture specific issues:
- ...
- ...
- ...
- ...
- ...
Users
The port is being actively used at the following sites:
- foo: xx machines, yy users, personal workstations
- bar: 1 machine, yyy users, development server
- ...
Popcon indicates zz users of the architecture as at 2005/xx/yy.
Installer
The installer is being maintained by ... and it's currently working effectively. Successful installation reports are available at: ...
Upstream support
Upstream support is provided by:
- glibc: ...
- gcc: ...
- g++: ...
- kernel: ...
- boot loader: ...
- ...
Archive coverage and Autobuilder support
The port is currently at xx% up to date according to the buildd stats (95% cut off)
The port has currently built xx% of the archive according to the buildd stats (90% cut off)
Archive cleanliness
The port builds from unmodified Debian source.
Autobuilders
The following machines run buildds for the port:
- oldstable (oldstable-proposed-updates, oldstable-security)
- foo.debian.org - connectivity via ..., buildd logs checked by ..., adminned by ...
- stable (proposed-updates, stable-security)
- foo.debian.org - connectivity via ..., buildd logs checked by ..., adminned by ...
- testing (testing-proposed-updates, testing-security)
- foo.debian.org - connectivity via ..., buildd logs checked by ..., adminned by ...
- unstable
- foo.debian.org - connectivity via ..., buildd logs checked by ..., adminned by ...
Vetoes
The security team have noted the following problems in supporting the architecture:
- None
The Debian admin team have noted the following problems in supporting the architecture:
- None
The stable release team have noted the following problems in supporting the architecture:
- None
The release team have noted the following problems in supporting the architecture:
- None