[opensuse-buildservice] aggregate issue
Hi, I switched a package to aggregate from another project. For some reason almost all targets show "blocked" for that package currently (it works for Factory though). The package in the original project are correctly built though. Is there a problem in OBS? Anything wrong in my project/package config? It's the package mozilla-nspr in mozilla:beta which should be aggregated from mozilla. Thanks, Wolfgang --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Wolfgang Rosenauer wrote:
I switched a package to aggregate from another project. For some reason almost all targets show "blocked" for that package currently (it works for Factory though). The package in the original project are correctly built though.
Is there a problem in OBS? Anything wrong in my project/package config?
It's the package mozilla-nspr in mozilla:beta which should be aggregated from mozilla.
OK, I consider it an issue in OBS actually. Another 24 hours later more targets have been aggregated but there are still quite some missing what means that my config is correct but OBS takes _days_ to actually do the work while it's idleing away (not really having packages to build in the queue currently). Wolfgang --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Sunday 04 May 2008 08:29:28 wrote Wolfgang Rosenauer:
Wolfgang Rosenauer wrote:
I switched a package to aggregate from another project. For some reason almost all targets show "blocked" for that package currently (it works for Factory though). The package in the original project are correctly built though.
Is there a problem in OBS? Anything wrong in my project/package config?
It's the package mozilla-nspr in mozilla:beta which should be aggregated from mozilla.
OK, I consider it an issue in OBS actually. Another 24 hours later more targets have been aggregated but there are still quite some missing what means that my config is correct but OBS takes _days_ to actually do the work while it's idleing away (not really having packages to build in the queue currently).
well, yes, aggregates gets currently only executed when a complete project has finished, not only the required packages. On the other hand, using aggregates is usually evil (just brings incompatibilities and increases server space without need). You may want to consider to build directly against the other project/repo. This would solve also the long waiting time. bye adrian -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) email: adrian@suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Adrian Schröter wrote:
On Sunday 04 May 2008 08:29:28 wrote Wolfgang Rosenauer:
Wolfgang Rosenauer wrote:
I switched a package to aggregate from another project. For some reason almost all targets show "blocked" for that package currently (it works for Factory though). The package in the original project are correctly built though.
Is there a problem in OBS? Anything wrong in my project/package config?
It's the package mozilla-nspr in mozilla:beta which should be aggregated from mozilla. OK, I consider it an issue in OBS actually. Another 24 hours later more targets have been aggregated but there are still quite some missing what means that my config is correct but OBS takes _days_ to actually do the work while it's idleing away (not really having packages to build in the queue currently).
well, yes, aggregates gets currently only executed when a complete project has finished, not only the required packages.
On the other hand, using aggregates is usually evil (just brings incompatibilities and increases server space without need). You may want to consider to build directly against the other project/repo. This would solve also the long waiting time.
In that case I'm pretty sure it doesn't bring incompatibilities but the project is actually built against the other repo so in theory everything should just work if I'd remove the package. But I have a strong belief that zypper would break that way on some systems :-( If people are using the repo and didn't install with a YMP they usually don't know about the dependency and zypper doesn't help the user to find the correct dependent repo, does it? Wolfgang --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Monday 05 May 2008 09:01:28 wrote Wolfgang Rosenauer:
Adrian Schröter wrote:
On Sunday 04 May 2008 08:29:28 wrote Wolfgang Rosenauer:
Wolfgang Rosenauer wrote:
I switched a package to aggregate from another project. For some reason almost all targets show "blocked" for that package currently (it works for Factory though). The package in the original project are correctly built though.
Is there a problem in OBS? Anything wrong in my project/package config?
It's the package mozilla-nspr in mozilla:beta which should be aggregated from mozilla.
OK, I consider it an issue in OBS actually. Another 24 hours later more targets have been aggregated but there are still quite some missing what means that my config is correct but OBS takes _days_ to actually do the work while it's idleing away (not really having packages to build in the queue currently).
well, yes, aggregates gets currently only executed when a complete project has finished, not only the required packages.
On the other hand, using aggregates is usually evil (just brings incompatibilities and increases server space without need). You may want to consider to build directly against the other project/repo. This would solve also the long waiting time.
In that case I'm pretty sure it doesn't bring incompatibilities but the project is actually built against the other repo so in theory everything should just work if I'd remove the package. But I have a strong belief that zypper would break that way on some systems :-( If people are using the repo and didn't install with a YMP they usually don't know about the dependency and zypper doesn't help the user to find the correct dependent repo, does it?
yes, that is true for now. But you can enforce this by defining requires in your package, really requiring the new version from the other project. bye adrian -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) email: adrian@suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Adrian Schröter wrote:
On the other hand, using aggregates is usually evil (just brings incompatibilities and increases server space without need). You may want to consider to build directly against the other project/repo. This would solve also the long waiting time. In that case I'm pretty sure it doesn't bring incompatibilities but the project is actually built against the other repo so in theory everything should just work if I'd remove the package. But I have a strong belief that zypper would break that way on some systems :-( If people are using the repo and didn't install with a YMP they usually don't know about the dependency and zypper doesn't help the user to find the correct dependent repo, does it?
yes, that is true for now. But you can enforce this by defining requires in your package, really requiring the new version from the other project.
That is done anyway but doesn't help zypper to find it if the repo is not added in the first place. Anyway I decided to go for it (and probably break some setups which were broken before by not having the top level project as well). And what I found is that I have the very same issue as with aggregation :-( The depedent packages are still blocked while the packages are built already. Is it the same issue that it waits for the whole project to finish before blocked items in other projects are scheduled? Wolfgang --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Monday 05 May 2008 16:20:47 wrote Wolfgang Rosenauer:
Adrian Schröter wrote:
On the other hand, using aggregates is usually evil (just brings incompatibilities and increases server space without need). You may want to consider to build directly against the other project/repo. This would solve also the long waiting time.
In that case I'm pretty sure it doesn't bring incompatibilities but the project is actually built against the other repo so in theory everything should just work if I'd remove the package. But I have a strong belief that zypper would break that way on some systems :-( If people are using the repo and didn't install with a YMP they usually don't know about the dependency and zypper doesn't help the user to find the correct dependent repo, does it?
yes, that is true for now. But you can enforce this by defining requires in your package, really requiring the new version from the other project.
That is done anyway but doesn't help zypper to find it if the repo is not added in the first place.
Anyway I decided to go for it (and probably break some setups which were broken before by not having the top level project as well). And what I found is that I have the very same issue as with aggregation :-( The depedent packages are still blocked while the packages are built already. Is it the same issue that it waits for the whole project to finish before blocked items in other projects are scheduled?
hm, no. I suspect it is caused, because the scheduler has too many events atm. There are currently 28100 low priority events, one of the them is your project/repo . It may take a while until it reach it. (a source change would change the state immediatly). Michael knows this and thinks about a solution for that. bye adrian -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) email: adrian@suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (2)
-
Adrian Schröter
-
Wolfgang Rosenauer