Description of problem: All very confusing: EPEL 9 contains: tesseract-langpack-afr.noarch 4.1.0-2.el9 tesseract-langpack-amh.noarch 4.1.0-2.el9 tesseract-langpack-ara.noarch 4.1.0-2.el9 tesseract-langpack-asm.noarch 4.1.0-2.el9 tesseract-langpack-eng.noarch 4.1.0-2.el9 and Appstream contains tesseract-langpack-eng 4.1.0-3.el9 This results in tessearct-osd installing -eng and -doc at versions 4.1.0-2.el9 but this then fails to update Problem 1: package tesseract-osd-4.1.0-2.el9.noarch requires tesseract-tessdata-doc = 4.1.0-2.el9, but none of the providers can be installed - cannot install both tesseract-tessdata-doc-4.1.0-3.el9.noarch and tesseract-tessdata-doc-4.1.0-2.el9.noarch - cannot install both tesseract-tessdata-doc-4.1.0-2.el9.noarch and tesseract-tessdata-doc-4.1.0-3.el9.noarch - cannot install the best update candidate for package tesseract-tessdata-doc-4.1.0-2.el9.noarch - cannot install the best update candidate for package tesseract-osd-4.1.0-2.el9.noarch Think the correct cause of action is to rebuild EPEL package to match RHEL version number. Bit tricky though.
I cannot find anything incorrect in the epel9 spec [1], in particular there is no versioned requires on tesseract in tesseract-tessdata. Furthermore, tesseract-tessdata-4.1.0-2.el9 is the latest build in Koji, tesseract-tessdata-4.1.0-3.el9 does not exist. Where does tesseract-tessdata-4.1.0-3.el9 come from? [1] https://src.fedoraproject.org/rpms/tesseract-tessdata/blob/epel9/f/tesseract-tessdata.spec
Hi, Thanks for replying. The 4.1.0-3.el9 is part of the the OSes AppStream: # dnf list tesseract\* --disablerepo=epel Last metadata expiration check: 1:41:44 ago on Tue 20 Dec 2022 09:43:55 AM CET. Available Packages tesseract.i686 4.1.1-7.el9 AppStream-testing tesseract.x86_64 4.1.1-7.el9 AppStream-testing tesseract-devel.i686 4.1.1-7.el9 CRB-testing tesseract-devel.x86_64 4.1.1-7.el9 CRB-testing tesseract-langpack-eng.noarch 4.1.0-3.el9 AppStream-testing tesseract-tessdata-doc.noarch 4.1.0-3.el9 AppStream-testing This is actually ALmaLinux I should say am assuming RHEL is the same. No reason not to be.
i.e RHEL as the tesseract-tessdata on 9 now but with only a tiny fraction of the resulting builds which is of course a bit of pain.
By EPEL policy [0], tesseract-tessdata must be retired from EPEL 9 if it exists in RHEL 9. The policy exists specifically to avoid the types of conflicts reported there. There are significantly more subpackages from this build shipped in EPEL than shipped in RHEL. Shipped in RHEL: tesseract-langpack-eng-4.1.0-3.el9 tesseract-tessdata-doc-4.1.0-3.el9 Shipped in EPEL: all the subpackages from the koji build [1] I'm not sure if those additional subpackages being removed will be disruptive for users or not. A quick repoquery doesn't show any EPEL packages that require or buildrequire those additional subpackages. for p in tesseract-equ tesseract-osd tesseract-langpack-\* tesseract-script-\* do echo "checking $p" repoquery --repo epel,epel-source -q --whatrequires $p done If the additional subpackages are useful to people, they can be built and shipped as a tesseract-tessdata-epel package as documented in the guidelines [2]. It is also possible to request these subpackages be shipped in RHEL, although that is not guaranteed to be approved and would need justification. [0] https://docs.fedoraproject.org/en-US/epel/epel-policy/#_policy [1] https://koji.fedoraproject.org/koji/buildinfo?buildID=1867307 [2] https://docs.fedoraproject.org/en-US/epel/epel-policy-missing-sub-packages/
Package is retired.