5
Comment:
|
3350
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
... | 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: 1. http://www.ibm.com/ 2. http://www.hp.com/ 3. http://www.dell.com/ 4. etc ad naseum = Developer machines = The following machines are available to developers: 1. '''gluck.debian.org''' - maintained by Debian System Administration, good connectivity 2. '''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 unnecessary.''' 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. = Port maintainers = The Debian port is maintained by the following developers, who are familiar with arch-specific issues for this port: 1. Joey Hess <joeyh@debian.org> 2. ... 3. ... 4. ... 5. ... '''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 = The port is being actively used at the following sites: 1. debian.org: multiple machines, over 100 active users on people.debian.org in first week of October, many more using services remotely such as bugs.debian.org Download statistics indicate i386 accounts for over 90% of Debian users. = Installer = 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 available on even days of the week. = Upstream support = Upstream support is provided by: * glibc: primary upstream arch * gcc: primary upstream arch * g++: primary upstream arch * kernel: primary upstream arch * boot loader: grub, lilo = Archive coverage and Autobuilder support = * The port is currently at 99% up to date according to the buildd stats (95% cut off) * The port has currently built 99% of the archive according to the buildd stats (90% cut off) = Archive cleanliness = The port builds from unmodified Debian source. = Autobuilders = The following machines run buildds for the port: * cyberhq - buildd logs checked by RyanMurray, adminned by RyanMurray '''Waiver (for redundancy, since there isn't any): Most developers upload for i386; buildd downtime can be made up for with manual uploads for the few other packages''' = 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: * None ---- 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 unnecessary.
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.
Port maintainers
The Debian port is maintained by the following developers, who are familiar with arch-specific issues for this port:
Joey Hess <joeyh@debian.org>
- ...
- ...
- ...
- ...
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
The port is being actively used at the following sites:
- debian.org: multiple machines, over 100 active users on people.debian.org in first week of October, many
- more using services remotely such as bugs.debian.org
Download statistics indicate i386 accounts for over 90% of Debian users.
Installer
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 available on even days of the week.
Upstream support
Upstream support is provided by:
- glibc: primary upstream arch
- gcc: primary upstream arch
- g++: primary upstream arch
- kernel: primary upstream arch
- boot loader: grub, lilo
Archive coverage and Autobuilder support
- The port is currently at 99% up to date according to the buildd stats (95% cut off)
- The port has currently built 99% of the archive according to the buildd stats (90% cut off)
Archive cleanliness
The port builds from unmodified Debian source.
Autobuilders
The following machines run buildds for the port:
cyberhq - buildd logs checked by RyanMurray, adminned by RyanMurray
Waiver (for redundancy, since there isn't any): Most developers upload for i386; buildd downtime can be made up for with manual uploads for the few other packages
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:
- None