Your message dated Thu, 28 Dec 2006 11:40:20 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#404631: missing files under /usr/share/doc/libtiff-tools/
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: libtiff-tools
Version: 3.8.2-6
Severity: serious
copyright file is not shipped along, which violates the policy.
Might be some cdbs flaw which led to such package?
> dpkg -L libtiff-tools | grep doc
/usr/share/doc
/usr/share/doc/libtiff-tools
> ls -l /usr/share/doc/libtiff-tools/
total 0
-- System Information:
Debian Release: 4.0
APT prefers unstable
APT policy: (600, 'unstable'), (300, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.19-rc6-mm1
Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R)
Versions of packages libtiff-tools depends on:
ii libc6 2.3.6.ds1-9 GNU C Library: Shared libraries
ii libjpeg62 6b-13 The Independent JPEG Group's JPEG
ii libtiff4 3.8.2-6 Tag Image File Format (TIFF) libra
ii zlib1g 1:1.2.3-13 compression library - runtime
libtiff-tools recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
> Yaroslav Halchenko <[EMAIL PROTECTED]> wrote:
>
>> Well. Situation persists after reinstallation.
>> Purging first and reinstallation of libtiff-tools helps.
>>
>> Thus I confirm the bug which probably exists due to improper handling of
>> link creation during upgrades, thus probably will be present in
>> etch shipped to people upgrading from sarge.
>>
> . . .
>
> I have reopened the bug and will look into the problem more deeply,
> attempting to determine whether the problem is in libtiff or something
> else such as dpkg or apt . . .
I'm closing this bug once again as the problem is not with tiff's
packaging but with dpkg or something related to it. I have confirmed
that upgrading from 3.7.2-7 (the sarge version) to 3.8.2-6 leaves an
empty /usr/share/doc/libtiff-tools behind and that dpkg -P
libtiff-tools followed apt-get install libtiff-tools creates the link
as expected. It appears that dpkg is not successfully replacing a
directory with a symbolic link, but I need to confirm this. I noticed
that my sid system, which I installed in 2003 or 2004 with an early
sarge debian-installer candidate version and have been upgrading since
contains several empty directories in /usr/share/doc:
/usr/share/doc/attr
/usr/share/doc/bogofilter
/usr/share/doc/cdrecord
/usr/share/doc/libxml2-dev
/usr/share/doc/libxml2-utils
/usr/share/doc/python-dev
/usr/share/doc/python-examples
/usr/share/doc/libapr1.0
Before I had /usr/share/doc/idle there as well. When I uninstalled
and reinstalled it, I got /usr/share/doc/idle as a link to python. So
this problem is obviously affecting multiple packages. Creating links
in /usr/share/doc seems completely valid though:
% find /usr/share/doc -maxdepth 1 -type l -print | wc -l
133
I will report a bug against dpkg (or whatever I determine to be
appropriate) after coming up with a reliable recipe to reproduce the
problem. I'll debbugs-cc you unless you tell me not to.
--
Jay Berkenbilt <[EMAIL PROTECTED]>
--- End Message ---
