Barry Scott wrote:I'm packaging pylint for python2 on centos8 and it builds fine but will not install.
(Yes I know python2 is end of life - working on it)
At least on EL8, python2 will be supported for a number ofyears still. Obviously, moving to python3 is still the wiseplan. :)mock is used to do the builds.
Here is what happens with I do the dnf install:
# dnf install -y ods-python-pylint
Last metadata expiration check: 0:19:59 ago on Fri 13 Mar 2020 16:22:30 UTC.
Error:
Problem: conflicting requests
- nothing provides /usr/bin/python needed by ods-python-pylint-1.9.3-2.noarch
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
And this is what rpm thinks are the requirements:
$ rpm -qpR ods-python-pylint-1.9.3-2.noarch.rpm
ods-python-astroid
ods-python-backports.functools_lru_cache
ods-python-configparser
ods-python-enum34
ods-python-futures
ods-python-isort
ods-python-lazy-object-proxy
ods-python-mccabe
ods-python-singledispatch
ods-python-wrapt
python(abi) = 2.7
python2
python2-six
rpmlib(CompressedFileNames) <= 3.0.4-1
rpmlib(FileDigests) <= 4.6.0-1
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
rpmlib(PayloadIsXz) <= 5.2-1
Anyone know where is the /usr/bin/python coming from or how I can debug this?
I would guess it's from a shebang in one of the scriptswithin the package. But I don't know what's in theods-python-pylint package so I can only guess.
I fixed up all the shebangs to be #!/usr/bin/python2.7 and that did not fix it.
Then I rm'ed all the files with a '#!' in the first line.
Then I rm'ed the egg stuff (I think the find_requires logic can dig something out of it)
What I expected to use is rpm -q -R would print the /usr/bin/python requirement, but it does not.
Barry