Hello,
just noticed on a 12.3 server:
# zypper lp Loading repository data... Warning: Repository 'openSUSE-12.3-Update-Non-Oss' appears to outdated. Consider using a different mirror or server. Reading installed packages... No updates found.
Looks like there are not enough non-oss updates ;-)
Nevertheless, someone[tm] should regularly update the "best before" ;-) timestamp of the repo.
# zypper lr -u -E # | Alias | Name | Enabled | Refresh | URI --+---------------------+------------------------------+---------+---------+---------------------------------------------------------------------- 1 | home:cboltz | home:cboltz | Yes | Yes | http://download.opensuse.org/repositories/home:/cboltz/openSUSE_12.3/ 4 | repo-non-oss | openSUSE-12.3-Non-Oss | Yes | Yes | http://download.opensuse.org/distribution/12.3/repo/non-oss/ 5 | repo-oss | openSUSE-12.3-Oss | Yes | Yes | http://download.opensuse.org/distribution/12.3/repo/oss/ 7 | repo-update | openSUSE-12.3-Update | Yes | Yes | http://download.opensuse.org/update/12.3/ 8 | repo-update-non-oss | openSUSE-12.3-Update-Non-Oss | Yes | Yes | http://download.opensuse.org/update/12.3-non-oss/
Regards,
Christian Boltz
On Mon, Aug 12, 2013 at 02:16:34AM +0200, Christian Boltz wrote:
Hello,
just noticed on a 12.3 server:
# zypper lp Loading repository data... Warning: Repository 'openSUSE-12.3-Update-Non-Oss' appears to outdated. Consider using a different mirror or server. Reading installed packages... No updates found.
Looks like there are not enough non-oss updates ;-)
Nevertheless, someone[tm] should regularly update the "best before" ;-) timestamp of the repo.
It currently requires releasing updates.
Lucky we had Opera 12.16 in the queue, I just released that one and it should reset the timestamp.
Flash Player is also due with tomorrows MS Patchday I suspect.
Ciao, Marcus
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
El 2013-08-12 a las 09:22 +0200, Marcus Meissner escribió:
Nevertheless, someone[tm] should regularly update the "best before" ;-) timestamp of the repo.
It currently requires releasing updates.
How about recoding zypper/yast to consider that? ;-)
- -- Cheers
Carlos E. R. (from 11.4, with Evergreen, x86_64 "Celadon" (Minas Tirith))
On Wed, Aug 14, 2013 at 02:10:30AM +0200, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
El 2013-08-12 a las 09:22 +0200, Marcus Meissner escribió:
Nevertheless, someone[tm] should regularly update the "best before" ;-) timestamp of the repo.
It currently requires releasing updates.
How about recoding zypper/yast to consider that? ;-)
No. It is basically a setting in the repo that could be adjusted to be longer, if it would not be configured in some perl script I have no access to in the buildservice.
Ciao, Marcus
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
El 2013-08-14 a las 07:49 +0200, Marcus Meissner escribió:
On Wed, Aug 14, 2013 at 02:10:30AM +0200, Carlos E. R. wrote:
It currently requires releasing updates.
How about recoding zypper/yast to consider that? ;-)
No. It is basically a setting in the repo that could be adjusted to be longer, if it would not be configured in some perl script I have no access to in the buildservice.
Oh, Ok.
I ask because it would be nice having something to adjust or disable the setting for update repos that do not change - I'm specifically thinking of evergreen: some people seeing the warning try to remove the old update repo, and that is wrong.
It would be nice to be able to disable the warning, be it locally or on the server.
- -- Cheers
Carlos E. R. (from 11.4, with Evergreen, x86_64 "Celadon" (Minas Tirith))
On Wed, Aug 14, 2013 at 01:38:25PM +0200, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
El 2013-08-14 a las 07:49 +0200, Marcus Meissner escribió:
On Wed, Aug 14, 2013 at 02:10:30AM +0200, Carlos E. R. wrote:
It currently requires releasing updates.
How about recoding zypper/yast to consider that? ;-)
No. It is basically a setting in the repo that could be adjusted to be longer, if it would not be configured in some perl script I have no access to in the buildservice.
Oh, Ok.
I ask because it would be nice having something to adjust or disable the setting for update repos that do not change - I'm specifically thinking of evergreen: some people seeing the warning try to remove the old update repo, and that is wrong.
It would be nice to be able to disable the warning, be it locally or on the server.
It is a necessary precaution for when you really use an outdated mirror or a mirror that is blocking updates for you.
Usability adjustments might however be necessary if users react the wrong way.
Ciao, Marcus
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
El 2013-08-14 a las 13:42 +0200, Marcus Meissner escribió:
It would be nice to be able to disable the warning, be it locally or on the server.
It is a necessary precaution for when you really use an outdated mirror or a mirror that is blocking updates for you.
Yes, I know. But when the system was designed the update repo always changed periodically, it would never be frozen. The situation is different now: there is the non-oss repo, that seldom changes, and there is evergreen, that has a frozen update repo plus an additional new update repo.
Thus now we need some kind of override. For evergreen, a manual override, perhaps a flag file that is downloaded as an update from the evergreen repo. For non-oss, just a longer override, perhaps, or dummy updates.
That's up to you devs and packagers to design ;-)
Usability adjustments might however be necessary if users react the wrong way.
True.
- -- Cheers Carlos E. R.
(from 11.4, with Evergreen, x86_64 "Celadon" (Minas Tirith))
-
Carlos E. R. -
Christian Boltz -
Marcus Meissner