On Tue, 2008-09-16 at 14:32 +0200, Miguel Aguado wrote: > > Ross Boylan is right in that indexing should not stop the upgrade of > other packages. Originally I thought it was hung up; however the problem seems to be that it takes a long time, like several hours.
It is possible the slow speed is a result of a bug in one of the indexing packages. The operation seems to me to take too long to be part of the regular upgrade process; I think many people will just decide something is broken. If delays of several hours happen while tracking testing, it seems likely the situation will be even worse for people upgrading from stable to the next release. > It should be run in the background after a prominent > warning for the user, along the lines of: This proposal might be inconsistent with how debconf is supposed to be used. It also has the problem that if someone interrupts it, for example by shutting the system down, it will not resume. Perhaps an anacron job would be an appropriate solution. That leaves open the question of what to do before or while the index is updating. > > dhelp: Indexing documentation in the background. > **Please note that this process may take HOURS on bulky doc upgrades.** > Documentation will not be fully accessible until indexing is complete. > > (if a further upgrade happens while /usr/bin/index++ is still running, > of course, duplicates should be avoided.) > > I am aware that users of the stable release need not upgrade as often as > those of testing or unstable. However, please consider raising the > severity of this bug This does appear to be a problem that could effectively break upgrades to lenny, at least for systems with significant documentation installed. > so that it can be at least circumvented for lenny, > by backgrounding the indexing. Anyone can ^C the process, but that is > probably not the best option... Ross -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
