On 31/10/2012 23:42, Peter Stuge wrote:
> Can you clarify? Do you propose that developers carry out wild
> experiments by committing things that probably don't work and
> masking them?
Dirty experiments, no. Testing stuff that's almost ready, yes. If you
run the tinderbox against dirty experiments
Diego Elio Pettenò wrote:
> > Um, so how come an overlay isn't the obvious method for testing,
> > before putting things in the main tree? What other method is *more*
> > convenient for testing?
>
> package.mask
Can you clarify? Do you propose that developers carry out wild
experiments by committ
On 31/10/2012 23:18, Peter Stuge wrote:
> Um, so how come an overlay isn't the obvious method for testing,
> before putting things in the main tree? What other method is *more*
> convenient for testing?
package.mask
> Diego, I would like to ask you to step off Arfrever.
And I would like that dev
Diego Elio Pettenò wrote:
> > One of major problems with this tinderbox is that it cannot be
> > used to test packages against newer versions of packages present
> > in overlays [1]
>
> Which is not a problem since we're _not_ talking about packages
> in overlays but of a bump in the main tree whi
On 30/10/2012 20:18, Arfrever Frehtes Taifersar Arahesis wrote:
> One of major problems with this tinderbox is that it cannot be used
> to test packages against newer versions of packages present in
> overlays [1]
Which is not a problem since we're _not_ talking about packages in
overlays but of a
2012-10-31 04:18:14 Arfrever Frehtes Taifersar Arahesis napisał(a):
> Besides founding problems in about 10% of packages
s/founding/finding/
--
Arfrever Frehtes Taifersar Arahesis
signature.asc
Description: This is a digitally signed message part.
2012-10-29 23:07:15 Diego Elio Pettenò napisał(a):
> c) try to get betas and rcs in asap _but masked_;
>=sys-devel/gcc-4.7.0, whose usage is required to trigger some problems, is
>already package.masked.
> d) call for a tinderbox run (I can do that with a quick email);
One of major problems wit
On Mon, Oct 29, 2012 at 5:17 PM, Alexis Ballier wrote:
> On Mon, 29 Oct 2012 15:07:15 -0700
> Diego Elio Pettenò wrote:
>
> [...]
>> d) call for a tinderbox run (I can do that with a quick email);
>
> For that part, I think everyone would benefit from an official
> tinderbox, infra-hosted and wit
On Mon, 29 Oct 2012 15:07:15 -0700
Diego Elio Pettenò wrote:
[...]
> d) call for a tinderbox run (I can do that with a quick email);
For that part, I think everyone would benefit from an official
tinderbox, infra-hosted and with a documented interface; not everyone
has the horsepower to build li
On 29/10/2012 14:37, Anthony G. Basile wrote:
>
> Anyhow, the question really remains, how to "deeply" test this package
> before adding it to the tree even ~arch?
a) check that there is nothing depending on =${oldver} — if there is,
notify maintainer;
b) check the documentation to see if there i
On 10/29/2012 04:59 PM, Diego Elio Pettenò wrote:
On 29/10/2012 13:19, Anthony G. Basile wrote:
I just generated the list of dependencies, 28 packages, see below.
Compile tests against each are easy enough. Run tests against
non-library packages are easy too. It would be harder to do an
exhaus
On 29/10/2012 13:19, Anthony G. Basile wrote:
> I just generated the list of dependencies, 28 packages, see below.
> Compile tests against each are easy enough. Run tests against
> non-library packages are easy too. It would be harder to do an
> exhaustive test against, say, dev-libs/boost becau
On 10/29/2012 03:45 PM, Mike Gilbert wrote:
On Mon, Oct 29, 2012 at 3:33 PM, Christoph Junghans wrote:
2012/10/29 Diego Elio Pettenò:
On 29/10/2012 10:37, Christoph Junghans wrote:
If Arfrever keeps maintaining it for a while, I will take it.
Do remember that whatever you commit, _You_ take
On Mon, Oct 29, 2012 at 3:33 PM, Christoph Junghans wrote:
> 2012/10/29 Diego Elio Pettenò :
>> On 29/10/2012 10:37, Christoph Junghans wrote:
>>> If Arfrever keeps maintaining it for a while, I will take it.
>>
>> Do remember that whatever you commit, _You_ take responsibility for it.
>> After a
On Mon, 2012-10-29 at 11:35 -0700, Diego Elio Pettenò wrote:
> The problem with ICU is worse than you expect. For once, with version
> 50, it changes ABI (but not soname as far as I can tell) depending on
> which compiler you build it with. Yes, this is pretty much fucked up.
It's even worse than
2012/10/29 Diego Elio Pettenò :
> On 29/10/2012 10:37, Christoph Junghans wrote:
>> If Arfrever keeps maintaining it for a while, I will take it.
>
> Do remember that whatever you commit, _You_ take responsibility for it.
> After a screwup, the answer "I didn't do anything, I just committed what
>
On Mon, 29 Oct 2012 19:30:40 +0100
Peter Stuge wrote:
> Diego Elio Pettenò wrote:
> > the understanding of "you're responsible for whatever you commit".
>
>> Outrageours rant deleted <<
> Isn't it outrageous to claim that people who create and
> contribute to and around Gentoo without being de
On Mon, Oct 29, 2012 at 2:40 PM, Diego Elio Pettenò
wrote:
> You're free to disagree and not become a developer. But with commit
> _rights_ come commit _responsibility_. If you commit something for
> somebody else, you're still responsible if it breaks somebody else's
> package, it doesn't exempt
On Mon, Oct 29, 2012 at 2:30 PM, Peter Stuge wrote:
> I expect that anyone and everyone who contribute to any open source
> project will do their damndest to contribute only "perfect" work.
Setting aside issues of tone, I want to touch on the more direct issue
of "quality" and "perfection."
I do
On 29/10/2012 11:30, Peter Stuge wrote:
> A load of bull IMO. Is this rooted in some stupid US law thing (via
> the foundation) or merely in some cowardly individual disconnected
> from the real world, phrasing stupid blanket rules? Or something else?
You're free to disagree and not become a devel
On 29/10/2012 11:10, Rich Freeman wrote:
> While I do agree in principle, I think that talking about going to
> devrel over "minor inconsistencies" is over-the-top.
It's not about the inconsistencies, it's about the excuse. If the
maintainer owns up to the mistake, that's fine by me, shit happens
Diego Elio Pettenò wrote:
> the understanding of "you're responsible for whatever you commit".
A load of bull IMO. Is this rooted in some stupid US law thing (via
the foundation) or merely in some cowardly individual disconnected
from the real world, phrasing stupid blanket rules? Or something els
On Mon, Oct 29, 2012 at 2:00 PM, Diego Elio Pettenò
wrote:
> In particular, if I hear such an answer from anybody (be it for icu or
> something else, be it for a minor inconsistency or a total fuckup), I'll
> be requesting devrel to re-evaluate their commit rights, as they are
> missing the unders
On 29/10/2012 10:37, Christoph Junghans wrote:
> If Arfrever keeps maintaining it for a while, I will take it.
Do remember that whatever you commit, _You_ take responsibility for it.
After a screwup, the answer "I didn't do anything, I just committed what
Arfrever gave me" is not a good answer.
I
2012/10/29 Brian Harring :
> On Sun, Oct 28, 2012 at 10:35:01PM +0100, Arfrever Frehtes Taifersar Arahesis
> wrote:
>> 2012-10-28 22:14:15 Mike Gilbert napisa??(a):
>> > This library is used for processing Unicode text in several high-profile
>> > packages, including Chromium and other Webkit brow
On Sun, Oct 28, 2012 at 10:35:01PM +0100, Arfrever Frehtes Taifersar Arahesis
wrote:
> 2012-10-28 22:14:15 Mike Gilbert napisa??(a):
> > This library is used for processing Unicode text in several high-profile
> > packages, including Chromium and other Webkit browsers, PHP, boost, and
> > many mor
2012-10-28 22:14:15 Mike Gilbert napisał(a):
> This library is used for processing Unicode text in several high-profile
> packages, including Chromium and other Webkit browsers, PHP, boost, and
> many more.
>
> Fair warning: ICU tends to break several packages with every major
> release, so thorou
This library is used for processing Unicode text in several high-profile
packages, including Chromium and other Webkit browsers, PHP, boost, and
many more.
Fair warning: ICU tends to break several packages with every major
release, so thorough testing is needed when bumping it.
This package is cu
28 matches
Mail list logo
