conffiles prompt on vivid upgrade if report_metrics is enabled
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | whoopsie (Ubuntu) |
Undecided
|
Unassigned | ||
| | whoopsie-preferences (Ubuntu) |
Undecided
|
Unassigned | ||
Bug Description
There is a potential conffiles prompt when upgrading to vivid if report_metrics has been enabled, as we remove the report_crashes and use service enablement.
Moving that value to a non conffiles (/ect/whoopsie) and using that in whoopsie-
The conffile (/etc/default/
[General]
report_crashes=true
For now, we remove the "report_crashes" (job enablement value) in preinst with sedding, and ship a new conffiles:
[General]
However, user might have changed the report metrics option in gnome-control-
[General]
report_crashes=true
report_metrics=true
Proposal:
1. we continue transitioning, removing "report_crashes" and cache that for job enablement/
2. we remove completely the conffile on upgrade/removal
3. we move report_metrics value (if present in conffiles) to /etc/whoopsie, file with only
[General]
report_metrics= true
if report_metrics was set to true
4. we patch whoopsie g-c-c capplet to read/update from /etc/whoopsie
| description: | updated |
| Launchpad Janitor (janitor) wrote : | #1 |
| Changed in whoopsie-preferences (Ubuntu): | |
| status: | New → Fix Released |
| Launchpad Janitor (janitor) wrote : | #2 |
This bug was fixed in the package whoopsie - 0.2.47
---------------
whoopsie (0.2.47) vivid; urgency=medium
[ Didier Roche ]
* Remove /etc/default/
(LP: #1431432)
- debian/
- debian/
by gnome-control-
(LP: #1412719)
Refactor the logic for caching report_crashes as well.
- debian/
service started after upgrade and keep it disable if it was disabled
- Makefile, data/whoopsie: remove the conffile so that we don't ship it
* Bump Standards-Version
[ Michael Blennerhassett ]
* Under upstart: Set the WAIT_STATE to get wait-for-state to do something
useful. GOAL is also not needed.
-- Didier Roche <email address hidden> Thu, 12 Mar 2015 17:21:58 +0100
| Changed in whoopsie (Ubuntu): | |
| status: | New → Fix Released |


This bug was fixed in the package whoopsie- preferences - 0.14
--------------- preferences (0.14) vivid; urgency=medium
whoopsie-
* Now use service status (upstart and systemd) to notify if crash reporting
is enabled (LP: #1412719)
* Default file for whoopsie settings (only used for report_metrics currently)
is now /etc/whoopsie (LP: #1431432)
* debian/control: add Breaks to ensure we dep on the right whoopsie version
* Update Standards-Version.
-- Didier Roche <email address hidden> Thu, 12 Mar 2015 17:39:30 +0100