Package: doc-base
Version: 0.10.1
Severity: important

# DOC_BASE_MAINT_DEBUG=y DOC_BASE_MAINT_VERBOSE=y dpkg --configure doc-base
Setting up doc-base (0.10.1) ...
entering doc-base postinst
+ dpkg --compare-versions 0.10.1 lt-nl 0.10.0~
+ [ ! -f /var/lib/doc-base/info/status.yml ]
+ reinstall_docs changed
+ status=0
+ install-docs -v --install-changed
Processing 29 added doc-base files...
Cannot open file `/usr/share/doc-base/python-policy.dpkg-tmp' for reading: No 
such file or directory.
+ status=3
+ [ 3 = 10 ]
+ [ 3 = 0 ]
+ exit 3
dpkg: error processing doc-base (--configure):
 subprocess installed post-installation script returned error exit status 3
Errors were encountered while processing:
 doc-base

The index /var/lib/doc-base/info/status.yml contains these lines:

--- BEGIN ---
python-policy:
  CF:
    /usr/share/doc-base/python-policy: ~
    /usr/share/doc-base/python-policy.dpkg-tmp: ~
  SD: {}
--- END ---

It was last updated some time ago:

-rw-r--r-- 1 root root 26031 Apr 11 01:16 /var/lib/doc-base/info/status.yml

Ben.

-- System Information:
Debian Release: wheezy/sid
  APT prefers proposed-updates
  APT policy: (500, 'proposed-updates'), (500, 'oldstable-proposed-updates'), 
(500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: i386 (x86_64)

Kernel: Linux 2.6.38-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages doc-base depends on:
ii  libuuid-perl                  0.02-4     Perl extension for using UUID inte
ii  libyaml-tiny-perl             1.48-1     Perl module for reading and writin

doc-base recommends no packages.

Versions of packages doc-base suggests:
ii  rarian-compat            0.8.1-5         Documentation meta-data library (c
ii  yelp                     2.30.1+webkit-1 Help browser for GNOME

-- no debconf information



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

Reply via email to