On Tue, 2005-12-06 at 21:13 +0100, Leopold Toetsch wrote:
> > If it helps - the t/perl/manifest test hangs on test 3. Looking at the
> > source, looks like someone intended a diag message to warn that it
> > would
> > appear to hang, but the diag doesn't get printed out until after the
> > fact.
>
On Tue, 2005-12-06 at 18:38 -0500, Michael Cummings wrote:
t/perl/manifest..Can't exec "svk": No such file or
directory at t/perl/manifest.t line 38.
ok
1/3 skipped: Not a working copy
Not a patch, but a better explanation of the problem. There is a f
I realize I'm talking to myself at this point (last post, promise), but
my last message failed to explain the paste at the top. On a box without
svk, using the 0.4.0 released tarball, all is fine (t/perl/manifest.t is
skipped/failed quickly). However, if a user has svk installed and
attempts to run
On Wed, 2005-12-07 at 02:18 +0100, Leopold Toetsch wrote:
> On Dec 7, 2005, at 0:29, Michael Cummings wrote:
>
> On that hardware it certainly shouldn't need minutes to finish. It's
> just strange:
> This is on a PowerBook G4 with 1.2 GHz - certainly not a fast syst
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Johnson wrote:
> On Fri, Jun 16, 2006 at 12:43:11PM +0530, Rajanikanth Dandamudi wrote:
>
>> Hi All,
>>
>> Can some one help me understand why I am getting the following message
>> on the following perl program :
>>
>> perl program
>> ==
Is "make parrot_so" not ready? (Or is it not what I think it is, chiefly a way
to generate a libparrot.so?) Attempts to run 'make parrot_so' after a 'make
all world' seems to always result in :
nomad parrot-0.2.2 # make parrot_so
echo -oimcc/imclexer.c imcc/imcc.l
-oimcc/imclexer.c imcc/imcc.l
/
On Wednesday 06 July 2005 06:39 am, Maxim Sloyko wrote:
> But this is not the point. The point was that usage of some file with
> passwords by *DEFAULT* is not the way to go, IMHO. It raises more
> problems than it solves.
To tack onto that, IMO it would make more sense if the password situation
