[SLUG] perl upgrade broke cyradm

From: Doug Koobs (dkoobs@dkoobs.com)
Date: Tue Mar 08 2005 - 08:44:40 EST


Anybody in SLUGadonia using Cyrus? I recently upgraded my installation of Perl from
5.8.0 (in /usr/lib/perl5) to 5.8.6 (in /usr/local/lib/perl5) using CPAN. I didn't
catch the difference in location when I installed... Now, when I try to run the
command "cyradm --user cyrus --auth login localhost" I got the error:

******************************************************
Can't locate Cyrus/IMAP/Shell.pm in @INC (@INC contains:
/usr/local/lib/perl5/5.8.6/i686-linux /usr/local/lib/perl5/5.8.6
/usr/local/lib/perl5/site_perl/5.8.6/i686-linux /usr/local/lib/perl5/site_perl/5.8.6
/usr/local/lib/perl5/site_perl .).
BEGIN failed--compilation aborted.
******************************************************

I did a locate Shell.pm:
/usr/lib/perl5/5.8.0/Shell.pm
/usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi/Cyrus/IMAP/Shell.pm
/usr/lib/perl5/vendor_perl/5.8.0/i386-linux-thread-multi/DBI/Shell.pm
/usr/local/lib/perl5/5.8.6/Shell.pm

Then I made the directory Cyrus in /usr/local/lib/perl5/5.8.6, and copied (with cp
-R) /usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi/Cyrus/ into it, which
contains IMAP.pm, IMAP/Shell.pm, and IMAP/Admin.pm. Now when I run cyradm, I get:

*********************************************************
Can't locate loadable object for module Cyrus::IMAP in @INC (@INC contains:
/usr/local/lib/perl5/5.8.6/i686-linux /usr/local/lib/perl5/5.8.6
/usr/local/lib/perl5/site_perl/5.8.6/i686-linux /usr/local/lib/perl5/site_perl/5.8.6
/usr/local/lib/perl5/site_perl .) at /usr/local/lib/perl5/5.8.6/Cyrus/IMAP/Admin.pm
line 44
Compilation failed in require at /usr/local/lib/perl5/5.8.6/Cyrus/IMAP/Admin.pm line
44.
BEGIN failed--compilation aborted at /usr/local/lib/perl5/5.8.6/Cyrus/IMAP/Admin.pm
line 44.
Compilation failed in require at /usr/local/lib/perl5/5.8.6/Cyrus/IMAP/Shell.pm line
60.
BEGIN failed--compilation aborted at /usr/local/lib/perl5/5.8.6/Cyrus/IMAP/Shell.pm
line 60.
Compilation failed in require.
BEGIN failed--compilation aborted.
*********************************************************

Line 44 in Admin.pm says "use Cyrus::IMAP;" So, I'm thinking I need to rebuild and
re-install the Cyrus::IMAP module. It isn't in CPAN... Since I had installed Cyrus
using Simon Matter's 2.2.12-1 source rpm, so I'm thinking this module must be part
of the perl-Cyrus-2.2.12-1.i386.rpm package. So, I try to rebuild from his source
rpm with the command "rpmbuild --rebuild cyrus-imapd-2.2.12-1.src.rpm" and after it
builds for a while, I get the following error:

***********************************************************
+ find
/var/tmp/cyrus-imapd-2.2.12-root/usr/local/lib/perl5/site_perl/5.8.6/i686-linux/Cyrus
/var/tmp/cyrus-imapd-2.2.12-root/usr/local/lib/perl5/site_perl/5.8.6/i686-linux/auto/Cyrus
-type f -print
find:
/var/tmp/cyrus-imapd-2.2.12-root/usr/local/lib/perl5/site_perl/5.8.6/i686-linux/Cyrus:
No such file or directory
find:
/var/tmp/cyrus-imapd-2.2.12-root/usr/local/lib/perl5/site_perl/5.8.6/i686-linux/auto/Cyrus:
No such file or directory
+ /bin/grep -v perllocal.pod
+ /bin/grep -v '\.packlist'
+ /bin/sed 's@^/var/tmp/cyrus-imapd-2.2.12-root@@g'
error: Bad exit status from /var/tmp/rpm-tmp.82056 (%install)

RPM build errors:
    Bad exit status from /var/tmp/rpm-tmp.82056 (%install)
************************************************************

Wow, sorry for the long email, I hope the detail is actually useful... What can I do
to correct the situation? Here is what I see as my options:

Uninstall perl 5.8.6 (not sure how to do this)
Use another method to manage Cyrus users (is there another method?)
Somehow change cyradm so that it only sees the old perl instal (how?)
Build a cyradm that works with perl 5.8.6 (other than rebuilding from src rpm's,
which I alredy tried)

Any guidance is much appreciated!
Doug

-----------------------------------------------------------------------
This list is provided as an unmoderated internet service by Networked
Knowledge Systems (NKS). Views and opinions expressed in messages
posted are those of the author and do not necessarily reflect the
official policy or position of NKS or any of its employees.



This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 20:23:06 EDT