Perl update breaks Bugzilla

Starting yesterday, a Bugzilla installation running on a SuSE 10.0
system of ours is failing, logging:

[Tue Nov 20 13:25:46 2007] [error] [client x.x.x.x] Storable object version 2.13
does not match $Storable::VERSION 2.15 at /usr/lib/perl5/5.8.7/x86_64-
linux-thread-multi/DynaLoader.pm line 253.

The most likely culprit appears to be the Perl update to
perl-32bit-5.8.7-5.6 installed the night before. I'm still investigating
possible solutions. In the meantime, all suggestions are welcome.

-- 
Tilman Schmidt                              t.schmidt@phoenixsoftware.de
Phoenix Software GmbH                             www.phoenixsoftware.de
Adolf-Hombitzer-Str. 12                        Amtsgericht Bonn HRB 2934
53227 Bonn, Germany                           Geschäftsführer: W. Gri

Tilman Schmidt wrote:
> Starting yesterday, a Bugzilla installation running on a SuSE 10.0
> system of ours is failing, logging:
> 
> [Tue Nov 20 13:25:46 2007] [error] [client x.x.x.x] Storable object version
2.13 does not match $Storable::VERSION 2.15 at /usr/lib/perl5/5.8.7/x86_64-
> linux-thread-multi/DynaLoader.pm line 253.
> 
> The most likely culprit appears to be the Perl update to
> perl-32bit-5.8.7-5.6 installed the night before. I'm still investigating
> possible solutions. In the meantime, all suggestions are welcome.

Ok, after three hours of wading through the CPAN swamp I think I solved
it now. What I did is (all at the CPAN prompt):
- install Storable
  (updating Storable to v2.17 and changing the error to "MIME::Base64
  object version 3.05 does not match bootstrap parameter 3.07")
- install Bundle::Bugzilla
  (which failed to install two dependencies and therefore aborted)
- install XSLoader
  (which didn't change anything)
- install <all modules listed by the 'r' command in order>
  (of which seven, including MIME-Tools, failed "make test" and were
  therefore not installed)
- force install MIME::Base64
  (after a hint on forums.macosxhints.com, of all the places; that
  finally did the trick)

I don't know, and am not sure I want to know, which of these steps
were actually necessary and which weren't.

HTH
T.

-- 
Tilman Schmidt                              t.schmidt@phoenixsoftware.de
Phoenix Software GmbH                             www.phoenixsoftware.de
Adolf-Hombitzer-Str. 12                        Amtsgericht Bonn HRB 2934
53227 Bonn, Germany                           Geschäftsführer: W. Gri

Tilman,

you didn't try backrevving perl, by any chance? It would have made a nice bug
report.

Uwe

-- 
Novell Support Connection Volunteer SysOp

Uwe Buckesfeld schrieb:
> you didn't try backrevving perl, by any chance? It would have made a nice
bug report.

The idea did pass my mind but I quickly dismissed it because I couldn't
think of a quick and easy way to do it. YOU doesn't seem to provide a
backout mechanism, so the only way I saw was to
- find out which version was running before the update
- find an rpm of that version
- install it with rpm -U --oldpackage

The second step in particular promised to be rather difficult, since
most of the 10.0 repositories I knew of seem to have gone away with the
SuSE -> openSUSE switch.

And the CPAN update was long overdue, anyway. ;-)

-- 
Tilman Schmidt                              t.schmidt@phoenixsoftware.de
Phoenix Software GmbH                             www.phoenixsoftware.de
Adolf-Hombitzer-Str. 12                        Amtsgericht Bonn HRB 2934
53227 Bonn, Germany                           Geschäftsführer: W. Gri

Tilman,

so it is hard to reproduce. You could try and open a bug though.

Uwe

-- 
Novell Support Connection Volunteer SysOp