Your message dated Sun, 6 Sep 2009 11:58:39 +0200
with message-id <20090906095839.ga16...@rivendell>
and subject line Re: Bug#59425: dpkg: install-info shouldn't modify directly 
info dir file
has caused the Debian Bug report #59425,
regarding [INSTALL-INFO] install-info: don't modify info/dir directly, use 
alternate data storage
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
59425: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=59425
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dpkg
Version: 1.6.9
Severity: wishlist

Bugs in install-info can cause dir file breakage which is hard to fix later
(like here, I'm seeing the TeX section before the "The list of major topics
 begins on the next line."). It would be a better idea to save the data in a
harder-to-break file format (like one package per file in some random
/usr/share dir) than doing read-modify-write in a fuzzly-formated file like dir
(which can cause hard-to-fix cumulative errors).

-- System Information
Debian Release: woody
Kernel Version: Linux cesarb2 2.2.14 #1 Fri Feb 11 20:16:40 BRST 2000 i586 
unknown

Versions of the packages dpkg depends on:
ii  libc6          2.1.3-5        GNU C Library: Shared libraries and Timezone
ii  libncurses5    5.0-5          Shared libraries for terminal handling

--- End Message ---
--- Begin Message ---
Version: 1.15.4

On Wed, 01 Mar 2000, [email protected] wrote:
> Package: dpkg
> Version: 1.6.9
> Severity: wishlist
> 
> Bugs in install-info can cause dir file breakage which is hard to fix later
> (like here, I'm seeing the TeX section before the "The list of major topics
>  begins on the next line."). It would be a better idea to save the data in a
> harder-to-break file format (like one package per file in some random
> /usr/share dir) than doing read-modify-write in a fuzzly-formated file like 
> dir
> (which can cause hard-to-fix cumulative errors).

This is solved by the fact that the dir file is regenerated from scratch
every time that a package installs a new info file in the info directory.

Thus, any previous bad modification is lost, and any install-info fix
applies immediately to all entries of all registered info files.

Cheers,
-- 
Raphaƫl Hertzog


--- End Message ---

Reply via email to