[opensuse-buildservice] issue with dangling builds
Hi, in home:frispete:python, I've linked in python{-base} for 11.1, since I needed to fix a bug, that Python v2.6.0 suffers from (resulting in misbehavior and strange crashes of current python-sip wrapped packages). For some reason, I forgot to disable build and use-for-build flags of python-base for the other targets (11.2 and 11.3). Now, that I noticed the issues, I wiped the offending packages via webui, and triggered rebuilds. But still the packages of 11.2 and 11.3 try to build against python-base-2.6.0. It looks, like OBS still uses the misguided builds, that I wiped already. What can I do? TIA, Pete -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Dienstag, 8. Februar 2011 schrieb Hans-Peter Jansen:
Hi,
in home:frispete:python, I've linked in python{-base} for 11.1, since I needed to fix a bug, that Python v2.6.0 suffers from (resulting in misbehavior and strange crashes of current python-sip wrapped packages).
For some reason, I forgot to disable build and use-for-build flags of python-base for the other targets (11.2 and 11.3). Now, that I noticed the issues, I wiped the offending packages via webui, and triggered rebuilds.
But still the packages of 11.2 and 11.3 try to build against python-base-2.6.0.
It looks, like OBS still uses the misguided builds, that I wiped already.
You can't wipe binaries that you disabled for useforbuild. Disable it for build, enable for useforbuild and then wipe. useforbuild is a very confusing flag and only people should use it that read a good part of the backend code ;( Greetings, Stephan -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Tuesday 08 February 2011, 10:09:03 Stephan Kulow wrote:
Am Dienstag, 8. Februar 2011 schrieb Hans-Peter Jansen:
Hi,
in home:frispete:python, I've linked in python{-base} for 11.1, since I needed to fix a bug, that Python v2.6.0 suffers from (resulting in misbehavior and strange crashes of current python-sip wrapped packages).
For some reason, I forgot to disable build and use-for-build flags of python-base for the other targets (11.2 and 11.3). Now, that I noticed the issues, I wiped the offending packages via webui, and triggered rebuilds.
But still the packages of 11.2 and 11.3 try to build against python-base-2.6.0.
It looks, like OBS still uses the misguided builds, that I wiped already.
You can't wipe binaries that you disabled for useforbuild. Disable it for build, enable for useforbuild and then wipe.
Well, I suspected something along these lines, but was impressed by the fact, that, even those flags were in action, the webui has shown the built packages, and offered me to remove them. After that, I checked the download repositories, and indeed, they vanished.
useforbuild is a very confusing flag and only people should use it that read a good part of the backend code ;(
Glad, you did, Stephan ;-) I've set useforbuild to "take defaults" in python{-base}, now only build is set to off for "All" and on just for 11.1 on these two packages. After that, I did: osc wipebinaries --build-disabled home:frispete:python python osc wipebinaries --build-disabled home:frispete:python python-base * triggered rebuild osc rebuild home:frispete:python python-decorator osc rebuild home:frispete:python python-ordereddict * still failed osc wipebinaries --unresolvable home:frispete:python python osc wipebinaries --unresolvable home:frispete:python python-base * triggered rebuild: still failed osc wipebinaries home:frispete:python -r openSUSE_11.2 osc wipebinaries home:frispete:python -r openSUSE_11.3 * triggered rebuild: still failed Unfortunately, I haven't found the magic spell to unlock this mess again. Interestingly, the build of python-ordereddict for 11.2/i586 succeeds, but it still is built against python-base-2.6.0, although 2.6.2 is expected. FYI: this is related to the python and python-base split, and dependencies to them, but this induces another dangerous aspect here. The x86_64 builds fail, because the noarch handling of python-base changed between 11.1 and 11.2.. Pete -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Tuesday 08 February 2011, 11:25:01 Hans-Peter Jansen wrote:
On Tuesday 08 February 2011, 10:09:03 Stephan Kulow wrote:
You can't wipe binaries that you disabled for useforbuild. Disable it for build, enable for useforbuild and then wipe.
useforbuild is a very confusing flag and only people should use it that read a good part of the backend code ;(
Unfortunately, I haven't found the magic spell to unlock this mess again.
Even a brute force approach: osc wipebinaries --all home:frispete:python osc rebuild home:frispete:python still suffers from the same symptoms. For some reason, the OBS uses packages for the build of other package in the same project, that should be long gone (e.g. even successfully built packages for 11.2 and 11.3 are built with the wrong python version (python-base-2.6.0) instead of 2.6.2 or 2.6.5. How can I resolve this? Pete -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Tuesday 08 February 2011, 17:20:05 Hans-Peter Jansen wrote:
On Tuesday 08 February 2011, 11:25:01 Hans-Peter Jansen wrote:
On Tuesday 08 February 2011, 10:09:03 Stephan Kulow wrote:
You can't wipe binaries that you disabled for useforbuild. Disable it for build, enable for useforbuild and then wipe.
useforbuild is a very confusing flag and only people should use it that read a good part of the backend code ;(
Unfortunately, I haven't found the magic spell to unlock this mess again.
Even a brute force approach:
osc wipebinaries --all home:frispete:python osc rebuild home:frispete:python
still suffers from the same symptoms.
For some reason, the OBS uses packages for the build of other package in the same project, that should be long gone (e.g. even successfully built packages for 11.2 and 11.3 are built with the wrong python version (python-base-2.6.0) instead of 2.6.2 or 2.6.5.
How can I resolve this?
Resolved it by rebuilding python-base-2.6.0 for 11.2 and 11.3 Only after finishing this totally useless, but successful build, I was able to wipe the binaries (checked with osc ll -b home:frispete:python). What-a-mess'ly y'rs, Pete -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (2)
-
Hans-Peter Jansen -
Stephan Kulow