On Sun, Mar 27, 2011 at 10:27 PM, Martin Bähr <
mba...@email.archlab.tuwien.ac.at> wrote:

> On Sun, Mar 27, 2011 at 11:25:24AM +0200, Rune Morling wrote:
> > <ermo> can we create the label now
> > <ermo> or do we need mkj?
> > <doniphon> ermo: iddeally mkj.
> > <doniphon> (i never did group redirect scripts)
>
> doesn't this only apply to the fl:2 -> fl:2.5 redirect?
> or does it really apply to the creation of the label itself?
>

A common misconception about conary repositories here... there's no such
thing as just "creating" a label.  A label is created when (and only when)
you commit something to it, via a promote, a "cvc commit", etc.  Depending
on how repository permissions are set up, you might have to give roles
access to the label after something's been committed, but there's no "create
a label" command.


> my thought is:
>
> create fl:2.5
> push fl:2-qa -> fl:2.5
> release isos based on fl:2.5
> wait for mkj to help with group redirect script
> test group redirect for fl:2 -> fl:2.5
> add group redirect to fl:2
>

I agree with this process.  I'm not sure that group redirects are going to
give you all the functionality that you might want, but it's a reasonable
way to at least give people a simple migrate option.  I can help to create
the redirects as soon as a target on fl:2.5 exists.

--Andy


> in other words, we do not need to wait for mkj to make a release.
> we can release 2.5 now, without affecting fl:2 users, and worry about
> those later...
>
> greetings, martin.
> --
> cooperative communication with sTeam      -     caudium, pike, roxen and
> unix
> services:   debugging, programming, training, linux sysadmin, web
> development
> --
> pike programmer      working in china
> community.gotpike.org
> foresight developer  (open-steam|caudium).org
> foresightlinux.org
> unix sysadmin        iaeste.at
> realss.com
> Martin Bähr          http://www.iaeste.at/~mbaehr/
> is.schon.org
> _______________________________________________
> Foresight-devel mailing list
> Foresight-devel@lists.rpath.org
> http://lists.rpath.org/mailman/listinfo/foresight-devel
>
_______________________________________________
Foresight-devel mailing list
Foresight-devel@lists.rpath.org
http://lists.rpath.org/mailman/listinfo/foresight-devel

Reply via email to