Feature changed by: jpxviii jpxviii (jpxviii) Feature #303517, revision 33 Title: Automatically refreshing repositories at recurring intervals openSUSE-11.1: Rejected by Stanislav Visnovsky (visnov) reject date: 2008-09-12 14:12:10 reject reason: Postponing. Priority Requester: Desirable Projectmanager: Important openSUSE-11.2: Rejected by Stephan Kulow (coolo) reject date: 2009-08-12 10:54:36 reject reason: noone volunteering Priority Requester: Desirable Projectmanager: Desirable + openSUSE-11.4: Unconfirmed + Priority + Requester: Desirable Requested by: Ladislav Slezak (lslezak) Description: Autorefresh configured repositories at certain times, this could be on certain days, or time of day, etc. A mockup and more details are in https://bugzilla.novell.com/show_bug.cgi?id=346966 Discussion: #1: Federico Lucifredi (flucifredi) (2008-06-13 15:12:52) there are some caveats I can think of requiring silent fail (for instance, a laptop), or requiring randomization (not hitting NCC with a volley all at the same time), but I think the idea is good. #2: Duncan Mac-Vicar (dmacvicar) (2008-07-07 11:13:37) If you think you can make it work in a reliable way, please present a concept. Right now PackageKit and updater applets do refresh often before checking for updates so the system repos _are_ refreshed. So I don't see much value in this feature (unless a concept is presented). #3: Stanislav Visnovsky (visnov) (2008-07-07 12:34:19) (reply to #2) We have a concept in the automatic online update configuration. #4: Jiri Srain (jsrain) (2008-07-07 12:58:59) (reply to #3) You mean running online update from cron? It should involve metadata refresh, but I do not see any reason for a separate metadata download from cron. #5: Ladislav Slezak (lslezak) (2008-07-09 10:30:09) (reply to #4) The feature should allow to disable "autorefresh" flag for all repositories so the package management can be started quickly without connecting to network. The cronjob would keep the metadata uptodate. Of course, there might be a problem when metadata are changed too often on the server, but in my opinion that's not a usual case in the real world. #6: Jiri Srain (jsrain) (2008-07-10 12:16:08) Let's extend the "automatic online update" module so that it offers whether to do real automatic online update, or just refresh the metadata (via one check box) #8: J. Daniel Schmidt (jdsn) (2008-07-18 18:13:38) (reply to #6) This would hide the feature in an update related module. But the feature does not restrict this only to update repositories. Build- Service Repos might need a refresh as well or think of Factory. The right place for this feature is the Repository Manager. It has no relation to the update process or a configuration concerning updates. #7: Jiří­ Suchomel (jsuchome) (2008-07-14 14:46:01) Daniel, what's the status of the plan to merge "online update configuration" into registration module? #9: J. Daniel Schmidt (jdsn) (2008-07-18 18:15:46) (reply to #7) Currently I plan to merge it into a new module together with "Online Update Configuration" related settings. Please do not extend it with this unrelated repo refreshing dialog. #10: J. Daniel Schmidt (jdsn) (2008-09-10 19:48:24) Why am I listed as the only developer here? I just said that I will merge the modules "automatic online update setup" and "online update setup". This feature is requesting something completely different. #11: Duncan Mac-Vicar (dmacvicar) (2008-09-10 22:21:17) (reply to #10) Don't worry, this feature will be dropped as because the OnStar work. It is just abandoned. #13: Jiří­ Suchomel (jsuchome) (2008-09-11 08:20:55) (reply to #11) Really? I don't think so.This feature is aimed for opensuse (it wants to extend the current "online update setup"), while OnStar is for SLE. #12: Jiří­ Suchomel (jsuchome) (2008-09-11 08:22:02) (reply to #10) Because the requested feature would be part of what is currently "online update setup". And after the merge, I assumed you should mainain the merged parts. #15: J. Daniel Schmidt (jdsn) (2008-09-11 12:37:19) (reply to #12) No the requested feature will not be part of the successor of "online update setup". Maybe you want it to be. But IMHO this has nothing to do with anything that is called "online update *something*". This feature is about a general refresh of repositories - not just the update repo. Software repositories are handled in the "Software repositories" module. And thats the place where this feature is asking for enhancement. Just look at the linked bug (bnc#346966). It even has a mockup (yes, I added one as well, but just look at the original one). And this is now quite the same I already wrote in comment #8. #16: Jiří­ Suchomel (jsuchome) (2008-09-11 12:44:53) (reply to #15) Ah, sorry. Looks like I have some other feature in mind while commenting this one. This one really is not online-update specific. #19: Robert Davies (robopensuse) (2009-01-16 16:30:40) As when I go into Software Repository management, I am offered check boxes like "autorefresh", it would seem when those boxes are checked, that I expect this to happen without knowing about it. Being made to wait, when I choose to run Online Update, or Software Management, seems to defeat purpose of auto-refresh feature, though it is understandable if no refresh was done for days. Some kind of cron job, ought to just handle this. Why should the user be asked more questions than "autorefresh" tick box? #20: Stephan Kulow (coolo) (2009-04-16 13:47:23) looking for community volunteers #21: Stephan Kulow (coolo) (2009-08-12 10:54:24) (reply to #20) 5 votes, no volunteer. I reject it -- openSUSE Feature: https://features.opensuse.org/303517