view release on metacpan or  search on metacpan

Todo  view on Meta::CPAN

/home/src/perl/repoperls/installed-perls/perl/peHlG5S/perl-5.8.0@29243/bin/perl -Ilib -MCPAN -eshell
CPAN: File::HomeDir loaded ok (v0.58)
CPAN: Term::ANSIColor loaded ok (v1.11)

cpan shell -- CPAN exploration and modules installation (v1.8861)
ReadLine support enabled

cpan[1]> o conf use_sqlite 1
Warning: unknown configuration variable 'use_sqlite'
    use_sqlite         [1]
Please use 'o conf commit' to make the config permanent!


cpan[2]> m CPAN             
CPAN: YAML::Syck loaded ok (v0.71)
Going to read /home/k/.cpan/build/
............................................................................DONE
Found 593 old builds, restored the state of 343
Updating database file ...
Can't exec "cpandb": No such file or directory at lib/CPAN.pm line 4152.
system cpandb --update failed: -1 at lib/CPAN.pm line 4152.
 at lib/CPAN.pm line 276
        CPAN::shell() called at -e line 1

	OK, let's patch the path to $^X in and retry:

% make run
/home/src/perl/repoperls/installed-perls/perl/peHlG5S/perl-5.8.0@29243/bin/perl -Ilib -MCPAN -eshell
CPAN: File::HomeDir loaded ok (v0.58)
CPAN: Term::ANSIColor loaded ok (v1.11)

cpan shell -- CPAN exploration and modules installation (v1.8861)
ReadLine support enabled

cpan[1]> o conf use_sqlite 1
Warning: unknown configuration variable 'use_sqlite'
    use_sqlite         [1]
Please use 'o conf commit' to make the config permanent!


cpan[2]> m CPAN
CPAN: YAML::Syck loaded ok (v0.71)
Going to read /home/k/.cpan/build/
............................................................................DONE
Found 593 old builds, restored the state of 343
Updating database file ...
Done!
Can't call method "set" on an undefined value at lib/CPAN.pm line 962.
 at lib/CPAN.pm line 276
        CPAN::shell() called at -e line 1


	Hmmm. So Randy wants to have use_sqlite to be set before we enter the
	shell and he wants it only within the shell. This is pretty likely
	wrong.

	Trying to set use_sqlite earlier with a tiny patch to Makefile.PL.
	Doesn't work because CPAN::SQLite loads MyConfig again according to the
	debugger:

	$ = require '/home/k/.cpan/CPAN/MyConfig.pm' called from file `/home/src/perl/repoperls/installed-perls/perl/peHlG5S/perl-5.8.0@29243/lib/site_perl/5.9.5/CPAN/SQLite.pm' line 50

	So we lose the switch again. Back to the drawing board.

	Either I need a way to use CPAN::SQLite without having it guess CPAN.pm
	internals all over the place. Or Randy needs a CPAN.pm that has API
	calls for all the CPAN.pm internals. I cannot allow a plugin that tries
	to reload the Config file and overwriting the Internals that I have
	currently set. This is happening and makes it hard to predict what will
	happen next.

	FIXED by Randy

	* Bug: When I tried to report MSCHWERN/B-Generate-1.06_2.tar.gz, it
	failed but did not try all 43 hosts.

Trying with "/usr/bin/lynx -source" to get
    http://mirror.eunet.fi/CPAN/authors/id/M/MS/MSCHWERN/B-Generate-1.06_2.tar.gz
Error while trying to rename '/home/k/.cpan/sources/authors/id/M/MS/MSCHWERN/B-Generate-1.06_2.tar.gz.tmp13806' to '/home/k/.cpan/sources/authors/id/M/MS/MSCHWERN/B-Generate-1.06_2.tar.gz': No such file or directory
 at lib/CPAN.pm line 267
        CPAN::shell() called at -e line 1

	Lynx again!

	Try
	/usr/bin/lynx -source http://mirror.eunet.fi/CPAN/authors/id/M/MS/MSCHWERN/B-Generate-1.06_2.tar.gz

	They send an error page that looks different than usual

	Fixed in SVK rev. 1298

	* degraded mode problems: I did an 'o conf commit' in degraded mode and
	blew away some config variables. We need a global that disallows commit
	from degraded shells. It would also disallow 'defaults' because that
	would restore the other config variables.

	DONE. But MAYBE we want to tie $CPAN::Config?

	* Bug: ~ expansion missing or warning demanded

	From: Adam Kennedy <cpan@ali.as>
Subject: Re: Trouble installing module: "LWP not available"
To: cpan-discuss@perl.org
Date: Wed, 08 Nov 2006 16:55:21 +1100

Andreas

Speaking of bad configs, I think I might be a good idea to start
adding some basic error checks.

Yesterday I got caught by the various paths not allowing the use of
tilde ~. Instead of my homedir, it installed to a directory called,
literally, "~".

Apart from being a little annoying, fixing it required I make the
scariest command I've ever done on a production system.

rm -rf "~"

:/