| Summary: | Upgrading M6.0 official to M7 B3 round 3 does not respect current timezone | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Dick Gevers <dvgevers> |
| Component: | Installer | Assignee: | Thierry Vignaud <thierry.vignaud> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | fri, henk, mageia, marja11, shybluenight |
| Version: | 7 | Keywords: | 7beta3, PATCH |
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | drakx-installer-stage2 | CVE: | |
| Status comment: | |||
| Attachments: |
Install of M6.0 bug report dated 20190414
report.bug from upgrade to M7 B3 Round 3 dated 20190415 Proposed patch |
||
|
Description
Dick Gevers
2019-04-15 11:52:54 CEST
Created attachment 10935 [details]
Install of M6.0 bug report dated 20190414
Created attachment 10936 [details]
report.bug from upgrade to M7 B3 Round 3 dated 20190415
Dick Gevers
2019-04-15 11:57:41 CEST
CC:
(none) =>
henk Can't confirm this bug. Tested yesterday a M6 (fully updated) to M7 upgrade, with the netinstall iso (afaik the same drakx-installer-stage2), language en_GB, country Netherlands, timezone was set in M6 to Europe/Amsterdam, the installer did respect the timezone, it was the same. Difference: not on real hardware but in vbox, I did not touch the wireless regulatory domain, M6 was fully updated. CC:
(none) =>
shybluenight
Marja Van Waes
2019-04-15 18:43:24 CEST
Assignee:
bugsquad =>
mageiatools Using M7beta3 Classic ISO x64 real EFI hardware. Locale English/GB, language Welsh, timezone Country/City = France/Paris. I have just done the 6->7 upgrade with a charged 13Gb system, which I brought up-to-date beforehand. It took hours, and there were a few errors necessitating re-launching the upgrade stage, which eventually reached its end. At the summary screen, all the cited elements were still *correct*; and remain so in the upgraded system which I am using. This is consistent with https://bugs.mageia.org/show_bug.cgi?id=24670#c3. For us two at least, the reported problem is not manifest. (In reply to Dick Gevers from comment #0) > * Remove 32 bit media, do NO updates at all. This raised an eyebrow, and made me wonder whether it was a factor. It is always stated that the system to upgrade should be up-to-date (at least to the date of the Classic ISO) before doing an upgrade. P.S. I think bugs 24670 & 24671 could have been posted as one. If there is a problem, it is very probably the same cause. CC:
(none) =>
lewyssmith Tested this in VirtualBox, following Dick's instructions. For me the time zone (UTC) was retained, although the country/region was set to United Kingdom, as reported in bug 24671. I got the same result when fully updating the M6 installation prior to the M7 upgrade. If you manually change the country/region at the Summary stage, that will change the time zone to match. CC:
(none) =>
mageia Created attachment 10949 [details]
Proposed patch
The attached patch (untested) should prevent the time zone being automatically updated when you change the country in the Summary screen.
Martin Whitaker
2019-04-18 21:23:47 CEST
Keywords:
(none) =>
PATCH @Dick I am unclear whether the bugged timezone change comes from the upgrade itself, i.e. on the summary screen, is the timezone initially shown [un]changed before correcting the country? (because of bug 24671) Or only changed due to correcting the country on the summary screen, re c6: > If you manually change the country/region at the Summary stage, > that will change the time zone to match @Martin If the latter, will the patch count as fixing this bug? The fix is okay for me testing with 6.0 > 7 RC round 3 Status:
NEW =>
RESOLVED So can FOR_ERRATA7 be removed? CC:
(none) =>
fri The fact that it is resolved | fixed does imply that, yes :)) Cleaning away the For Errata label then... Keywords:
FOR_ERRATA7 =>
(none)
Lewis Smith
2019-06-30 20:28:25 CEST
CC:
lewyssmith =>
(none) |