Differences between revisions 18 and 20 (spanning 2 versions)
Revision 18 as of 2005-11-18 07:39:04
Size: 4403
Editor: ?IngoJuergensmann
Comment:
Revision 20 as of 2005-11-21 09:34:46
Size: 4852
Editor: ?IngoJuergensmann
Comment:
Deletions are marked like this. Additions are marked like this.
Line 54: Line 54:
 * boot loader: Emile (Laurent Vivier <lvivier@users.sourceforge.net>)  * boot loader: see Bootloaders on http://wiki.debian.org/DebianInstallerM68kTodo
   *
Emile (Laurent Vivier <lvivier@users.sourceforge.net>) (not yet packaged, but planned by Wouter & Stephen)
Line 56: Line 57:
   * amiboot
Line 59: Line 61:
   -- 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)    -- 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? ''Higher severity, affecting more packages, and no evidence for a long time that the bugs were being worked on. However, recently upstream seems to actually be getting such bugs fixed, which certainly qualifies as upstream support.'' The requirement was to have upstream binutils support, which m68k has, not if this upstream support produces bugfree software. (ij)
  -> so can we remove these comments now?
Line 64: Line 68:
 * 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 xx% of the archive according to [http://buildd.debian.org/stats/graph-week.png the buildd stats] (90% cut off)
 * The port is currently at 94.5% (2005/11/20) up to date according to [http://buildd.debian.org/stats/graph2-week.png the buildd stats] (95% cut off)
 * The port has currently built 96.5% (2005/11/20) 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 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:

  • glibc: Andreas Schwab <schwab@suse.de>

  • gcc: Andreas Schwab <schwab@suse.de>

  • kernel: linux-m68k@vger.kernel.org -- central mailinglist for m68k kernel development; rather active, with ~5-10 regular posters and (on average) a few posts each day.

  • boot loader: see Bootloaders on http://wiki.debian.org/DebianInstallerM68kTodo

    • Emile (Laurent Vivier <lvivier@users.sourceforge.net>) (not yet packaged, but planned by Wouter & Stephen) -- If you're going to list upstream support for the bootloader, it would be good to pick one that's in Debian today, please. ?SteveLangasek

    • amiboot
  • binutils: Ben Elliston <bje@gnu.org>

    • bugs like Debian 327780 crop up regularly anyway though

      -- 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? Higher severity, affecting more packages, and no evidence for a long time that the bugs were being worked on. However, recently upstream seems to actually be getting such bugs fixed, which certainly qualifies as upstream support. The requirement was to have upstream binutils support, which m68k has, not if this upstream support produces bugfree software. (ij)

    • -> so can we remove these comments now?

  • ...

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