* Barak A. Pearlmutter <ba...@cs.nuim.ie>, 2014-01-14, 09:33:
Well dagnabit. So an i386 autobuilder is running an old pod2man or
dependencies thereof.
-.\" Automatically generated by Pod::Man 2.22 (Pod::Simple 3.07)
+.\" Automatically generated by Pod::Man 2.27 (Pod::Simple 3.28)
I don't think the autobuilder was running an old pod2man. That would be
a very old version of perl-modules, older than in wheezy. It's more
likely that on i386 the manpages didn't get rebuilt from source, i.e.
the pre-built ones from the source package are shipped. No idea why
would that happen on one architecture but not on another.
For completeness, amd64 appears to be the only architecture on which the
manpages where rebuilt. For example, these are MD5 sums of
/usr/share/man/man3/liboping.3.gz:
2888fbc87a50f8a4494ffbd003dadce9 on amd64;
c3d41657a5c90753e51d099d1cd2d9f5 on i386, powerpc, armel, ... and everywhere
else.
Naturally the differences in the generated man pages are pretty
trivial.
I'm not sure if this is really "Severity: important", assuming dpkg
just installs one or the other for each file it doesn't make any real
difference. Or does dpkg error out? That would be unfortunate.
dpkg has no way of knowing whether the difference is "real" or not, so
to be on the safe side, it errors out:
Preparing to unpack .../liboping-dev_1.6.2-3_amd64.deb ...
Unpacking liboping-dev:amd64 (1.6.2-3) ...
Selecting previously unselected package liboping-dev:i386.
Preparing to unpack .../liboping-dev_1.6.2-3_i386.deb ...
Unpacking liboping-dev:i386 (1.6.2-3) ...
dpkg: error processing archive
/var/cache/apt/archives/liboping-dev_1.6.2-3_i386.deb (--unpack):
trying to overwrite shared '/usr/share/man/man3/ping_send.3.gz', which is
different from other instances of package liboping-dev:i386
--
Jakub Wilk
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
