Chain builds for non-rawhide

[Thomas Spura]

On Thu, 07 Oct 2010 15:37:19 -0700
Jesse Keating wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On 10/5/10 2:30 PM, Mamoru Tasaka wrote:
> > Well, how about creating "dist-f14-for-chainbuild" build target and
> > allow people to tag or untag build as/from that tag freely?
> > 
> > For example currently
> > http://koji.fedoraproject.org/koji/buildtargetinfo?targetID=67
> > says that build target "dist-f14-kde" uses "dist-f14-kde" tagged
> > packages for buildroot, and built packages are tagged as
> > "dist-f14-kde" and the destination tag "dist-f14-kde" is not locked.
> > (and on the other hand build target "dist-f14" still exists, using
> >   "dist-f14-build" tagged packages when building but the destination
> >   "dist-f14" is locked)
> > So as far as I am correct, we can freely do chain-build using
> > dist-f14-kde build target for F-14 packages. And actually this
> > status was used when fixing ImageMagick related dependency breakage
> > on F-14 (see latest ImageMagick group update request on F-14 on
> > bodhi, and tag history on koji for ImageMagick-6.6.4.1-13.fc14,
> >   autotrace-0.31.1-24.fc14.1 for example)
> >   
> > So creating build target for chain-build purpose only seems
> > reasonable to me.
> > 
> 
> Without creating different tags for each and every build attempt,
> using a tag like dist-f14-kde would suffer from the same problem as
> using dist-f14-updates-candidate.  That is something could get built
> and tagged into there, that is later either never shipped in an
> update, or pulled out of updates-testing due to problems, and we'd be
> left with any number of other packages that were built using the now
> dead package.
> 
> In short, it doesn't actually solve any problems to use a
> dist-f14-chainbuild like tag.

How about let bodhi do the tagging?
When there is an update, you could click on "tag this package", and
bodhi will do the rest. If the update is deleted or obsoleted by
another one, the tag will be deleted again.

This doesn't solve the problem, that maintainers could tag a package
and never push the update out, but that could happen with manual
tagging too, isn't it?

	Thomas