tags 301449 + sarge
thanks

hi :)

On Sat, Mar 26, 2005 at 05:13:22PM -0800, Ross Boylan wrote:
> 
> Unfortunately, this is to confirm that the problem still exists with
> the latest libboost.  So apparently it was the 2 upgrades that fixed
> it.
> 
> I just upgraded another system from 1.31.0-9 directly to 1.32.0-4.
> Once again, there are missing files, including at least the 2 I
> mentioned previously.

this bug is due to the broken way /usr/share/doc/libboost-doc/HTML/boost
was created on the filesystem. it has been fixed in package 1.32.0-4,
bug #290333 and others merged with it. please read those bug reports
for the complete story.


bug explanation
~~~~~~~~~~~~~~~~
package libboost-doc used to install some stuff under $DOC/HTML/boost/ [0].
dpkg then known this stuff in dir $DOC/HTML/boost/ was of package
libboost-doc.

problem was that libboost-doc postinst script removed $DOC/HTML/boost/
and made it a symlink to /usr/include/boost.

now, when dpkg removed libboost-doc's files to replace them with the
new ones, it instead removed those in /usr/include/boost, owned by some
other boost package. if that package was not going to be re-installed,
they were then definitively removed and resulted missing.  please note
that which files and which packages were involved depended by the order
of package upgrade!

since 1.32.0-4 the symlink is created in the correct way. this guarantees
the upgrade bug is not present in *future* (>= 1.32.0-4) version upgrades
but nothing can be done for the past versions ones.

this explanation does not explain why the bug is seen only between
1.31.0 <-> 1.32.0 transition and why reinstalling the same version
packages works around it. i suppose only to not know all the details
required to explain them.

cheers
domenico

[0] $DOC is /usr/share/doc/libboost-doc/

-----[ Domenico Andreoli, aka cavok
 --[ http://people.debian.org/~cavok/gpgkey.asc
   ---[ 3A0F 2F80 F79C 678A 8936  4FEE 0677 9033 A20E BC50


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

Reply via email to