Can't install on Alma 8 (Centos 8)
cshabazian opened this issue · 6 comments
This is a brand new minimal build, with only the following run/failing:
[root@patchman ~]# cat <<EOF >> /etc/yum.repos.d/openbytes.repo
[openbytes]
name=openbytes
baseurl=https://repo.openbytes.ie/patchman/el8
enabled=1
gpgcheck=0
EOF
[root@patchman ~]# dnf -y install epel-release
AlmaLinux 8 - BaseOS 5.2 MB/s | 5.1 MB 00:00
AlmaLinux 8 - AppStream 7.0 MB/s | 11 MB 00:01
AlmaLinux 8 - Extras 38 kB/s | 19 kB 00:00
openbytes 16 kB/s | 20 kB 00:01
Dependencies resolved.
=========================================================================================================================================
Package Architecture Version Repository Size
=========================================================================================================================================
Installing:
epel-release noarch 8-18.el8 extras 24 k
Transaction Summary
=========================================================================================================================================
Install 1 Package
Total download size: 24 k
Installed size: 35 k
Downloading Packages:
epel-release-8-18.el8.noarch.rpm 307 kB/s | 24 kB 00:00
-----------------------------------------------------------------------------------------------------------------------------------------
Total 56 kB/s | 24 kB 00:00
AlmaLinux 8 - Extras 583 kB/s | 3.4 kB 00:00
Importing GPG key 0xC21AD6EA:
Userid : "AlmaLinux <packager@almalinux.org>"
Fingerprint: E53C F5EF 91CE B0AD 1812 ECB8 51D6 647E C21A D6EA
From : /etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux
Key imported successfully
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
Preparing : 1/1
Installing : epel-release-8-18.el8.noarch 1/1
Running scriptlet: epel-release-8-18.el8.noarch 1/1
Many EPEL packages require the CodeReady Builder (CRB) repository.
It is recommended that you run /usr/bin/crb enable to enable the CRB repository.
Verifying : epel-release-8-18.el8.noarch 1/1
Installed:
epel-release-8-18.el8.noarch
Complete!
[root@patchman ~]# dnf makecache
AlmaLinux 8 - BaseOS 9.3 kB/s | 3.8 kB 00:00
AlmaLinux 8 - AppStream 9.6 kB/s | 4.1 kB 00:00
AlmaLinux 8 - Extras 9.3 kB/s | 3.8 kB 00:00
Extra Packages for Enterprise Linux 8 - x86_64 3.0 MB/s | 14 MB 00:04
openbytes 5.5 kB/s | 3.0 kB 00:00
Metadata cache created.
[root@patchman ~]# dnf -y install patchman patchman-client
Last metadata expiration check: 0:00:03 ago on Mon 27 Feb 2023 11:14:46 AM PST.
Error:
Problem: package python3-django-filter-22.1-1.el8.noarch requires python3.6dist(django) >= 3.2, but none of the providers can be installed
- package python3-django3-3.2.15-4.el8.noarch conflicts with python3-django provided by python3-django-2.2.24-1.el8.noarch
- package patchman-2.0.11-1.noarch requires python3-django-filter, but none of the providers can be installed
- package patchman-2.0.11-1.noarch requires python3-django >= 2.2.9, but none of the providers can be installed
- cannot install the best candidate for the job
(try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
Hi,
same on my side under rockylinux 8 and 9. If you have any ideas.
Looks like the deps for python3-django-filter have been updated to django3. There is a branch for 2022/2023 distro support (which includes django3) but some pieces are missing. I'll follow up on those to see where they are at now.
See the branch here: https://github.com/furlongm/patchman/tree/django3
I was able to get an install to complete without errors by adding the following rpms:
httpd python3-colorama python3-requests python3-magic python3-progressbar2 python3-django-extensions python3-django-tagging django-bootstrap3 python3-importlib-metadata python3-debian python3-defusedxml python3-lxml python3-humanize python3-memcached policycoreutils-python-utils
I still had to install with a --nodeps flag, which we don't want to do, but I figure this may help point you towards what is needed in the rpmspec file
Outstanding issues are documented here: #468
If django doesn't get added to EPEL9, may need to drop support for patchman server on RHEL9 and derivatives.
I followed the instructions in the INSTALL in a Centos8 Stream container today and everything installed successfully:
cat <<EOF >> /etc/yum.repos.d/openbytes.repo
[openbytes]
name=openbytes
baseurl=https://repo.openbytes.ie/patchman/el8
enabled=1
gpgcheck=0
EOF
dnf -y install epel-release
dnf makecache
dnf -y install patchman patchman-client
@furlongm would you consider removing the apache dependency maybe? I'd rather use NGINX as an example and a hard dependency on apache/httpd might be a little inflexible for different environments.
Version 3 released with support for EL9