Re: [gentoo-dev] irregular metdata.xml check
Hans de Graaff said: > On Mon, 2009-12-07 at 12:56 +0100, Thilo Bangert wrote: > > Welcome to this years edition of the metadata check. > > > > dev-util/cucumbermissing > > Fixed, but this is really a bug in metadata.dtd, which specifies > upstream)* )> > > That should probably be: > > upstream)* )> > indeed: http://bugs.gentoo.org/show_bug.cgi?id=279206 > Kind regards, > > Hans > signature.asc Description: This is a digitally signed message part.
Re: [gentoo-dev] irregular metdata.xml check
On Mon, 2009-12-07 at 12:56 +0100, Thilo Bangert wrote: > Welcome to this years edition of the metadata check. > dev-util/cucumbermissing Fixed, but this is really a bug in metadata.dtd, which specifies That should probably be: Kind regards, Hans signature.asc Description: This is a digitally signed message part
Re: [gentoo-dev] irregular metdata.xml check
Ulrich Mueller 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: esel...@gentoo.org > > But it's in good company: > | unknown maintainer: catal...@gentoo.org > | unknown maintainer: dev-port...@gentoo.org > | unknown maintainer: genker...@gentoo.org > | unknown maintainer: g...@gentoo.org > | unknown maintainer: portage-ut...@gentoo.org > | unknown maintainer: sand...@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 > signature.asc Description: This is a digitally signed message part.
Re: [gentoo-dev] irregular metdata.xml check
> 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: esel...@gentoo.org But it's in good company: | unknown maintainer: catal...@gentoo.org | unknown maintainer: dev-port...@gentoo.org | unknown maintainer: genker...@gentoo.org | unknown maintainer: g...@gentoo.org | unknown maintainer: portage-ut...@gentoo.org | unknown maintainer: sand...@gentoo.org > As usual, feedback is highly appreciated. Could you make your script recognise Gentoo hosted projects as valid maintainers? Ulrich
[gentoo-dev] irregular metdata.xml check
Welcome to this years edition of the metadata check. Todays fingerpointing herd without email: secure-tunneling herd without email: middle-east app-admin/eselect-audicleempty app-admin/eselect-chuck empty app-admin/eselect-miniaudicleempty app-admin/eselect-sndpeekempty net-im/minbifempty sys-kernel/dracutempty x11-libs/libvdpauempty x11-misc/vdpauinfo empty virtual/perl-Filter empty virtual/perl-i18n-langtags empty virtual/perl-Package-Constants empty virtual/perl-parent empty virtual/perl-Parse-CPAN-Meta empty app-office/homebank missing dev-libs/faxpp missing dev-libs/librelp missing dev-libs/ossp-uuid missing dev-util/cucumbermissing dev-util/hg-git missing games-rpg/sacred-goldmissing gnome-extra/gnome-color-chooser missing media-gfx/engaugemissing media-gfx/greycstoration missing media-plugins/gimp-greycstorationmissing net-dialup/dgcmodem missing net-irc/irssi-xmpp missing net-libs/udnsmissing net-misc/openswanmissing sys-apps/edac-utils missing Statistics == Total number of packages:13623 metadata.xml missing 0 missing 16 empty13 unknown 0 =no-herd1999 missing 8383 retired 0 is a herd1187 unknown 203 =maintainer-needed 715 Proxy maintainer without gentoo association10 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 signature.asc Description: This is a digitally signed message part.
Re: [gentoo-dev] irregular metdata.xml check - 3rd edition
On Wed, Feb 13, 2008 at 09:30:14AM +0100, Thilo Bangert wrote: > > 2. Check that metadata with a proxy maint also has a non-retired Gentoo > > person listed. > 'Proxy maintainer without gentoo association' means 'there is neither a > herd nor a gentoo maintainer listed'. you want to require a maintainer? a > lot more ebuilds will fail this check... > > one may actually want to restrict that even further, and require both a > herd and a maintainer, as to define a pool of backup people in case the > gentoo maintainer retires. I actually ran into this when jakub asked me to check some email addresses that were in metadata.xml for bugzilla validity. Originally, the one package was proxy maintained, having the external and two Gentoo devs, with no-herd. The devs then retired, but the external contributer was still interested, just lacking a contact. -- Robin Hugh Johnson Gentoo Linux Developer & Infra Guy E-Mail : [EMAIL PROTECTED] GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85 pgp6fAkxCY5mZ.pgp Description: PGP signature
Re: [gentoo-dev] irregular metdata.xml check - 3rd edition
"Robin H. Johnson" <[EMAIL PROTECTED]> said: > On Tue, Feb 12, 2008 at 10:01:16PM +0100, Thilo Bangert wrote: > > Noteworthy errors > > === > > herd without email: comm-fax > > Proxy maintainer without gentoo association 15 > > Two specific feature requests: > 1. Check that every email address has a bugzilla account. i'll look into it. a hashed list of gentoo.org bugzilla accounts would definitivly help! just the query is a good start though - i suppose (lets try that first). the script runs a couple of minutes anyway - if that doubles, triples or quadruples its not a problem... > 2. Check that metadata with a proxy maint also has a non-retired Gentoo > person listed. 'Proxy maintainer without gentoo association' means 'there is neither a herd nor a gentoo maintainer listed'. you want to require a maintainer? a lot more ebuilds will fail this check... one may actually want to restrict that even further, and require both a herd and a maintainer, as to define a pool of backup people in case the gentoo maintainer retires. thanks! kind regards Thilo signature.asc Description: This is a digitally signed message part.
Re: [gentoo-dev] irregular metdata.xml check - 3rd edition
On Tue, Feb 12, 2008 at 10:21:19PM -0800, Alec Warner wrote: > On 2/12/08, Robin H. Johnson <[EMAIL PROTECTED]> wrote: > > On Tue, Feb 12, 2008 at 10:01:16PM +0100, Thilo Bangert wrote: > > > Noteworthy errors > > > === > > > herd without email: comm-fax > > > Proxy maintainer without gentoo association 15 > > Two specific feature requests: > > 1. Check that every email address has a bugzilla account. > How is he going to do this without db access? There's a creative bugzilla query for it, but you have to test each one individually. For mass-checking, I'd offer sets of the email addresses, hashed, so that you have to know an address to check it against a static list. -- Robin Hugh Johnson Gentoo Linux Developer & Infra Guy E-Mail : [EMAIL PROTECTED] GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85 pgpfRPUYysADs.pgp Description: PGP signature
Re: [gentoo-dev] irregular metdata.xml check - 3rd edition
On 2/12/08, Robin H. Johnson <[EMAIL PROTECTED]> wrote: > On Tue, Feb 12, 2008 at 10:01:16PM +0100, Thilo Bangert wrote: > > Noteworthy errors > > === > > herd without email: comm-fax > > Proxy maintainer without gentoo association 15 > Two specific feature requests: > 1. Check that every email address has a bugzilla account. How is he going to do this without db access? > 2. Check that metadata with a proxy maint also has a non-retired Gentoo > person listed. > > -- > Robin Hugh Johnson > Gentoo Linux Developer & Infra Guy > E-Mail : [EMAIL PROTECTED] > GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85 > > -- gentoo-dev@lists.gentoo.org mailing list
Re: [gentoo-dev] irregular metdata.xml check - 3rd edition
On Tue, Feb 12, 2008 at 10:01:16PM +0100, Thilo Bangert wrote: > Noteworthy errors > === > herd without email: comm-fax > Proxy maintainer without gentoo association 15 Two specific feature requests: 1. Check that every email address has a bugzilla account. 2. Check that metadata with a proxy maint also has a non-retired Gentoo person listed. -- Robin Hugh Johnson Gentoo Linux Developer & Infra Guy E-Mail : [EMAIL PROTECTED] GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85 pgpTVW4W8jtXT.pgp Description: PGP signature
Re: [gentoo-dev] irregular metdata.xml check - 3rd edition
Le mardi 12 février 2008 à 22:01 +0100, Thilo Bangert a écrit : > Welcome to the third edition of the irregular metadata.xml check. [snip] > net-wireless/gnome-bluetoothretired maintainer removed liquidx and added gnome to the list of herds. [snip] -- Gilles Dartiguelongue <[EMAIL PROTECTED]> Gentoo signature.asc Description: Ceci est une partie de message numériquement signée
[gentoo-dev] irregular metdata.xml check - 3rd edition
Welcome to the third edition of the irregular metadata.xml check. Noteworthy errors === 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: s390 herd without email: sh net-misc/netcomics-cvs retired maintainer net-wireless/gnome-bluetoothretired maintainer sys-devel/distcc-config retired maintainer x11-plugins/gkrellm-countdown retired maintainer dev-util/crossvc empty app-emulation/virtinst missing dev-dotnet/dbus-glib-sharp missing dev-dotnet/dbus-sharpmissing dev-libs/dclog missing dev-util/cmt missing dev-util/osdtmissing mail-filter/dovecot-antispam missing mail-filter/dovecot-dspammissing media-libs/capseomissing media-libs/libcapturymissing media-video/captury missing media-video/undvdmissing net-fs/wdfs missing net-irc/mistbot missing net-misc/goog-sitemapgen missing net-misc/ng-utilsmissing net-misc/s3cmd missing sys-auth/nsvsmissing sys-fs/encfs missing sys-fs/flickrfs missing sys-fs/fuse-python missing sys-fs/python-fuse missing sys-fs/zfs-fuse missing sys-kernel/kerneloopsmissing Here are the stats summarising the current state of metadata in the tree. Statistics == Total number of packages:12410 metadata.xml missing 0 missing 24 empty 1 unknown 0 =no-herd1929 missing 7287 retired 4 is a herd1285 unknown 256 =maintainer-needed 556 Proxy maintainer without gentoo association 15 Unmaintained packages 717 You will find the complete log at [1]. The script that generated above logfile can be found at [2]. As always, feedback is higly 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 signature.asc Description: This is a digitally signed message part.
Re: [gentoo-dev] irregular metdata.xml check
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. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-dev] irregular metdata.xml check
On Mon, Jun 11, 2007 at 11:26:27AM +0300, Petteri R??ty wrote: > Marijn Schouten (hkBst) kirjoitti: > > Thilo Bangert wrote: > >> is a herd1300 > > These seem intentional. Is there anything wrong with it? > Yes. You use the element to mark herds. I do see a valid usage case for a herd to be in the maintainers with a element, but certainly those that add no value should be moved to herd only. -- Robin Hugh Johnson Gentoo Linux Developer & Council Member E-Mail : [EMAIL PROTECTED] GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85 pgpsMI4zNpIQW.pgp Description: PGP signature
Re: [gentoo-dev] irregular metdata.xml check
Marijn Schouten (hkBst) kirjoitti: > Thilo Bangert wrote: >> is a herd1300 > > These seem intentional. Is there anything wrong with it? > > Marijn Yes. You use the element to mark herds. Regards, Petteri signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] irregular metdata.xml check
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thilo Bangert wrote: > is a herd1300 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- -- [EMAIL PROTECTED] mailing list
Re: [gentoo-dev] irregular metdata.xml check
Thilo Bangert wrote: [great stuff here] Thanks for your useful work Thilo :) /me tips hat Rémi -- [EMAIL PROTECTED] mailing list
[gentoo-dev] irregular metdata.xml check
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. no-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 missing 2 empty 0 unknown 0 =no-herd1887 missing 6611 retired 0 is a herd1300 unknown 201 =maintainer-needed 438 Proxy maintainer without gentoo association13 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 pgp3vzg6mRCqm.pgp Description: PGP signature
Re: [gentoo-dev] irregular metdata.xml check
On 27/05/07, Thilo Bangert <[EMAIL PROTECTED]> 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. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-dev] irregular metdata.xml check
"Robin H. Johnson" <[EMAIL PROTECTED]> 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 > > . This is simply redundant and unless complaints are > > raised, all herd tags will be removed and replaced by > > the appropriate 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 on every single package in the tree (well ~1900 packages with no-herd). my guess is that most of the roughly 4500 packages that currently have a and a which is not a , 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 give you that the 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 pgp9fOV1ObYKO.pgp Description: PGP signature
Re: [gentoo-dev] irregular metdata.xml check
On Wed, May 23, 2007 at 07:49:43PM +0200, Thilo Bangert wrote: > Also, many ebuilds put the herds email address as an additional > . This is simply redundant and unless complaints are raised, > all herd tags will be removed and replaced by the > appropriate 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 : [EMAIL PROTECTED] GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85 pgpl9s9fOvO2u.pgp Description: PGP signature
Re: [gentoo-dev] irregular metdata.xml check
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 > > . This is simply redundant and unless complaints are raised, > > all herd tags will be removed and replaced by the > > appropriate 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 [EMAIL PROTECTED] 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 -- [EMAIL PROTECTED] mailing list
Re: [gentoo-dev] irregular metdata.xml check
On Wed, 2007-05-23 at 19:49 +0200, Thilo Bangert wrote: > Also, many ebuilds put the herds email address as an additional > . This is simply redundant and unless complaints are raised, > all herd tags will be removed and replaced by the > appropriate 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 [EMAIL PROTECTED] 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 signature.asc Description: This is a digitally signed message part
[gentoo-dev] irregular metdata.xml check
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 . This is simply redundant and unless complaints are raised, all herd tags will be removed and replaced by the appropriate tag instead. Work on this will start over the weekend. Statistics = Total number of packages:11701 metadata.xml missing 0 missing 0 empty 0 unknown 0 =no-herd1880 missing 6616 retired 0 is a herd1306 unknown 193 =maintainer-needed 438 Proxy maintainer without gentoo association11 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 pgp1OFUyQs7Ty.pgp Description: PGP signature
