Package: xpdf
Version: 3.02-9
Severity: important

The upgrade for xpdf from xpdf-reader is not clean.

$ ls -la /usr/share/doc/xpdf
lrwxrwxrwx 1 root root 11 Apr  8 20:13 /usr/share/doc/xpdf -> xpdf-common
$

I did my upgrade interactively using a recent version of aptitude and
purged xpdf-common during that upgrade, cause it was no longer needed
anyway.

I set the severity to important, because it can cause a subsequent
policy violation (copyright file being unavailable).

Could you have a look into this?

Helmut

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.33.2 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash

Versions of packages xpdf depends on:
ii  lesstif2                1:0.95.2-1       OSF/Motif 2.1 implementation relea
ii  libc6                   2.11.2-2         Embedded GNU C Library: Shared lib
ii  libgcc1                 1:4.5-20100103-1 GCC support library
ii  libpoppler5             0.12.4-1         PDF rendering library
ii  libstdc++6              4.5-20100103-1   The GNU Standard C++ Library v3
ii  libx11-6                2:1.3.3-3        X11 client-side library
ii  libxt6                  1:1.0.7-1        X11 toolkit intrinsics library

Versions of packages xpdf recommends:
pn  poppler-data                  <none>     (no description available)
ii  poppler-utils                 0.12.4-1   PDF utilitites (based on libpopple

xpdf suggests no packages.

-- no debconf information

-- debsums errors found:
debsums: missing file /usr/share/doc/xpdf/README.gz (from xpdf package)
debsums: missing file /usr/share/doc/xpdf/changelog.Debian.gz (from xpdf 
package)
debsums: missing file /usr/share/doc/xpdf/changelog.gz (from xpdf package)
debsums: missing file /usr/share/doc/xpdf/copyright (from xpdf package)



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to