Status of the debian-maintainer-field spec ?

[Lucas Nussbaum]

Hi,

The topic of the debian-maintainer-field spec[0] was raised again today
on #debian-devel. This has been running for a long time, and I really
think that we should solve this for feisty, or it will look like Ubuntu
is not living up to its promises of good behaviour towards Debian.

[0] https://wiki.ubuntu.com/DebianMaintainerField

In the spec, a X-Original-Maintainer field is supposed to be used.  It
seems that this is a mistake, since the current implementation uses
Original-Maintainer (without X-).

The current status in feisty is:

Binary packages:
(A) Total packages: 21103
(B) Packages without Original-Maintainer: 8621 (41%)
(C) Packages without OM, but that's OK (@ubuntu.com): 1644 (8%)
(D) (B) - (C) = packages to fix: 6977 (33%)

Source packages (only the packages that were modified - version with
ubuntuX - needs to be changed according to [1]):
(A) Total packages: 12704
(B) Packages without Original-Maintainer: 12704 (100%)
(C) Packages without OM, but that's OK (not ubuntuX | @ubuntu.com): 10815 (85%)
(D) (B) - (C) = packages to fix: 1889 (14%)

Both cases could be quickly addressed using a script. Is it planned to
fix all those packages before the feisty release ?

The script I used to generate the data, as well as a list of binary packages
needed to be fixed sorted by maintainer, are available at [2].

[1] https://lists.ubuntu.com/archives/ubuntu-devel-announce/2007-January/000235.html
[2] http://people.debian.org/~lucas/debian-maintainer-field/

Thank you,
-- 
| Lucas Nussbaum
| lucas at lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lucas at nussbaum.fr             GPG: 1024D/023B3F4F |