* [gentoo-dev] irregular metdata.xml check
@ 2007-05-23 17:49 Thilo Bangert
2007-05-23 18:24 ` Chris Gianelloni
2007-05-23 21:19 ` Robin H. Johnson
0 siblings, 2 replies; 20+ messages in thread
From: Thilo Bangert @ 2007-05-23 17:49 UTC (permalink / raw
To: gentoo-dev
[-- Attachment #1: Type: text/plain, Size: 1688 bytes --]
Hi all,
welcome to the IMC - irregular metdata.xml check, issue 1.
As can be seen from the statistcis below, the herd tags have been fixed.
Thanks to those who have helped with the cleanup.
Whats next?
==========
The current policy in the devmanual demands a maintainer tag -
nevertheless half the tree is without it.
The policy should perhaps be changed to reflect the reality.
Also, many ebuilds put the herds email address as an additional
<maintainer>. This is simply redundant and unless complaints are raised,
all herd <maintainer> tags will be removed and replaced by the
appropriate <herd> tag instead. Work on this will start over the weekend.
Statistics
=================================
Total number of packages: 11701
metadata.xml missing 0
<herd> missing 0
<herd> empty 0
<herd> unknown 0
<herd>=no-herd 1880
<maintainer> missing 6616
<maintainer> retired 0
<maintainer> is a herd 1306
<maintainer> unknown 193
<maintainer>=maintainer-needed 438
Proxy maintainer without gentoo association 11
Unmaintained packages 596
The full metadata-check.log is available from:
http://dev.gentoo.org/~bangert/metadata-check.log
The script used to generate the log can be found here:
http://overlays.gentoo.org/dev/bangert/browser/scripts/check-metadata.rb
Feedback welcome.
Kind regards
Thilo
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: [gentoo-dev] irregular metdata.xml check
2007-05-23 17:49 [gentoo-dev] irregular metdata.xml check Thilo Bangert
@ 2007-05-23 18:24 ` Chris Gianelloni
2007-05-23 18:34 ` [gentoo-dev] " Markus Ullmann
2007-05-23 19:01 ` [gentoo-dev] " Timothy Redaelli
2007-05-23 21:19 ` Robin H. Johnson
1 sibling, 2 replies; 20+ messages in thread
From: Chris Gianelloni @ 2007-05-23 18:24 UTC (permalink / raw
To: gentoo-dev
[-- Attachment #1: Type: text/plain, Size: 1016 bytes --]
On Wed, 2007-05-23 at 19:49 +0200, Thilo Bangert wrote:
> Also, many ebuilds put the herds email address as an additional
> <maintainer>. This is simply redundant and unless complaints are raised,
> all herd <maintainer> tags will be removed and replaced by the
> appropriate <herd> tag instead. Work on this will start over the weekend.
Remember that some do this legitimately. If the herd is, for example,
"portage" but the email/bugzilla address is dev-portage@gentoo.org then
I think it is a good idea to leave the maintainer tag alone. Remember
that this is an example and isn't what is actually in the tree. I just
used it as a simple example. The point is that in cases where the herd
name doesn't equal the email address used for that herd, the maintainer
tag should probably be filled in with the proper email address.
--
Chris Gianelloni
Release Engineering Strategic Lead
Alpha/AMD64/x86 Architecture Teams
Games Developer/Council Member/Foundation Trustee
Gentoo Foundation
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 20+ messages in thread
* [gentoo-dev] Re: irregular metdata.xml check
2007-05-23 18:24 ` Chris Gianelloni
@ 2007-05-23 18:34 ` Markus Ullmann
2007-05-23 19:01 ` [gentoo-dev] " Timothy Redaelli
1 sibling, 0 replies; 20+ messages in thread
From: Markus Ullmann @ 2007-05-23 18:34 UTC (permalink / raw
To: gentoo-dev
Chris Gianelloni schrieb:
> The point is that in cases where the herd
> name doesn't equal the email address used for that herd, the maintainer
> tag should probably be filled in with the proper email address.
I think we have herds.xml for a good reason ;)
-Jokey
--
gentoo-dev@gentoo.org mailing list
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: [gentoo-dev] irregular metdata.xml check
2007-05-23 18:24 ` Chris Gianelloni
2007-05-23 18:34 ` [gentoo-dev] " Markus Ullmann
@ 2007-05-23 19:01 ` Timothy Redaelli
1 sibling, 0 replies; 20+ messages in thread
From: Timothy Redaelli @ 2007-05-23 19:01 UTC (permalink / raw
To: gentoo-dev
Alle mercoledì 23 maggio 2007, Chris Gianelloni ha scritto:
> On Wed, 2007-05-23 at 19:49 +0200, Thilo Bangert wrote:
> > Also, many ebuilds put the herds email address as an additional
> > <maintainer>. This is simply redundant and unless complaints are raised,
> > all herd <maintainer> tags will be removed and replaced by the
> > appropriate <herd> tag instead. Work on this will start over the weekend.
>
> Remember that some do this legitimately. If the herd is, for example,
> "portage" but the email/bugzilla address is dev-portage@gentoo.org then
> I think it is a good idea to leave the maintainer tag alone. Remember
> that this is an example and isn't what is actually in the tree. I just
> used it as a simple example. The point is that in cases where the herd
> name doesn't equal the email address used for that herd, the maintainer
> tag should probably be filled in with the proper email address.
http://thread.gmane.org/gmane.linux.gentoo.devel/48485
--
Timothy `Drizzt` Redaelli - http://dev.gentoo.org/~drizzt/
FreeSBIE Developer, Gentoo Developer, GUFI Staff
There are two major products that come out of Berkeley: LSD and UNIX.
We don't believe this to be a coincidence. -- Jeremy S. Anderson
--
gentoo-dev@gentoo.org mailing list
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: [gentoo-dev] irregular metdata.xml check
2007-05-23 17:49 [gentoo-dev] irregular metdata.xml check Thilo Bangert
2007-05-23 18:24 ` Chris Gianelloni
@ 2007-05-23 21:19 ` Robin H. Johnson
2007-05-27 12:17 ` Thilo Bangert
1 sibling, 1 reply; 20+ messages in thread
From: Robin H. Johnson @ 2007-05-23 21:19 UTC (permalink / raw
To: gentoo-dev
[-- Attachment #1: Type: text/plain, Size: 754 bytes --]
On Wed, May 23, 2007 at 07:49:43PM +0200, Thilo Bangert wrote:
> Also, many ebuilds put the herds email address as an additional
> <maintainer>. This is simply redundant and unless complaints are raised,
> all herd <maintainer> tags will be removed and replaced by the
> appropriate <herd> tag instead. Work on this will start over the weekend.
No.
See the thread about automatic assignment for more about this.
More importantly, once the automatic stuff goes into play, the existence
of the herd tag will only matter on metadata that does not have any
other maintainer.
--
Robin Hugh Johnson
Gentoo Linux Developer & Council Member
E-Mail : robbat2@gentoo.org
GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85
[-- Attachment #2: Type: application/pgp-signature, Size: 321 bytes --]
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: [gentoo-dev] irregular metdata.xml check
2007-05-23 21:19 ` Robin H. Johnson
@ 2007-05-27 12:17 ` Thilo Bangert
2007-05-27 14:30 ` Radoslaw Stachowiak
2007-06-10 20:58 ` [gentoo-dev] " Ryan Hill
0 siblings, 2 replies; 20+ messages in thread
From: Thilo Bangert @ 2007-05-27 12:17 UTC (permalink / raw
To: gentoo-dev
[-- Attachment #1: Type: text/plain, Size: 1709 bytes --]
"Robin H. Johnson" <robbat2@gentoo.org> said:
> On Wed, May 23, 2007 at 07:49:43PM +0200, Thilo Bangert wrote:
> > Also, many ebuilds put the herds email address as an additional
> > <maintainer>. This is simply redundant and unless complaints are
> > raised, all herd <maintainer> tags will be removed and replaced by
> > the appropriate <herd> tag instead. Work on this will start over the
> > weekend.
>
> No.
>
> See the thread about automatic assignment for more about this.
> More importantly, once the automatic stuff goes into play, the
> existence of the herd tag will only matter on metadata that does not
> have any other maintainer.
sorry - to have missed this earlier.
from your proposal:
>Case 2 - Metadata contains a single maintainer
>----------------------------------------------
> The herd field is not used.
so, you want to ignore the herd tag, as soon as there is a single
maintainer tag? why?
we have <herd> on every single package in the tree (well ~1900 packages
with <herd>no-herd</herd>). my guess is that most of the roughly 4500
packages that currently have a <herd> and a <maintainer> which is not a
<herd>, will need to adjust their metadata to reflect the situation where
the maintainer should get the bug asssigned and the herd gets CC'd...
IMHO the herd should always get an email on bugs with packages belonging
to the herd... if this is not the case, what is the purpose of the herd?
or asked differently: what can the herd in <maintainer> give you that the
<herd> can't?
other than that i (still) agree with the overall proposal. lets just make
sure to codify the policy which has been agreed upon...
regards
Thilo
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: [gentoo-dev] irregular metdata.xml check
2007-05-27 12:17 ` Thilo Bangert
@ 2007-05-27 14:30 ` Radoslaw Stachowiak
2007-06-10 20:58 ` [gentoo-dev] " Ryan Hill
1 sibling, 0 replies; 20+ messages in thread
From: Radoslaw Stachowiak @ 2007-05-27 14:30 UTC (permalink / raw
To: gentoo-dev
On 27/05/07, Thilo Bangert <bangert@gentoo.org> wrote:
[...and many others...]
What I deeply miss from gentoo-dev mailing list is lack of summary at
end of discussions. Current situation is that at the end of such
disputes very often (of course not always :) is still unclear if:
* decision has been made (and what it is)
* previous approach has been changed (or it hasn't, with pointer (URL) to it)
* documents were updated (to address change or to simply provide
better wording) w/ URLs
* nothing has been changed due to X, and next approach will be in X months.
It's even more difficult to grasp outcome for non native english speakers.
Solution I propose is, that author of the first post in a thread, who
started the discussion (if there was some discusion), should at end of
it (let's assume it's 3 days after last mail) write summary with those
4 points I outlined above. Simple and will help greatly to track later
decisions/changes, or postponed items.
--
radoslaw.
--
gentoo-dev@gentoo.org mailing list
^ permalink raw reply [flat|nested] 20+ messages in thread
* [gentoo-dev] Re: irregular metdata.xml check
2007-05-27 12:17 ` Thilo Bangert
2007-05-27 14:30 ` Radoslaw Stachowiak
@ 2007-06-10 20:58 ` Ryan Hill
2007-06-10 22:20 ` Robin H. Johnson
1 sibling, 1 reply; 20+ messages in thread
From: Ryan Hill @ 2007-06-10 20:58 UTC (permalink / raw
To: gentoo-dev
Thilo Bangert wrote:
> "Robin H. Johnson" <robbat2@gentoo.org> said:
>> See the thread about automatic assignment for more about this.
>> More importantly, once the automatic stuff goes into play, the
>> existence of the herd tag will only matter on metadata that does not
>> have any other maintainer.
>
> sorry - to have missed this earlier.
> from your proposal:
>> Case 2 - Metadata contains a single maintainer
>> ----------------------------------------------
>> The herd field is not used.
>
> so, you want to ignore the herd tag, as soon as there is a single
> maintainer tag? why?
>
> we have <herd> on every single package in the tree (well ~1900 packages
> with <herd>no-herd</herd>). my guess is that most of the roughly 4500
> packages that currently have a <herd> and a <maintainer> which is not a
> <herd>, will need to adjust their metadata to reflect the situation where
> the maintainer should get the bug asssigned and the herd gets CC'd...
>
> IMHO the herd should always get an email on bugs with packages belonging
> to the herd... if this is not the case, what is the purpose of the herd?
>
> or asked differently: what can the herd in <maintainer> give you that the
> <herd> can't?
I agree here, we have many packages that are assigned to a herd, with a
certain member of that herd listed as maintainer. For example I'll use
freetype since I've been working on it today:
dirtyepic@tycho /usr/portage/media-libs/freetype $ cat metadata.xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
<pkgmetadata>
<herd>fonts</herd>
<maintainer>
<email>foser@gentoo.org</email>
</maintainer>
</pkgmetadata>
In this case, a bug should be assigned to foser and fonts@gentoo.org
should be CCed. Freetype has frequent security bugs and foser is
usually not present to deal with them. If the herd wasn't CC'd there'd
be trouble.
Another case is where we have a maintainer who isn't a member of the
herd, like dejavu for example.
dirtyepic@tycho /usr/portage/media-fonts/dejavu $ cat metadata.xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
<pkgmetadata>
<herd>fonts</herd>
<maintainer>
<email>pva@gentoo.org</email>
<name>Peter Volkov</name>
</maintainer>
<longdescription>
The DejaVu fonts are a font family based on the Vera Fonts release 1.10. Its
purpose is to provide a wider range of characters while maintaining the
original
look and feel through the process of collaborative development. Available
families (Sans = sans serif, Mono = monospaced): DejaVu Sans, DejaVu
Sans Mono,
DejaVu Sans Condensed (experimental), DejaVu Serif, DejaVu Serif Condensed
</longdescription>
</pkgmetadata>
We would want bugs filed against dejavu to be CC'd to the fonts herd, in
case pva isn't present or it's something more generally font-related.
No matter what, if the herd tag is not "no-herd", it should be CC'd on
all bugs.
--
dirtyepic salesman said this vacuum's guaranteed
gentoo org it could suck an ancient virus from the sea
9B81 6C9F E791 83BB 3AB3 5B2D E625 A073 8379 37E8 (0x837937E8)
--
gentoo-dev@gentoo.org mailing list
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: [gentoo-dev] Re: irregular metdata.xml check
2007-06-10 20:58 ` [gentoo-dev] " Ryan Hill
@ 2007-06-10 22:20 ` Robin H. Johnson
0 siblings, 0 replies; 20+ messages in thread
From: Robin H. Johnson @ 2007-06-10 22:20 UTC (permalink / raw
To: gentoo-dev
[-- Attachment #1: Type: text/plain, Size: 672 bytes --]
On Sun, Jun 10, 2007 at 02:58:27PM -0600, Ryan Hill wrote:
> I agree here, we have many packages that are assigned to a herd, with a
> certain member of that herd listed as maintainer. For example I'll use
> freetype since I've been working on it today:
....
> No matter what, if the herd tag is not "no-herd", it should be CC'd on
> all bugs.
Please see my latest email about automatic processing.
I did agree with bangert's points, but I just hadn't gotten to revising
my original proposal.
--
Robin Hugh Johnson
Gentoo Linux Developer & Council Member
E-Mail : robbat2@gentoo.org
GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85
[-- Attachment #2: Type: application/pgp-signature, Size: 321 bytes --]
^ permalink raw reply [flat|nested] 20+ messages in thread
* [gentoo-dev] irregular metdata.xml check
@ 2007-06-10 23:41 Thilo Bangert
2007-06-11 5:55 ` Rémi Cardona
` (2 more replies)
0 siblings, 3 replies; 20+ messages in thread
From: Thilo Bangert @ 2007-06-10 23:41 UTC (permalink / raw
To: gentoo-dev
[-- Attachment #1: Type: text/plain, Size: 2039 bytes --]
Hi all,
welcome to the second issue of the irregular metadata.xml check.
Did you know that only 16% of all packages in the tree do not belong to
any herd (ie. <herd>no-herd</herd>). Nevertheless, as no-herd is not a
nice place to be, perhaps your herd can adopt a package or two. If you
get really lucky you even get a dev with the deal - for free!
Herds with no email
===================
As robbat2 points out, in order to allow for automatic bug assignment all
herds need to have an email address. The following herds do not have an
email address specified in herds.xml.
herd without email: comm-fax
herd without email: dev-tools
herd without email: haskell
herd without email: common-lisp
herd without email: secure-tunneling
herd without email: ia64-kernel
herd without email: middle-east
herd without email: arm
herd without email: lang-misc
herd without email: s390
herd without email: sh
Statistics
==============================================
Total number of packages: 11684
metadata.xml missing 0
<herd> missing 2
<herd> empty 0
<herd> unknown 0
<herd>=no-herd 1887
<maintainer> missing 6611
<maintainer> retired 0
<maintainer> is a herd 1300
<maintainer> unknown 201
<maintainer>=maintainer-needed 438
Proxy maintainer without gentoo association 13
Unmaintained packages 602
As always, the full metadata-check.log is available from [1].
The script used to generate the log can be found at [2].
Feedback welcome.
Kind regards
Thilo
[1] Full metadata-check.log
http://dev.gentoo.org/~bangert/metadata-check.log
[2] Metadata checking script.
http://overlays.gentoo.org/dev/bangert/browser/scripts/check-metadata.rb
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: [gentoo-dev] irregular metdata.xml check
2007-06-10 23:41 [gentoo-dev] " Thilo Bangert
@ 2007-06-11 5:55 ` Rémi Cardona
2007-06-11 8:20 ` Marijn Schouten (hkBst)
2007-06-11 16:34 ` Harald van Dijk
2 siblings, 0 replies; 20+ messages in thread
From: Rémi Cardona @ 2007-06-11 5:55 UTC (permalink / raw
To: gentoo-dev
Thilo Bangert wrote:
[great stuff here]
Thanks for your useful work Thilo :)
/me tips hat
Rémi
--
gentoo-dev@gentoo.org mailing list
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: [gentoo-dev] irregular metdata.xml check
2007-06-10 23:41 [gentoo-dev] " Thilo Bangert
2007-06-11 5:55 ` Rémi Cardona
@ 2007-06-11 8:20 ` Marijn Schouten (hkBst)
2007-06-11 8:26 ` Petteri Räty
2007-06-11 16:34 ` Harald van Dijk
2 siblings, 1 reply; 20+ messages in thread
From: Marijn Schouten (hkBst) @ 2007-06-11 8:20 UTC (permalink / raw
To: gentoo-dev
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Thilo Bangert wrote:
> <maintainer> is a herd 1300
These seem intentional. Is there anything wrong with it?
Marijn
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGbQXqp/VmCx0OL2wRAqdJAJ9SX1NMUcSm1f35cx596xTD6W72SQCeKB8g
CG85MGBmgYaq3hwoFDjEHmI=
=IITB
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: [gentoo-dev] irregular metdata.xml check
2007-06-11 8:20 ` Marijn Schouten (hkBst)
@ 2007-06-11 8:26 ` Petteri Räty
2007-06-11 9:07 ` Robin H. Johnson
0 siblings, 1 reply; 20+ messages in thread
From: Petteri Räty @ 2007-06-11 8:26 UTC (permalink / raw
To: gentoo-dev
[-- Attachment #1: Type: text/plain, Size: 266 bytes --]
Marijn Schouten (hkBst) kirjoitti:
> Thilo Bangert wrote:
>> <maintainer> is a herd 1300
>
> These seem intentional. Is there anything wrong with it?
>
> Marijn
Yes. You use the <herd> element to mark herds.
Regards,
Petteri
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: [gentoo-dev] irregular metdata.xml check
2007-06-11 8:26 ` Petteri Räty
@ 2007-06-11 9:07 ` Robin H. Johnson
0 siblings, 0 replies; 20+ messages in thread
From: Robin H. Johnson @ 2007-06-11 9:07 UTC (permalink / raw
To: gentoo-dev
[-- Attachment #1: Type: text/plain, Size: 621 bytes --]
On Mon, Jun 11, 2007 at 11:26:27AM +0300, Petteri R??ty wrote:
> Marijn Schouten (hkBst) kirjoitti:
> > Thilo Bangert wrote:
> >> <maintainer> is a herd 1300
> > These seem intentional. Is there anything wrong with it?
> Yes. You use the <herd> element to mark herds.
I do see a valid usage case for a herd to be in the maintainers with a
<role> element, but certainly those that add no value should be moved to
herd only.
--
Robin Hugh Johnson
Gentoo Linux Developer & Council Member
E-Mail : robbat2@gentoo.org
GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85
[-- Attachment #2: Type: application/pgp-signature, Size: 321 bytes --]
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: [gentoo-dev] irregular metdata.xml check
2007-06-10 23:41 [gentoo-dev] " Thilo Bangert
2007-06-11 5:55 ` Rémi Cardona
2007-06-11 8:20 ` Marijn Schouten (hkBst)
@ 2007-06-11 16:34 ` Harald van Dijk
2 siblings, 0 replies; 20+ messages in thread
From: Harald van Dijk @ 2007-06-11 16:34 UTC (permalink / raw
To: gentoo-dev
On Mon, Jun 11, 2007 at 01:41:30AM +0200, Thilo Bangert wrote:
> Herds with no email
> ===================
>
> As robbat2 points out, in order to allow for automatic bug assignment all
> herds need to have an email address. The following herds do not have an
> email address specified in herds.xml.
>
> herd without email: lang-misc
Fixed now.
--
gentoo-dev@gentoo.org mailing list
^ permalink raw reply [flat|nested] 20+ messages in thread
* [gentoo-dev] irregular metdata.xml check
@ 2009-12-07 11:56 Thilo Bangert
2009-12-07 12:13 ` Ulrich Mueller
2009-12-07 17:04 ` Hans de Graaff
0 siblings, 2 replies; 20+ messages in thread
From: Thilo Bangert @ 2009-12-07 11:56 UTC (permalink / raw
To: gentoo-dev
[-- Attachment #1: Type: text/plain, Size: 2812 bytes --]
Welcome to this years edition of the metadata check.
Todays fingerpointing
herd without email: secure-tunneling
herd without email: middle-east
app-admin/eselect-audicle <herd> empty
app-admin/eselect-chuck <herd> empty
app-admin/eselect-miniaudicle <herd> empty
app-admin/eselect-sndpeek <herd> empty
net-im/minbif <herd> empty
sys-kernel/dracut <herd> empty
x11-libs/libvdpau <herd> empty
x11-misc/vdpauinfo <herd> empty
virtual/perl-Filter <herd> empty
virtual/perl-i18n-langtags <herd> empty
virtual/perl-Package-Constants <herd> empty
virtual/perl-parent <herd> empty
virtual/perl-Parse-CPAN-Meta <herd> empty
app-office/homebank <herd> missing
dev-libs/faxpp <herd> missing
dev-libs/librelp <herd> missing
dev-libs/ossp-uuid <herd> missing
dev-util/cucumber <herd> missing
dev-util/hg-git <herd> missing
games-rpg/sacred-gold <herd> missing
gnome-extra/gnome-color-chooser <herd> missing
media-gfx/engauge <herd> missing
media-gfx/greycstoration <herd> missing
media-plugins/gimp-greycstoration <herd> missing
net-dialup/dgcmodem <herd> missing
net-irc/irssi-xmpp <herd> missing
net-libs/udns <herd> missing
net-misc/openswan <herd> missing
sys-apps/edac-utils <herd> missing
Statistics
==================================================================
Total number of packages: 13623
metadata.xml missing 0
<herd> missing 16
<herd> empty 13
<herd> unknown 0
<herd>=no-herd 1999
<maintainer> missing 8383
<maintainer> retired 0
<maintainer> is a herd 1187
<maintainer> unknown 203
<maintainer>=maintainer-needed 715
Proxy maintainer without gentoo association 10
Unmaintained packages 731
You will find the complete log at [1].
The script that generated above logfile can be found at [2].
As usual, feedback is highly appreciated.
Warm regards
Thilo
[1] Full metadata-check.log
http://dev.gentoo.org/~bangert/metadata-check.log
[2] Metadata checking script.
http://overlays.gentoo.org/dev/bangert/browser/scripts/check-metadata.rb
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: [gentoo-dev] irregular metdata.xml check
2009-12-07 11:56 Thilo Bangert
@ 2009-12-07 12:13 ` Ulrich Mueller
2009-12-07 13:20 ` Thilo Bangert
2009-12-07 17:04 ` Hans de Graaff
1 sibling, 1 reply; 20+ messages in thread
From: Ulrich Mueller @ 2009-12-07 12:13 UTC (permalink / raw
To: gentoo-dev
>>>>> On Mon, 7 Dec 2009, Thilo Bangert wrote:
> Welcome to this years edition of the metadata check.
> [...]
> You will find the complete log at [1].
Hmm, eselect is not known:
| unknown maintainer: eselect@gentoo.org
But it's in good company:
| unknown maintainer: catalyst@gentoo.org
| unknown maintainer: dev-portage@gentoo.org
| unknown maintainer: genkernel@gentoo.org
| unknown maintainer: gnap@gentoo.org
| unknown maintainer: portage-utils@gentoo.org
| unknown maintainer: sandbox@gentoo.org
> As usual, feedback is highly appreciated.
Could you make your script recognise Gentoo hosted projects as valid
maintainers?
Ulrich
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: [gentoo-dev] irregular metdata.xml check
2009-12-07 12:13 ` Ulrich Mueller
@ 2009-12-07 13:20 ` Thilo Bangert
0 siblings, 0 replies; 20+ messages in thread
From: Thilo Bangert @ 2009-12-07 13:20 UTC (permalink / raw
To: gentoo-dev
[-- Attachment #1: Type: Text/Plain, Size: 851 bytes --]
Ulrich Mueller <ulm@gentoo.org> said:
> >>>>> On Mon, 7 Dec 2009, Thilo Bangert wrote:
> >
> > Welcome to this years edition of the metadata check.
> > [...]
> >
> > You will find the complete log at [1].
>
> Hmm, eselect is not known:
> | unknown maintainer: eselect@gentoo.org
>
> But it's in good company:
> | unknown maintainer: catalyst@gentoo.org
> | unknown maintainer: dev-portage@gentoo.org
> | unknown maintainer: genkernel@gentoo.org
> | unknown maintainer: gnap@gentoo.org
> | unknown maintainer: portage-utils@gentoo.org
> | unknown maintainer: sandbox@gentoo.org
> |
> > As usual, feedback is highly appreciated.
>
> Could you make your script recognise Gentoo hosted projects as valid
> maintainers?
are these availabe somewhere? AFAICT we dont have them systematically
available...
>
> Ulrich
>
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: [gentoo-dev] irregular metdata.xml check
2009-12-07 11:56 Thilo Bangert
2009-12-07 12:13 ` Ulrich Mueller
@ 2009-12-07 17:04 ` Hans de Graaff
2009-12-07 20:20 ` Thilo Bangert
1 sibling, 1 reply; 20+ messages in thread
From: Hans de Graaff @ 2009-12-07 17:04 UTC (permalink / raw
To: gentoo-dev
[-- Attachment #1: Type: text/plain, Size: 456 bytes --]
On Mon, 2009-12-07 at 12:56 +0100, Thilo Bangert wrote:
> Welcome to this years edition of the metadata check.
> dev-util/cucumber <herd> missing
Fixed, but this is really a bug in metadata.dtd, which specifies
<!ELEMENT pkgmetadata ( (herd|maintainer|longdescription|use|
upstream)* )>
That should probably be:
<!ELEMENT pkgmetadata ( (herd)+ (maintainer|longdescription|use|
upstream)* )>
Kind regards,
Hans
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: [gentoo-dev] irregular metdata.xml check
2009-12-07 17:04 ` Hans de Graaff
@ 2009-12-07 20:20 ` Thilo Bangert
0 siblings, 0 replies; 20+ messages in thread
From: Thilo Bangert @ 2009-12-07 20:20 UTC (permalink / raw
To: gentoo-dev
[-- Attachment #1: Type: Text/Plain, Size: 598 bytes --]
Hans de Graaff <graaff@gentoo.org> said:
> On Mon, 2009-12-07 at 12:56 +0100, Thilo Bangert wrote:
> > Welcome to this years edition of the metadata check.
> >
> > dev-util/cucumber <herd> missing
>
> Fixed, but this is really a bug in metadata.dtd, which specifies
> <!ELEMENT pkgmetadata ( (herd|maintainer|longdescription|use|
> upstream)* )>
>
> That should probably be:
>
> <!ELEMENT pkgmetadata ( (herd)+ (maintainer|longdescription|use|
> upstream)* )>
>
indeed:
http://bugs.gentoo.org/show_bug.cgi?id=279206
> Kind regards,
>
> Hans
>
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
^ permalink raw reply [flat|nested] 20+ messages in thread
end of thread, other threads:[~2009-12-07 20:22 UTC | newest]
Thread overview: 20+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-05-23 17:49 [gentoo-dev] irregular metdata.xml check Thilo Bangert
2007-05-23 18:24 ` Chris Gianelloni
2007-05-23 18:34 ` [gentoo-dev] " Markus Ullmann
2007-05-23 19:01 ` [gentoo-dev] " Timothy Redaelli
2007-05-23 21:19 ` Robin H. Johnson
2007-05-27 12:17 ` Thilo Bangert
2007-05-27 14:30 ` Radoslaw Stachowiak
2007-06-10 20:58 ` [gentoo-dev] " Ryan Hill
2007-06-10 22:20 ` Robin H. Johnson
-- strict thread matches above, loose matches on Subject: below --
2007-06-10 23:41 [gentoo-dev] " Thilo Bangert
2007-06-11 5:55 ` Rémi Cardona
2007-06-11 8:20 ` Marijn Schouten (hkBst)
2007-06-11 8:26 ` Petteri Räty
2007-06-11 9:07 ` Robin H. Johnson
2007-06-11 16:34 ` Harald van Dijk
2009-12-07 11:56 Thilo Bangert
2009-12-07 12:13 ` Ulrich Mueller
2009-12-07 13:20 ` Thilo Bangert
2009-12-07 17:04 ` Hans de Graaff
2009-12-07 20:20 ` Thilo Bangert
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox