September 2008 - openSUSE Features - openSUSE Mailing Lists

[openFate 303517] Configure a cronjob for refreshing repositories
by fate_noreply＠suse.de 11 Sep '08

11 Sep '08

Feature changed by: Jiří Suchomel <jsuchome(a)novell.com> Feature #303517, revision 20 Title: Configure a cronjob for refreshing repositories openSUSE-11.1: Evaluation Priority Requester: Desirable Projectmanager: Mandatory Requested by: Ladislav Slezak <lslezak(a)novell.com> Partner organization: openSUSE.org 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(a)novell.com> (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(a)novell.com> (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(a)novell.com> (2008-07-07 12:34:19) (reply to #2) We have a concept in the automatic online update configuration. #4: Jiri Srain <jsrain(a)novell.com> (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(a)novell.com> (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(a)novell.com> (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(a)novell.com> (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(a)novell.com> (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(a)novell.com> (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(a)novell.com> (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(a)novell.com> (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(a)novell.com> (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(a)novell.com> (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(a)novell.com> (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(a)novell.com> (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. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=303517

1 0

[openFate 303517] Configure a cronjob for refreshing repositories
by fate_noreply＠suse.de 11 Sep '08

11 Sep '08

Feature changed by: J. Daniel Schmidt <jdsn(a)novell.com> Feature #303517, revision 19 Title: Configure a cronjob for refreshing repositories openSUSE-11.1: Evaluation Priority Requester: Desirable Projectmanager: Mandatory Requested by: Ladislav Slezak <lslezak(a)novell.com> Partner organization: openSUSE.org 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(a)novell.com> (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(a)novell.com> (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(a)novell.com> (2008-07-07 12:34:19) (reply to #2) We have a concept in the automatic online update configuration. #4: Jiri Srain <jsrain(a)novell.com> (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(a)novell.com> (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(a)novell.com> (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(a)novell.com> (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(a)novell.com> (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(a)novell.com> (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(a)novell.com> (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(a)novell.com> (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(a)novell.com> (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(a)novell.com> (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(a)novell.com> (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. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=303517

1 0

[openFate 303708] [CODE11-GM] Mascot for YaST
by fate_noreply＠suse.de 11 Sep '08

11 Sep '08

Feature changed by: Stanislav Visnovsky <visnov(a)novell.com> Feature #303708, revision 12 - Title: Mascot for YaST + Title: [CODE11-GM] Mascot for YaST openSUSE-11.1: Candidate Priority Requester: Mandatory Projectmanager: Desirable Requested by: Andreas Jaeger <aj(a)novell.com> Partner organization: openSUSE.org Description: Every successfull product has it's own logo and mascot. We should create and market one for YaST as well, display it prominently on all YaST project pages and also in YaST, e.g. in any About screens or as easter egg. Discussion: #2: Michael Loeffler <michl(a)novell.com> (2008-04-24 12:46:55) I'm fine with that. I think this should come out of the inner YaST circle with some help from design people like Jakub. #3: Michael Loeffler <michl(a)novell.com> (2008-04-24 19:54:31) (reply to #2) And we should inlcude the community on that. Zonker might call for ideas/participation for logo creation on his blog and news.openSUSE. org #4: Duncan Mac-Vicar <dmacvicar(a)novell.com> (2008-04-25 12:08:16) # zypper moo \\\\\ \\\\\\\__o __\\\\\\\'/_ http://en.wikipedia.org/wiki/Hedgehog -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=303708

1 0

[openFate 303517] Configure a cronjob for refreshing repositories
by fate_noreply＠suse.de 11 Sep '08

11 Sep '08

Feature changed by: Jiri Srain <jsrain(a)novell.com> Feature #303517, revision 18 Title: Configure a cronjob for refreshing repositories - openSUSE-11.1: Candidate + openSUSE-11.1: Evaluation Priority Requester: Desirable Projectmanager: Mandatory Requested by: Ladislav Slezak <lslezak(a)novell.com> Partner organization: openSUSE.org 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(a)novell.com> (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(a)novell.com> (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(a)novell.com> (2008-07-07 12:34:19) (reply to #2) We have a concept in the automatic online update configuration. #4: Jiri Srain <jsrain(a)novell.com> (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(a)novell.com> (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(a)novell.com> (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(a)novell.com> (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(a)novell.com> (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(a)novell.com> (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(a)novell.com> (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(a)novell.com> (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(a)novell.com> (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(a)novell.com> (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. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=303517

1 0

[openFate 302119] Load package selector and libzypp only when needed
by fate_noreply＠suse.de 11 Sep '08

11 Sep '08

Feature changed by: Jiri Srain <jsrain(a)novell.com> Feature #302119, revision 28 Title: Load package selector and libzypp only when needed openSUSE-10.3: Rejected by Stanislav Visnovsky <visnov(a)novell.com> reject date: 2007-08-01 16:40:54 reject reason: Postponing. Priority Requester: Desirable Projectmanager: Important openSUSE-11.0: Rejected by Stanislav Visnovsky <visnov(a)novell.com> reject date: 2008-04-28 13:42:30 reject reason: Did not make it, postponing. Priority Requester: Desirable Projectmanager: Important - openSUSE-11.1: Candidate + openSUSE-11.1: Evaluation Priority Requester: Desirable Projectmanager: Important Requested by: Stefan Hundhammer <sh(a)novell.com> Partner organization: openSUSE.org Description: The YaST2 UI should load the code for the package selector and libzypp only when needed. Not all applications / YaST2 modules need package selection code, yet for all of them the respective code from the YaST2 UI and libzypp is loaded. Discussion: #1: Stefan Hundhammer <sh(a)novell.com> (2007-04-13 18:13:44) In the YaST2 Qt the package management related code is now moved to a separate plugin that is loaded upon demand only if the calling YCP application actually requests a PackageSelector widget. This reduces the memory footprint from 20 MB VmRSS minimum (HelloWorld. ycp) to 18 MB minimum (PackageSelector-empty.ycp). #3: Katarina Machalkova <kmachalkova(a)novell.com> (2007-04-16 14:41: 35) Stano, do we want this for curses UI as well? If yes, than it's not 'done' ... #4: Stanislav Visnovsky <visnov(a)novell.com> (2007-04-16 14:47:02) (reply to #3) Agreed. Reopening for ncurses and possibly gtk+. #5: Jiri Srain <jsrain(a)novell.com> (2007-06-13 13:54:26) JP, both Qt and NCurses are done, but GTK is still missing. #6: Stefan Hundhammer <sh(a)novell.com> (2007-06-13 15:08:58) Looks like yast2-pkg-bindings are also loaded unconditionally. It shouldn't be too hard to do that with "lazy initialization" like UI built-ins: Postpone loading the Y2Component until it's really needed. #7: Stanislav Visnovsky <visnov(a)novell.com> (2007-06-19 15:01:54) (reply to #6) Jiri, if Pkg bindings problem is not addressed, it does not make sense to fix Gtk UI. #8: Jiri Srain <jsrain(a)novell.com> (2007-07-18 13:59:50) (reply to #7) Sorry for missing this. Martin, please, solve this for the Pkg bindings. #10: Stanislav Visnovsky <visnov(a)novell.com> (2007-11-08 11:38:22) (reply to #9) Please, follow up on this. #11: Martin Vidner <mvidner(a)novell.com> (2008-04-10 15:23:51) yast2-perl-bindings-2.16.6 no longer links to libzypp, which means libzypp will not be loaded at the very start of yast (perl still will be loaded, but that is relatively cheap). That helps in some cases, but mostly it only delays loading of libzypp, which occurs as soon as Pkg (or Package) is imported. Now I need to make Pkg lazy. #12: Martin Vidner <mvidner(a)novell.com> (2008-04-21 15:32:09) I have it almost working, but got stopped by bug 381917 (https://bugzilla.novell.com/show_bug.cgi?id=381917) : problems with destructors of static objects #13: JP Rosevear <jpr(a)novell.com> (2008-07-21 13:59:18) (reply to #12) Martin, what's the status here? Will we need to do anything explicit in packagekit to get this functionality? #14: Stanislav Visnovsky <visnov(a)novell.com> (2008-09-08 16:44:06) (reply to #13) There is nothing regarding packagekit for this feature. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=302119

1 0

[openFate 303700] Ability to log all configuration changes done via YaST
by fate_noreply＠suse.de 11 Sep '08

11 Sep '08

Feature changed by: Jiri Srain <jsrain(a)novell.com> Feature #303700, revision 18 Title: Ability to log all configuration changes done via YaST - openSUSE-11.1: Candidate + openSUSE-11.1: Done Priority Requester: Mandatory Projectmanager: Mandatory - SLED-11: Candidate + SLED-11: Done Priority Requester: Mandatory Projectmanager: Mandatory - SLES-11: Candidate + SLES-11: Done Priority Requester: Mandatory Projectmanager: Mandatory Requested by: Matthias Eckermann <mge(a)novell.com> Partner organization: openSUSE.org Description: Provide the ability to log all configuration changes done via YaST. Additionally, in this mode an admin would be prompted to document what was the nature/purpose of the change as the module is being closed, akin to commit messages in a versioning system. Documentation Impact: The new log file needs to be documentated in admin guide. Discussion: #1: Federico Lucifredi <flucifredi(a)novell.com> (2008-04-30 15:27:04) note fate 303688 related: packaging CFT. I am not sure CFT is the right way to provide this functionality, but a consideration is that an admin using CFT will probably log both manual-editing and YaST-driven conf changes via the same tool. #2: Stanislav Visnovsky <visnov(a)novell.com> (2008-06-03 12:40:41) Duncan, Jiri, this might be an architectural change, please, look into this. Also, we might need to define scope of which changes we are able to track. #3: Jiri Srain <jsrain(a)novell.com> (2008-07-07 10:45:35) Martin, please, have a look at possibilities to record all changes and suggest an infrastructure. Federico, we will hardly be able to make all modules record all the changes they do. Could you, please, give us some priorities for SLE11? #6: Federico Lucifredi <flucifredi(a)novell.com> (2008-07-28 19:58:20) (reply to #3) Sure: network, users+groups would be a start. #4: Martin Vidner <mvidner(a)novell.com> (2008-07-08 11:44:54) This looks like a superset of feature 100386. Note that that one was downgraded because it is large (it requires touching all YaST modules). #5: Stanislav Visnovsky <visnov(a)novell.com> (2008-07-08 12:08:56) (reply to #4) Please, look into enabling of the stuff, not covering all YaST modules. #7: Federico Lucifredi <flucifredi(a)novell.com> (2008-07-28 19:59:34) (reply to #5) Indeed. Look at this architecturally. Also please keep in mind that the maintainer of CFT will help in getting that too to work on SLE (eventually, not for 11 GA timeframe), so please keep in mind these logs could feed into CFT eventually (and we would not want to change too much to make that happen :-) + #8: Jiri Srain <jsrain(a)novell.com> (2008-09-11 09:34:17) + Infrastructure is in, module using it will come later. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=303700

1 0

[openFate 100386] Support a verbose logging mode in yast
by fate_noreply＠suse.de 11 Sep '08

11 Sep '08

Feature changed by: Jiri Srain <jsrain(a)novell.com> Feature #100386, revision 31 Title: Support a verbose logging mode in yast openSUSE-10.2: Rejected by Andreas Jaeger <aj(a)novell.com> reject date: 2006-09-30 20:43:33 reject reason: for 10.3. Priority Requester: Desirable Projectmanager: Desirable openSUSE-10.3: Rejected by Stanislav Visnovsky <visnov(a)novell.com> reject date: 2007-08-01 10:24:26 reject reason: Postponing, needs more research. Priority Requester: Important Projectmanager: Important openSUSE-11.0: Rejected by Federico Lucifredi <flucifredi(a)novell.com> reject date: 2008-06-28 19:27:16 reject reason: fixing my typo. Mandatories in the past don't work (yet). Priority Requester: Important Projectmanager: Important - openSUSE-11.1: Candidate + openSUSE-11.1: Done Priority Requester: Important Projectmanager: Important SL-10.0: Rejected by Andreas Jaeger <aj(a)novell.com> reject date: 2005-12-02 14:56:13 reject reason: not done. Priority Requester: Desirable - SLES-11: Candidate + SLES-11: Done Priority Requester: Important Projectmanager: Important Requested by: Andreas Jaeger <aj(a)novell.com> Partner organization: openSUSE.org Description: Create a verbose logging mode in yast, where any action yast performs is logged. Any file yast touches should be logged (to /var/log/YaST2/y2log AND clean up the structure of that log file, to make it easier to read and interpret) and all changes on the systems configuration. The goal is to make it really transparent what yast does. Documentation Impact: Admin guide needs to contain information about the new log file. Please add it to the Log file section in the troubleshooting chapter Discussion: #1: Edith Parzefall <emap(a)novell.com> (2006-09-28 17:17:54) Can't be done for 10.2. Back to TPMs. #2: Edith Parzefall <emap(a)novell.com> (2007-07-31 16:17:45) Sorry, couldn't be done for 10.3. We need a concept for this. Even within the team different developers have different needs. Improving the logging to give all developers the best possible debugging information will be difficult, but it's definitely something we should attempt in the near future. #3: Stanislav Visnovsky <visnov(a)novell.com> (2007-11-08 10:48:48) Can we get some traction here finally? #4: Stanislav Visnovsky <visnov(a)novell.com> (2007-11-28 10:16:38) Reopening, the YaST transparency is often cited as a problem for users. #6: Federico Lucifredi <flucifredi(a)novell.com> (2008-06-28 17:13:54) I think this has enough user benefit and is trivial enough, we should just get it done. #7: Federico Lucifredi <flucifredi(a)novell.com> (2008-06-28 19:28:04) PM-Priority for product openSUSE-11.0 downgraded from mandatory to : oops. Too many widgets for my tired brain. #8: Stanislav Visnovsky <visnov(a)novell.com> (2008-07-01 16:49:08) (reply to #7) This cannot be done completely - this is non-trivial amount of work. I suggest to start this though, having the YaST infrastructure in place ASAP. Federico, please, downgrade the priority. #9: Federico Lucifredi <flucifredi(a)novell.com> (2008-07-02 14:01:05) PM-Priority for product SLES-11 downgraded from mandatory to important: too much work for a one-off apparently. #10: Federico Lucifredi <flucifredi(a)novell.com> (2008-07-02 14:01:27) PM-Priority for product openSUSE-11.1 downgraded from mandatory to important: too much work for a one-shot. #12: Stanislav Visnovsky <visnov(a)novell.com> (2008-09-10 11:03:50) I've added y2useritem and y2usernote builtins into yast2-core. This might be helpful for this feature. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=100386

1 0

[openFate 303517] Configure a cronjob for refreshing repositories
by fate_noreply＠suse.de 11 Sep '08

11 Sep '08

Feature changed by: Jiří Suchomel <jsuchome(a)novell.com> Feature #303517, revision 16 Title: Configure a cronjob for refreshing repositories openSUSE-11.1: Candidate Priority Requester: Desirable Projectmanager: Mandatory Requested by: Ladislav Slezak <lslezak(a)novell.com> Partner organization: openSUSE.org 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(a)novell.com> (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(a)novell.com> (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(a)novell.com> (2008-07-07 12:34:19) (reply to #2) We have a concept in the automatic online update configuration. #4: Jiri Srain <jsrain(a)novell.com> (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(a)novell.com> (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(a)novell.com> (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(a)novell.com> (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(a)novell.com> (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(a)novell.com> (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(a)novell.com> (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(a)novell.com> (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(a)novell.com> (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(a)novell.com> (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. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=303517

1 0

[openFate 303517] Configure a cronjob for refreshing repositories
by fate_noreply＠suse.de 10 Sep '08

10 Sep '08

Feature changed by: Duncan Mac-Vicar <dmacvicar(a)novell.com> Feature #303517, revision 15 Title: Configure a cronjob for refreshing repositories openSUSE-11.1: Candidate Priority Requester: Desirable Projectmanager: Mandatory Requested by: Ladislav Slezak <lslezak(a)novell.com> Partner organization: openSUSE.org 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(a)novell.com> (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(a)novell.com> (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(a)novell.com> (2008-07-07 12:34:19) (reply to #2) We have a concept in the automatic online update configuration. #4: Jiri Srain <jsrain(a)novell.com> (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(a)novell.com> (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(a)novell.com> (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(a)novell.com> (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(a)novell.com> (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(a)novell.com> (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(a)novell.com> (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(a)novell.com> (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. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=303517

1 0

[openFate 303517] Configure a cronjob for refreshing repositories
by fate_noreply＠suse.de 10 Sep '08

10 Sep '08

Feature changed by: J. Daniel Schmidt <jdsn(a)novell.com> Feature #303517, revision 14 Title: Configure a cronjob for refreshing repositories openSUSE-11.1: Candidate Priority Requester: Desirable Projectmanager: Mandatory Requested by: Ladislav Slezak <lslezak(a)novell.com> Partner organization: openSUSE.org 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(a)novell.com> (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(a)novell.com> (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(a)novell.com> (2008-07-07 12:34:19) (reply to #2) We have a concept in the automatic online update configuration. #4: Jiri Srain <jsrain(a)novell.com> (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(a)novell.com> (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(a)novell.com> (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(a)novell.com> (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(a)novell.com> (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(a)novell.com> (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(a)novell.com> (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. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=303517

1 0