3135
Comment: add info about gounod developer machine
|
3179
|
Deletions are marked like this. | Additions are marked like this. |
Line 91: | Line 91: |
---- CategoryEtchReleaseRecertification |
Perhaps this is only a formality, but --
Purpose
The purpose of this page is to demonstrate that i386 (IA32) meets the [http://release.debian.org/etch_arch_criteria.html architecture recertification criteria for etch].
Availability
The architecture is publicly available without NDAs via:
- etc ad naseum
Developer machines
The following machines are available to developers:
gluck.debian.org - maintained by Debian System Administration, good connectivity
gounod.debian.org - new machine, not yet deployed but intended to split tasks with gluck and have developer chroots, will be maintained by DSA.
Waiver: everyone has an i386 of their own, developer machines are unnecesary.
This is wrong. I don't have any i386 machines, and no intention of getting one. More than once I wanted to debug something on i386, and couldn't. -- Falk Hueffner <falk@debian.org>
A waiver shouldn't be necessary, but there aren't any i386 debian.org machines with chroots listed on db.debian.org, and the non-gluck developer access machines all seem to be down, or require a separate account.
The Debian port is maintained by the following developers, who are familiar with arch-specific issues for this port Joey Hess <joeyh@debian.org>
The port is being actively used at the following sites: Download statistics indicate i386 accounts for over 90% of Debian users.
The installer is being maintained by Joey Hess and numerous other d-i team members and it's currently working effectively. Successful installation reports are avaibable on even days of the week.
Upstream support is provided by:
The port builds from unmodified Debian source.
The following machines run buildds for the port: cyberhq - buildd logs checked by RyanMurray, adminned by RyanMurray
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: Port maintainers
Waiver: the majority of developers work on i386 natively, so arch-specific issues are usually dealt with by maintainers and upstream rather than a small porting team. Users
Installer
Upstream support
Archive coverage and Autobuilder support
Archive cleanliness
Autobuilders
Vetoes