indexing fails after a upgrade if the apt-xapian-index is not yet regenerated
Bug #646018 reported by
Michael Vogt
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apt-xapian-index (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
software-center (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Binary package hint: software-center
If the apt-xapian-index is not re-generated fully (a update-
Changed in software-center (Ubuntu): | |
milestone: | none → ubuntu-10.10 |
importance: | Undecided → Medium |
status: | New → In Progress |
Changed in apt-xapian-index (Ubuntu): | |
status: | New → In Progress |
importance: | Undecided → Medium |
milestone: | none → ubuntu-10.10 |
To post a comment you must log in.
There are two issues here, one is that update- software- center does not index without catalogedtime, that is fixed now.
The other one is that on upgrade we need to run a full re-index of apt-xapian-index so that the cataloged time data is written for all packages. By default the apt-xapian-index weekly cron job rus with "--update" and the dbus service that software-center triggers run with --update as well. But update will only look at the changed packages, in this case (and in every case when a new index plugin is availalbe) we want to do a full-reindex to benefit from the new plugin.