From: Tracey on
Hi all,

I force installed DBD::mysql when I shouldn't have and have broken
just about everything I had running on this particular server. I'm
getting 'perl:relocation error' all over the place. Any idea how I
restore this or uninstall it and get my server back to normal?

Thanks.

From: Randal L. Schwartz on
>>>>> "Tracey" == Tracey <tlundrigan(a)gmail.com> writes:

Tracey> I force installed DBD::mysql when I shouldn't have and have broken
Tracey> just about everything I had running on this particular server. I'm
Tracey> getting 'perl:relocation error' all over the place. Any idea how I
Tracey> restore this or uninstall it and get my server back to normal?

The CPAN and CPANPLUS installers are just that... installers. They are not
package managers, although they have a bit of dependency-chasing built in.
(And they can never be package managers, because they don't care if two
different CPAN distros both write to the same file.)

Your only safe bet is to roll back via some other mechanism, like a backup
archive.

print "Just another Perl hacker,";
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn(a)stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!

--
Posted via a free Usenet account from http://www.teranews.com

From: Michele Dondi on
On Thu, 15 Feb 2007 14:40:29 -0800, merlyn(a)stonehenge.com (Randal L.
Schwartz) wrote:

>The CPAN and CPANPLUS installers are just that... installers. They are not
>package managers, although they have a bit of dependency-chasing built in.
>(And they can never be package managers, because they don't care if two
>different CPAN distros both write to the same file.)
>
>Your only safe bet is to roll back via some other mechanism, like a backup
>archive.

However CPANPLUS has a mechanism for creating (Linux) distro specific
packages on the fly. Probably this is not the case for the OP. But if
one is under Linux and uses this feature, then he may use his distro's
specific package managing tool(s) to uninstall modules. Never tried,
just guessing!


Michele
--
{$_=pack'B8'x25,unpack'A8'x32,$a^=sub{pop^pop}->(map substr
(($a||=join'',map--$|x$_,(unpack'w',unpack'u','G^<R<Y]*YB='
..'KYU;*EVH[.FHF2W+#"\Z*5TI/ER<Z`S(G.DZZ9OX0Z')=~/./g)x2,$_,
256),7,249);s/[^\w,]/ /g;$ \=/^J/?$/:"\r";print,redo}#JAPH,
From: Bart Lateur on
Tracey wrote:

>I force installed DBD::mysql when I shouldn't have and have broken
>just about everything I had running on this particular server. I'm
>getting 'perl:relocation error' all over the place. Any idea how I
>restore this or uninstall it and get my server back to normal?

You may try to partially install it again, at least, make it. That way
you can see what files are added, and then, delete them manually.

But of course, that won't restore the files you accidently overwrite.
Your best option, in that case, is to install an older version of the
DBD::mysql module, but this time, do it properly. Well, unless you
happend to have a backup archive ready...

--
Bart.
From: gf on
On Feb 15, 3:40 pm, mer...(a)stonehenge.com (Randal L. Schwartz) wrote:

> Your only safe bet is to roll back via some other mechanism, like a backup
> archive.

That makes me think that cpan's autobundle command might come in
handy.

(That's cpan the app, not CPAN the site.)