Bug#533545: perl: Byte order is not compatible on a 64bit system

[Marco Benecke]

Package: perl
Version: 5.10.0-19
Severity: important

We use OpenID on our Webapp, wich runnes good on Etch. But after our upgrade to Lenny we geht this Message on our 64bit Systems:
Byte order is not compatible at ../../lib/Storable.pm (autosplit into ../../lib/auto/Storable/thaw.al) line 415, at /usr/share/perl5/URI/Fetch.pm line 49

I think this is a error in the binary part of Storable, a right recompile should help.

For help, please send mail to the INFORMATION:
Debian Release: 5.0.1
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.18-6-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages perl depends on:
ii libc6 2.7-18 GNU C Library: Shared libraries
ii libdb4.6 4.6.21-11 Berkeley v4.6 Database Libraries [
ii libgdbm3 1.8.3-3 GNU dbm database routines (runtime
ii perl-base 5.10.0-19 minimal Perl system
ii perl-modules 5.10.0-19 Core Perl modules

Versions of packages perl recommends:
ii netbase 4.34 Basic TCP/IP networking system

Versions of packages perl suggests:
pn libterm-readline-gnu-perl | l <none> (no description available)
pn perl-doc <none> (no description available)

-- no debconf information

--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

[Niko Tyni]

On Thu, Jun 18, 2009 at 05:36:41PM +0200, Marco Benecke wrote:
> Package: perl
> Version: 5.10.0-19
> Severity: important

> We use OpenID on our Webapp, wich runnes good on Etch. But after our upgrade to Lenny we geht this Message on our 64bit Systems:
> Byte order is not compatible at ../../lib/Storable.pm (autosplit into ../../lib/auto/Storable/thaw.al) line 415, at /usr/share/perl5/URI/Fetch.pm line 49
>
> I think this is a error in the binary part of Storable, a right recompile should help.

Sorry for the delay.

I don't think recompiling Storable would help, this means that the
stored data is not compatible with it.

I tested this by fetching a URL on Etch/amd64 with this script, created
based on URI::Fetch documentation:

#!/usr/bin/perl -w
use strict;
use URI::Fetch;
use Cache::File;

## Fetch using an on-disk cache that URI::Fetch manages for you.
my $cache = Cache::File->new( cache_root => '/tmp/cache' );
my $res = URI::Fetch->fetch(shift,
Cache => $cache
)
or die URI::Fetch->errstr;

I then copied /tmp/cache over to a Lenny system with the same architecture,
and the script succesfully retrieved the URL from the cache.

Could you please give more details? Is the serialized data stored and
retrieved on the same system? I take it the system architecture
wasn't changed from 32-bit to 64-bit along with the upgrade?

Cheers,
--
Niko Tyni nt...@debian.org