Differences between revisions 8 and 9
Revision 8 as of 2008-05-29 20:04:27
Size: 3187
Editor: ?ArthurLoiret
Comment:
Revision 9 as of 2009-03-16 03:31:46
Size: 3197
Editor: anonymous
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
The purpose of this page is to demonstrate that '''alpha''' meets the [http://release.debian.org/lenny_arch_policy.html architecture re-certification criteria for lenny]. The purpose of this page is to demonstrate that '''alpha''' meets the [[http://release.debian.org/lenny_arch_policy.html|architecture re-certification criteria for lenny]].
Line 10: Line 10:
 1. [http://www.example.com/ some vendor]
 2. [http://www.example.com/ some other vendor]
 1. [[http://www.example.com/|some vendor]]
 2. [[http://www.example.com/|some other vendor]]
Line 57: Line 57:
 * The port is currently at 99% up to date according to [http://buildd.debian.org/stats/graph2-week.png the buildd stats] (95% cut off)
 * The port has currently built 98% of the archive according to [http://buildd.debian.org/stats/graph-week.png the buildd stats] (90% cut off)
 * The port is currently at 99% up to date according to [[http://buildd.debian.org/stats/graph2-week.png|the buildd stats]] (95% cut off)
 * The port has currently built 98% of the archive according to [[http://buildd.debian.org/stats/graph-week.png|the buildd stats]] (90% cut off)

Purpose

The purpose of this page is to demonstrate that alpha meets the architecture re-certification 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:

  1. some vendor

  2. some other vendor

Developer machines

The following machines are available to developers:

  1. albeniz.debian.org - ?AlphaServer ES45 maintained by TimCutts.

  2. sarah.lri.fr - ?AlphaServer 1200 maintainer by ?ArthurLoiret.

Please send a mail to arthur <dot> loiret <at> u-psud <dot> fr for an account on sarah.

Port maintainers

The Debian port is maintained by the following developers, who actively work on architecture specific issues:

  1. ?SteveLangasek

  2. ...
  3. ...
  4. ...
  5. ...

Users

The port is being actively used at the following sites:

  1. ente.limmat.ch: 1 machine, 90 users, internet server
  2. fsffrance.org: 1 machine (gcc30), 44 users, GCC devel machine

Popcon indicates 80 users of the architecture as at 2008/05/29.

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 99% up to date according to the buildd stats (95% cut off)

  • The port has currently built 98% 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 1, buildd logs checked by ..., adminned by ...
  • stable (proposed-updates, stable-security)
    • goetz.debian.org - connectivity via ..., buildd logs checked by neuro, adminned by TimCutts

  • testing (testing-proposed-updates, testing-security)
    • goetz.debian.org - connectivity via GBit, buildd logs checked by neuro, adminned by TimCutts

  • unstable
    • goetz.debian.org - connectivity via GBit, buildd logs checked by neuro, adminned by TimCutts

goetz is a quad-CPU 1.25 GHz ES45 with 8 GB RAM.

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


CategoryLennyReleaseRecertification