Purpose

The purpose of this page is to demonstrate that m68k meets the [http://release.debian.org/lenny_arch_policy.html 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:

  1. http://www.bvm.co.uk/

  2. http://www.czuba-tech.com/CT60/english/welcome.htm

  3. http://www.q40.de/

Developer machines

The following machines are available to developers:

  1. crest.debian.org - maintained by DSA, hosted at NMMN

  2. kullervo.debian.org - maintained by DSA, hosted at NMMN, account on request.

Port maintainers

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

  1. Stephen R. Marenka < smarenka@debian.org >

  2. Christian T. Steigies < cts@debian.org >

  3. Michael A. Casadevall < mcasadevall@buildd.net >

  4. ...
  5. ...

Users

The port is being actively used at the following sites:

  1. http://www.buildd.net/cgi/archvote.phtml lists >120 users

  2. regarding to http://lists.debian.org/stats/: 210 subscribers in 2007-11

  3. ...

Popcon indicates 8 users of the architecture as at 2008/02/14.

Installer

The installer is being maintained by Stephen R. Marenka < smarenka@debian.org > and Wouter Verhelst < wouter@grep.be > and it's currently working effectively. Successful installation reports are available at: ...

Upstream support

Upstream support is provided by:

Archive coverage and Autobuilder support

Archive cleanliness

The port builds from unmodified Debian source.

Autobuilders

The following machines run buildds for the port:

Vetoes

The security team have noted the following problems in supporting the architecture:

The Debian admin team have noted the following problems in supporting the architecture:

The stable release team have noted the following problems in supporting the architecture:

The release team have noted the following problems in supporting the architecture: