# from David Golden
# on Thursday 04 September 2008 11:30:
>On Thu, Sep 4, 2008 at 1:09 PM, chromatic <[EMAIL PROTECTED]> wrote:
>> I fail to understand the mechanism by which CPAN Testers has
>> seemingly removed the ability of testers to report bugs to the
>> correct places. For example,
>
>I t
# from David Golden
# on Friday 05 September 2008 04:53:
>One of my potential weekend projects (after patching CPAN::Reporter
>and Test::Reporter) is to write a CPAN Testers nag-bot that checks for
>reports sent with out-of-date tools and emails authors (probably only
>once a day) with a reminder
# from Andy Lester
# on Friday 05 September 2008 09:34:
>> Well, yeah, I have too. And sometimes I make a tweak to get things
>> working on 5.005, and other times I tell my users that it runs 5.006
>> or later by saying so in Build.PL. Seems reasonable to me to
>> specify such dependencies.
>
# from Aristotle Pagaltzis
# on Friday 05 September 2008 06:07:
>> UNIVERSAL::isa and UNIVERSAL::can are examples of applying the
>> design principle of Report Bugs Where They Are, Not Where They
>> Appear.
>
>How do you propose doing that in the general case? I am certainly
>interested in what te
# from David Golden
# on Friday 05 September 2008 15:22:
>On Fri, Sep 5, 2008 at 5:48 PM, Eric Wilhelm wrote:
>The one thing that concerns me is that some authors
>object to FAIL reports showing up on their search.cpan.org page and
>will just want them all blanked out.
>
>So
Hi Nadim,
# from nadim khemir
# on Saturday 06 September 2008 01:18:
>Why not let authors decide which modules they want to get smoked?
>Why not let authors decide which platform they want their modules
> smoked on?
Because they might decide 'none'? This might eliminate information that
is use
# from imacat
# on Sunday 07 September 2008 12:52:
>> On Wed, Sep 03, 2008 at 03:00:40PM +0300, Gabor Szabo wrote:
>> This requires the tester to have the infrastructure in place to
>> clean up afterwards - probably by running in a VM (which itself
>> limits testing to
>
> I believe there is "c
# from David Landgren
# on Monday 08 September 2008 13:09:
>>>I've played with unionfs on debian
>>> etch and I think it would do everything you need (possibly even
>>> from within a chroot) unless your needs involve a few particular
>>> things with nfs, which is where the aufs "new hotness" comes
# from Andreas J. Koenig
# on Monday 08 September 2008 15:16:
>Since yesterday I have downloaded and analysed ~56000 testreports from
>cpantesters and found ~135 distros that have been tested by both MB
>0.2808 and 0.2808_03. There is only one result (Test-Group-0.12) that
>looks bad but it turns
# from Andreas J. Koenig
# on Tuesday 09 September 2008 00:09:
>OK, I walk you through them. First off, there are ten cases in the
>file I sent you.
>...
> So the above is a case where it's impossible to judge without
> looking at the report but at the same time we cannot have any
> expectation
# from David Golden
# on Tuesday 09 September 2008 16:00:
>This would be better if I finally updated CPAN::Reporter::Smoker to
>take an arbitrary list of distributions instead of just working
>backwards through CPAN and if you had a list of distributions with
>Build.PL.
Indeed I do have such a li
# from David Golden
# on Wednesday 10 September 2008 04:07:
>I would suggest just including a link to the wiki.
>It has information on how to get set up to send tests and they can get
>to the reports page from there. Having a choice of two websites
>decreases the chance they'll look at either. (
hing about it, of which I would be greatly
appreciative.
>And the "Reply via email to Eric Wilhelm" link takes me to an error
> page.
Where did this come from?
--Eric
--
So malloc calls a timeout and starts rummaging around the free chain,
sorting things out, and merging adjacent s
# from Randy J. Ray
# on Thursday 11 September 2008 12:22:
>> [1] If you can think of a suitable word beginning with 'L' to
>> replace 'Service' let me know ;)
>
>"Labors"?
"CENTRAS" would probably google better than "CENTRAL", but my thought
was "too bad Xs aren't cool anymore (hmm, but could y
# from Michael G Schwern
# on Thursday 11 September 2008 14:17:
>At first glance this new system is going to generate a lot more work
> per report. Let's step through the old procedure...
>
>1. Read report
>2. Reply to report
Did you actually get every report on a CC? I never seemed to get mo
# from David Golden
# on Friday 12 September 2008 16:33:
><[EMAIL PROTECTED]> wrote:
>> define(`confSINGLE_THREAD_DELIVERY', True)dnl
>> define(`SMTP_MAILER_MAXMSGS', 1)dnl
>> define(`RELAY_MAILER_MAXMSGS', 1)dnl
>
>Ah. For me, everything gets relayed to my ISP's smart-host and I
>guess they don'
# from CPAN Tester Report Server
# on Friday 12 September 2008 19:42:
>File-Fu-v0.0.4:
>- i86pc-solaris-thread-multi-64int / 5.10.0:
> - FAIL http://nntp.x.perl.org/group/perl.cpan.testers/2201908
>- i686-linux-thread-multi-64int-ld / 5.8.8:
> - FAIL http://nntp.x.perl.org/group/perl.cpan.tester
# from Dmitry Karasik
# on Saturday 27 September 2008:
>Prima::noX11 is a part of Prima. It is not found because CPANPLUS
> apparently doesn't execute "make install", but relies on hacking
> $ENV{PERL5LIB}. This doesn't work for Prima, because its build
> process is not based on populating ./blib.
# from Dmitry Karasik
# on Sunday 28 September 2008:
>> Would it be enough to just add the distribution directory itself to
>> PERL5LIB? That has some risk of polluting @INC in a way that could
>> cause problems -- but I think the risk is low.
>
>In Prima's case that should work, but it won't in
# from Eric Wilhelm
# on Sunday 28 September 2008:
># from Dmitry Karasik
># on Sunday 28 September 2008:
>
>>> Would it be enough to just add the distribution directory itself to
>>> PERL5LIB? That has some risk of polluting @INC in a way that could
>>> cause
Hi all,
I don't have time to triage all of the M::B bugs and we really need to
get some of these cleared out.
This one looks like it may have been resolved within the last year and
possibly been made a non-issue by recent cpantesters improvements.
Could I please have a volunteer to look into
21 matches
Mail list logo
