* Frank Griffin <ftg@(protected)]:
> Adam Williamson wrote:
> >They are supposed to hit mirrors at the same time; they're released as
> >part of the same advisory. As far as I know, this has worked for all
> >2008 Spring kernel updates so far. I haven't had any other report of the
> >driver not being updated when the kernel was.
> >
> There is never a guarantee of this. An ML thread years ago established
> that there was absolutely no correlation between when Mandriva dumps
> stuff onto rsync.mandriva (or whatever it is these days) and when the
> mirrors choose to rsync and pick it up.
>
> What they pick up in any particular execution of rsync depends on the
> state of the repository directory when rsync determines which files to
> transfer. If this overlaps the updating of the MDV rsync host from
> internal sources, you'll get a partial and inconsistent update.

Indeed this is impossible with Rsync, it requires atomicity..
--delay-updates would help, but we can't demand/guarantee mirrors use it.
But I'm gonna check if we use it internally, at least.


> So, whether Mandriva tries to "schedule" different packages to be in a
> certain "advisory" unit or not, there is no guarantee that all such
> packages will be transmitted as a group.

But there's another problem here.. synthesis shouldn't miss an update's
files (i.e. have a partial update).. it is likely this happened due to the
kernel update having many files and big size. I'll see how we can improve or
fix that.