Differences between revisions 15 and 17 (spanning 2 versions)
Revision 15 as of 2005-11-10 10:25:15
Size: 3830
Editor: ?SteveLangasek
Comment:
Revision 17 as of 2005-11-18 07:36:49
Size: 4401
Editor: ?IngoJuergensmann
Comment:
Deletions are marked like this. Additions are marked like this.
Line 36: Line 36:
  Please see http://www.buildd.net/cgi/archvote.phtml -- voluntary registration of some users since the requirement was made public. Lists 51 users as of 2005/10/10, after the page had been somewhat advertised for about a week. 67 users are listed on 2005/10/16.   Please see http://www.buildd.net/cgi/archvote.phtml -- voluntary registration of some users since the requirement was made public. Lists 51 users as of 2005/10/10, after the page had been somewhat advertised for about a week. 95 users are listed on 2005/11/18.
Line 41: Line 41:
Popcon indicates 3 users of the architecture as at 2005/10/10. Popcon indicates 5 users of the architecture as at 2005/11/18.
Line 58: Line 58:
   -- there are bugs on other archs as well, such as http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=210809 (ppc) or http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=223767 (i386) and there's no criticism on the binutils for those ports on their wiki pages. So why here? The requirement was to have upstream binutils support, which m68k has, not if this upstream support produces bugfree software. (ij)
Line 71: Line 72:
For an overview of current autobuilders, please see http://unstable.buildd.net/index-m68k.html. 15 active machines as of this writing. For an overview of current autobuilders, please see http://unstable.buildd.net/index-m68k.html. 15 active machines as of this writing. Quickstep might be considered as redundancy. It usually builds experimental, but can do unstable, too.
Line 88: Line 89:
   -- backlog cleared since ~2 weeks (as of 2005/11/18) (ij)

Purpose

The purpose of this page is to demonstrate that m68k meets the [http://release.debian.org/etch_arch_criteria.html architecture recertification criteria for etch].

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, connectivity via 10Mbit Ethernet.

  2. kullervo.debian.org - maintained by DSA, connectivity via 10Mbit Ethernet -- kullervo was not available for aba on 2005-10-29

Port maintainers

The Debian port is maintained by the following developers, who are familiar with arch-specific issues for this port

  1. Wouter Verhelst <wouter@debian.org>

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

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

  4. Adam Conrad <adconrad@debian.org>

  5. Michael Schmitz <schmitz@debian.org>

  6. ...

Users

The port is being actively used at the following sites:

Popcon indicates 5 users of the architecture as at 2005/11/18.

Installer

The installer is being maintained by Stephen Marenka and Wouter Verhelst and the Sarge version is currently working effectively (the Etch version needs some more work, see ?DebianInstallerM68kTodo).

Upstream support

Upstream support is provided by:

Archive coverage and Autobuilder support

Archive cleanliness

The port builds from unmodified Debian source.

Autobuilders

For an overview of current autobuilders, please see http://unstable.buildd.net/index-m68k.html. 15 active machines as of this writing. Quickstep might be considered as redundancy. It usually builds experimental, but can do unstable, too.

Also note that the release team has agreed on grandfathering in the m68k port wrt this requirement.

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 release team have noted the following problems in supporting the architecture:

  • Not keeping up ATM.
    • -- backlog cleared since ~2 weeks (as of 2005/11/18) (ij)


CategoryEtchReleaseRecertification