Purpose

The purpose of this page is to demonstrate that sparc meets the 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. Sun Microsystems

  2. Fujitsu

  3. Tatung

  4. NextCom

  5. Tadpole

Developer machines

The following machines are available to developers:

  1. vore.debian.org - hosted at visi.net

  2. auric.debian.org - hosted at visi.net

As of 2006-07-10, none of these do actually work. auric is restricted and vore has been down for quite some time.

Port maintainers

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

  1. ClintAdams (Debian Developer)

  2. Blars Blarson (Debian Developer)
  3. Stephen Frost (Debian Developer)
  4. Brendan O'Dea (Debian Developer)
  5. GuillemJover (Debian Developer)

  6. Jurij Smakov (Debian Developer)

Users

The port is being actively used at the following sites:

  1. Dead Beast Enterprises: deadbeast.net
  2. c47.org: londo.c47.org, lennier.c47.org
  3. ...

Popcon indicates 90 users of the architecture as of 2005-10-11.

Installer

The installer is being maintained by the d-i team with Frans Pop taking a special interest in Sparc and it's currently working effectively. Help is needed on getting d-i working better for newer hardware though. 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 release team have noted the following problems in supporting the architecture:


CategoryEtchReleaseRecertification