On 02/04/14 05:02, Matt Turner wrote:
On Tue, Apr 1, 2014 at 9:38 AM, Tom Wijsman tom...@gentoo.org wrote:
Projects like the Council, ComRel and QA are there to protect Gentoo;
and yes, people are (or should be) lining up to protect Gentoo.
... from QA.
You don't seem to understand what
On Tue, 1 Apr 2014 19:47:07 -0700
Matt Turner matts...@gentoo.org wrote:
On Tue, Apr 1, 2014 at 12:18 PM, hasufell hasuf...@gentoo.org wrote:
Tom... I am not sure if you know that, but your posts are difficult
to read. You split up posts horribly and I am often unable to
follow what you
On Tue, 1 Apr 2014 19:02:08 -0700
Matt Turner matts...@gentoo.org wrote:
On Tue, Apr 1, 2014 at 9:38 AM, Tom Wijsman tom...@gentoo.org wrote:
You don't seem to understand what Samuli is saying. QA is being used
as an offensive weapon. It's a stick to bludgeon others with.
Yes, I understood;
On Wed, 02 Apr 2014 09:00:19 +0300
Samuli Suominen ssuomi...@gentoo.org wrote:
On 02/04/14 05:02, Matt Turner wrote:
You don't seem to understand what Samuli is saying. QA is being used
as an offensive weapon. It's a stick to bludgeon others with.
Exactly. Anyone remembers what happened
On 02/04/14 11:28, Tom Wijsman wrote:
On Wed, 02 Apr 2014 09:00:19 +0300
Samuli Suominen ssuomi...@gentoo.org wrote:
On 02/04/14 05:02, Matt Turner wrote:
You don't seem to understand what Samuli is saying. QA is being used
as an offensive weapon. It's a stick to bludgeon others with.
On 1 April 2014 21:58, Alexandre Rostovtsev tetrom...@gentoo.org wrote:
On Tue, 2014-04-01 at 13:13 +0800, Ben de Groot wrote:
On 1 April 2014 06:16, Michał Górny mgo...@gentoo.org wrote:
Hello, all.
The late multilib ppc issues made me re-check our stable masks on
abi_x86_* flags and,
On 2 April 2014 07:38, Patrick Lauer patr...@gentoo.org wrote:
On 04/01/2014 01:13 PM, Ben de Groot wrote:
On 1 April 2014 06:16, Michał Górny mgo...@gentoo.org wrote:
Hello, all.
The late multilib ppc issues made me re-check our stable masks on
abi_x86_* flags and, honestly, I'm not sure if
Problem 1:
https://bugs.gentoo.org/show_bug.cgi?id=472766#c21
I'm not sure if wildcards are supported by /etc/sandbox.d/ files
Problem 2:
I don't know if this bug is ImageMagick+OpenCL _or_ OpenCL alone
specific since emacs
is having similar issues? Assistance required from emacs maintainer to
On Wed, 02 Apr 2014 11:29:28 +0300
Samuli Suominen ssuomi...@gentoo.org wrote:
On 02/04/14 11:28, Tom Wijsman wrote:
On Wed, 02 Apr 2014 09:00:19 +0300
Samuli Suominen ssuomi...@gentoo.org wrote:
On 02/04/14 05:02, Matt Turner wrote:
You don't seem to understand what Samuli is saying.
On Wed, Apr 2, 2014 at 5:58 AM, Jonathan Callen jcal...@gentoo.org wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 04/01/2014 10:03 AM, Kfir Lavi wrote:
On Mon, Mar 31, 2014 at 11:53 PM, Duncan 1i5t5.dun...@cox.net wrote:
Alexandre Rostovtsev posted on Mon, 31 Mar 2014
Am Mittwoch, 2. April 2014, 10:29:28 schrieb Samuli Suominen:
On 02/04/14 11:28, Tom Wijsman wrote:
On Wed, 02 Apr 2014 09:00:19 +0300
Samuli Suominen ssuomi...@gentoo.org wrote:
On 02/04/14 05:02, Matt Turner wrote:
You don't seem to understand what Samuli is saying. QA is being used
On 02/04/14 13:45, Andreas K. Huettel wrote:
Am Mittwoch, 2. April 2014, 10:29:28 schrieb Samuli Suominen:
On 02/04/14 11:28, Tom Wijsman wrote:
On Wed, 02 Apr 2014 09:00:19 +0300
Samuli Suominen ssuomi...@gentoo.org wrote:
On 02/04/14 05:02, Matt Turner wrote:
You don't seem to understand
On Wed 02 Apr 2014 13:01:25 Samuli Suominen wrote:
Problem 1:
https://bugs.gentoo.org/show_bug.cgi?id=472766#c21
I'm not sure if wildcards are supported by /etc/sandbox.d/ files
they are not. however, path matching is based on prefixes, so there's always
an implicit glob at the end.
On Wed 02 Apr 2014 17:14:02 Ben de Groot wrote:
On 1 April 2014 21:58, Alexandre Rostovtsev tetrom...@gentoo.org wrote:
On Tue, 2014-04-01 at 13:13 +0800, Ben de Groot wrote:
On 1 April 2014 06:16, Michał Górny mgo...@gentoo.org wrote:
Hello, all.
The late multilib ppc issues made
On Wed, 2014-04-02 at 17:25 +0800, Ben de Groot wrote:
I'm strongly considering reverting these changes in the packages I
maintain. I'm tired of having to deal time and again with multilib
breakage.
Either that, or someone else can take over primary maintainership.
Ben, if you are
On 02/04/14 16:01, Mike Frysinger wrote:
On Wed 02 Apr 2014 13:01:25 Samuli Suominen wrote:
Problem 1:
https://bugs.gentoo.org/show_bug.cgi?id=472766#c21
I'm not sure if wildcards are supported by /etc/sandbox.d/ files
they are not. however, path matching is based on prefixes, so there's
Samuli Suominen schrieb:
You are right
I believe this started after a major mesa version bump, so I'd start
looking for the culprit
in Mesa's OpenCL code, but I have no idea howto go futher with the
debugging... yet
The problem is finding a general way for OpenCL to force it to run on
the
The 30 days maintainer time out stabilization policy isn't working
when package has multiple SLOTs, because
the bugs are filed for only latest SLOT, where as some packages require
stabilization in sync at both SLOTs
Option 1:
Either revert the whole policy, and never CC arches on unanswered bugs
On Tue, 1 Apr 2014 20:58:30 -0400
Rich Freeman ri...@gentoo.org wrote:
On Tue, Apr 1, 2014 at 8:13 PM, Patrick Lauer patr...@gentoo.org
wrote:
Now let's just continue to ignore the existing multilib-portage
work so we can claim it's irrelevant, while shifting the conditions
for accepting
On Wed, Apr 2, 2014 at 12:52 PM, Samuli Suominen ssuomi...@gentoo.org wrote:
The 30 days maintainer time out stabilization policy isn't working
when package has multiple SLOTs, because
the bugs are filed for only latest SLOT, where as some packages require
stabilization in sync at both SLOTs
On 02/04/14 21:22, Mike Gilbert wrote:
On Wed, Apr 2, 2014 at 12:52 PM, Samuli Suominen ssuomi...@gentoo.org wrote:
The 30 days maintainer time out stabilization policy isn't working
when package has multiple SLOTs, because
the bugs are filed for only latest SLOT, where as some packages
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I'm just not sure what any of the randomly filed stablereqs are for.
It doesn't help anyone, unless the guy who filed it actually uses it
or if it is a blocker for another stabilization.
It's annoying me for some time now. I expect maintainers to
On Wed, Apr 2, 2014 at 3:28 PM, hasufell hasuf...@gentoo.org wrote:
I'm just not sure what any of the randomly filed stablereqs are for.
It doesn't help anyone, unless the guy who filed it actually uses it
or if it is a blocker for another stabilization.
It's annoying me for some time now. I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/01/2014 11:55 AM, Samuli Suominen wrote:
On 01/04/14 18:28, Tom Wijsman wrote:
On Tue, 01 Apr 2014 12:23:43 +
hasufell hasuf...@gentoo.org wrote:
And this is going to get worse if people don't trust them. Currently
it looks more like
Dnia 2014-04-02, o godz. 19:28:30
hasufell hasuf...@gentoo.org napisał(a):
I'm just not sure what any of the randomly filed stablereqs are for.
It doesn't help anyone, unless the guy who filed it actually uses it
or if it is a blocker for another stabilization.
It's annoying me for some
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/01/2014 02:41 PM, Samuli Suominen wrote:
On 01/04/14 21:33, Tom Wijsman wrote:
Okay, but this isn't what happened yet; because your plan was to send
out a mail after stabilization for everyone to adapt the reverse
dependencies, and I
On Wed, Apr 2, 2014 at 3:55 PM, Mike Gilbert flop...@gentoo.org wrote:
On the packages I maintain, I tend to use the latest unstable version
of the software. Stabilizing them rarely crosses my mind.
I rather like the semi-automated reminders. They come in handy for my
own packages, as well as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/02/2014 02:00 AM, Samuli Suominen wrote:
On 02/04/14 05:02, Matt Turner wrote:
On Tue, Apr 1, 2014 at 9:38 AM, Tom Wijsman tom...@gentoo.org wrote:
Projects like the Council, ComRel and QA are there to protect Gentoo;
and yes, people are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Ok, noted that other people like to have those reminders.
Rich Freeman:
Another option might be to have a tag in metadata.xml that flags
packages as never-stable or indicating that stabilization requires
coordination, which might help with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/24/2014 12:32 AM, Samuli Suominen wrote:
If it's okay, I'd want to post this fast, before adding KEYWORDS to
sys-fs/udev-209's ebuild
Should means required now? Man if I only knew that last week...
- -Zero
-BEGIN PGP SIGNATURE-
Hi,
www-apps/tt-rss is configured through a file config.php sitting
in its install directory. At the moment the file is overwritten
when upgrading with webapp-config. Who is responsible for
config-protecting this file?
a) the ebuild should install an env file (www-apps/otrs does this)
b) the
On 02/04/14 04:02 PM, Rich Freeman wrote:
Another option might be to have a tag in metadata.xml that flags
packages as never-stable
Arguments have been made that such packages do not belong in g-x86.
signature.asc
Description: OpenPGP digital signature
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/10/2014 07:29 PM, Gilles Dartiguelongue wrote:
Picking a random mail in the thread.
Making udev dependency always on is a deliberate choice here, as noted
by Alexandre, the library will be most likely useless without it and we
simply don't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Alex Xu:
On 02/04/14 04:02 PM, Rich Freeman wrote:
Another option might be to have a tag in metadata.xml that flags
packages as never-stable
Arguments have been made that such packages do not belong in
g-x86.
I did understand it the way
(picking this email to reply to, but it isn't mean to single anybody out)
On Wed, Apr 2, 2014 at 4:07 PM, Rick Zero_Chaos Farina
zeroch...@gentoo.org wrote:
Wow, now that I can see it your way I agree, I'm a horrible person.
I'll stick to randomly changing the tree as I see fit with no
On 02/04/14 23:07, Rick Zero_Chaos Farina wrote:
On 04/02/2014 02:00 AM, Samuli Suominen wrote:
On 02/04/14 05:02, Matt Turner wrote:
On Tue, Apr 1, 2014 at 9:38 AM, Tom Wijsman tom...@gentoo.org wrote:
Projects like the Council, ComRel and QA are there to protect Gentoo;
and yes,
On Wed, Apr 2, 2014 at 4:23 PM, Alex Xu alex_y...@yahoo.ca wrote:
On 02/04/14 04:02 PM, Rich Freeman wrote:
Another option might be to have a tag in metadata.xml that flags
packages as never-stable
Arguments have been made that such packages do not belong in g-x86.
Why not? In general I
On Wed, Apr 2, 2014 at 4:27 PM, Rick Zero_Chaos Farina
zeroch...@gentoo.org wrote:
Honestly I'd rather see this split up into libbluetooth and bluez than
make it possible to build a nearly entirely crippled bluez with no udev
support.
I think the right approach really depends on usefulness.
On 02/04/14 23:15, Rick Zero_Chaos Farina wrote:
On 02/24/2014 12:32 AM, Samuli Suominen wrote:
If it's okay, I'd want to post this fast, before adding KEYWORDS to
sys-fs/udev-209's ebuild
Should means required now? Man if I only knew that last week...
Sorry?
On Wed, Apr 2, 2014 at 2:25 AM, Ben de Groot yng...@gentoo.org wrote:
I'm strongly considering reverting these changes in the packages I
maintain. I'm tired of having to deal time and again with multilib
breakage.
Either that, or someone else can take over primary maintainership.
I'd be
Maybe it is just me, but I take the chance and responsibility.
This commit caused /usr/bin/clang being 32bit on my amd64 system. I
compiled it 3 times.
I have reverted the commit for the live ebuild, reverted it for 3.4-r1
and hardmasked 3.4 to ensure that people who unmasked 3.4 on stable arch
On 04/03/2014 12:52 AM, Samuli Suominen wrote:
The 30 days maintainer time out stabilization policy isn't working
when package has multiple SLOTs, because
the bugs are filed for only latest SLOT, where as some packages require
stabilization in sync at both SLOTs
Question: Why is the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 02/04/14 03:28 PM, hasufell wrote:
I'm just not sure what any of the randomly filed stablereqs are
for. It doesn't help anyone, unless the guy who filed it actually
uses it or if it is a blocker for another stabilization.
It's annoying me
43 matches
Mail list logo
