Need to enable apport bug reporting in non-installed packages

[Philip Peitsch]

Apport bug reporting currently only works after a package is installed. Ideally, apport hooks & configs should exectuable from the dev folder to allow testing of this feature.

[Didier Roche-Tolomelli (didrocks)]

In fact, there are three cases:
- trunk not yet binded to LP (show not show / or output something in the commands line)
- trunk binded with a LP project: should work (maybe adding additional info like "trunk"? that's not important and can be done later)
- installed package (this should already work ;))

[Didier Roche-Tolomelli (didrocks)]

Oh, I was forgetting, try to use a project name which isn't the same like the LP one.

For instance I use "gooby" and the LP project that I bind to is "fooby". This one is dedicated to Quickly test, if you want to bind and open bug report against it, it doesn't hurt :)

[Philip Peitsch (philip-peitsch)]

The problem seems quite deeply rooted in how launchpad-integration works. Currently, lpi supports:

* fromProcessID(options.pid, logger)
* fromFilename(options.filename, logger)
* fromPackageName(options.package, logger)
* fromXID(options.xid, logger)

It uses these options to look up the relevant information from a package. Basically, another option needs to be added somehow to allow overriding the lookup functionality to use a hardcoded control file for a particular package.

I've raised a bug upstream for this and will spend some time addressing that. That is the required functionality to address both this issue, and the associated crash as seen when attempting to launch the report a bug feature prior to installing the package under development.

[Philip Peitsch (philip-peitsch)]

Previous comment is really a new bug I think. I have raised Bug #534982 to more correctly track that detailing

[Didier Roche-Tolomelli (didrocks)]

Hum, you didn't propose a merge-request, so I don't know if I can merge this branch or not :)

[Philip Peitsch (philip-peitsch)]

Whups. wrong bug report again. That must have been a bad day. Sorry :S. Solution is coming for this one soon :)

[Philip Peitsch (philip-peitsch)]

This is currently blocked on bug #534968. I was never able to get the patch reviewed or landed unfortunately.