what is the approximate time that a build is added to rawhide repositories? I have chained build dependencies (trilead-ssh2, svnkit, eclipse-subclipse), and after trying "make chain-build", it tells me a "Build already exists" for trilead-ssh2, do I need to bump the relase tag each time?
Robert Marcano wrote:
what is the approximate time that a build is added to rawhide repositories? I have chained build dependencies (trilead-ssh2, svnkit, eclipse-subclipse), and after trying "make chain-build", it tells me a "Build already exists" for trilead-ssh2, do I need to bump the relase tag each time?
I think you're misunderstanding how chain-build works.
Kevin Kofler
On Wed, Feb 25, 2009 at 12:45 PM, Kevin Kofler kevin.kofler@chello.atwrote:
Robert Marcano wrote:
what is the approximate time that a build is added to rawhide repositories? I have chained build dependencies (trilead-ssh2, svnkit, eclipse-subclipse), and after trying "make chain-build", it tells me a "Build already exists" for trilead-ssh2, do I need to bump the relase tag each time?
I think you're misunderstanding how chain-build works.
Can you help me to understand it?
from https://fedoraproject.org/wiki/Using_the_Koji_build_system
"Sometimes you want to make sure than one build succeeded before launching the next one, for example when you want to rebuild a package against a just rebuilt dependency. In that case you can use a chain build with"
This is exactly what I want to do, I want to build svnkit just after trilead-ssh2 was successfully built, "make chain-build" rebuilds trilead-ssh2 before svnkit but it tells me a build already exists
Kevin Kofler-- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
On Wed, Feb 25, 2009 at 1:03 PM, Kevin Kofler kevin.kofler@chello.atwrote:
Robert Marcano wrote:
Can you help me to understand it?
A chain-build of A B ... Z builds A, waits for A to be in the repo, builds B, waits for B to be in the repo, ..., builds Z. You can't issue a chain-build including stuff you already built.
then it is not of much help for this case "rebuild a package against a just rebuilt dependency" as the wiki says. It only helps if you are 100% sure all builds will run without error
Kevin Kofler-- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
2009/2/24 Robert Marcano robert@marcanoonline.com:
On Wed, Feb 25, 2009 at 1:03 PM, Kevin Kofler kevin.kofler@chello.at wrote:
Robert Marcano wrote:
Can you help me to understand it?
A chain-build of A B ... Z builds A, waits for A to be in the repo, builds B, waits for B to be in the repo, ..., builds Z. You can't issue a chain-build including stuff you already built.
then it is not of much help for this case "rebuild a package against a just rebuilt dependency" as the wiki says. It only helps if you are 100% sure all builds will run without error
To make an analogy, what you want is the equivalent of 'mkdir -p': my package require the latest tagged versions of A, B, C, ....; for each, please build them if they have not already been built, otherwise go ahead.
That would be useful. Saves the hassle of checking the status of each component manually, esp. if you do not control some parts of the chain.
Regards,
-
Kevin Kofler -
Michel Salim -
Robert Marcano