- Create empty config dir (it doesn't matter for discovery):
mkdir -p /tmp/config/Ubuntu\ 12.10
- Run crash-digger on gala:
$ APPORT_CRASHDB_CONF=etc/apport/crashdb.conf PYTHONPATH=. bin/crash-digger -C /tmp/cache -a ~/.cache/apport/launchpad.credentials --crash-db=gala -v --config-dir=/tmp/config
10/18/12 17:06:16: Available releases: ['Ubuntu 12.10']
10/18/12 17:06:17: fill_pool: retrace pool now: set([1061853])
10/18/12 17:06:17: retracing #1061853 (left in pool: 0)
10/18/12 17:06:17: crash is release elementary 0.2 which does not have a config available, skipping
bug 1054602 is a duplicate, so crash-digger won't consider that.
Can you please be more specific which bugs should be discovered? Do you confirm that you can see this bug with crash-digger? Can you ensure that your bot has the privileges to see private bugs when they come in?
Here is what I tried:
- I created a crashdb.conf for gala:
$ cat etc/apport/ crashdb. conf.d/ gala-crashdb. conf
gala = {
'impl' : 'launchpad',
'project' : 'gala',
'bug_pattern_base' : None,
}
- Create empty config dir (it doesn't matter for discovery):
mkdir -p /tmp/config/Ubuntu\ 12.10
- Run crash-digger on gala:
$ APPORT_ CRASHDB_ CONF=etc/ apport/ crashdb. conf PYTHONPATH=. bin/crash-digger -C /tmp/cache -a ~/.cache/ apport/ launchpad. credentials --crash-db=gala -v --config- dir=/tmp/ config
10/18/12 17:06:16: Available releases: ['Ubuntu 12.10']
10/18/12 17:06:17: fill_pool: retrace pool now: set([1061853])
10/18/12 17:06:17: retracing #1061853 (left in pool: 0)
10/18/12 17:06:17: crash is release elementary 0.2 which does not have a config available, skipping
This does discover bug 1061853, which indeed matches what I can see on https:/ /bugs.launchpad .net/gala/ +bugs?field. tag=need- amd64-retrace (there might be others which are private and not visible to me, of course).
bug 1054602 is a duplicate, so crash-digger won't consider that.
Can you please be more specific which bugs should be discovered? Do you confirm that you can see this bug with crash-digger? Can you ensure that your bot has the privileges to see private bugs when they come in?