This bug was fixed in the package whoopsie - 0.2.49
---
whoopsie (0.2.49) wily; urgency=medium
[ Evan Dandrea ]
* Helper to create recoverable problem reports. Thanks Ted Gould!
[ Brian Murray ]
* Switch build-depends from transitional libgcrypt11-dev to libgcrypt20-dev.
** Branch linked: lp:ubuntu/wily-proposed/whoopsie
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1389357
Title:
whoopsie reuses CRASH_DB_IDENTIFIER on next run
To manage notifications about this bu
** Branch linked: lp:whoopsie
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1389357
Title:
whoopsie reuses CRASH_DB_IDENTIFIER on next run
To manage notifications about this bug go to:
https://bugs
** Changed in: whoopsie (Ubuntu)
Assignee: (unassigned) => Brian Murray (brian-murray)
** Changed in: whoopsie (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
** Tags added: rls-w-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1389357
Title:
whoopsie reuses CRASH_DB_IDENTIFIER on next run
To manage notifications about this bug go to:
https://bugs
** Changed in: whoopsie (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1389357
Title:
whoopsie reuses CRASH_DB_IDENTIFIER on next run
To manage notifications
This will mean that tests in CI will negligibly skew the results, but I
think we can live with that for now. I agree that this is low priority.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1389357
Ti
