|
Bugzilla – Full Text Bug Listing |
| Summary: | YaST2 doesnt hold settings in date/time-module and is checking repositories when launching this module | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.3 | Reporter: | Jens Nixdorf <jens.nixdorf> |
| Component: | YaST2 | Assignee: | Jiří Suchomel <jsuchome> |
| Status: | RESOLVED FEATURE | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | coolo |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | Yast2-Logfile: starting YaST2 (GUI), starting date-time-module, changing entries, cloing module, recheck again. | ||
|
Description
Jens Nixdorf
2008-02-29 16:50:39 UTC
Created attachment 197924 [details]
Yast2-Logfile: starting YaST2 (GUI), starting date-time-module, changing entries, cloing module, recheck again.
Updating repositories: As I wrote in bug #327336, this is WONTFIX for 10.3. The only way to get the fix into 10.3 final would be to release online update for yast2-ntp-client, but this must be first approved by the release manager. In bug #327336, comment #21, coolo says: "These days (and next year when the world changes back to summer time) we'll see more duplicates. But usually changing time isn't a daily operation, so I would see this as annoying not as worth an update." (Adding coolo to Cc:) Always seeing 'manual' option: I believe this should be fixed in yast2-country 2.15.20, changelog says: Thu Sep 13 18:26:15 CEST 2007 - kmachalkova@suse.cz - In 'change date and time' dialog, remember whether synchronization with NTP server has been selected (#308238) But this holds true only within the same 'yast->change date&time' session and it works for me pretty well on my system. If you leave the module (e.g. by clicking finish or abort) and then run it again, you will have 'manual' options checked again, which is, I believe, intentional, not a buggy behaviour. Jirko, can you please comment? yeah, fixing this for 11.0 has to be good enough - plus there is a yast:backports build service repo that Duncan setup, but I'm not sure what other yast dependencies an update would drag in. (In reply to comment #3 from Katarina Machalkova) > But this holds true only within the same 'yast->change date&time' session and > it works for me pretty well on my system. > If you leave the module (e.g. by clicking finish or abort) and then run it > again, you will have 'manual' options checked again, which is, I believe, > intentional, not a buggy behaviour. Jirko, can you please comment? I think it is bug, because it means that ntp client was actually not configured, only the time was synchronized. But this is already addressed in feature 302917 and will be fixed for 11.0 |