pkg_add and pkg_delete parse error after upgrade to 4.9

[Oliver Rompcik]

Hi guys,

i got a problem with pkg_add and pkg_delete after release upgrade from 4.8
to 4.9. This is the first problem afer a release upgrade since years (the
machine started with 3.8 in 2005).

pkg_info:
bash-4.1.7p0GNU Bourne Again Shell
bzip2-1.0.5 block-sorting file compressor, unencumbered
curl-7.20.0 get files from FTP, Gopher, HTTP or HTTPS servers
gettext-0.18.1  GNU gettext
gnupg-1.4.10p0  GNU privacy guard - a free PGP replacement
libiconv-1.13p1 character set conversion library
libidn-1.11 internationalized string handling
p5-Digest-HMAC-1.02 interface to HMAC Message-Digest Algorithms
p5-Digest-SHA1-2.12 module to calculate SHA1 digests
p5-Net-DNS-0.65 module to interface the DNS resolver
p5-Net-IP-1.25p0perl module for IPv4/IPv6 address parsing
pcre-8.02p1 perl-compatible regular expression library
postfix-2.7.1   fast, secure sendmail replacement
unzip-6.0   extract, list & test files in a ZIP archive
wget-1.12p0 retrieve files from the web via HTTP, HTTPS and FTP

pkg_add -ui:
Fatal error: can't parse  object version 5.47 does not match bootstrap
parameter %_ at /usr/libdata/perl5/i386-openbsd/5.12.2/DynaLoader.pm line
223, <$fh> line 6.
Compilation failed in require at /usr/libdata/perl5/OpenBSD/md5.pm line
114, <$fh> line 6.
BEGIN failed--compilation aborted at /usr/libdata/perl5/OpenBSD/md5.pm
line 114, <$fh> line 6.
Compilation failed in require at
/usr/libdata/perl5/OpenBSD/PackingElement.pm line 706, <$fh> line 6, in
SCALAR(0x85430780),  at /usr/libdata/perl5/OpenBSD/PackingList.pm line
355, <$fh> line 6.

Same with pkg_delete.

Help appreciated.

Yours,
O. Rompcik

Re: pkg_add and pkg_delete parse error after upgrade to 4.9

[Oliver Rompcik]

Tasmanian Devil schrieb:
>> I think that one shouldn't be there anymore since OpenBSD 4.5:
>> http://openbsd.org/faq/upgrade45.html#Pkgup
>
> On the other hand, I might be wrong...  p5-Digest-SHA1, not
> p5-Digest-SHA.
>
> Sorry for the noise.

Wasn't all that. The Upgrade Guide has been followed accurately, including
purge of old files.
Seems DynaLoader.pm loaded a wrong library version which was still present.
The fastest solution was a backup of config and a new install, as this was
a production failover mailcluster.

Sincerely,
Oliver Rompcik