On Tue, Aug 10, 2010 at 04:28:01PM +0200, Milan Zazrivec wrote:
> With respect to upcoming release of Spacewalk 1.1, following changes
> (affecting Spacewalk 1.2) have been made:
> 
> * Bumped up versions of packages in current spacewalk.git master [1]
> 
> * New koji tags:
> dist-5E-sw-1.2-candidate
> dist-f12-sw-1.2-candidate
> dist-f13-sw-1.2-candidate
> 
> * Nightly repos [2] are going to be mashed out of the tags above
> 
> * rel-eng/build-missing-builds-in-koji.sh and rel-eng/tito.props
> have been changed appropriately
> 
> * 1.2 version has been added to the Spacewalk product in bugzilla [3]

We have a problem. If you run

        ./rel-eng/koji-missing-builds.py dist-5E-sw-1.2-candidate

you will see a *lot* of missing builds. If you run it for f12, there's
not so many of them, but there are some, like
spacewalk-web-1.1.8-1.fc12.

So build-missing-builds-in-koji.sh will schedule a lot of tasks which
will fail eventually, because the builds are in fact there.

The problem is that we only have 27 builds explicitly tagged to
dist-5E-sw-1.1. And dist-5E-sw-1.2-candidate inherits from
dist-5E-sw-1.2 and that inherits from dist-5E-sw-1.1.

The spacewalk-web-1.1.8-1.fc12 is not tagged either.

Could you please finish the tagging of 1.1 packages?

-- 
Jan Pazdziora
Principal Software Engineer, Satellite Engineering, Red Hat

_______________________________________________
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel

Reply via email to