Cloud images do not need apt-xapian-index

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1227425/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

Just for the record, this comes from an 'aptitude' recommends.
aptitude comes from tasksel.
tasksel comes from explicit list in the cloud image seed.
tasksel line in the seed references bug 649833.

just history. I've been annoyed by xapian before also.

http://people.canonical.com/~ubuntu-archive/germinate-output/ubuntu.saucy/cloud-image.depends

Can we just drop it then? For 12.04 and later, the message was dropped from images. I would be in favor of removing it from Saucy.

I'm not personally opposed to dropping tasksel.
a ncurses based interactive program doesn't seem like a terribly necessary thing for a cloud image targetted at automation.

Thanks for considering it. I agree that tasksel seems like something from a more server-centric time and it is pretty obsolete in a cloud-instance world.

James page reported:
<jamespage> smoser, I'm seeing update-apt-xapian-index running on first boot of cloud-images
<jamespage> smoser, which is chewing a fair bit of memory and causing some juju/charm related issue
<smoser> i dont kno when that got into the images.
<jamespage> smoser, maybe sometime recently as this was not problem until sometime in the last 3 weeks

I just checked, though and per manifests apt-xapian-index was present in cloud-images since 12.04.

I think that this is probably the root cause of bug 1227533 in juju-core as well.

Thinking about this a bit more I suspect that the reason that this has started happening on first boot is due to the SRU to apt-xapian-index in 12.04. This is being installed on first boot (by cloud-init upgrade) resulting in an index upgrade (triggered by the maintainer script). I guess this will get better once the next 12.04 images are released with this update included.

I moved this to 'aptitude' as the bug because I'd like to keep aptitude in the images as it is popular with users, but I'd like to *not* have apt-xapian-index or at least have a way that we could turn it off.

On 08/10/2013 2:42 AM, "Scott Moser" <email address hidden> wrote:
>
> I moved this to 'aptitude' as the bug because I'd like to keep aptitude
> in the images as it is popular with users, but I'd like to *not* have
> apt-xapian-index or at least have a way that we could turn it off.
>

Aptitude will run fine without axi.

affects ubuntu/aptitude
status invalid

On Tue, 8 Oct 2013, Daniel Hartwig wrote:

> On 08/10/2013 2:42 AM, "Scott Moser" <email address hidden> wrote:
> >
> > I moved this to 'aptitude' as the bug because I'd like to keep aptitude
> > in the images as it is popular with users, but I'd like to *not* have
> > apt-xapian-index or at least have a way that we could turn it off.
> >

>
> Aptitude will run fine without axi.

Well, would you support me moving it from Recommends to Suggests ?

By "turn it off" I really meant the cron job/postinst that runs in
apt-xapian-index.

Configuration of cloud images has nothing to do with packaging of aptitude.

apt-xapian-index isn't in the cloud images any longer.