slashcode-general

[Slashcode-general] Can't locate DBIx/Password.pm in @INC

[Mike B. <ko...@mi...>]

Attempting to install Slash 2.0.0 via RPM

1) Downloaded slash rpm
2) Got MySQL running; created virtual user slash@localhost
3) Got Apache/mod_perl running (I think)
4) Ran CPAN and installed Bundle::Slash and DBIx::Password

Actually, also had to CPAN install mysql before DBIx::Password.

And even more to the point, I did a bad thing by installing CPAN::Perl
before I did any of this (and told it my architecture was i586...).

I now have Perl 5.6.0 installed in /usr/lib/perl5/  and Perl 5.6.1 installed
in /usr/local/lib/perl5 (arch i586...).

Uh oh.

So the install Bundle::Slash and install DBIx::Password went into the 5.6.1
libraries in /usr/local/lib/perl5.

/usr/local/slash/bin> ./install-slashsite slash@localhost gives following
errors:

Can't locate DBIx/Password.pm in @INC (@INC contains:
/usr/lib/perl5/5.6.0/i386-linux /usr/lib/perl5/5.6.0
/usr/lib/perl5/site_perl/5.6.0/i386-linux /usr/lib/perl5/site_perl/5.6.0
/usr/lib/perl5/site_perl .) at
/usr/lib/perl5/site_perl/5.6.0/i386-linux/Slash/DB.pm line 9.
BEGIN failed--compilation aborted at
/usr/lib/perl5/site_perl/5.6.0/i386-linux/Slash/DB.pm line 9.
Compilation failed in require at ./install-slashsite line 18.
BEGIN failed--compilation aborted at ./install-slashsite line 18.

Ah, so brilliant guy that I am, I change the first line of install-slashsite
to:

#!/usr/local/bin/perl -w

Ooops, all the Perl modules for Slashcode were installed by the RPM into
5.6.0.  Tried to erase the package and reinstall, goes back into the 5.6.0
directories (even though "which perl" shows /usr/local/bin/perl so @INC
should have pointed to the 5.6.1 libraries, right?

Is there any way to get out of this short of formatting the system and
reinstalling RH7.0 (short of rebuilding the slash rpm)???  If so, how?

Mike Boatright
BBC Technology, Digital Media Solutions

[Slashcode-general] Can't locate DBIx/Password.pm in @INC

[Mike B. <ko...@mi...>]

Attempting to install Slash 2.0.0 via RPM

1) Downloaded slash rpm
2) Got MySQL running; created virtual user slash@localhost
3) Got Apache/mod_perl running (I think)
4) Ran CPAN and installed Bundle::Slash and DBIx::Password

Actually, also had to CPAN install mysql before DBIx::Password.

And even more to the point, I did a bad thing by installing CPAN::Perl
before I did any of this (and told it my architecture was i586...).

I now have Perl 5.6.0 installed in /usr/lib/perl5/  and Perl 5.6.1 installed
in /usr/local/lib/perl5 (arch i586...).

Uh oh.

So the install Bundle::Slash and install DBIx::Password went into the 5.6.1
libraries in /usr/local/lib/perl5.

/usr/local/slash/bin> ./install-slashsite slash@localhost gives following
errors:

Can't locate DBIx/Password.pm in @INC (@INC contains:
/usr/lib/perl5/5.6.0/i386-linux /usr/lib/perl5/5.6.0
/usr/lib/perl5/site_perl/5.6.0/i386-linux /usr/lib/perl5/site_perl/5.6.0
/usr/lib/perl5/site_perl .) at
/usr/lib/perl5/site_perl/5.6.0/i386-linux/Slash/DB.pm line 9.
BEGIN failed--compilation aborted at
/usr/lib/perl5/site_perl/5.6.0/i386-linux/Slash/DB.pm line 9.
Compilation failed in require at ./install-slashsite line 18.
BEGIN failed--compilation aborted at ./install-slashsite line 18.

Ah, so brilliant guy that I am, I change the first line of install-slashsite
to:

#!/usr/local/bin/perl -w

Ooops, all the Perl modules for Slashcode were installed by the RPM into
5.6.0.  Tried to erase the package and reinstall, goes back into the 5.6.0
directories (even though "which perl" shows /usr/local/bin/perl so @INC
should have pointed to the 5.6.1 libraries, right?

Is there any way to get out of this short of formatting the system and
reinstalling RH7.0 (short of rebuilding the slash rpm)???  If so, how?

Mike Boatright
BBC Technology, Digital Media Solutions

[Slashcode-general] Can't locate DBIx/Password.pm in @INC

[Mike B. <ko...@mi...>]

Attempting to install Slash 2.0.0 via RPM

1) Downloaded slash rpm
2) Got MySQL running; created virtual user slash@localhost
3) Got Apache/mod_perl running (I think)
4) Ran CPAN and installed Bundle::Slash and DBIx::Password

Actually, also had to CPAN install mysql before DBIx::Password.

And even more to the point, I did a bad thing by installing CPAN::Perl
before I did any of this (and told it my architecture was i586...).

I now have Perl 5.6.0 installed in /usr/lib/perl5/  and Perl 5.6.1 installed
in /usr/local/lib/perl5 (arch i586...).

Uh oh.

So the install Bundle::Slash and install DBIx::Password went into the 5.6.1
libraries in /usr/local/lib/perl5.

/usr/local/slash/bin> ./install-slashsite slash@localhost gives following
errors:

Can't locate DBIx/Password.pm in @INC (@INC contains:
/usr/lib/perl5/5.6.0/i386-linux /usr/lib/perl5/5.6.0
/usr/lib/perl5/site_perl/5.6.0/i386-linux /usr/lib/perl5/site_perl/5.6.0
/usr/lib/perl5/site_perl .) at
/usr/lib/perl5/site_perl/5.6.0/i386-linux/Slash/DB.pm line 9.
BEGIN failed--compilation aborted at
/usr/lib/perl5/site_perl/5.6.0/i386-linux/Slash/DB.pm line 9.
Compilation failed in require at ./install-slashsite line 18.
BEGIN failed--compilation aborted at ./install-slashsite line 18.

Ah, so brilliant guy that I am, I change the first line of install-slashsite
to:

#!/usr/local/bin/perl -w

Ooops, all the Perl modules for Slashcode were installed by the RPM into
5.6.0.  Tried to erase the package and reinstall, goes back into the 5.6.0
directories (even though "which perl" shows /usr/local/bin/perl so @INC
should have pointed to the 5.6.1 libraries, right?

Is there any way to get out of this short of formatting the system and
reinstalling RH7.0 (short of rebuilding the slash rpm)???  If so, how?

Mike Boatright
BBC Technology, Digital Media Solutions

Re: [Slashcode-general] Can't locate DBIx/Password.pm in @INC

[Jamie M. <ja...@mc...>]

ko...@mi... (Mike Boatright) writes:

> And even more to the point, I did a bad thing by installing
> CPAN::Perl before I did any of this [...]
> 
> I now have Perl 5.6.0 installed in /usr/lib/perl5/  and Perl
> 5.6.1 installed in /usr/local/lib/perl5 (arch i586...).

This isn't the end of the world (see below for fix) but you're the
second person I've seen recently who's done this.

Slash team, this isn't really our issue, but it's an issue that
affects us.  I propose as a workaround, we change the INSTALL file
to strongly recommend an upgrade to the latest version of perl, in
step 2.  I know of no side-effects (bender and fry run fine with
perl 5.6.1).

Mike, the short version of what happened is that there are some ugly
glitches in the CPAN module installation process.  It would be nice
if there were a way for a module to say "install version X on
systems with perl version X1;  install version Y on systems with
perl version Y1."  But with some modules, it doesn't work that way.
You install the module, you get a free half-baked upgrade to the
latest version of perl along with it.  It's dumb and it needs to be
fixed but if you're not running 5.6.1 there's not much we can do
about it.

"Half-baked" apparently means exactly what you (and the other person)
describe:  one version of perl in /usr/*, another in /usr/local/*.
Needless to say, this causes problems.

If perl 5.6.1 were installed before the user began the CPAN module
installation process, this problem would not occur.

> Is there any way to get out of this short of formatting the
> system and reinstalling RH7.0 (short of rebuilding the slash
> rpm)???

Oh my yes -- nothing so drastic required!  Perl is pretty good about
looking backward into previous versions for its modules.  So once
you get fully up to 5.6.1, your installed 5.6.0 modules should still
be present.

Personally, I always go behind the back of the package manager for
installing perl.  It's happy because it thinks/knows a copy of perl
is indeed installed.  I'm happy because I always get the latest
version of perl and I watch it install with my own two eyes so I
know right where it goes.

Here's what I'd do.  There may be quicker fixes but I'm a little
paranoid about getting a clean installation:



1)  Recompile a fresh perl 5.6.1 from scratch and install it over
    the top of whatever you have.

This is quite simple.  As root:

cd /usr/local/src # or wherever
GET 'http://www.perl.com/CPAN/src/stable.tar.gz' > perl-5.6.1.tar.gz
tar zxf perl-5.6.1.tar.gz
cd perl-5.6.1
./Configure -des && make && make test && make install

If it asks you any questions (it shouldn't), hit return for default.

2)  Reinstall modules.  "perl -MCPAN -e shell" for the CPAN shell,
"r" to list out of date modules, and "install X" to install anything
that looks out of date.  (Note that some modules may be misversioned
and list as out of date when they're not -- DBD::ADO, DBI::Shell,
and Template::Plugin::XML::DOM are prime culprits.)

Then install the big bundles, Bundle::CPAN and Bundle::LWP would be
my suggestions, and then install Bundle::Slash.  Then do
DBIx::Password again -- and be sure to read its README!

3)  Remove /usr/local/slash/slash.sites, put install-slashsite back
the way it was (whatever was before #!/usr/local/bin/perl), and
re-run install-slashsite.



I haven't used the slash RPM so I'm not sure where in there it would
go.  I imagine right before step 3 -- though from your description,
my step 2 should almost be unnecessary...anyway, give that a try.
--
 Jamie McCarthy
 ja...@mc...

Re: [Slashcode-general] Can't locate DBIx/Password.pm in @INC

[Alessio B. <al...@se...>]

Jamie McCarthy:

> Mike, the short version of what happened is that there are some ugly
> glitches in the CPAN module installation process.

This doesn't happen if you have the latest CPAN module. In this case
you have just a warning, for example "Data::Dumper is available with
perl 5.6.1, I will install it if you use the command..." etc.

I suggest to do, first

install CPAN
reload cpan (or quit and restart shell)

then

install Bundle::Slash

BTW, If you use UNINST=1 as a parameter to 'make install', CPAN shell
will clean up older versions for you.

> I haven't used the slash RPM

Which doesn't exist, talking about release version and not pre.
 
-- 
Alessio F. Bragadini		al...@se...

La Citta` Invisibile: notizie e dibattiti per i cittadini della Rete
http://www.citinv.it

Re: [Slashcode-general] Can't locate DBIx/Password.pm in @INC

[Patrick G. <cap...@sl...>]

The one question in requiring perl 5.6 is "how many systems come
preinstalled with perl 5.6?" 
I don't see any problem with requiring 5.6, I'm just curious as to how
many people would then have to upgrade perl?

Jamie McCarthy wrote:
> 
> ko...@mi... (Mike Boatright) writes:
> 
> > And even more to the point, I did a bad thing by installing
> > CPAN::Perl before I did any of this [...]
> >
> > I now have Perl 5.6.0 installed in /usr/lib/perl5/  and Perl
> > 5.6.1 installed in /usr/local/lib/perl5 (arch i586...).
> 
> This isn't the end of the world (see below for fix) but you're the
> second person I've seen recently who's done this.
> 
> Slash team, this isn't really our issue, but it's an issue that
> affects us.  I propose as a workaround, we change the INSTALL file
> to strongly recommend an upgrade to the latest version of perl, in
> step 2.  I know of no side-effects (bender and fry run fine with
> perl 5.6.1).
> 
> Mike, the short version of what happened is that there are some ugly
> glitches in the CPAN module installation process.  It would be nice
> if there were a way for a module to say "install version X on
> systems with perl version X1;  install version Y on systems with
> perl version Y1."  But with some modules, it doesn't work that way.
> You install the module, you get a free half-baked upgrade to the
> latest version of perl along with it.  It's dumb and it needs to be
> fixed but if you're not running 5.6.1 there's not much we can do
> about it.
> 
> "Half-baked" apparently means exactly what you (and the other person)
> describe:  one version of perl in /usr/*, another in /usr/local/*.
> Needless to say, this causes problems.
> 
> If perl 5.6.1 were installed before the user began the CPAN module
> installation process, this problem would not occur.
> 
> > Is there any way to get out of this short of formatting the
> > system and reinstalling RH7.0 (short of rebuilding the slash
> > rpm)???
> 
> Oh my yes -- nothing so drastic required!  Perl is pretty good about
> looking backward into previous versions for its modules.  So once
> you get fully up to 5.6.1, your installed 5.6.0 modules should still
> be present.
> 
> Personally, I always go behind the back of the package manager for
> installing perl.  It's happy because it thinks/knows a copy of perl
> is indeed installed.  I'm happy because I always get the latest
> version of perl and I watch it install with my own two eyes so I
> know right where it goes.
> 
> Here's what I'd do.  There may be quicker fixes but I'm a little
> paranoid about getting a clean installation:
> 
> 1)  Recompile a fresh perl 5.6.1 from scratch and install it over
>     the top of whatever you have.
> 
> This is quite simple.  As root:
> 
> cd /usr/local/src # or wherever
> GET 'http://www.perl.com/CPAN/src/stable.tar.gz' > perl-5.6.1.tar.gz
> tar zxf perl-5.6.1.tar.gz
> cd perl-5.6.1
> ./Configure -des && make && make test && make install
> 
> If it asks you any questions (it shouldn't), hit return for default.
> 
> 2)  Reinstall modules.  "perl -MCPAN -e shell" for the CPAN shell,
> "r" to list out of date modules, and "install X" to install anything
> that looks out of date.  (Note that some modules may be misversioned
> and list as out of date when they're not -- DBD::ADO, DBI::Shell,
> and Template::Plugin::XML::DOM are prime culprits.)
> 
> Then install the big bundles, Bundle::CPAN and Bundle::LWP would be
> my suggestions, and then install Bundle::Slash.  Then do
> DBIx::Password again -- and be sure to read its README!
> 
> 3)  Remove /usr/local/slash/slash.sites, put install-slashsite back
> the way it was (whatever was before #!/usr/local/bin/perl), and
> re-run install-slashsite.
> 
> I haven't used the slash RPM so I'm not sure where in there it would
> go.  I imagine right before step 3 -- though from your description,
> my step 2 should almost be unnecessary...anyway, give that a try.
> --
>  Jamie McCarthy
>  ja...@mc...
> 
> _______________________________________________
> Slashcode-general mailing list
> Sla...@li...
> http://lists.sourceforge.net/lists/listinfo/slashcode-general

Re: [Slashcode-general] Can't locate DBIx/Password.pm in @INC

[Jamie M. <ja...@mc...>]

cap...@sl... (Patrick Galbraith) writes:

> The one question in requiring perl 5.6 is "how many systems come
> preinstalled with perl 5.6?"

That I don't know.  Red Hat 7.1 comes with 5.6.0...

> I don't see any problem with requiring 5.6, I'm just curious as
> to how many people would then have to upgrade perl?

We're already requiring them to build apache and mod_perl from
scratch; perl itself is even easier.  5.6 is over a year old
(March 2000), well OK, 5.6.1 is only two months old.  But there
are no major backwards compatibility issues.
--
 Jamie McCarthy
 ja...@mc...

Re: [Slashcode-general] Can't locate DBIx/Password.pm in @INC

[Chris N. <pu...@po...>]

I am late on this, but wanted to reiterate something about perl versions.

At 09:23 -0400 2001.06.16, Patrick Galbraith wrote:
>The one question in requiring perl 5.6 is "how many systems come
>preinstalled with perl 5.6?"
>I don't see any problem with requiring 5.6, I'm just curious as to how
>many people would then have to upgrade perl?

I see a BIG HUGE NASTY problem with requiring 5.6.  Namely, that there is
no significant advantage in the code for it, and it will cause huge
problems for people who for one reason or another cannot upgrade perl.
Upgrading perl can be a pain in the arse if you are not familiar with perl.
It's not like mysql or Apache where you just recompile and install and
everything is OK.  perl is bigger and more complex and harder to upgrade.

Recommending perl 5.6.1 is good.  Requiring it is bad.

-- 
Chris Nandor                      pu...@po...    http://pudge.net/
Open Source Development Network    pu...@os...     http://osdn.com/

Re: [Slashcode-general] Can't locate DBIx/Password.pm in @INC

[Jamie M. <ja...@mc...>]

pu...@po... (Chris Nandor) writes:

> Recommending perl 5.6.1 is good.  Requiring it is bad.

I agree, and I'm actively taking out 5.6-isms when I see them
(apparently three-argument open() is new to 5.6, which I didn't know
when I put that code into a couple of places).

But I've never thought perl was that hard to install or upgrade.
"./Configure -des && make install"

Of course, now that I say that, I'm reminded how perl5.6 failed
about 3 of its tests on my new debian/reiser system, leaving me
skeptical about installing it.  Heh.  Never mind.
--
 Jamie McCarthy
 ja...@mc...

Re: [Slashcode-general] Can't locate DBIx/Password.pm in @INC

[Chris N. <pu...@po...>]

At 10:18 -0400 2001.07.06, Jamie McCarthy wrote:
>pu...@po... (Chris Nandor) writes:
>
>> Recommending perl 5.6.1 is good.  Requiring it is bad.
>
>I agree, and I'm actively taking out 5.6-isms when I see them
>(apparently three-argument open() is new to 5.6, which I didn't know
>when I put that code into a couple of places).

Yeah.  perl 5.6 has some really nice syntax changes (like autovivifying
filehandle references!), but nothing we need.

>But I've never thought perl was that hard to install or upgrade.
>"./Configure -des && make install"
>
>Of course, now that I say that, I'm reminded how perl5.6 failed
>about 3 of its tests on my new debian/reiser system, leaving me
>skeptical about installing it.  Heh.  Never mind.

Exactly.  Now, it is not as bad as if we still supported 5.004 (which we do
not), because perl 5.6 can be built with binary compatability to perl
5.005, so you don't need to rebuild shared libraries, etc.  But there are
still little problems here and there that many people can, do, and will run
into, such so that it is not worth the trouble.

A strong recommendation for 5.6.1 is warranted, but that's where I'd stop it.

-- 
Chris Nandor                      pu...@po...    http://pudge.net/
Open Source Development Network    pu...@os...     http://osdn.com/

Re: [Slashcode-general] Can't locate DBIx/Password.pm in @INC

[Micah Y. <yo...@ho...>]

> But I've never thought perl was that hard to install or upgrade.
> "./Configure -des && make install"

Seems like the hardest part is what to do with all your installed modules.  
You pretty much have to do the complete install of all the packages again, if 
I'm not mistaken...

-- 
Like to travel?                        http://TravTalk.org
Micah Yoder Internet Development       http://yoderdev.com

Re: [Slashcode-general] Can't locate DBIx/Password.pm in @INC

[ben h k. <ja...@mo...>]

> Seems like the hardest part is what to do with all your installed modules.  
> You pretty much have to do the complete install of all the packages again, if 
> I'm not mistaken...

Well, yes, but that is what autobundle is for.  To make a Bundle consisting of every module you have already installed.

.b

-- 
"Mir's outstanding success is that it has survived."
			Dr. David Whitehouse
			BBC News Online science editor