On Friday 16 December 2011 11:42:15 justin wrote:
Hi,
I really like that you open all those bugs. But it makes no sense to add
arches after a time out.
Personally, I agree with have more stable packages in tree, but I just point
out one thing. If me, or another arch tester find ebuild
On 12/16/2011 06:06 AM, Agostino Sarubbo wrote:
On Friday 16 December 2011 11:42:15 justin wrote:
Hi,
I really like that you open all those bugs. But it makes no sense to add
arches after a time out.
Personally, I agree with have more stable packages in tree, but I just
point
out one
# Johannes Huber j...@gentoo.org (16 Dec 2011)
# Masked for removal in 30 days. Dead upstream. Package
# is not full functional. Last release was on 2010-01-14.
# See bug #394881
kde-misc/kcheckgmail
--
Johannes Huber (johu)
Gentoo Linux Developer / KDE Team
GPG Key ID F3CFD2BD
signature.asc
On Friday 16 December 2011 06:10:13 Anthony G. Basile wrote:
Does your script do any checking on the quality of the ebuild, eg that
it respects C/LDFLAGS. If so, that's useful and would help package
maintainers to better prepare their ebuilds for stabilization.
Unfortunately no.
For LDFLAGS
On 12/16/11 12:21 PM, Agostino Sarubbo wrote:
On Friday 16 December 2011 06:10:13 Anthony G. Basile wrote:
Does your script do any checking on the quality of the ebuild, eg that
it respects C/LDFLAGS. If so, that's useful and would help package
maintainers to better prepare their ebuilds for
On 12/16/11 11:42 AM, justin wrote:
I really like that you open all those bugs. But it makes no sense to
add arches after a time out. At least not after a such a short
one.
I'm sorry this has annoyed/upset you. Let me just point out some facts:
- in November I first wrote about this new
On Fri, Dec 16, 2011 at 8:27 AM, Paweł Hajdan, Jr.
phajdan...@gentoo.org wrote:
- people complain that a week-long timeout is too short, while after I
CC arches the answer often comes within minutes.
So, I agree with pretty-much everything you said, and I completely
agree that
That said, there is probably room for debate over the length of time
we leave the bug open. Maybe a week isn't quite long enough - maybe
two weeks is better.
I'd like to support that suggestion. The new process is a great thing, just
give us a little bit more time to respond please... :)
On 12/16/11 2:27 PM, Paweł Hajdan, Jr. wrote:
On 12/16/11 11:42 AM, justin wrote:
I really like that you open all those bugs. But it makes no sense to
add arches after a time out. At least not after a such a short
one.
I'm sorry this has annoyed/upset you. Let me just point out some
On 2011-12-16 Fri 06:05, Andreas K. Huettel wrote:
That said, there is probably room for debate over the length of time
we leave the bug open. Maybe a week isn't quite long enough - maybe
two weeks is better.
When you do timeout a bug and assign it to arches, it would be great if
you could
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 12/12/2011 05:44 PM, Tomas Chvatal (scarabeus) wrote:
scarabeus11/12/12 17:44:48
Modified: ChangeLog Added:
libreoffice-3.4.99.1.ebuild Removed:
libreoffice-3.5.0.0.ebuild Log: Remove miss-named beta0. Add beta1
with better
On Friday 16 December 2011 02:29:25 Steven J Long wrote:
Mike Frysinger wrote:
+ [[ $# -eq 0 ]] die estack_push: incorrect # of arguments
((..)) is quicker than [[ .. ]] for arithmetic stuff, and usually easier to
grok swiftly.
i'm not used to using this style, so for now i think i'll
On Wednesday 14 December 2011 14:18:46 Samuli Suominen wrote:
I guess we can remove the ChangeLog from eclass/ directory since only
small portition of people seem to use it.
i wasn't doing this on purpose ... just hadn't really noticed the ChangeLog in
there. i'm skeptical of its usefulness
13 matches
Mail list logo