Re: [gentoo-dev] Re: [gentoo-core] Google Summer of Code and Gentoo
On Fri, 14 Apr 2006 17:39:14 -0400 Thomas Cort [EMAIL PROTECTED] wrote: Alec Warner wrote: always portage portage portage. :) Can't you people think of another project to pick on^H^H^H^H^H^H^H^H that needs help? What about a Gentoo stats? Hmm, maybe the server component could be used for such a project (I'm already having most of the code for the client), I'll have to think about this. Marius -- gentoo-dev@gentoo.org mailing list
[gentoo-dev] xorg-x11 and local (RgbPath) rgb.txt database files [informal survey]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 For xorg-x11 (X11R6) users only, If you specify a local rgb database in your xorg.conf RgbPath entry, I'd be interested in hearing about it. Also, why you need it would be interesting and useful information: For example, My users and I prefer 'jaune' to 'yellow', I need more (or different) color names than rgb.txt supplies, and so on. If this question means anything to you, you may use https://bugs.gentoo.org/show_bug.cgi?id=130003 as background (or comment on the bug, for that matter). If the question doesn't mean anything to you, or if you use the default rgb.txt, no response needed. Thanks, Ferris - -- Ferris McCormick (P44646, MI) [EMAIL PROTECTED] Developer, Gentoo Linux (Devrel, Sparc) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2-ecc0.1.6 (GNU/Linux) iD8DBQFEQjq3Qa6M3+I///cRAt2AAKDm9rljAy6nFxqGM58TWqAu0y/MXgCgoC5G sxV0TahcpQhxU6z9SRef2dQ= =Fcm1 -END PGP SIGNATURE- -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Last rites for dev-util/cccc
On Sat, 2006-04-15 at 14:24 -0400, Mike Frysinger wrote: and it helps no one to go around cutting packages that have no outstanding issues with them Sure it helps keep Gentoo clean and up-to-date, the load of packages that are outdated are often unmaintained as well. The one leads to the other. Anyway, nobody would know about outstanding issues that popped up, because there is no maintainer to assign them to. there was an outstanding issue with , but i resolved that How do you know you resolved it, you don't get bugreports on it do you ? I mean, you aren't the maintainer. And there is still the outstanding issue that it is unmaintained in Gentoo, are you going to fix that or not ? Otherwise it should be masked and removed. - foser signature.asc Description: This is a digitally signed message part
[gentoo-dev] New developer: Thomas Cort (tcort)
Hi all. Thomas Cort has recently joined the gentoo team to work on sound and (more importantly) Alpha stuff :) He's been helping the alpha team for quite a while already and doing a great job. Thomas hails from Quebec, Canada and joins the already busy Canadian conspiracy. Give Thomas a warm welcome if you haven't already done so :) Regards, Bryan Østergaard -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Last rites for dev-util/cccc
On Sunday 16 April 2006 11:17, foser wrote: On Sat, 2006-04-15 at 14:24 -0400, Mike Frysinger wrote: and it helps no one to go around cutting packages that have no outstanding issues with them Sure it helps keep Gentoo clean and up-to-date, the load of packages that are outdated are often unmaintained as well. The one leads to the other. Anyway, nobody would know about outstanding issues that popped up, because there is no maintainer to assign them to. and then people send out last-rites notices in those cases there was an outstanding issue with , but i resolved that How do you know you resolved it, you don't get bugreports on it do you ? well the logical thing would be to go to bugzilla and search for ... and guess what ? no more open bug reports I mean, you aren't the maintainer. And there is still the outstanding issue that it is unmaintained in Gentoo, are you going to fix that or not ? Otherwise it should be masked and removed. this is the same argument as already made and rejected ... feel free to mask and remove the hundreds of other packages that have no maintainer -mike -- gentoo-dev@gentoo.org mailing list
[gentoo-dev] New ebuild Developer: Christian Hartmann (ian!)
Hi, It is my pleasure to announce publicly that ian! has passed all necessary quizzes to touch our holy gra^H^H^H portage tree. He'll be helping mcummings in his perpetuate combat with perl and its dependencies. May the source be with him. Congratulations Christian! :-) Danny -- Danny van Dyk [EMAIL PROTECTED] Gentoo/AMD64 Project, Gentoo Scientific Project -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] New ebuild Developer: Christian Hartmann (ian!)
Danny van Dyk wrote: Hi, It is my pleasure to announce publicly that ian! has passed all necessary quizzes to touch our holy gra^H^H^H portage tree. He'll be helping mcummings in his perpetuate combat with perl and its dependencies. May the source be with him. Congratulations Christian! :-) Danny Hooray for ian! Congratulations. signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] New ebuild Developer: Christian Hartmann (ian!)
YaY, b0rkage will go away :) Welcome ian -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] New ebuild Developer: Christian Hartmann (ian!)
On Mon, 2006-04-17 at 01:15 +0200, Danny van Dyk wrote: Hi, It is my pleasure to announce publicly that ian! has passed all necessary quizzes to touch our holy gra^H^H^H portage tree. He'll be helping mcummings in his perpetuate combat with perl and its dependencies. May the source be with him. Congratulations Christian! :-) Danny -- Danny van Dyk [EMAIL PROTECTED] Gentoo/AMD64 Project, Gentoo Scientific Project congrats to mcummings signature.asc Description: This is a digitally signed message part
Re: [gentoo-dev] New developer: Thomas Cort (tcort)
On Sunday, 16 April 2006 02:24 pm, [EMAIL PROTECTED] wrote: Thomas hails from Quebec, Canada and joins the already busy Canadian conspiracy. Another dev from Québec city! Welcome to the team, Thomas. -- Olivier Fisette (ribosome) Gentoo Linux Developer Scientific applications, Developer relations pgpQm3KfwbgJu.pgp Description: PGP signature
Re: [gentoo-dev] New developer: Thomas Cort (tcort)
On Sun, 2006-04-16 at 20:24 +0200, [EMAIL PROTECTED] wrote: Hi all. Thomas Cort has recently joined the gentoo team to work on sound and (more importantly) Alpha stuff :) He's been helping the alpha team for quite a while already and doing a great job. Thomas hails from Quebec, Canada and joins the already busy Canadian conspiracy. Give Thomas a warm welcome if you haven't already done so :) Congrats again Thomas!! -- gentoo-dev@gentoo.org mailing list
[gentoo-dev] aging ebuilds with unstable keywords
Hi,
This is an automatically created email message.
http://gentoo.tamperd.net/stable has just been updated with 14762 ebuilds.
The page shows results from a number of tests that are run against the ebuilds.
The tests are:
* if a version has been masked for 30 days or more.
* if an arch was in KEYWORDS in an older ebuild, but not in the newer ones.
* if SRC_URI contains hosts specified in thirdpartymirrors.
* if ebuild uses patch instead of epatch.
* if ebuild sets S to ${WORKDIR}/${P}.
* if ebuild redefines P, PV, PN or PF.
* if ebuild doesn't inherit eutils when it uses functions from eutils.
* if ebuild doesn't inherit flag-o-matic when it uses functions from
flag-o-matic.
* if ebuild has $HOMEPAGE in SRC_URI (cosmetic).
* if ebuild has $PN in SRC_URI (cosmetic).
* if ebuild forces -fPIC flag to CFLAGS.
* if ebuild has deprecated WANT_AUTO(CONF|MAKE)_?_?.
* if ebuild uses is-flag -fPIC, should be changed to has_fpic.
* if ebuild appends $RDEPEND or $DEPEND to $RDEPEND or $DEPEND to $DEPEND.
* if ebuild has arch keyword(s) in iuse.
* if ebuild overrides MAKEOPTS.
* if ebuild has automake, autoconf or libtool in RDEPEND.
* if ebuild exists in ChangeLog.
* if ebuild installs COPYING and/or INSTALL into doc.
The database is updated once a day and this email is sent once a week.
Questions and comments may be directed to [EMAIL PROTECTED]
Script has been running for 221 minutes.
--
gentoo-dev@gentoo.org mailing list
[gentoo-dev] xorg-server 1.0.99/1.1 ABI break
Hi all, Just wanted to make you aware that xorg-server 1.1 (and all release candidates, including 1.0.99 and up) breaks the server-driver ABI from 1.0. This means drivers are not compatible following an upgrade of xorg-server, and both sides will require an update to work again properly. This also means that all binary drivers (nvidia, ati, etc) will be broken with xorg-server 1.1 and RC's until their upstream vendor provides a compatible update. Everything with the new ABI is currently masked, but when X.Org 7.1 is released, will come out of package.mask. We are working to ensure the dependencies work as smoothly as possible, but I expect there will be some issues since it's difficult to require updates to all these optional drivers following an update to the server. Thanks, Donnie signature.asc Description: OpenPGP digital signature
Re: [gentoo-portage-dev] Outstanding decisions
Simon Stelling wrote: Hey all, I'm just wading through a list of ~200 bugs of which some need decisions what should be done, whether it should be done at all or simply whether it is a bug or not. Bug: SRC_URI: spaces not supported http://bugs.gentoo.org/show_bug.cgi?id=102607 Is this a 'NOTABUG' case? Need to check the SRC_URI documentation, if it's noted there, then close it, if its not noted in the docs, add that spaces are not allowed and close it ;) Bug: gpg: strict incorrectly takes priority over severe http://bugs.gentoo.org/show_bug.cgi?id=68906 What's the expected behaviour? Is it NOTABUG? Bug: Method to monitor a package without installing/upgrading it http://bugs.gentoo.org/show_bug.cgi?id=47456 Same thing. Do we want this? Alternative tool. Bug: Support for a pre-compile pkg_config http://bugs.gentoo.org/show_bug.cgi?id=99529 As Jason mentioned: Is this worth the effort? Effort is minimal, but I'm unsure of the real usefulness. Bug: per profile package.keywords http://bugs.gentoo.org/show_bug.cgi?id=55321 Voting seems to be a bit... incomplete ;) This is down to a design issue. package.keywords is a repository control measure, do we currently allow profiles to mess with repos? Only via use.mask at present. profile mangling of a repository is difficult when multiple repositories are brought in because we really don't have any type of repo binding in the current source. I personally think it's an important feature, but it's difficult to not implement it in a half assed manner. Bug: Wording These are the packages that I would merge, in order: http://bugs.gentoo.org/show_bug.cgi?id=112439 This needs a decision too. What wording do we prefer? Either way, the bug should be closed, the fix is trivial in case we want to change it. Ummm someone just make a decision, I don't think it's that big a deal. Bug: global exception handling http://bugs.gentoo.org/show_bug.cgi?id=28535 Should tracebacks be thrown in the users' face or not? Yes, Not saying you shouldn't write code that catches exceptions and all that but writing stupid code that catches any exception and then tries to print some useful info is...not as useful. I'd prefer to have documented a bit more what functions throw ( docstrings )? so that when users use portage functionality they know what to catch. Bug: /usr/lib/portage/bin/clean_locks documentation example could make use use DISTDIR http://bugs.gentoo.org/show_bug.cgi?id=116676 Call portageq or not? Voting time ;) nfc :0 That should be enough for the moment. More will probably follow, considering that I only checked the first 60 bugs or so :/ It would be nice if we could make the needed decision and then close the bugs where it is NOTABUG/INVALID/LATER. I hate stale bug listings ;) -- gentoo-portage-dev@gentoo.org mailing list
Re: [gentoo-portage-dev] Outstanding decisions
Next bunch of bugs that need a decision: Bug: portage: emerge unmerge ... should stop in case of an error http://bugs.gentoo.org/show_bug.cgi?id=118515 Another WONTFIX/WILLFIX issue Bug: need a way to package.unmask packages in profiles http://bugs.gentoo.org/show_bug.cgi?id=118440 Is this LATER? Alec mentioned a patch, but i couldn't find it when grepping through my archives, and nothing is attached to the bug. Bug: emerge/ebuild - a bit more verbosity please http://bugs.gentoo.org/show_bug.cgi?id=67892 This obviously lacks any discussion. RFC :) Bug: Support for src_test deps required http://bugs.gentoo.org/show_bug.cgi?id=69021 WONTFIX/WILLFIX? Bug: no documentation on the elog functions http://bugs.gentoo.org/show_bug.cgi?id=116018 AFAICS it's documented in make.conf.example and man make.conf, but the user requested a howto. Is a howto really needed? IMHO it's not that complex... Bug: Split CONFIG_PROTECT into separate installing and uninstalling options (nuke untouched files) http://bugs.gentoo.org/show_bug.cgi?id=8423 The classical one with a huge CC list. Whatever decision is made, this finally needs to get (fixed and) closed. -- Kind Regards, Simon Stelling Gentoo/AMD64 Developer -- gentoo-portage-dev@gentoo.org mailing list
