On Tue, Jul 10, 2012 at 08:16:59PM +0200, Kacper Kornet wrote: > On Tue, Jul 10, 2012 at 07:54:11PM +0200, Marcin Krol wrote: > > >What do you mean by shouldn't fell. Script builder will fail if you run > > >like: builder -bs -Tp auto/th/ -tt ..... > > >and the auto tag generated from required revision already exist. It was > > >the case in CVS, it is the case in git.
> > It will fail on git, it wasn't failing on CVS due to difference in > > return codes I've mentioned before. At least thats how it behave > > when I was setting up TLD git. On CVS ready builds using auto tags > > worked fine (without using -cf) and thats how they should work on > > git as well. Developers must be able to do: > > ./make-request.sh -d th -r some.spec:auto/th/some-1.2 > > and get their packages built. > Propably I don't understand something. So sorry for still bothering you > but I just tried: > ./builder -bs -Tp auto/th/ -tt -r auto/th/git-core-slug-0.13.2-1 \ > git-core-slug.spec > in using script builder for CVS and it fails with: > Searching for tag auto-th-git-core-1_7_11_1-1... > Tag auto-th-git-core-1_7_11_1-1 already exists (spec release: 1.283). > What am I missing. How did you exactly send the request to rebuild the > old tag previously in CVS? Ok. Now I understand. I have missed the second condition in: if ("test-build" in r.flags) or b.branch and b.branch.startswith(config.tag_prefixes[0]): I'm sorry for being slow. -- Kacper _______________________________________________ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en