Mailinglist Archive: opensuse-features (58 mails)

< Previous Next >
[openFate 303517] Configure a cronjob for refreshing repositories
  • From: fate_noreply@xxxxxxx
  • Date: Wed, 10 Sep 2008 19:49:45 +0200 (CEST)
  • Message-id: <feature-303517-14@xxxxxxxxxxxxxx>
Feature changed by: J. Daniel Schmidt <jdsn@xxxxxxxxxx>
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@xxxxxxxxxx>
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@xxxxxxxxxx> (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@xxxxxxxxxx> (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@xxxxxxxxxx> (2008-07-07 12:34:19)
(reply to #2)
We have a concept in the automatic online update configuration.

#4: Jiri Srain <jsrain@xxxxxxxxxx> (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@xxxxxxxxxx> (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@xxxxxxxxxx> (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@xxxxxxxxxx> (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@xxxxxxxxxx> (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@xxxxxxxxxx> (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@xxxxxxxxxx> (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

< Previous Next >
This Thread