should have a consistent "last upgrade date"

Bug #1215943 reported by Sebastien Bacher
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Ubuntu system image
Fix Released
Critical
Barry Warsaw
system-image (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Currently the ubuntu-system-image seems to record its own "last update date", that's inconsistant with what the system settings information are doing which is reading the timestamp written on upgrades:

http://phablet.ubuntu.com/gitweb?p=CyanogenMod/android_bootable_recovery.git;a=commitdiff;h=b4760bf291a535d51747ebd03a732c535bf698d3

That timestamp file was added because stgraber said that with the ro image it wouldn't be possible for the service to store the upgrade date information... is that still the case?

Tags: client
summary: - should have a consistant "last upgrade date"
+ should have a consistent "last upgrade date"
Revision history for this message
Barry Warsaw (barry) wrote :

The file that gets touched in recovery is /userdata/.last_update

Use that file if it exists, if not, fall back to the sqlite db entry.

Barry Warsaw (barry)
tags: added: client
Barry Warsaw (barry)
Changed in ubuntu-system-image:
importance: Undecided → Critical
Changed in ubuntu-system-image:
status: New → Triaged
Barry Warsaw (barry)
Changed in ubuntu-system-image:
milestone: none → 1.7
Barry Warsaw (barry)
Changed in ubuntu-system-image:
assignee: nobody → Barry Warsaw (barry)
milestone: 1.7 → 1.6
status: Triaged → Fix Committed
Barry Warsaw (barry)
Changed in ubuntu-system-image:
status: Fix Committed → Fix Released
Barry Warsaw (barry)
Changed in system-image (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.