Mailinglist Archive: opensuse-factory (626 mails)

< Previous Next >
Re: [opensuse-factory] Experience of switching to Factory from Ubuntu
  • From: Eberhard Moenkeberg <emoenke@xxxxxxx>
  • Date: Sun, 2 Mar 2008 23:38:44 +0100 (CET)
  • Message-id: <Pine.LNX.4.64.0803022330060.21504@xxxxxxxxxxxxxx>

On Fri, 29 Feb 2008, Dr. Peter Poeml wrote:
On Thu, Feb 28, 2008 at 01:31:44PM +0000, Sid Boyce wrote:
Dr. Peter Poeml wrote:
On Thu, Feb 28, 2008 at 12:00:32PM +0000, Sid Boyce wrote:
Stephan Kulow wrote:

the factory tree is synced out. It would take _even_ longer to get to a
factory snapshot being online.

Out of sync mirrors do cause problems, zypper dup will throw up lots of
conflicts one day and be largely fine next day when the full synch is
completed. The list could be informed of when synch is about to happen

Which mirror(s) do you regularly use? Did you also try to access directly?

The latter should help you to avoid the need to wait for an up to date
mirror. Does that work for you? Please let me know if not.

That's the one I normally used. Recently I had to switch to I would guess that was in update
and was up to date with the last synch.

So you have actually more problems with the origin server than with the
mirror? Then I assume it's caused by inconsistent Factory snapshots
being put there, or by the tree being in flux (while you were updating).
(It depends on the kind of error you got.)

This actually reminds me of this bug:
(old, but somehow managed to be still in state "NEW")

It might be due to the way *how* Factory is synced to

I don't know details about that, yet -- I only know that there is no
synchronisation that I know of. It is on my todo list to find out.

You will never be able to force the internet to be synchronous.

How about the following two funky possibilities to sync the client with
the server. The client could check (when tracking Factory) if there's
some kind of lock file which indicates that the tree is being worked on,
and refuse to use it. Or the server could simply block access to the
tree during that time, and open up after the sync completed.

Blocking access during change times could help a little bit.
Better would be to speed up everything as far as possible. ;-))

and when the mirrors are likely to be fully synched - confusing things
happen when the synch is in progress. Emperically I observe that
Saturday is a bad day to update, Tuesdays usually OK.

Should not. The average time for updating factory is 7 minutes at, but sometimes it needs more than 1 hour (4 hours
repetition interval).
Best would be a push service here, like we already have for repositories.
And using it by the mirrors, of course. ;-))

Viele Grüße
Eberhard Mönkeberg (emoenke@xxxxxxx, em@xxxxxxx)
< Previous Next >
List Navigation