Red Hat Bugzilla – Bug 1280209
Cyclic dependency in javapackages-tools
Last modified: 2016-04-18 06:17:27 EDT
javapackages-tools build requires itself also javapackages-tools requires python3-javapackages which is subpackage of javapackages-tools, this creates conflict when you try rebuild javapackages-tools for a new minor release of Python3.
DEBUG util.py:393: Last metadata expiration check performed 0:02:10 ago on Tue Nov 10 20:44:32 2015.
DEBUG util.py:393: Package make-1:4.1-4.fc24.x86_64 is already installed, skipping.
DEBUG util.py:393: Package python3-devel-3.5.0-2.fc24.x86_64 is already installed, skipping.
DEBUG util.py:393: Package python3-setuptools-18.5-2.fc24.noarch is already installed, skipping.
DEBUG util.py:393: Package python3-six-1.9.0-4.fc24.noarch is already installed, skipping.
DEBUG util.py:393: Error: nothing provides python(abi) = 3.4 needed by python3-javapackages-4.6.0-8.fc24.noarch.
DEBUG util.py:393: nothing provides python(abi) = 3.4 needed by python3-javapackages-4.6.0-8.fc24.noarch
To workaround the issue I propose to create bootstrap macro which when turned off/on will drop Requires: python3-javapackages so javapackages-tools can be rebuilt with a new minor release of Python3.
bumping priority, this is blocking a number of dependent packages of the python3.5 rebuild.
If you could add a boostrap option to the package it means we can easily deal with this in the future.
kalev: looks good, please push
OK, bootstrapping done in f24-python3. I first built javapackages-tools-4.6.0-10.fc24 with bootstrap enabled, followed by a regular javapackages-tools-4.6.0-11.fc24 build with bootstrap disabled.
Thanks for handling this guys, much appreciated ;)