> > - do not modify the DB "in-place" with --update to avoid
> > software-center seeing a corrupted database when it has
> > it open at the same time
Yes, that appears to be the argument for removing --update, which was otherwise added in an upstream patch.
It is unfortunate that update-apt-xapian-index resource use is increased many-fold due to Software Center not (gracefully) handling an in-progress update. Depending on the nature of the Software Center issue, this choice is perhaps understandable.
I should note that I was NOT able to reproduce any issue with Software Center while running update-apt-xapian-index --update. The closest thing I could get was a 10 second "animated loading ring" coinciding with the update process being at 99% (any io heavy activity could probably give that result, though).
> fyo, do you mean this statement:
> > - do not modify the DB "in-place" with --update to avoid
> > software-center seeing a corrupted database when it has
> > it open at the same time
Yes, that appears to be the argument for removing --update, which was otherwise added in an upstream patch.
It is unfortunate that update- apt-xapian- index resource use is increased many-fold due to Software Center not (gracefully) handling an in-progress update. Depending on the nature of the Software Center issue, this choice is perhaps understandable.
I should note that I was NOT able to reproduce any issue with Software Center while running update- apt-xapian- index --update. The closest thing I could get was a 10 second "animated loading ring" coinciding with the update process being at 99% (any io heavy activity could probably give that result, though).