Re: [gentoo-dev] New Forums Staff : NeddySeagoon
On Sun, May 28, 2006 at 10:50:55PM -0700, Josh Saddler wrote: Welcome to the team! Wow, you've some credentials. I've certainly seen your unfailingly polite, helpful presence around the forums for a long time. I'm glad you bring a lot to Gentoo. Yes, those posts are really extraordinary - keep up the good work! cheers, Wernfried -- Wernfried Haas (amne) - amne at gentoo dot org Gentoo Forums: http://forums.gentoo.org IRC: #gentoo-forums on freenode - email: forum-mods at gentoo dot org pgp91lVDBD1Hg.pgp Description: PGP signature
Re: [gentoo-dev] Last rights for dev-util/perforce
Stuart Herbert wrote: Hi, The dev-util/perforce packages: - dev-util/perforce - dev-util/perforce-cli - dev-util/perforce-gui - dev-util/perforce-proxy - dev-util/perforce-server are in need of a new maintainer. If no-one volunteers in time, the packages will be masked Saturday 8th April, and removed from the tree shortly after. Best regards, Stu This has been masked as of today, awaiting it's 30 day countdown for removal. -Alec signature.asc Description: OpenPGP digital signature
[gentoo-dev] [Last Rites] dev-libs/nana
Good candidate for last rites... - SRC_URI dead, so this only lives on Gentoo mirrors - no maintainer, this bug[1] has been sitting here for 2 1/2 years So without further ado, pmasked for 30 days pending removal. [1] http://bugs.gentoo.org/show_bug.cgi?id=32672 signature.asc Description: OpenPGP digital signature
[gentoo-dev] net-www/awstats: security issues, revbump (and probably maintainer) needed
Hi Gang, net-www/awstats is masked because it has open security issues (including remote code execution), see bug #130487 for details. Version 6.6 was made to fix it, but unfortunately this version is not working at all (see bug #134296), so we are trapped between unusable and vulnerable versions. Jakub made a patch for version 6.5 to fix this vulnerabilities, but that very patch still needs to be incorporated into an ebuild and commited as revbump. So, if anyone volunteers to step up and revbump 6.5 with patch (or fix 6.6 so that it's usable), please don't hesitate. It would be also cool to have a new maintainer for this one, since ka0ttic seems to be missing. Thanks in advance, Stefan 'DerCorny' Cornelius -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Security/QA Spring Cleaning
On Sun, 2006-05-28 at 14:20 -0400, Ned Ludd wrote: Package: games-fps/cube Herd: games Maintainer: games This will likely be removed soon, as upstream has abandoned it. Package: games-fps/doomsday Herd: games Maintainer: games Waiting on a new upstream release. Upstream is active, so we expect one some time soon. Package: games-roguelike/falconseye Herd: games Maintainer: games Package: games-roguelike/nethack Herd: games Maintainer: games Package: games-roguelike/slashem Herd: games Maintainer: games These three will be unmasked soon with a changed policy wrt games on portage. Package: games-strategy/scorched3d Herd: games Maintainer: games Waiting for upstream. Basically, we're keeping track of our masked packages as well as we can. There are many times where we don't want to remove the package, knowing that upstream will be coming out with a newer version any day now as it tends to upset our users. -- Chris Gianelloni Release Engineering - Strategic Lead x86 Architecture Team Games - Developer Gentoo Linux signature.asc Description: This is a digitally signed message part
Re: [gentoo-dev] Summer of Code students and Planet Gentoo
On Sunday 28 May 2006 14:42, Christel Dahlskjaer wrote: On Sat, 2006-05-27 at 20:30 -0700, Donnie Berkholz wrote: Daniel Drake wrote: 1. We encourage our students to write about their projects on weblogs, and will set them up temporary weblogs at gentoo-soc.com if they do not have them already Why a new domain? We've already got a blog setup at http://planet.gentoo.org/developers/ and could just add http://planet.gentoo.org/summerofcode/ or something. If you want something like this, why not (soc|summerofcode).gentoo.org/? The worry there was whether it would create controversy if they were hosted with other developer blogs, so we figured we'd host the actual blogs off-site (should irk less people, although presumably most will already have external blogs already) and just aggregate them on planet/universe (hopefully). Perhaps add a nice logo for them on the planet website. This will serve identifying purposes, and as well give extra visibility to the SoC project. Paul -- Paul de Vrieze Gentoo Developer Mail: [EMAIL PROTECTED] Homepage: http://www.devrieze.net pgp4qrVILhGtf.pgp Description: PGP signature
[gentoo-dev] Last rites for media-libs/nurbs++
Upstream's last release for this package was in 2002, it doesn't compile with gcc-3.4 (bug #120303), and hasn't had a maintainer for a long time. Unless someone steps up to fix up this package, it will be punted in 30 days. Thanks, -- Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86) email - halcy0n AT gentoo DOT org mark AT halcy0n DOT com web - http://dev.gentoo.org/~halcy0n/ http://www.halcy0n.com pgp1dYzBd0FHP.pgp Description: PGP signature
Re: [gentoo-dev] Last rites for app-laptop/ibm-acpi
On Mon, May 01, 2006 at 01:18:38PM +0200, Henrik Brix Andersen wrote: I have now p.masked app-laptop/ibm-acpi. It will be removed from the tree in 30 days. Gone. ./Brix -- Henrik Brix Andersen [EMAIL PROTECTED] Gentoo Metadistribution | Mobile computing herd pgpgwdui5RTi6.pgp Description: PGP signature
[gentoo-dev] [RFC Maintainer-Wanted Bugs/Cleaning]
So we created this awesome alias to put ebuilds that need a maintainer. Good idea at the time, decent idea still. The problem? We have nearly 2000 open bugs assigned to maintainer-wanted[1]. I would like to discuss policy on these. Do we keep them, do we get a group of people to slowly review and discard them? Do we mind having a ton of things open like this (a quasi-ebuild db of sorts). Is bugs the right place for this sort of thing, or can we improve somewhere/how? [1] http://tinyurl.com/m3dmq signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] [RFC Maintainer-Wanted Bugs/Cleaning]
Alec Warner [EMAIL PROTECTED] said: So we created this awesome alias to put ebuilds that need a maintainer. Good idea at the time, decent idea still. The problem? We have nearly 2000 open bugs assigned to maintainer-wanted[1]. I would like to discuss policy on these. Do we keep them, do we get a group of people to slowly review and discard them? Do we mind having a ton of things open like this (a quasi-ebuild db of sorts). Is bugs the right place for this sort of thing, or can we improve somewhere/how? Yea, the current situation has quickly turned into a mess. I definately think that QA should definately be watching maintainer-wanted/maintainer-needed and helping clean up new ebuilds, or removing old unmaintained packages that no one cares about anymore. The problem with maintainer-wanted is the pure number of possible packages we *could* have in the tree, but no one wants to add. After discussing this briefly with antarus, I agree that it might be cool to write up our own homebrewed app to handle this. Basically, it would be something that allowed you to browse the current tree of submitted ebuilds. This way users that submit something can categorize it for devs to easily look for ebuilds they may be interested in, and we can make it so we could easily grab the ebuilds from this hacked up idea of a tree. It would make it a lot easier to do automated checks against submitted ebuilds for QA issues, and we would offload all of those submissions from bugs.g.o to this app. I guess you could think of it as the overlays.g.o idea, but I tend to think overlays are experimental things that aren't necessarily going to be added to the tree. This would be for ebuilds/packages that are ready to be added to the tree, but just lack someone that wants to maintain them. Comments on this idea are appreciated. I wouldn't mind helping write it and maintain it, but having interest and support in doing something like this is definately going to be needed :) -- Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86) email - halcy0n AT gentoo DOT org mark AT halcy0n DOT com web - http://dev.gentoo.org/~halcy0n/ http://www.halcy0n.com pgp5aKA0jGhzU.pgp Description: PGP signature
Re: [gentoo-dev] [RFC Maintainer-Wanted Bugs/Cleaning]
Mark Loeser wrote: Yea, the current situation has quickly turned into a mess. I definately think that QA should definately be watching maintainer-wanted/maintainer-needed and helping clean up new ebuilds, or removing old unmaintained packages that no one cares about anymore. A bugzilla feature to automatically close bugs these bugs after a set period of inactivity would certainly help. Dunno if it's possible, though. :) Otherwise, some review used to be done, but there's been a negative opinion about closing bugs w/ sucky broken ebuilds as WONTFIX/CANTFIX expressed by some of the devs; as it stands now - it's basically impossible to reasonably track the bugs unless it can be sorted by status and users reopen the bugs when they think they've fixed the outstanding issues... Finally - I'd suggest marking all ebuild *requests* as CANTFIX or NEEDINFO or whatever you think would be best resolution, there's tons of bugs w/ ebuilds submitted that can't find a maintainer. If you want something in portage, do you homework at least and attempt an ebuild. Just my $0.02... -- Best regards, Jakub Moc mailto:[EMAIL PROTECTED] GPG signature: http://subkeys.pgp.net:11371/pks/lookup?op=getsearch=0xCEBA3D9E Primary key fingerprint: D2D7 933C 9BA1 C95B 2C95 B30F 8717 D5FD CEBA 3D9E ... still no signature ;) signature.asc Description: OpenPGP digital signature
[gentoo-dev] GLEP 27 Proposal - Feedback Requested
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, I'm Mike Kelly, one of the SoC-ers. I'll be working on GLEP 27 for the summer. Right now I'm looking for some basic feedback on my proposal. In particular, I know that at one point there was a push for the user info files to be XML, but I think it may be easier to implement them as simple shell variable files (like /etc/conf.d/*), since my plan was to write the core of the implementation in shell (e.g. as an eclass). My proposal is available at: http://www.pioto.org/~pioto/gentoo/soc2006/glep27-proposal.txt. Any feedback would be appreciated; I wanna get things started on the right foot. Thanks! - -- Mike Kelly Happiness adds and multiplies as we divide it with others. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEe7wEokMzJ47YCzoRAps/AJ9pET/7BBjwiouJeIeVLPj91Dau0wCeM+jH KyJjXcpv2jMwBvNZjvYqr3w= =b+Bf -END PGP SIGNATURE- -- gentoo-dev@gentoo.org mailing list
