[opensuse-buildservice] How can I eradicate python3-3.2 from home:plater:blender
I'm trying to build blender-2.57b against python3-3.1 which is current. I had python3 linked from devel:languages:python which is python3-3.2, I now need to test with 3.1, I deleted the python3 and python3-base packages a few weeks ago but the build system still finds it somehow. Arbuthnot:/data/packages # find /var/tmp/osbuild-packagecache/ -name 'python3*' -delete -print /var/tmp/osbuild-packagecache/home:plater:blender/openSUSE_Factory/x86_64/python3-devel-3.2-12.1.x86_64.rpm /var/tmp/osbuild-packagecache/home:plater:blender/openSUSE_Factory/x86_64/python3-base-3.2-12.1.x86_64.rpm /var/tmp/osbuild-packagecache/home:plater:blender/openSUSE_Factory/x86_64/python3-3.2-17.1.x86_64.rpm /var/tmp/osbuild-packagecache/home:plater:blender/openSUSE_Factory/x86_64/python3-base-3.2-26.2.x86_64.rpm /var/tmp/osbuild-packagecache/home:plater:blender/openSUSE_Factory/x86_64/python3-devel-3.2-26.2.x86_64.rpm /var/tmp/osbuild-packagecache/home:plater:blender/openSUSE_Factory/x86_64/python3-3.2-26.1.x86_64.rpm /var/tmp/osbuild-packagecache/openSUSE.org:openSUSE:Factory/standard/x86_64/python3-3.1.3-5.1.x86_64.rpm /var/tmp/osbuild-packagecache/openSUSE.org:openSUSE:Factory/standard/x86_64/python3-devel-3.1.3-5.1.x86_64.rpm Arbuthnot:/data/packages # find /var/tmp/osbuild-packagecache/ -name 'python3*' -delete -print This is after osc build openSUSE_Factory has found it somewhere, it downloads "cpio" from the project. Arbuthnot:/data/packages # find /var/tmp/osbuild-packagecache/ -name 'python3*' /var/tmp/osbuild-packagecache/home:plater:blender/openSUSE_Factory/x86_64/python3-base-3.2-26.2.x86_64.rpm /var/tmp/osbuild-packagecache/home:plater:blender/openSUSE_Factory/x86_64/python3-devel-3.2-26.2.x86_64.rpm /var/tmp/osbuild-packagecache/home:plater:blender/openSUSE_Factory/x86_64/python3-3.2-26.1.x86_64.rpm How can I kill "cpio". Thanks Dave P -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Saturday 30 April 2011, 14:54:31 Dave Plater wrote:
I'm trying to build blender-2.57b against python3-3.1 which is current. I had python3 linked from devel:languages:python which is python3-3.2, I now need to test with 3.1, I deleted the python3 and python3-base packages a few weeks ago but the build system still finds it somehow. Arbuthnot:/data/packages # find /var/tmp/osbuild-packagecache/ -name 'python3*' -delete -print /var/tmp/osbuild-packagecache/home:plater:blender/openSUSE_Factory/x8 6_64/python3-devel-3.2-12.1.x86_64.rpm /var/tmp/osbuild-packagecache/home:plater:blender/openSUSE_Factory/x8 6_64/python3-base-3.2-12.1.x86_64.rpm /var/tmp/osbuild-packagecache/home:plater:blender/openSUSE_Factory/x8 6_64/python3-3.2-17.1.x86_64.rpm /var/tmp/osbuild-packagecache/home:plater:blender/openSUSE_Factory/x8 6_64/python3-base-3.2-26.2.x86_64.rpm /var/tmp/osbuild-packagecache/home:plater:blender/openSUSE_Factory/x8 6_64/python3-devel-3.2-26.2.x86_64.rpm /var/tmp/osbuild-packagecache/home:plater:blender/openSUSE_Factory/x8 6_64/python3-3.2-26.1.x86_64.rpm /var/tmp/osbuild-packagecache/openSUSE.org:openSUSE:Factory/standard/ x86_64/python3-3.1.3-5.1.x86_64.rpm /var/tmp/osbuild-packagecache/openSUSE.org:openSUSE:Factory/standard/ x86_64/python3-devel-3.1.3-5.1.x86_64.rpm Arbuthnot:/data/packages # find /var/tmp/osbuild-packagecache/ -name 'python3*' -delete -print
This is after osc build openSUSE_Factory has found it somewhere, it downloads "cpio" from the project. Arbuthnot:/data/packages # find /var/tmp/osbuild-packagecache/ -name 'python3*' /var/tmp/osbuild-packagecache/home:plater:blender/openSUSE_Factory/x8 6_64/python3-base-3.2-26.2.x86_64.rpm /var/tmp/osbuild-packagecache/home:plater:blender/openSUSE_Factory/x8 6_64/python3-devel-3.2-26.2.x86_64.rpm /var/tmp/osbuild-packagecache/home:plater:blender/openSUSE_Factory/x8 6_64/python3-3.2-26.1.x86_64.rpm
How can I kill "cpio".
You won't. It's just a download optimization. The osbuild-packagecache is innocent as well, as it simply avoids to download a single package twice.. You need to adjust the dependencies of your project, e.g. remove d:l:p from the target repos, and just depend on python3 in the package. If your dependency chain contains more then one python 3 version, you should get "have choice" unresolvables. Then, you do a osc meta -e prjconf yourproject and add: Prefer: python-devel-3.1 or something along these lines.. Hth, Pete -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On 04/30/2011 10:31 PM, Hans-Peter Jansen wrote:
How can I kill "cpio". You won't. It's just a download optimization. The osbuild-packagecache is innocent as well, as it simply avoids to download a single package twice..
You need to adjust the dependencies of your project, e.g. remove d:l:p from the target repos, and just depend on python3 in the package.
If your dependency chain contains more then one python 3 version, you should get "have choice" unresolvables. Then, you do a
osc meta -e prjconf yourproject
and add:
Prefer: python-devel-3.1
or something along these lines..
Hth, Pete -
Doesn't work, maybe the python3-3.2 packages in home:plater:blender weren't properly deleted. Dave P -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (2)
-
Dave Plater -
Hans-Peter Jansen