Re: Why is Bugzilla dead?
[EMAIL PROTECTED] said: > I've always wondered about those supermen, sometimes referred to as > RH engineers. Having about a dozen/half a dozen people manage about > 500 packages is no picnic. 1) It depends on how you count (I was going to do a rpm -qa | wc -l to see how many I have installed), but I think there are considerably more than 500 packages, and some of the packaging is passing strange (the contents of kdebase for starters). 2) That said, there's a great number of packages where there's not much action and which consequently don't require much attention. Probably the most volatile packages are components of gnome and kde. ___ Redhat-devel-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-devel-list
Re: Why is Bugzilla dead?
On Mon, 20 Nov 2000 [EMAIL PROTECTED] wrote: > On Mon, Nov 20, 2000 at 03:00:23PM +0300, Alex Kanavin wrote: > > On Sun, 19 Nov 2000 [EMAIL PROTECTED] wrote: > > > > > Maybe select outside contributors should have write-access to the tree - or is > > > that already the case? It would open up development and allow bugs to be fixed > > > faster, features to be added faster, a la Debian. No? > > > > Yeah, leave crucial stuff to RH and let others mantain the rest of the > > packages seems like a nice idea to me too. Especially if RH can find a way > > to pay them some money, not full salaries, but, well, something. > > I suppose we have two suggestions then, because I'm not suggesting paying anyone > anything. But it may be possible to get more benefit from the community than Red > Hat is currently getting. > > Zack My opinion about the latter: paying complicates things considerably. If you prefer that way, perhaps you should send your application to RH. ;-) Community is more about team effort, and fiddling with stuff that interest you anyway. --- Well.. I'd be _really_ glad about just the read access. Rawhide snapshots (really, new RPMs) aren't generated often enough (IMO), and I'd really like to help in testing those security fixes too (usually QA takes a week or so) before the final version is released. I've always wondered about those supermen, sometimes referred to as RH engineers. Having about a dozen/half a dozen people manage about 500 packages is no picnic. Surely there would be something to be gained from the community. As it is, this is limited to creating good Bugzilla reports, commenting them, attaching patches etc. This is considerable help, I nonetheless, but it _could_ be more. However, there's always a problem with a _commercial_ organization getting direct help/commit from outsiders. They're the ones responsible if something hits the fan. There are some other issues with this too. I'd like to know if there is _any_ company that'd let "outsiders" make direct commits.. Not that this has to be the way it is though. One of the greatest potentials of GPL + Linux etc. is the effort of the community. It should not be wasted -- but is there any real way how it could be used without problems? -- Pekka Savola "Tell me of difficulties surmounted, [EMAIL PROTECTED] not those you stumble over and fall" ___ Redhat-devel-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-devel-list
Re: Why is Bugzilla dead?
On Mon, Nov 20, 2000 at 03:00:23PM +0300, Alex Kanavin wrote: > On Sun, 19 Nov 2000 [EMAIL PROTECTED] wrote: > > > Maybe select outside contributors should have write-access to the tree - or is > > that already the case? It would open up development and allow bugs to be fixed > > faster, features to be added faster, a la Debian. No? > > Yeah, leave crucial stuff to RH and let others mantain the rest of the > packages seems like a nice idea to me too. Especially if RH can find a way > to pay them some money, not full salaries, but, well, something. I suppose we have two suggestions then, because I'm not suggesting paying anyone anything. But it may be possible to get more benefit from the community than Red Hat is currently getting. Zack > > The reason I write this is: I submitted a bug report about ppp-watch more > than 4 months ago (#14071). It does include a patch of mine. And it's > still marked as NEW without any comments. C'mon Red Hat people, you can't > be THAT busy. > > -- > Alexander > > Homepage: http://www.sensi.org/~ak/ > > > > > ___ > Redhat-devel-list mailing list > [EMAIL PROTECTED] > https://listman.redhat.com/mailman/listinfo/redhat-devel-list -- -- Zack Brown, Linuxcare, Inc. tel: 1-415-354-4878x284, fax: 1-415-701-7457 [EMAIL PROTECTED], http://www.linuxcare.com/ Linuxcare. Support for the revolution. ___ Redhat-devel-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-devel-list
Re: Problem with man and makewhatis: Broken pipe errors
> Hello all, > > Mmm. It seems zoot-list requires subscribtion. Anyway, this seems like a I think that's true of all lists@redhat. > little more generic issue, so here we go... redhat-list? (requires subscription) > --- > > This has plagued me on a lot of systems ranging from RH60 to RH62, all > up-to-date. > > 'man perl' [then 'q' immediately] gives output like: > --- > Formatting page, please wait... > :203: warning: can't break line man page is not formatted properly. You can probably still read it. > > gunzip: stdout: Broken pipe > --- or --- > > gunzip: stdout: Broken pipe > > gunzip: stdout: Broken pipe > --- gzip ws decompressing something (quite likely from a pipe) into a pipe. It died when the program on the other end of the pipe (less) quit (you typed q). > > On the other hand, some other pages work ok, e.g. h2ph. Smaller? > > Running /usr/sbin/makewhatis shows hundreds of Broken pipe errors in zcat; > -v flag will show which. These are also broken if used with 'man'. > > This doesn't seem to be a problem on RHL7. > > Anyone else notice this? It's not really a problem in RHL 6.x either. Just a cosmetic thing. Perhaps it annoyed someone who could fix it so they did? ___ Redhat-devel-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-devel-list
Problem with man and makewhatis: Broken pipe errors
Hello all, Mmm. It seems zoot-list requires subscribtion. Anyway, this seems like a little more generic issue, so here we go... --- This has plagued me on a lot of systems ranging from RH60 to RH62, all up-to-date. 'man perl' [then 'q' immediately] gives output like: --- Formatting page, please wait... :203: warning: can't break line gunzip: stdout: Broken pipe --- or --- gunzip: stdout: Broken pipe gunzip: stdout: Broken pipe --- On the other hand, some other pages work ok, e.g. h2ph. Running /usr/sbin/makewhatis shows hundreds of Broken pipe errors in zcat; -v flag will show which. These are also broken if used with 'man'. This doesn't seem to be a problem on RHL7. Anyone else notice this? -- Pekka Savola "Tell me of difficulties surmounted, [EMAIL PROTECTED] not those you stumble over and fall" ___ Redhat-devel-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-devel-list
Re: carriage return
Pranita S <[EMAIL PROTECTED]> writes: > We use CVS as our source control system. In this case, you probably want to remove the carraige returns from the repository and let the NT version of CVS put them back when checking things out. The linux version of CVS will not strip ^Ms, afaik. Where are you storing your CVS repository? It should probably be using a CVS server instead of file access... that gets messy. -- Alan Shutko <[EMAIL PROTECTED]> - In a variety of flavors! 2 hours, 9 seconds till we run away. Sir, I would rather have my problem than yours. ___ Redhat-devel-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-devel-list
Re: Why is Bugzilla dead?
On Sun, 19 Nov 2000 [EMAIL PROTECTED] wrote: > Maybe select outside contributors should have write-access to the tree - or is > that already the case? It would open up development and allow bugs to be fixed > faster, features to be added faster, a la Debian. No? Yeah, leave crucial stuff to RH and let others mantain the rest of the packages seems like a nice idea to me too. Especially if RH can find a way to pay them some money, not full salaries, but, well, something. The reason I write this is: I submitted a bug report about ppp-watch more than 4 months ago (#14071). It does include a patch of mine. And it's still marked as NEW without any comments. C'mon Red Hat people, you can't be THAT busy. -- Alexander Homepage: http://www.sensi.org/~ak/ ___ Redhat-devel-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-devel-list
