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:
Developer machines
The following machines are available to developers:
crest.debian.org - maintained by DSA, hosted at NMMN
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:
Stephen R. Marenka < smarenka@debian.org >
Christian T. Steigies < cts@debian.org >
Michael A. Casadevall < mcasadevall@buildd.net >
- ...
- ...
Users
The port is being actively used at the following sites:
http://www.buildd.net/cgi/archvote.phtml lists >120 users
regarding to http://lists.debian.org/stats/: 210 subscribers in 2007-11
- ...
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:
- glibc: ...
gcc: Michael Casadevall < mcasadevall@buildd.net>
g++: Michael Casadevall < mcasadevall@buildd.net>
- kernel: Geert Uytterhoeven and others
- boot loader: ...
- ...
Archive coverage and Autobuilder support
The port is currently at xx% up to date according to [http://buildd.debian.org/stats/graph2-week.png the buildd stats] (95% cut off)
The port has currently built 77.07% of the archive according to [http://buildd.debian.org/stats/graph-week.png the buildd stats] (90% cut off) (Updated 02/26/2008)
Archive cleanliness
The port builds from unmodified Debian source.
Autobuilders
The following machines run buildds for the port:
- oldstable (oldstable-proposed-updates, oldstable-security)
- crest.debian.net - connectivity via ....
buildd logs checked by Luk Claes < luk@debian.org >, adminned by DSA
- poseidon.marenka.net - connectivity via ....
buildd logs checked by Stephen R. Marenka < smarenka@debian.org >, adminned by Stephen R. Marenka < smarenka@debian.org >.
- zeus.marenka.net - connectivity via ....
buildd logs checked by Stephen R. Marenka < smarenka@debian.org >, adminned by Stephen R. Marenka < smarenka@debian.org >.
- crest.debian.net - connectivity via ....
- stable (proposed-updates, stable-security)
- etch-m68k has no proposed-updates or security available
- testing (testing-proposed-updates, testing-security)
- no testing distribution available
- unstable
- aahz.debian.net - connectivity via DSL (Ethernet? What do you want to see here?)
buildd logs checked by Christian T. Steigies < cts@debian.org >, adminned by Christian T. Steigies < cts@debian.org >.
- akire.buildd.net - connectivity via ....
buildd logs checked by Stephen R. Marenka < smarenka@debian.org >, adminned by Matthias Urlichs < smurf@smurf.noris.de >.
- arrakis.buildd.org - connectivity via 2 Mbps DSL
buildd logs checked by Wouter Verhelst < wouter@grep.be >, adminned by Ingo Juergensmann < [mailto:ij@2007.bluespice.org ij@2008.bluespice.org] >.
- garkin.debian.net - connectivity via ....
buildd logs checked by Christian T. Steigies < cts@debian.org >, adminned by Christian T. Steigies < cts@debian.org >.
- crest.debian.net - connectivity via 10 Mbps
buildd logs checked by Luk Claes < luk@debian.org >, adminned by DSA.
- hobbes - connectivity via ....
buildd logs checked by Michael Schmitz < schmitz@zirkon.biophys.uni-duesseldorf.de >, adminned by Michael Schmitz < schmitz@zirkon.biophys.uni-duesseldorf.de .
- kiivi.cyber.ee - connectivity via ....
buildd logs checked by Wouter Verhelst < wouter@grep.be >, adminned by Meelis Roos < mroos@linux.ee >.
- kullervo.debian.net - connectivity via 10 Mbps
buildd logs checked by Christian T. Steigies < cts@debian.org >, adminned by DSA.
- poseidon.marenka.net - connectivity via ....
buildd logs checked by Stephen R. Marenka < smarenka@debian.org >, adminned by Stephen R. Marenka < smarenka@debian.org >.
- q650.biophys.uni-duesseldorf.de - connectivity via ....
buildd logs checked by Michael Schmitz < schmitz@zirkon.biophys.uni-duesseldorf.de >, adminned by Michael Schmitz < schmitz@zirkon.biophys.uni-duesseldorf.de >.
- spice.buildd.net - connectivity via 16 Mbps DSL
buildd logs checked by Stephen R. Marenka < smarenka@debian.org >, adminned by Ingo Juergensmann < [mailto:ij@2007.bluespice.org ij@2008.bluespice.org] >.
- tanda.debian.net - connectivity via ....
buildd logs checked by Christian T. Steigies < cts@debian.org >, adminned by Christian T. Steigies < cts@debian.org >.
- vault13.mine.nu - connectivity via ....
buildd logs checked by Stephen R. Marenka < smarenka@debian.org >, adminned by Tuomas Vainikka < tvainikk@cc.hut.fi >.
- vivaldi.buildd.org - connectivity via 2 Mbps DSL
buildd logs checked by Stephen R. Marenka < smarenka@debian.org >, adminned by Ingo Juergensmann < [mailto:ij@2007.bluespice.org ij@2008.bluespice.org] >.
- zeus.marenka.net - connectivity via ...
buildd logs checked by Stephen R. Marenka < smarenka@debian.org >, adminned by Stephen R. Marenka < smarenka@debian.org >.
- diablos.nemesisnetworks.com - connectivity via 2 Mbps T1
buildd logs checked by Stephen R. Marenka < smarenka@debian.org >, adminned by Michael A. Casadevall < mcasadevall@buildd.net >
- cronos.nemesisnetworks.com - connectivity via 2 Mbps T1
buildd logs checked by Stephen R. Marenka < smarenka@debian.org >, adminned by Michael A. Casadevall < mcasadevall@buildd.net >
- hades.nemesisnetworks.com - connectivity via 2 Mbps T1
buildd logs checked by Stephen R. Marenka < smarenka@debian.org >, adminned by Michael A. Casadevall < mcasadevall@buildd.net >
- aahz.debian.net - connectivity via DSL (Ethernet? What do you want to see here?)
Vetoes
The security team have noted the following problems in supporting the architecture:
- Needs a fast security buildd (Note: cronos or diablos may be fast enough for security)
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:
- Required up-to-date glibc with TLS