3352
Comment:
|
3419
|
Deletions are marked like this. | Additions are marked like this. |
Line 29: | Line 29: |
1. ... 2. ... |
1. DannFrazier 2. LaMontJones |
Line 39: | Line 39: |
1. foo: xx machines, yy users, personal workstations | 1. HP/OSLO: > 3 machines, > 200, shared login systems, mail, web, ... |
Line 43: | Line 43: |
Popcon indicates zz users of the architecture as at 2005/xx/yy. | Popcon indicates 45 users of the architecture as at 2007/10/22. |
Line 47: | Line 47: |
The installer is being maintained by ... and it's currently working effectively. Successful installation reports are available at: ... | The installer is being maintained by DannFrazier and it's currently working effectively. Successful installation reports are available at: ... |
Line 56: | Line 56: |
* kernel: ... * boot loader: ... |
* kernel: Tony Luck * boot loader: Jason Fleischli (elilo) |
Line 62: | Line 62: |
* 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 97% 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% 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 ia64 meets the [http://release.debian.org/lenny_arch_policy.html architecture recertification criteria for lenny].
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:
[http://www.hp.com/products1/servers/integrity/index.html HP]
[http://www.necsam.com/servers/products/series.cfm?series=4 NEC]
[http://www.supermicro.com/products/motherboard/Itanium/ ?SuperMicro]
and others
Developer machines
The following machines are available to developers:
merulo.debian.org - maintained by DSA (Matt Taggart and dann frazier local admins), connectivity via HP, porting machine.
merkel.debian.org - maintained by DSA (Matt Taggart and dann frazier local admins), connectivity via HP, general use machine (no chroots).
Port maintainers
The Debian port is maintained by the following developers, who actively work on architecture specific issues:
- ...
- ...
- ...
Users
The port is being actively used at the following sites:
HP/OSLO: > 3 machines, > 200, shared login systems, mail, web, ...
- bar: 1 machine, yyy users, development server
- ...
Popcon indicates 45 users of the architecture as at 2007/10/22.
Installer
The installer is being maintained by DannFrazier and it's currently working effectively. Successful installation reports are available at: ...
Upstream support
Upstream support is provided by:
- glibc: ...
- gcc: ...
- g++: ...
- kernel: Tony Luck
- boot loader: Jason Fleischli (elilo)
- ...
Archive coverage and Autobuilder support
The port is currently at 97% 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% of the archive according to [http://buildd.debian.org/stats/graph-week.png the buildd stats] (90% cut off)
Archive cleanliness
The port builds from unmodified Debian source.
Autobuilders
The following machines run buildds for the port:
- oldstable (oldstable-proposed-updates, oldstable-security)
- foo.debian.org - connectivity via ..., buildd logs checked by ..., adminned by ...
- stable (proposed-updates, stable-security)
- foo.debian.org - connectivity via ..., buildd logs checked by ..., adminned by ...
- testing (testing-proposed-updates, testing-security)
- foo.debian.org - connectivity via ..., buildd logs checked by ..., adminned by ...
- unstable
- foo.debian.org - connectivity via ..., buildd logs checked by ..., adminned by ...
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 stable release team have noted the following problems in supporting the architecture:
- None
The release team have noted the following problems in supporting the architecture:
- None