[Mageia-sysadm] things to do for release
boklm at mars-attacks.org
Fri May 27 17:28:32 CEST 2011
On Fri, 27 May 2011, nicolas vigier wrote:
> On Wed, 25 May 2011, Michael Scherer wrote:
> > Le mardi 24 mai 2011 à 21:35 +0200, nicolas vigier a écrit :
> > > On Tue, 24 May 2011, nicolas vigier wrote:
> > >
> > > > - upload trees and isos on primary mirror on private directory
> > >
> > > For this, does anyone know what this means exactly ?
> > I guess "copy the tree on a directory not exported, check this is using
> > hardlink for package, make sure that others files ( such as hdlist ) are
> > not hardlink in order to prepare for the release by doing mv".
> > I spoke about this with Nanar, and the idea is to minimize the data to
> > transfert by using hardlink on rpms, as they are all already on mirror
> > ( since they are in cauldron ). This save the time needed to letting
> > people take the release, since rsync will not transfer them again.
> > However, this can be used only for rpm files, and not for hdlist, for
> > others files, etc, since they will be updated on cauldron and we do not
> > want to have them changed on stable as a side effect.
> So we can do something like that :
> - copy cauldron directory to directory .tmp-mageia-1
> - rsync cauldron to .tmp-mageia-1 until release day
> - on release day, we make hardlinks between files from '.tmp-mageia-1'
> and '1' directories
> - files in directory '1' become immediatly available on mirrors (as they
> are hardlinks to files in .tmp-mageia-1 already uploaded)
> - after a few days we remove .tmp-mageia-1
> Does it look correct ?
Ok, after discussing with Nanar, this is not what we will do. We will do
what was described by misc, hardlink rpms between cauldron and stable.
And Nanar will prepare a script to do it.
More information about the Mageia-sysadm