[opensuse-arm] "dead lock" between autoyast2 and yast2-schema
All, Currently there is a "dead lock" between package autoyast2 and yast2-schema (for the openSUSE:Factory:ARM build). The thing is that autoyast2 Requires yast2-schema. Because of this yast2-schema is blocked. I got around this by removing the autoyast2 requirement. Until yast2-schema has been build. When this package was build I added the Requirement again. I wonder if there is a better "mechanism" in OBS that solves such "lock issue" automatically? Otherwise someone has to handle this by hand. Regards, Joop. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Sunday 25 December 2011, Joop Boonen wrote:
issue" automatically? Otherwise someone has to handle this by hand.
Hi Joop, this is called "buildcycle" and should be avoided. in cases where it isn't possible one needs to manually break the cycle to make bootstrapping work. we have many such buildcycles that are not a problem with incremental builds, but with bootstrapping (like for example java-1_6_0-openjdk requiring ant, which requires java-1_6_0-openjdk for building). This is the part where it gets ugly :-) if this is not a real dependency (e.g. the package works just fine without the dependency) then it might be a good idea to permanently remove it. Greetings, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
participants (2)
-
Dirk Müller -
Joop Boonen