Closed
Bug 928432
Opened 11 years ago
Closed 11 years ago
Story - metroapp.ini doesn't get upgraded for pave over installs with a changed base name
Categories
(Firefox for Metro Graveyard :: Install/Update, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: bbondy, Unassigned)
Details
emtwo noticed that pave over installs doesn't upgrade the metroapp.ini file. This may also be a problem for upgrades. We need to look into that case or possibly change the ini file name. p=2
Updated•11 years ago
|
Blocks: metrov1backlog
Summary: metroapp.ini doesn't get upgraded for pave over installs with a changed base name → Story - metroapp.ini doesn't get upgraded for pave over installs with a changed base name
Whiteboard: feature=story c=tbd u=tbd p=2
Updated•11 years ago
|
Whiteboard: feature=story c=tbd u=tbd p=2 → [block28] feature=story c=tbd u=tbd p=2
Reporter | ||
Updated•11 years ago
|
No longer blocks: metrov1backlog, metroprofilesharing
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
Whiteboard: [block28] feature=story c=tbd u=tbd p=2
Reporter | ||
Comment 1•11 years ago
|
||
Turns out this wasn't a problem, moving points back to replenish the contingency bug.
You need to log in
before you can comment on or make changes to this bug.
Description
•