Re: [gentoo-dev] Monthly Gentoo Council Reminder for September
On Mon, Sep 01, 2008 at 05:30:01AM +, Mike Frysinger <[EMAIL PROTECTED]> wrote: > This is your monthly friendly reminder ! Same bat time (typically > the 2nd Thursday at 2000 UTC / 1600 EST), same bat channel > (#gentoo-council @ irc.freenode.net) ! > > If you have something you'd wish for us to chat about, maybe even > vote on, let us know ! Simply reply to this e-mail for the whole > Gentoo dev list to see. > > Keep in mind that every GLEP *re*submission to the council for review > must first be sent to the gentoo-dev mailing list 7 days (minimum) > before being submitted as an agenda item which itself occurs 7 days > before the meeting. Simply put, the gentoo-dev mailing list must be > notified at least 14 days before the meeting itself. > > For more info on the Gentoo Council, feel free to browse our homepage: > http://www.gentoo.org/proj/en/council/ If i am not too late then I wish to request the council consider bug 216219 and all it implies. Thanks, -- tomaw pgpkBLIYLgpFJ.pgp Description: PGP signature
Re: [gentoo-dev] Gentoo Council Reminder for August 7
Hi, For clarity, I am tomaw, a member of freenode staff. For even more clarity, I am a member of OFTC staff, although that's not relevant to this posting. I have spent many hours discussing this issue with Chrissy and others and feel some points require clarification. On Fri, 1 Aug 2008 08:39:41 -0700 "Chrissy Fullam" <[EMAIL PROTECTED]> wrote: > > Fair enough. Let me wrap up the IRC part. > > > > 1. I'd like to ask Council to discuss possible reactions to our > > developer being banned from Freenode without providing us with a > > reason. The situation looks like one of Freenode staffers > > overreacted over something Chris said during previous Council > > meeting and banned him to prevent him from attending next meetings > > when he was supposed to provide more information on the CoC topic. > > The ban was removed after an hour, > > The ban was put in place on Sunday; the ban was lifted on Tuesday > evening = way longer than one hour. Chris tried to speak to Freenode > staff on Freenode but was told he was evading the ban and they would > not speak to him there. He had to find out from me what the email I have previously indicated on IRC that the omission of the email address to respond to with questions about klines in this kline message was a mistake. He did not have to find out which email address to use from you. I told him myself. I am quite upset that you did not feel it prudent to indicate that we admit this mistake in your email. > address was (as it's not documented on Freenode's site) and email > them to ask why he was banned. Christel responded later that day and > simply apologized and removed the ban. Chris again emailed to ask > *why* he was banned but Freenode staff has ignored his second email > requesting information about his own ban. I responded personally to this request. I did consider writing another response earlier today asking for more time due to staff availability but decided doing so was overly verbose. If your personal knowledge of the person in question indicates that he prefers more verbose interaction please have him convey this to us and I will be happy to help. > To me it looks like they > not only will not tell us, they will not tell the individual who was > actually banned and that is in poor professional taste and only > further serves to drive a wedge between our ability to work with > Freenode. freenode can currently only discuss this with the person banned due to legal issues. I am not a lawyer, but I suspect much of what fmccor said to be true. > > 2. I want Council to consider moving their meetings somewhere where > > third parties can't control who in Gentoo can attend and who can't. > > This is an interesting idea. Perhaps a good trial for a transition? > > > 3. I want Council to consider creating and using irc.gentoo.org > > alias instead of irc.freenode.net in our docs, news items and so > > on. > > Seems pretty logical so I just want to say that I like this whoever > came up with this. :) This seems sensible. Thanks, -- Tom Wesley <[EMAIL PROTECTED]> signature.asc Description: PGP signature
Re: [gentoo-dev] Commits filtering procmail recipes
On Sun, Sep 30, 2007 at 01:26:57AM -0700, Donnie Berkholz <[EMAIL PROTECTED]> wrote: > Hey all, > > Here's my .procmailrc chunks relevant to filtering -commits. I've got > some for filtering specific to developers and some for > categories/packages. It also has a nice bit that cuts out everything > that isn't an ebuild bump (aka keywording and such). > > Thanks, > Donnie Perfect! I was planning on writing similar rules myself, you saved me most of the work. -- tomaw pgpSFWksYcVuG.pgp Description: PGP signature
Re: [gentoo-dev] ML changes
On Thu, Jul 12, 2007 at 10:31:31PM +0200, Bryan Østergaard <[EMAIL PROTECTED]> wrote: > Degrading non-dev contributers like myself to second-class > citizens is definitely not going to make me want to contribute > anything more. +1 This move would be shooting Gentoo in the foot, in my opinion. -- tomaw pgp0UnZh8Lq3W.pgp Description: PGP signature
Re: [gentoo-dev] Pre-Last Rites: net-irc/bitchx
On Thu, Jul 05, 2007 at 01:48:20PM +0200, Luca Barbato <[EMAIL PROTECTED]> wrote: > > is there a script to mimic bx in irssi or epic5? > > lu There are specific scripts to minic specific functionality, so whatever you're missing can probably be replicated. Find a #irssi :) tomaw pgpmZ7Wi0XvfU.pgp Description: PGP signature
Re: [gentoo-dev] New (old) Developer: Deedra Waters (dmwaters)
On Mon, Jun 04, 2007 at 06:08:48PM +0200, Christian Heim <[EMAIL PROTECTED]> wrote: > > It's my pleasure to welcome back Deedra Waters (also known as dmwaters on > IRC). Welcome back Deedra :) tomaw pgp4cdwpBVWlW.pgp Description: PGP signature
Re: [gentoo-dev] comments on how flamewars are handled elsewhere
On Thu, Mar 08, 2007 at 02:50:11PM +0100, [EMAIL PROTECTED] wrote: > Hi, > > to place my personal opinion, too but seperated from information/facts: > > I feel like a netiquette should be developed, people who break it too often > should be warned, then banned. > When the situation normalizes again, there will be no banning anymore anyway > automatically. > > Would be nice to know how others feel, wether something should be changed or > (why) not, and if so, what ideas are like. > > Doing this quick overview showed (even though I never mentioned Gentoo > myself) > that the message of Gentoo and it's mailinglists spreaded quickly on IRC, > which is something else I dislike to see... > Please could you stop attempting to create new threads by replying to existing emails to the list? It's considered bad netiquette and generally makes new threads difficult to spot. The list is hard enough to parse as it is, without this added hindrance. http://en.wikipedia.org/wiki/Thread_hijacking has the details if it is something you're unaware of. Tom pgpHVR2tw6yYd.pgp Description: PGP signature
Re: [gentoo-dev] The long story behind our new developer: Peter Weller (welp)
On Tue, 19 Dec 2006 14:59:09 +0100 Markus Ullmann <[EMAIL PROTECTED]> wrote: snip > > Now you know the story behind our new amd64/bugday/xfce dev from UK. I > think he deserves the usual happy welcome :) > > Jokey > Welcome, welp. Hopefully you'll spend hours every week enhancing my xfce experience. -- tomaw -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Resignation
On Sat, Oct 07, 2006 at 09:19:14PM +, Tim Yamin <[EMAIL PROTECTED]> wrote: > All, > > I'm afraid that I find that my position with Gentoo is no longer > tenable. Over the past year and especially over the past few months > Sorry to see you leave. Good luck. tomaw. > pgpsUI71BNcK3.pgp Description: PGP signature
Re: [gentoo-dev] Re: Improving Gentoo User Relations
On Fri, 7 Apr 2006 11:37:01 +0100 Jonathan Coome <[EMAIL PROTECTED]> wrote: > I think planet.gentoo.org helps in this regard, but there could be a > lot more done to keep end users aware of what's going on. > It certainly does, but having some way to further organise this information by package or area of interest rather than developer would be very useful. Perhaps this information could somehow by used to enhance the previously discussed news reporting features to include progress information for future work as well as information about changes that have already been committed. It will need more thought and discussion, but it might work quite nicely. -- Tom Wesley <[EMAIL PROTECTED]> -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Keywording, for the umpteenth time
On Fri, 2005-05-20 at 22:22 +0100, Ciaran McCreesh wrote: > Not gonna happen. Emulators don't cut it and won't find all the problems > (but they will find a load of other bogus non-issues). Plus, from > experience I'd say that at least half our devs wouldn't have a clue > where to start when doing arch testing... Add this HOWTO arch test to your developer docs. Very nice by the way. > Then there's the issue of most alt-archs having far higher QA standards > than x86 anyway, and us not wanting to sink to what x86 considers > acceptable for marking stable. > > From experience -- the current policy as it is now *works*, so long as > everyone follows it. And as long as ciaranm, or someone from a non x86 arch bitches once a month here. -- Tom Wesley <[EMAIL PROTECTED]> signature.asc Description: This is a digitally signed message part
Portage bitching out loud [Re: [gentoo-dev] List of packages which 'inherit gcc']
On Sun, 2005-05-15 at 17:21 -0400, Mike Frysinger wrote: > On Sunday 15 May 2005 05:11 pm, Michael Cummings wrote: > > Would have been nice to get this email before portage started griping a day > > or so ago. > > portage isnt griping, gcc.eclass is because i put it there > > besides, i didnt use caps and i said 'Please', so it's just a friendly > notice ! > -mike Can portage moaning about various validation that end users don't care about be made a FEATURE? I hate upgrading package-x and the guy standing over my shoulder seeing "Invalid blah blah". -- Tom Wesley <[EMAIL PROTECTED]> signature.asc Description: This is a digitally signed message part
Re: [gentoo-dev] i have an idea ! (erescue)
On Sun, 2005-05-15 at 17:18 -0400, Mike Frysinger wrote: > one advantage that other binary based package managers have over Gentoo is > ease of recovery from broken core packages ... break your gcc ? no problem ! > > simply do `apt-get install gcc` or `rpm -i gcc` or whatever > > my proposal is to implement a new utility (called 'erescue' for lack of a > better name) that is written in C and designed to be statically linked ... > then next time you break a core system package which cannot be recovered by > simply running `emerge` a few times, you run `erescue ` > > for example, when i broke binutils in unstable with a gcc4 patch, i noticed > that it's hard for users to *easily* recover from this ... we developers end > up scrambling to build a bunch of binary packages for a variety of compatible > compiler/libc combinations so the user can just wget the file and run `emerge > binutils.tbz2` and be on their way > > the packages that would be eligible for an 'erescue' package would be just > about everything when you do `USE=-* emerge system -ep` ... i'm sure we can > trim many of those out though :) maybe even create a new USE flag for some > of these core packages so that we can trim out more files > > the idea would be to create very bare min packages so that the user can > simply > 'rescue' themselves ... after that, they it's up to them to re-emerge the > package to apply all their fun ricer-optimizations as they see fit > > i dont think it'd be too hard to integrate this 'rescue set' into a catalyst > target so that it'll become part of our normal release schedule of stage > tarballs > -mike This would really help me at work, as I generally have to partimage my workstation PC before updates that might break stuff. I nominate "ecockup-reverse" as the name. -- Tom Wesley <[EMAIL PROTECTED]> signature.asc Description: This is a digitally signed message part
Re: [gentoo-dev] New global USE flag: logrotate
On Thu, 2005-04-28 at 10:30 +0200, Henrik Brix Andersen wrote: > Hi, > > I'd like to propose a new global USE flag named 'logrotate' to add > support for app-admin/logrotate (by installing logrotate config files > to /etc/logrotate.d/). > > There are currently one local USE flag named logrotate in > net-proxy/squid, which of course isn't enough to justify having a global > USE flag - but it seems other packages, at least app-admin/syslog-ng, > currently unconditionally install a config file to /etc/logrotate.d/. > > There are 4 open enhancement requests in Gentoo bugzilla about ebuilds > which could install such a config file, and I am sure many other ebuilds > could as well (anything that logs to a file). > > If there are no objections to this I will make 'logrotate' a global USE > flag once I add a logrotate config file to sys-power/acpid. > > Sincerely, > Brix I would welcome such a flag. -- Tom Wesley <[EMAIL PROTECTED]> signature.asc Description: This is a digitally signed message part
Re: [gentoo-dev] Portage ebuild cruft
On Thu, 2005-04-28 at 18:40 +0200, Heinrich Wendel wrote: > Hi, > > Portage is slow? How to make it faster? By removing unused ebuilds! > > I wrote a little script to check which ebuilds in portage aren't used > anylonger, here the result: > > Total packages checked: 9076 > Total ebuilds checked: 18662 > Total ebuilds to remove: 4643 > > Of course the script can't detect every ebuild situation, so take the numbers > with care. But still it shows that 1/4 of all ebuilds could be removed. This > would improve portage performance by at least 1/4, so developers go ahead. > The script is attached, just run it as if it was repoman, it won't do > anything, just show the orphaned packages. > > mfg, heinrich :-) I feel that I should point out that "large style" corporations, and the smaller PLC's whose Systems departments like to play at being larger corporations don't like changing version numbers of packages, full stop. Purging old versions for a few seconds speed increase in portage operations would potentially cause some, if not many people to make extensive use of the overlay, just to satisfy their PHB's. -- Tom Wesley <[EMAIL PROTECTED]> signature.asc Description: This is a digitally signed message part
