[arch-releng] [PATCH 3/5] document how to sync releng isonames

Dieter Plaetinck dieter at plaetinck.be
Mon May 2 11:37:33 EDT 2011


On Mon, 2 May 2011 10:31:01 -0500
Dan McGee <dpmcgee at gmail.com> wrote:

> On Sun, May 1, 2011 at 5:38 AM, Dieter Plaetinck
> <dieter at plaetinck.be> wrote:
> >
> > Signed-off-by: Dieter Plaetinck <dieter at plaetinck.be>
> > ---
> >  README |   11 ++++++++---
> >  1 files changed, 8 insertions(+), 3 deletions(-)
> >
> > diff --git a/README b/README
> > index 6509729..ed1eafa 100644
> > --- a/README
> > +++ b/README
> > @@ -58,15 +58,20 @@ packages, you will probably want the following:
> >
> >         (archweb-env) $ ./manage.py loaddata */fixtures/*.json
> >
> > -7. Use the following commands to start a service instance
> > +7. Optionally populate the database with real releng iso names:
> >
> > -        (archweb-env) $ ./manage.py runserver
> > +        (archweb-env) $ ./manage.py syncisos
> >
> > -8. To optionally populate the database with real data:
> > +8. Optionally populate the database with real data:
> >
> >         (archweb-env) $ wget
> > ftp://ftp.archlinux.org/core/os/i686/core.db.tar.gz (archweb-env)
> > $ ./manage.py reporead i686 core.db.tar.gz
> >
> > +9. Use the following commands to start a service instance
> > +
> > +        (archweb-env) $ ./manage.py runserver
> > +
> > +
> >  Alter architecture and repo to get x86\_64 and packages from other
> > repos if needed.
> 
> I'm not sure why you had to renumber everything when you could have
> just added one line below the reporead line. I'll do that instead.
> 
> -Dan

it made more sense to me to do all the "add data" stuff 1)
together, 2) before starting the server.

Dieter


More information about the arch-releng mailing list