On 11/03/2012 09:29 PM, Ben de Groot wrote:
On 4 November 2012 08:28, Ian Stakenvicius a...@gentoo.org wrote:
03.11.12 09:04, Ben de Groot написав(ла):
I think we need to come up with a better policy regarding elog
messages, which would improve the signal to noise ratio.
As of EAPI=4 (i
On 31 October 2012 23:17, Chris Reffett creff...@gentoo.org wrote:
Basically, I would rather the user get too many
elog messages than not enough, since I feel that a lot of people skip
over them anyway and so the only display once method makes it far
too easy for important messages to get lost
03.11.12 09:04, Ben de Groot написав(ла):
On 31 October 2012 23:17, Chris Reffett creff...@gentoo.org wrote:
Basically, I would rather the user get too many
elog messages than not enough, since I feel that a lot of people skip
over them anyway and so the only display once method makes it far
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 03/11/12 08:19 PM, Jauhien Piatlicki wrote:
03.11.12 09:04, Ben de Groot написав(ла):
On 31 October 2012 23:17, Chris Reffett creff...@gentoo.org
wrote:
Basically, I would rather the user get too many elog messages
than not enough, since I
On 4 November 2012 08:28, Ian Stakenvicius a...@gentoo.org wrote:
03.11.12 09:04, Ben de Groot написав(ла):
I think we need to come up with a better policy regarding elog
messages, which would improve the signal to noise ratio.
As of EAPI=4 (i think? maybe 3?) ebuild authors can use a simple
On Wed, Oct 31, 2012 at 5:08 PM, Jeroen Roovers j...@gentoo.org wrote:
Though if you don't know these kinds of basics, I'm not sure you
should be doing *any* (semi- or not) automated bug filing.
What if you don't have the privilege to assign bugs, but are willing to
do the work of filing the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/01/2012 03:59 AM, Dirkjan Ochtman wrote:
On Wed, Oct 31, 2012 at 5:08 PM, Jeroen Roovers j...@gentoo.org wrote:
Though if you don't know these kinds of basics, I'm not sure you
should be doing *any* (semi- or not) automated bug filing.
What
On Thu, Nov 1, 2012 at 7:59 AM, Dirkjan Ochtman d...@gentoo.org wrote:
On Wed, Oct 31, 2012 at 5:08 PM, Jeroen Roovers j...@gentoo.org wrote:
Though if you don't know these kinds of basics, I'm not sure you
should be doing *any* (semi- or not) automated bug filing.
What if you don't have the
On Thu, 1 Nov 2012 08:59:09 +0100
Dirkjan Ochtman d...@gentoo.org wrote:
What if you don't have the privilege to assign bugs, but are
willing to do the work of filing the bugs?
Yeah, that kind of sucks. Perhaps we should extend the privilege a
little more often?
In this case no prior
Simply look at the metadata.xml files which can be found in each
package directory.
Though if you don't know these kinds of basics, I'm not sure you
should be doing *any* (semi- or not) automated bug filing.
Cheers,
Dirkjan
On Wed, Oct 31, 2012 at 1:34 PM, Marco Poletti poletti.ma...@gmail.com
2012/10/31 Dirkjan Ochtman d...@gentoo.org:
That's rather unsurprising...
If you're going to file bugs in a semi-automated manner, might as
well try to assign to the correct maintainer?
Yep he should've assign them, but anyway the annoying elog messages
are an issue. And quite few packages
On Wed, Oct 31, 2012 at 8:31 AM, Dirkjan Ochtman d...@gentoo.org wrote:
If you're going to file bugs in a semi-automated manner, might as
well try to assign to the correct maintainer?
How about a policy - no automated bugs may be logged to the bug
wranglers without their prior approval/review.
The php herd is the maintainer, so you should php-b...@gentoo.org (the
herd-to-email mapping can probably be found elsewhere).
Still, please get more of a feeling for how the Portage tree is put
together before doing more automated bug filing, please.
Cheers,
Dirkjan
On Wed, Oct 31, 2012 at
Maybe you should remember that non-devs simply /aren't allowed/ to
assign bugs correctly...
And if you look closer into these bugs, you might discover that jer
instructed this guy to file separate bugs. (see #440178)
aranea
signature.asc
Description: PGP signature
On Wed, Oct 31, 2012 at 9:18 AM, li...@aixah.de wrote:
Maybe you should remember that non-devs simply /aren't allowed/ to
assign bugs correctly...
And if you look closer into these bugs, you might discover that jer
instructed this guy to file separate bugs. (see #440178)
Fair points, and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/31/2012 08:52 AM, Tomáš Chvátal wrote:
2012/10/31 Dirkjan Ochtman d...@gentoo.org:
That's rather unsurprising...
If you're going to file bugs in a semi-automated manner, might
as well try to assign to the correct maintainer?
Yep he
On Wed, 31 Oct 2012 13:49:37 +0100
Dirkjan Ochtman d...@gentoo.org wrote:
Though if you don't know these kinds of basics, I'm not sure you
should be doing *any* (semi- or not) automated bug filing.
What if you don't have the privilege to assign bugs, but are willing to
do the work of filing
On 10/31/2012 10:05 AM, Rich Freeman wrote:
On Wed, Oct 31, 2012 at 9:18 AM, li...@aixah.de wrote:
Maybe you should remember that non-devs simply /aren't allowed/ to
assign bugs correctly...
And if you look closer into these bugs, you might discover that jer
instructed this guy to file
On Wed, Oct 31, 2012 at 02:18:42pm +0100, li...@aixah.de wrote:
maybe you should remember that non-devs simply /aren't allowed/ to
assign bugs correctly...
That is not correct. I am no dev and i do have edit-bugs privileges.
They were given to me on request by a developer from a project i am
Quoting Chris Reffett (2012-10-31 16:17:20)
Yep he should've assign them, but anyway the annoying elog messages
are an issue. And quite few packages suffer from it :-)
It would actually be hard to find useful message which place is in elog
showing up every install. Why not move such thing on
On Wed, Oct 31, 2012 at 5:54 AM, Rich Freeman ri...@gentoo.org wrote:
On Wed, Oct 31, 2012 at 8:31 AM, Dirkjan Ochtman d...@gentoo.org wrote:
If you're going to file bugs in a semi-automated manner, might as
well try to assign to the correct maintainer?
How about a policy - no automated bugs
21 matches
Mail list logo
