Re: [gentoo-dev] invalid in metadata.xml

2007-05-10 Thread Steve Dibb

Thilo Bangert wrote:

Doug Goldstein <[EMAIL PROTECTED]> said:

Thilo Bangert wrote:

All packages with maintainer-needed will be moved to
no-herd.

maintainer-needed is different from no-herd. no-herd is valid when a
dev is maintaining a pkg outside of a herd. no-herd is not valid for
when the package is entirely unmaintained, maintainer-needed would be a
better tag for it. I would not make that change.


if that were so, we would need to document it.
from my reading of the current policies[1,2,3]  is required and 
either no-herd or in herds.xml, no-herd only being allowed if no herd 
fits.


This is where all the discussions died from last time, that I can tell.  We 
never really decided on a specific policy change, and nothing got documented, or 
done.


In the end, we still have a few ebuilds in the tree that have no maintainer or 
no herd, and nobody really cares since all the portage utilities work around it 
anyway.


Still, as a matter of QA, it'd be nice to fix.

Steve
--
[EMAIL PROTECTED] mailing list



Re: [gentoo-dev] [RFC] missing tag in metadata.xml

2007-05-10 Thread Thilo Bangert

>  you should look at
> the archives to see what people decided.

from reading the archives and the response so far as well as the current 
documentation on the subject i conclude that the issue is still not clear 
and people make up their own stuff as they go along.

the following may be a formalisation of current (best) practices:

 - maintainers fall into three categories. herds, gentoo developers and
   non-gentoo proxy maintainers.

 -  a herd is defined in herds.xml. exception: no-herd. no-herd is limited
to the situation where no suitable herd can be found.

 - a gentoo developer is defined in dev-rel/roll-call/userinfo.xml.

 - every ebuild has a herd.

 - a package can belong to more than one herd.

 - a package can be maintened by no or more parties.

 - a package with herd different from 'no-herd' is said to be maintained
   by the members of that herd.

 - all maintainers different from herds state their maintainership using
   the  tag. the  tag requires the  tag.

 - a package with herd 'no-herd' and no additional maintainers  is said to
   be unmaintained.

 - a  of [EMAIL PROTECTED] indicates no maintainership and
   is only allowed as the sole maintainer. meaning a single 
   tag and a single no-herd tag. infact it is semantically
   equivalent to a single no-herd tag and no additional
   maintainers.

 - a package that is proxy maintained needs an additional gentoo
   association in form of a maintaining herd or gentoo developer.
   [EMAIL PROTECTED] may be such an association, but only if the
   original one disappeared.

optionally one may want to include, although personally i prefer to state 
it explicitly:

 - a missing or empty  tag is equivalent to no-herd

open questions:

 - what does it mean when the package is maintained by a herd and an
   additional maintainer? how does one determine the order in which to
   contact multiple maintainers?

 - are there situations in which we specify a  other than no-herd
   but don't want its members to act as maintainers?

...

what are your current best practices regarding metadata?
regards
Thilo


pgpA6IXbqq6cC.pgp
Description: PGP signature


Re: [gentoo-dev] Last rites sys-apps/855resolution

2007-05-10 Thread Seemant Kulleen
On Fri, 2007-05-11 at 00:33 +0300, Alon Bar-Lev wrote:
> Hello All,
> 
> sys-apps/915resolution superseed this package and support 855 configurations.
> 
> Please upgrade your configuration to sys-apps/915resolution.
> 
> Comments/suggestions can be entered at bug#159586.
> 
> Package will be masked at 2007-05-25, removed at 2005-06-08.
> 
> Best Regards,
> Alon Bar-Lev.

Why not just remove both when xf86-video-intel-2.* goes stable?

thanks,

Seemant



signature.asc
Description: This is a digitally signed message part


Re: [gentoo-dev] invalid in metadata.xml

2007-05-10 Thread Thilo Bangert
Doug Goldstein <[EMAIL PROTECTED]> said:
> Thilo Bangert wrote:
> > All packages with maintainer-needed will be moved to
> > no-herd.
>
> maintainer-needed is different from no-herd. no-herd is valid when a
> dev is maintaining a pkg outside of a herd. no-herd is not valid for
> when the package is entirely unmaintained, maintainer-needed would be a
> better tag for it. I would not make that change.

if that were so, we would need to document it.
from my reading of the current policies[1,2,3]  is required and 
either no-herd or in herds.xml, no-herd only being allowed if no herd 
fits.

>
> I tried to fix up your list and 

thanks

> found a handful of the packages not 
> even in existence in the tree. Can you re-run this with a fully up to
> date tree?

funny - so why would cvs up not be enough? which packages? i was able to 
find all packages on packages.gentoo.org

thanks

[1]http://devmanual.gentoo.org/ebuild-writing/misc-files/metadata/index.html
[2]http://www.gentoo.org/proj/en/metastructure/herds/index.xml
[3]http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=2&chap=4


pgpGNreQAXTcz.pgp
Description: PGP signature


[gentoo-dev] Last rites sys-apps/855resolution

2007-05-10 Thread Alon Bar-Lev

Hello All,

sys-apps/915resolution superseed this package and support 855 configurations.

Please upgrade your configuration to sys-apps/915resolution.

Comments/suggestions can be entered at bug#159586.

Package will be masked at 2007-05-25, removed at 2005-06-08.

Best Regards,
Alon Bar-Lev.
--
[EMAIL PROTECTED] mailing list



[gentoo-dev] Re: invalid in metadata.xml

2007-05-10 Thread Stefan Schweizer
Thilo Bangert wrote:
> All packages with maintainer-needed will be moved to
> no-herd.

I think that is not quite right, and since maintainer-needed is not a
maintainer but multiple people listening to the alias and users I would
like to suggest the following addition to herds.xml to make it legal:


maintainer-needed
[EMAIL PROTECTED]
Orphaned packages. Every developer is encouraged to fix
bugs here, proxy-maintain or take over maintainance

[EMAIL PROTECTED]
Maintainer Needed




Best regards,
Stefan

-- 
[EMAIL PROTECTED] mailing list



Re: [gentoo-dev] [RFC] missing tag in metadata.xml

2007-05-10 Thread Bo Ørsted Andresen
On Thursday 10 May 2007 19:38:13 Thilo Bangert wrote:
> /me goes back to reading up on some history:

missing metadata.xml - 2006-11-22
http://thread.gmane.org/gmane.linux.gentoo.devel/44407

-- 
Bo Andresen


signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-dev] invalid in metadata.xml

2007-05-10 Thread Doug Goldstein
Thilo Bangert wrote:
> Hi everybody,
>
> the following list of packages uses a invalid  tag in its 
> metadata.xml. Invalid in the sense of 'could-not-be-found-in-herds.xml'
>
> Most of them appear to be simple mis-spellings or minor misunderstandings. 
> Others may lack an entry in herds.xml (s390?).
>
> AFAICT most packages have straight forward fixes, which will be applied in 
> about 24 hours. Beat me to it if you want or stop my insanity by speaking 
> up.
>
> All packages with maintainer-needed will be moved to
> no-herd.
>
> kind regards
> Thilo
>   
maintainer-needed is different from no-herd. no-herd is valid when a dev
is maintaining a pkg outside of a herd. no-herd is not valid for when
the package is entirely unmaintained, maintainer-needed would be a
better tag for it. I would not make that change.

I tried to fix up your list and found a handful of the packages not even
in existence in the tree. Can you re-run this with a fully up to date tree?
-- 
[EMAIL PROTECTED] mailing list



Re: [gentoo-dev] Optional Package Dependencies for netscape-flash -> libflashsupport

2007-05-10 Thread Olivier Crête
On Thu, 2007-10-05 at 14:20 -0400, Patrick McLean wrote:
> Jim Ramsay wrote:
> > 
> > 1) Create a single local USE flag (flashsupport or something) that will
> > just pull in this dependency.
> > 
> > 2) Use the same set of USE flags as libflashsupport has, with any of
> > them adding libflashsupport to the dep list, since these are all global
> > flags and will most likely be enabled for both netscape-flash and
> > libflashsupport
> > 
> > I'm personally thinking (1) is the better of the 2 options, but I'd
> > like to know if anyone has any other wondrous solutions to this.
> 
> Does/will anything else dep on flashsupport? If not, why not just add
> the USE flags to netscape-flash and install libflashsupport as part of
> the netscape-flash install instead of a separate package.

If its a separate package that will be updated separately, then it
doesn't make sense to put it in the separate package and I support
option 1. Otherwise, if they'll always be together, then just put it in
the same package.

-- 
Olivier Crête
[EMAIL PROTECTED]
Gentoo Developer


signature.asc
Description: This is a digitally signed message part


Re: [gentoo-dev] Optional Package Dependencies for netscape-flash -> libflashsupport

2007-05-10 Thread Patrick McLean
Jim Ramsay wrote:
> 
> 1) Create a single local USE flag (flashsupport or something) that will
> just pull in this dependency.
> 
> 2) Use the same set of USE flags as libflashsupport has, with any of
> them adding libflashsupport to the dep list, since these are all global
> flags and will most likely be enabled for both netscape-flash and
> libflashsupport
> 
> I'm personally thinking (1) is the better of the 2 options, but I'd
> like to know if anyone has any other wondrous solutions to this.

Does/will anything else dep on flashsupport? If not, why not just add
the USE flags to netscape-flash and install libflashsupport as part of
the netscape-flash install instead of a separate package.
-- 
[EMAIL PROTECTED] mailing list



Re: [gentoo-dev] [RFC] missing tag in metadata.xml

2007-05-10 Thread Thilo Bangert
> >
> > Is it reasonable to simply add the no-herd or should
> > perhaps the policy be relaxed, such that a missing  tag is
> > equivalent with no-herd?

>
> iirc there was a flamewar about this a while ago.  you should look at
> the archives to see what people decided.

whatever the outcome of the discussion was, the current situation is still 
unclear, which is why it needs to be addressed again.

either we decide to relax the policy and change the documentation, or we 
dont and fix the ebuilds.

/me goes back to reading up on some history:

The Dreaded herd tag - 2006-10-28
http://thread.gmane.org/gmane.linux.gentoo.devel/43733

Herds suck, fix them - 2006-06-15
http://thread.gmane.org/gmane.linux.gentoo.devel/39385

Please use land-misc herd where appropriate! No no-herd madness!!!
2004-10-07
http://thread.gmane.org/gmane.linux.gentoo.devel/21899

Packages with non-existent herd in metadata.xml - 2004-09-27
http://thread.gmane.org/gmane.linux.gentoo.devel/21633

kind regards
Thilo


pgpy8WyjAHBdD.pgp
Description: PGP signature


[gentoo-dev] Optional Package Dependencies for netscape-flash -> libflashsupport

2007-05-10 Thread Jim Ramsay
I am about to add libflashsupport[1] to the tree, which optionally adds
pulseaudio, oss, esd, and ssl (via openssl or gnutls) support to
netscape-flash-9.0.31.0

This libflashsupport-1.2 will have the following use flags:

  pulseaudio oss esd ssl gnutls

Now, I was thinking that it would be much easier for users if
the netscape-flash ebuild automatically pulled this in, and was
wondering the best way to do this.  I have 2 ideas:

1) Create a single local USE flag (flashsupport or something) that will
just pull in this dependency.

2) Use the same set of USE flags as libflashsupport has, with any of
them adding libflashsupport to the dep list, since these are all global
flags and will most likely be enabled for both netscape-flash and
libflashsupport

I'm personally thinking (1) is the better of the 2 options, but I'd
like to know if anyone has any other wondrous solutions to this.

[1] http://pulseaudio.revolutionlinux.com/PulseAudio

-- 
Jim Ramsay
Gentoo/Linux Developer (rox,gkrellm)


signature.asc
Description: PGP signature


Re: [gentoo-dev] invalid in metadata.xml

2007-05-10 Thread Steve Dibb
> Hi everybody,
>
> the following list of packages uses a invalid  tag in its
> metadata.xml. Invalid in the sense of 'could-not-be-found-in-herds.xml'

FWIW, I've been providing similar results on a daily basis for some time
now at GPNL (Gentoo Packages that Need Lovin) website:

http://spaceparanoids.org/gentoo/gpnl/

Feel free to fixxor your ebuilds. :)

Steve
-- 
[EMAIL PROTECTED] mailing list



Re: [gentoo-dev] dev-db/firebird needs an active maintainer

2007-05-10 Thread William L. Thomson Jr.
On Thu, 2007-05-10 at 12:20 +0200, Timothy Redaelli wrote:
> Sune Kloppenborg Jeppesen ha scritto:
> > dev-db/firebird is without an active maintainer and have an open 
> > security bug #120343 ¹.
> > 
> > Anyone willing to take care of this package in the future, please update 
> > metadata.xml and CC yourself on the bug.
> > 
> > ¹ https://bugs.gentoo.org/show_bug.cgi?id=120343
> > 
> 
> I can do it :)
> I'm fixing the ebuild to use doenv, doinitd, etc instead of insinto and
> to use external libedit

I am willing to help as well. Was trying to work with sekretarz on
getting an ebuild for 2.0. I have one in the works just needs some
review, and I believe and update to 2.0.1. Wanted to commit it to tree,
but did not want to step on current maintainers toes.

Tim, can we collaborate on it? I use Fb daily, clients businesses, as
well as mine depend on it. Joined upstream fb-dev ml but spent most time
playing middle man with sekretarz and fb-dev ml. You can email me
directly or hit me up on irc to proceed with this.

At min would like to get you a copy or etc of what I have so far for
2.0. It's a mixture of the ebuild in bugzilla, and existing 1.5.x
ebuilds in tree.

-- 
William L. Thomson Jr.
Gentoo/Java


signature.asc
Description: This is a digitally signed message part


Re: [gentoo-dev] [RFC] missing tag in metadata.xml

2007-05-10 Thread Mike Doty
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Thilo Bangert wrote:
> The metadata cleanup continues... 
> 
> A list of 427 packages found at 
> 
>   http://dev.gentoo.org/~bangert/herd-metadata-check.log
> 
> do not have the required  tag in their metadata.xml[1].
> 
> Is it reasonable to simply add the no-herd or should perhaps 
> the policy be relaxed, such that a missing  tag is equivalent with 
> no-herd?
> 
> kind regards
> Thilo
> 
> [1] Gentoo Development Guide - Package and Category metadata.xml 
> http://devmanual.gentoo.org/ebuild-writing/misc-files/metadata/index.html
iirc there was a flamewar about this a while ago.  you should look at
the archives to see what people decided.

- --
===
Mike Doty  kingtaco -at- gentoo.org
Gentoo Council
Gentoo Infrastructure
Gentoo/AMD64 Strategic Lead
GPG: E1A5 1C9C 93FE F430 C1D6  F2AF 806B A2E4 19F4 AE05
===
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.3 (GNU/Linux)

iQCVAwUBRkM+KoBrouQZ9K4FAQIfigP+K447icY7rWKLnltRkm+omZqVGfj5AbwE
ahY3UlIb/McOxor+IDwbw05BJ85Mys1fVdB4NWK6UZJu3bGLA2Gl4nHHQJjnwp1b
FPHeE/C15E1U0lkuY0AppH/ABOEi3Sdw9gMxlQTQvLD/qTQ1+thcMrBvYjb1r7DH
5H23iAxxB6U=
=kmPd
-END PGP SIGNATURE-
-- 
[EMAIL PROTECTED] mailing list



[gentoo-dev] [RFC] missing tag in metadata.xml

2007-05-10 Thread Thilo Bangert
The metadata cleanup continues...   

A list of 427 packages found at 

  http://dev.gentoo.org/~bangert/herd-metadata-check.log

do not have the required  tag in their metadata.xml[1].

Is it reasonable to simply add the no-herd or should perhaps 
the policy be relaxed, such that a missing  tag is equivalent with 
no-herd?

kind regards
Thilo

[1] Gentoo Development Guide - Package and Category metadata.xml 
http://devmanual.gentoo.org/ebuild-writing/misc-files/metadata/index.html


pgp1MBpXu4fX8.pgp
Description: PGP signature


[gentoo-dev] missing metadata.xml

2007-05-10 Thread Thilo Bangert
Hi everybody,

the packages in the attached list have no metadata.xml.

The following basic metadata.xml will be added to each package in about 24 
hours. Speak up to stop the insanity.

Thanks.
kind regards
Thilo


http://www.gentoo.org/dtd/metadata.dtd";>

no-herd

[EMAIL PROTECTED]


app-crypt/keylookup missing metadata.xml
app-doc/doc++   missing metadata.xml
app-doc/linux-kernel-in-a-nutshell  missing metadata.xml
app-misc/grabcartoons   missing metadata.xml
app-text/expander   missing metadata.xml
dev-libs/mm missing metadata.xml
dev-libs/mpatrolmissing metadata.xml
dev-util/byacc  missing metadata.xml
dev-util/egypt  missing metadata.xml
media-libs/libipod  missing metadata.xml
net-misc/monmotha   missing metadata.xml
net-misc/zssh   missing metadata.xml
sys-apps/einit  missing metadata.xml
sys-cluster/wulfstatmissing metadata.xml
sys-cluster/xmlsysd missing metadata.xml
sys-devel/autoconf-archive  missing metadata.xml
sys-fs/ddrescue missing metadata.xml
www-apps/browser-config missing metadata.xml
www-client/downman  missing metadata.xml
www-client/netrik   missing metadata.xml
www-client/w3mirmissing metadata.xml
www-servers/plb missing metadata.xml
x11-libs/ViewKlass  missing metadata.xml
x11-libs/dndmissing metadata.xml
x11-libs/kylixlibs3-borqt   missing metadata.xml
x11-libs/libPropListmissing metadata.xml
x11-libs/xclass missing metadata.xml
Found 27 packages with missing metadata.xml


pgpihy3Q9SH8o.pgp
Description: PGP signature


[gentoo-dev] invalid in metadata.xml

2007-05-10 Thread Thilo Bangert
Hi everybody,

the following list of packages uses a invalid  tag in its 
metadata.xml. Invalid in the sense of 'could-not-be-found-in-herds.xml'

Most of them appear to be simple mis-spellings or minor misunderstandings. 
Others may lack an entry in herds.xml (s390?).

AFAICT most packages have straight forward fixes, which will be applied in 
about 24 hours. Beat me to it if you want or stop my insanity by speaking 
up.

All packages with maintainer-needed will be moved to
no-herd.

kind regards
Thilo
app-cdr/powerisoinvalid herd: app-cdr
app-editors/xxe invalid herd: maintainer-needed
app-emulation/hercules  invalid herd: s390
dev-libs/libffi invalid herd: [EMAIL PROTECTED]
dev-libs/liboil invalid herd: media-video
dev-libs/libvc  invalid herd: maintainer-needed
dev-python/python-lzo   invalid herd: noherd
dev-ruby/jabber4r   invalid herd: Ruby
dev-ruby/net-sftp   invalid herd: Ruby
dev-ruby/net-sshinvalid herd: Ruby
dev-ruby/pdf-writer invalid herd: Ruby
dev-util/cgvg   invalid herd: dev-util
media-libs/schroedinger invalid herd: media-video
media-tv/freevo invalid herd: maintainer-needed
net-fs/fex  invalid herd: noherd
net-ftp/tftp-hpainvalid herd: basesystem
net-misc/netkit-rusers  invalid herd: maintainer-needed
net-misc/netkit-rwall   invalid herd: maintainer-needed
net-misc/redir  invalid herd: maintainer-needed
net-misc/vncsnapshotinvalid herd: maintainer-needed
net-misc/xf4vnc invalid herd: maintainer-needed
sci-electronics/splat   invalid herd: ci-electronics
sys-apps/cpint  invalid herd: s390
sys-apps/lkcdutils  invalid herd: s390
sys-apps/s390-oco   invalid herd: s390
x11-libs/libsexyinvalid herd: Gentopia
x11-libs/openmotif  invalid herd: maintainer-needed
x11-misc/gromit invalid herd: maintainer-needed
Found 28 packages with invalid 


pgpgBSRLMoNIw.pgp
Description: PGP signature


Re: [gentoo-dev] dev-db/firebird needs an active maintainer

2007-05-10 Thread Timothy Redaelli
Sune Kloppenborg Jeppesen ha scritto:
> dev-db/firebird is without an active maintainer and have an open 
> security bug #120343 ¹.
> 
> Anyone willing to take care of this package in the future, please update 
> metadata.xml and CC yourself on the bug.
> 
> ¹ https://bugs.gentoo.org/show_bug.cgi?id=120343
> 

I can do it :)
I'm fixing the ebuild to use doenv, doinitd, etc instead of insinto and
to use external libedit

-- 
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



signature.asc
Description: OpenPGP digital signature