How should chains be done in non-rawhide?
Jesse Keating
jkeating at redhat.com
Wed Apr 14 21:55:11 UTC 2010
On Wed, 2010-04-14 at 17:31 -0400, Jeff Johnston wrote:
> I am trying to update the eclipse-egit package to 0.7.1 and it requires
> eclipse-jgit >= 0.7.1 which I just built. I would like both packages to
> be in updates-testing at the same time since use of the eclipse-egit
> package is the real test of the eclipse-jgit package.
>
> For rawhide, I just used the chain-build target, but this doesn't work
> for F-13. I don't really want to promote eclipse-jgit to stable just so
> I can build eclipse-egit.
>
> What is the recommended procedure? Ideally, I would like to use a
> chain-build-like mechanism.
>
> -- Jeff J.
Unfortunately we can't use chain-build on repos that don't self-update.
You'll need to file a releng ticket for a buildroot override to get your
eclipse-jgit into the buildroot, then you can use a koji wait-repo ...
&& make build type command to automatically wait for the build to show
up in the buildroot and kick off your second build. Then you can create
a single bodhi update that includes both builds to keep them grouped
together.
--
Jesse Keating
Fedora -- Freedom² is a feature!
identi.ca: http://identi.ca/jkeating
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
Url : http://lists.fedoraproject.org/pipermail/devel/attachments/20100414/37c9f72a/attachment.bin
More information about the devel
mailing list