Re: [gentoo-dev] new herd suggestion: religion
William L. Thomson Jr. wrote: On Fri, 2007-02-02 at 08:41 -0600, Andrew Gaffney wrote: Steve Dibb wrote: I'd like to propose a new herd: religion. The herd would take care of Would the non-believers in the group be able to ignore it like we do the real thing? :P Would Jihad related packages fall under this category as well? Not sure about them, but... http://bip.chibs.edu.tw/MyWebs/englishWebpage.html lu - something different that the usual j-c religion... -- Luca Barbato Gentoo/linux Gentoo/PPC http://dev.gentoo.org/~lu_zero -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Mass filing of bugs/Gentoo sanitation
On Fri, 2007-02-02 at 21:54 +0100, Marius Mauch wrote: On Fri, 02 Feb 2007 20:25:55 +0100 Tom Fredrik Blenning Klaussen [EMAIL PROTECTED] wrote: On Fri, 2007-02-02 at 19:56 +0100, Marius Mauch wrote: On Fri, 02 Feb 2007 19:29:06 +0100 Tom Fredrik Blenning Klaussen [EMAIL PROTECTED] wrote: On Fri, 2007-02-02 at 14:04 +0200, Petteri Räty wrote: Tom Fredrik Blenning Klaussen wrote: A file that needs to be looked at fulfills the following demands. 1. Is a gentoo installed file, in particular is found within /var/db/pkg/*/*/CONTENTS 2. Is executable 3. Is not a link, it is assumed that a link goes to another file within the same packet. 4. Is not a directory Anything that fullfills those demands and is not handled within the program is a possible bug. So all executable files in a package are bugs? I hope I'm missing something here ... Maybe you could just post your script, code is sometimes better than humans for explaining algorithms. Well, you're missing the part about not handled and possible bug. As I said, some of the file types are handled, and are known to be bugs, some are unhandled and are probably bugs. Among the filetypes I handle are gif files. I can not see any reason why gif files should be executable, can you? Ok, so you're looking for executable files that shouldn't be executables. That's much easier to understand, all that handling stuff was a bit confusing to me as you never listed your goal. Sorry about that, I did list my goal in the first mail, but it wasn't my real question. My real question concerned how to mass file bugs. Anyway, my real goal is to find lacking dependencies in ebuilds. All the bugs I've discovered so far are discovered as a sideeffect of the main goal which as stated is to find dependency problems. -- Tom Fredrik Blenning Klaussen [EMAIL PROTECTED] -- gentoo-dev@gentoo.org mailing list
[gentoo-dev] alternatives.eclass and ecompress
Hi all, I stumbled about a problem with alternatives.eclass when fixing a user submitted bug report about missing man page symlinks. The new ecompress allows compression of manpages in bz2, if I am right. So now ebuilds as dev-lang/python have a hard coded compression extension for alternatives_auto_makesym. emacs-cvs now has a regex to determine the correct extension to set a working symlink. Shouldn't that be handled by alternatives.eclass? alternatives_auto_makesym /usr/share/man/man1/python.1.gz \ python[0-9].[0-9].1.gz V-Li signature.asc Description: PGP signature
Re: [gentoo-dev] New developer: Sebastien Fabbro (bicatali)
Thanks for the welcome! Gastronomy or astronomy? I'm confused ;) It's nice to switch. The sky has more than 3 stars ;) If you're a cosmology researcher, does that mean that you like astronomy photography? I admire it more than I can do. Sébastien On Friday 02 February 2007 10:49, Marcus D. Hanwell wrote: It is my pleasure to introduce Sebastien Fabbro (also known as bicatali) to you as the latest addition to the Gentoo scientific applications team. In his own words he is a French guy (don't worry - we won't hold that against you ;) ) living and working n Portugal. He is experienced with C, C++, Python and bash and so should fit in great around here. He also has some experience of autotools which always helps when working with some of the less well thought out build systems we seem to encounter in some scientific applications! He is a post-doctoral researcher in observational cosmology - I think that means he gets paid to stare up at the sky and tell us all how big it is. May be you could ask him to clarify, His interests include gastronomy, outdoor activities and programming. He has plenty of Gentoo experience having already acted as a herd tester since the inception of the herd tester programme. He administers a small LAN of Gentoo machines on their network at work and has already been very helpful for the scientific applications herd. Thanks also go to Kugelfang for sorting out his developer bug ;) I hope you will all join me in welcoming Sebastien as a fellow developer. Thanks, Marcus -- gentoo-dev@gentoo.org mailing list
[gentoo-dev] Last rites for media-sound/choad
During today's cleanup this package turned up missing an upstream site or sources, the package is mostly unmaintained for a while, jmglov, who's currently set as maintainer, is in kloeri's list to be retired. As there are tons of different tools to do the same thing (rip audio from CD to mp3 and tag them), the package will be masked and removed in 30 days, as usual. -- Diego Flameeyes Pettenò - http://farragut.flameeyes.is-a-geek.org/ Gentoo/Alt lead, Gentoo/FreeBSD, Video, Sound, ALSA, PAM, KDE, CJK, Ruby ... pgp0U3Cv6chQ1.pgp Description: PGP signature
[gentoo-dev] Last rites for media-sound/gradio
This package too is unfetchable (upstream's site is password protected, wtf?), the last release is in 2000, and still using GTK 1.2 Scheduled for removal on March 3rd again. -- Diego Flameeyes Pettenò - http://farragut.flameeyes.is-a-geek.org/ Gentoo/Alt lead, Gentoo/FreeBSD, Video, Sound, ALSA, PAM, KDE, CJK, Ruby ... pgppOIEcd17xU.pgp Description: PGP signature
[gentoo-dev] Last rites for media-sound/liteamp
As per summary, the development seems to be stopped for more than three years now, and latest version does not build on either x86 or amd64; one of the old versions is not even fetchable anymore. Unless somebody goes around to fix this, it will be removed March 3rd. -- Diego Flameeyes Pettenò - http://farragut.flameeyes.is-a-geek.org/ Gentoo/Alt lead, Gentoo/FreeBSD, Video, Sound, ALSA, PAM, KDE, CJK, Ruby ... pgpLpaaUd7r7Z.pgp Description: PGP signature
[gentoo-dev] Last rites for media-sound/pd-cyclone
This package was added and never maintained as far as I can see; the version in portage is versioned as 0.1_alpha (which is not a good foresight) and has incorrect PIC handling. If nobody gets around fixing this, it is doomed to go away on March 3rd. -- Diego Flameeyes Pettenò - http://farragut.flameeyes.is-a-geek.org/ Gentoo/Alt lead, Gentoo/FreeBSD, Video, Sound, ALSA, PAM, KDE, CJK, Ruby ... pgp9fhidMic6X.pgp Description: PGP signature
[gentoo-dev] Last rites for media-sound/mpio
Another package that hasn't seen releases since 2004; it also requires specific hardware to be used (Digitalway/Adtec audio players), currently depending on hotplug too. Unless someone can get around to fix this (and has the hardware to actually test this), it will go away on March 3rd. -- Diego Flameeyes Pettenò - http://farragut.flameeyes.is-a-geek.org/ Gentoo/Alt lead, Gentoo/FreeBSD, Video, Sound, ALSA, PAM, KDE, CJK, Ruby ... pgpIliByTq41w.pgp Description: PGP signature
[gentoo-dev] Re: Monthly Gentoo Council Reminder for February
Kevin F. Quinn wrote: It would but having some kind of deadline after which you are for example free to take over the package if you want to would be nice. That's going too far; there's certainly no need to take over a package just to get a fix in. If you want to take over a package, asking the current maintainer has to be the first step, not to quietly wait for a timeout then just grab it. Similarly asking the current maintainer if they mind you putting a fix in. That's of course a given. I think the question here relates to non-responsive maintainers or herds. I have been in the situation many many times with gcc-porting where I file a bug with a simple patch (say removing extra qualification) to get a package to build with GCC 4.1, and get no response for months from the maintainer despite multiple pings. In that case, i'll apply the fix myself. I always try to wait a month or more before going ahead and always ping at least once. So far i've not received any major complaints, but i'm just waiting for the day someone will get territorial about their packages and decide rip me a new one. It'd be nice to have some kind of asshole insurance. This also affects things like treecleaners. How long does a herd team or maintainer have to be unresponsive to warrant the package falling into maintainer-needed? Right now the most common way we find these packages is when Jakub gets annoyed enough with the accumulating bugs and lack of response to CC us. ;P I personally think that for bug fixes a month is a long enough wait to allow someone to respond. Keep in mind that's to respond, not to fix the bug. A simple yep, i'll get to this later is enough. -- by design, by neglect dirtyepic gentoo orgfor a fact or just for effect 9B81 6C9F E791 83BB 3AB3 5B2D E625 A073 8379 37E8 (0x837937E8) signature.asc Description: OpenPGP digital signature
[gentoo-dev] Last rites for media-sound/psmix
This time it's a fantastic package that can save state and window position, but what would you expect from a package added in 2002 that seems to still use gtk 1.2 (the dependencies aren't cleaned up, it depends on generic gtk+). It is also unfetchable, so unless someone _really_ wants it, it will go away in the usual 30 days. -- Diego Flameeyes Pettenò - http://farragut.flameeyes.is-a-geek.org/ Gentoo/Alt lead, Gentoo/FreeBSD, Video, Sound, ALSA, PAM, KDE, CJK, Ruby ... pgpujhNqYVuVh.pgp Description: PGP signature
[gentoo-dev] Re: new herd suggestion: religion
Steve Dibb wrote: @devs, I'd like to propose a new herd: religion. The herd would take care of the Bible and religious software along with any genealogy programs in the tree, which there actually are a few of. Sword, gnomesword, sword modules, bibletime, gramps would all fall under the responsibilty of the herd. I talked to squinky86 who was previously maintaining most of these, and since he is temporarily retiring I've assumed ownership of the packages in his absence. A herd would of course let anyone else interested work on them, and be recognized as joint maintainers as well. Any comments? Anything that makes it easier to identify and work on packages you're interested in seems okay to me. Maybe emacs, vim, kde, and gnome could be added. ;P -- by design, by neglect dirtyepic gentoo orgfor a fact or just for effect 9B81 6C9F E791 83BB 3AB3 5B2D E625 A073 8379 37E8 (0x837937E8) signature.asc Description: OpenPGP digital signature
[gentoo-dev] Last rites for media-video/ks3switch
Missing upstream, requires an S3 card, even s3switch does not build here at all (not sure on x86 right now), so it will be removed on march 3rd unless someone can fix this _and_ s3switch. -- Diego Flameeyes Pettenò - http://farragut.flameeyes.is-a-geek.org/ Gentoo/Alt lead, Gentoo/FreeBSD, Video, Sound, ALSA, PAM, KDE, CJK, Ruby ... pgpU64WW8BvZA.pgp Description: PGP signature
[gentoo-dev] Last rites for sys-apps/s3switch
As I've already last rited ks3switch, this one is also going away, as it doesn't currently build at all. Unless someone wants to pick this up (currently unmaintained), it will be removed in the usual 30 days. -- Diego Flameeyes Pettenò - http://farragut.flameeyes.is-a-geek.org/ Gentoo/Alt lead, Gentoo/FreeBSD, Video, Sound, ALSA, PAM, KDE, CJK, Ruby ... pgpzWQvsFIkHa.pgp Description: PGP signature
[gentoo-dev] New developer: Samuli Suominen (drac)
It's my pleasure to introduce to you Samuli drac Suominen. He is joining us to look after the Xfce desktop environment and take care of packages that have been proxy maintained before. A fellow countryman so he hails from Finland. He has been using Linux for about 10 years now. He says he spents about 75% of his free time on Gentoo so expect Xfce 4.4 to be unmasked sometime soon :) Hopefully this will be a start for a Finnish conspiracy. Regards, Petteri signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] Re: Monthly Gentoo Council Reminder for February
On Sat, 03 Feb 2007 14:04:49 -0600 Ryan Hill [EMAIL PROTECTED] wrote: Kevin F. Quinn wrote: It would but having some kind of deadline after which you are for example free to take over the package if you want to would be nice. That's going too far; there's certainly no need to take over a package just to get a fix in. If you want to take over a package, asking the current maintainer has to be the first step, not to quietly wait for a timeout then just grab it. Similarly asking the current maintainer if they mind you putting a fix in. That's of course a given. I think the question here relates to non-responsive maintainers or herds. Well, this thread didn't start with MIA devs (which is what you're talking about), it started with devs being too slow to take action. I wouldn't have a standard timeout (far too regulatory) - just apply common sense and do what needs to be done. I have been in the situation many many times with gcc-porting where I file a bug with a simple patch (say removing extra qualification) to get a package to build with GCC 4.1, and get no response for months from the maintainer despite multiple pings. In that case, i'll apply the fix myself. I always try to wait a month or more before going ahead and always ping at least once. So far i've not received any major complaints, but i'm just waiting for the day someone will get territorial about their packages and decide rip me a new one. It'd be nice to have some kind of asshole insurance. Well, my experience so far has been that provided you fix stuff decently (both technically and politically ;) ), people don't mind Maintainers can always tweak later if they prefer a different solution. If things get antsy, there's always devrel to mediate. One obvious point, is to check a dev's away status if they're not responding, before diving in. This also affects things like treecleaners. How long does a herd team or maintainer have to be unresponsive to warrant the package falling into maintainer-needed? Right now the most common way we find these packages is when Jakub gets annoyed enough with the accumulating bugs and lack of response to CC us. ;P I personally think that for bug fixes a month is a long enough wait to allow someone to respond. Keep in mind that's to respond, not to fix the bug. A simple yep, i'll get to this later is enough. -- Kevin F. Quinn signature.asc Description: PGP signature
Re: [gentoo-dev] alternatives.eclass and ecompress
On Saturday 03 February 2007, Christian Faulhammer wrote: The new ecompress allows compression of manpages in bz2, if I am right. it allows any compression; it's up to the user ... so you cant assume any extension So now ebuilds as dev-lang/python have a hard coded compression extension for alternatives_auto_makesym. you should not be generating symlinks to compressed manpages -mike pgpCpUs377tTC.pgp Description: PGP signature
Re: [gentoo-dev] New developer: Samuli Suominen (drac)
On Saturday 03 February 2007, Petteri Räty wrote: It's my pleasure to introduce to you Samuli drac Suominen. He is joining us to look after the Xfce desktop environment and take care of packages that have been proxy maintained before. YAI! Welcome Samuli, now you can take care of your bugs yourself :) -- Diego Flameeyes Pettenò - http://farragut.flameeyes.is-a-geek.org/ Gentoo/Alt lead, Gentoo/FreeBSD, Video, Sound, ALSA, PAM, KDE, CJK, Ruby ... pgpJVaGTiAvZW.pgp Description: PGP signature
Re: [gentoo-dev] Another council topic for Feb
Mike Doty wrote:
We're going to talk about arch keywording policies. IMO we should have
a standard policy if you own and use ${ARCH} then you may keyword your
packages for ${ARCH} with the exception of the sys-*/ categories.
keyword ~${ARCH} exclusively or also marking stable?
--
Kind Regards,
Simon Stelling
Gentoo/AMD64 developer
--
gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Another council topic for Feb
On 03/02/07, Mike Doty [EMAIL PROTECTED] wrote:
We're going to talk about arch keywording policies. IMO we should have
a standard policy if you own and use ${ARCH} then you may keyword your
packages for ${ARCH} with the exception of the sys-*/ categories.
Speakup now to get your input in.
I'm not sure that making that a standard policy would be in the spirit
of GLEP 40.
--
Richard Brown
--
gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Re: new herd suggestion: religion
Ryan Hill wrote: Steve Dibb wrote: @devs, I'd like to propose a new herd: religion. The herd would take care of the Bible and religious software along with any genealogy programs in the tree, which there actually are a few of. Sword, gnomesword, sword modules, bibletime, gramps would all fall under the responsibilty of the herd. I talked to squinky86 who was previously maintaining most of these, and since he is temporarily retiring I've assumed ownership of the packages in his absence. A herd would of course let anyone else interested work on them, and be recognized as joint maintainers as well. Any comments? Anything that makes it easier to identify and work on packages you're interested in seems okay to me. Maybe emacs, vim, kde, and gnome could be added. ;P I'm for it - I'm willing to join such a herd, in fact - I did classical languages before I was in technology. Thanks, Marty -- gentoo-dev@gentoo.org mailing list
[gentoo-dev] Last rites for app-admin/kcmgrunlevel
As per summary; unfetchable, it's probably incompatible with current baselayout, as it was developed in 2004, and the version number suggests an alpha/beta version. If nobody wants to take over maintainership, it will be removed in 30 days. -- Diego Flameeyes Pettenò - http://farragut.flameeyes.is-a-geek.org/ Gentoo/Alt lead, Gentoo/FreeBSD, Video, Sound, ALSA, PAM, KDE, CJK, Ruby ... pgp3nMjQ3ACgp.pgp Description: PGP signature
[gentoo-dev] Re: Another council topic for Feb
Mike Doty schrieb: Speakup now to get your input in. Why opening up the keywording like that? Most times a friendly ping on irc to get permissions to keyword x packages on own hardware succeedes and you're done. communication++ Jokey -- gentoo-dev@gentoo.org mailing list
[gentoo-dev] Last rites for ruby-gnome (1) packages
For some reasons they escaped the big gnome 1.x removal, and now I'm going to remove them as they likely don't build anymore (with the exception of ruby-libart and ruby-gtk that anyway seems to be deprecated nowadays): dev-ruby/ruby-gtk dev-ruby/ruby-gconf dev-ruby/ruby-gdkimlib dev-ruby/ruby-gdkpixbuf dev-ruby/ruby-libart -- Diego Flameeyes Pettenò - http://farragut.flameeyes.is-a-geek.org/ Gentoo/Alt lead, Gentoo/FreeBSD, Video, Sound, ALSA, PAM, KDE, CJK, Ruby ... pgpR6PolRoPDH.pgp Description: PGP signature
[gentoo-dev] Re: Another council topic for Feb
On Saturday 03 February 2007, Mike Doty wrote:
We're going to talk about arch keywording policies. IMO we should have
a standard policy if you own and use ${ARCH} then you may keyword your
packages for ${ARCH} with the exception of the sys-*/ categories.
after all the pains we went through to enforce if you want to stabilize on
$ARCH, talk to the $ARCH team, how is this a good thing ?
i guess i dont see anything wrong with the current stabilization policy ... if
you want to stable for $ARCH, ask the $ARCH team or join the $ARCH team and
do it yourself
-mike
pgpCH1uUYQxIP.pgp
Description: PGP signature
Re: [gentoo-dev] new herd suggestion: religion
Steve Dibb [EMAIL PROTECTED] wrote: I'd like to propose a new herd: religion. The herd would take care of the Bible and religious software along with any genealogy programs in the tree, which there actually are a few of. I previously suggested philosophy as an alternate name, as that would make more sense for the subjects you mentioned. While I still support that assertion, it was met with a bit of opposition. Dominique Michel [EMAIL PROTECTED] wrote: Philosophy is also a science. Alexandre Buisse [EMAIL PROTECTED] wrote: Sorry but no, religion is *not* included in philosophy. It's as if you wanted to put creationism packages (not that there exists any, I hope) in the science herd. If either of these arguments make sense to anyone else, perhaps something more academic, humanities or some such, could be chosen. -- mount /dev/wyrm /mnt/bed ; sleep 28800 pgpsnAr5T9gwU.pgp Description: PGP signature
Re: [gentoo-dev] Another council topic for Feb
On Sat, 03 Feb 2007 13:19:58 -0800 Mike Doty [EMAIL PROTECTED]
wrote:
| We're going to talk about arch keywording policies. IMO we should
| have a standard policy if you own and use ${ARCH} then you may
| keyword your packages for ${ARCH} with the exception of the sys-*/
| categories.
Archs aren't standard. On sparc, for example, only testing on v8 is
insufficient. On mips it's even worse because a single keyword covers
big and little endian, 32 and 64 bit. It should be down to the
individual arch teams to decide their policy and have it documented in
the devmanual (which some of them have done already).
--
Ciaran McCreesh
Mail: ciaranm at ciaranm.org
Web : http://ciaranm.org/
Paludis, the secure package manager : http://paludis.pioto.org/
signature.asc
Description: PGP signature
Re: [gentoo-dev] Re: Another council topic for Feb
On Sat, 3 Feb 2007 17:17:40 -0500
Mike Frysinger [EMAIL PROTECTED] wrote:
after all the pains we went through to enforce if you want to stabilize on
$ARCH, talk to the $ARCH team, how is this a good thing ?
I think Mike meant adding ~arch keywords - if you own and use ${ARCH} then
you may keyword your packages for ${ARCH}
(keyword, not stabilize)
As for the proposal itself, I'd add a suggestion to let the arch team know by
e-mail about it, so they can maintain general knowledge (better wording here,
probably) about their (~)keyword in the tree.
I don't think keywording happens often enough for these emails to become a
burden.
Kind regards,
--
Andrej Ticho Kacian ticho at gentoo dot org
Gentoo Linux Developer - net-mail, antivirus, sound, x86
signature.asc
Description: PGP signature
Re: [gentoo-dev] Re: Another council topic for Feb
On Saturday 03 February 2007, Andrej Kacian wrote: (keyword, not stabilize) keywording $ARCH and stabilizing mean the same thing to me -mike pgpWOeiXy7ljw.pgp Description: PGP signature
Re: [gentoo-dev] Re: Another council topic for Feb
On Sat, 3 Feb 2007 23:31:02 +0100 Andrej Kacian [EMAIL PROTECTED] wrote: As for the proposal itself, I'd add a suggestion to let the arch team know by e-mail about it, so they can maintain general knowledge (better wording here, probably) about their (~)keyword in the tree. Please do not change the policy to allow people who are not in arch teams to keyword anything for a given arch BEFORE getting approval from that arch team. This goes for any type of keyword. People did this before and it resulted in bad things, man. Yeah we may be sometimes slow to respond and a bit under staffed, but that burning hole in your committing pocket can wait. Cheers, -- Jason Wever Gentoo/Sparc Team Co-Lead signature.asc Description: PGP signature
Re: [gentoo-dev] Another council topic for Feb
On Sat, Feb 03, 2007 at 01:19:58PM -0800, Mike Doty wrote:
We're going to talk about arch keywording policies. IMO we should have
a standard policy if you own and use ${ARCH} then you may keyword your
packages for ${ARCH} with the exception of the sys-*/ categories.
Speakup now to get your input in.
Developers can just make an agreement with an architecture team if they
own such box.
I would not like to see random people marking random stuff stable on the
architectures that I am an arch team member on.
Ciaran gives some very good examples for MIPS and Sparc. I really think
this would be a bad idea.
Best regards,
Alex
--
Alexander Færøy
Bugday Lead
Alpha/IA64/MIPS Architecture Teams
User Relations, Quality Assurance
pgpQ2tK2lEx57.pgp
Description: PGP signature
[gentoo-dev] Last rites for app-portage/kentoo
As per summary: unfetchable, homepage 404ing, and pretty old, likely not working with current Portage system. Removal on March 4th. -- Diego Flameeyes Pettenò - http://farragut.flameeyes.is-a-geek.org/ Gentoo/Alt lead, Gentoo/FreeBSD, Video, Sound, ALSA, PAM, KDE, CJK, Ruby ... pgpJOP4y78v3U.pgp Description: PGP signature
[gentoo-dev] Last rites for www-client/khttrack
Alright, I start to feel like an undertaker, another package to remove. This one is in the tree since 2003, no more releases, the source tarball 404's and it's currently using an obsolete admindir with broken arts handling. Masked for removal in 30 days. -- Diego Flameeyes Pettenò - http://farragut.flameeyes.is-a-geek.org/ Gentoo/Alt lead, Gentoo/FreeBSD, Video, Sound, ALSA, PAM, KDE, CJK, Ruby ... pgpbcQf8e4Zal.pgp Description: PGP signature
