Having a problem when upgrading an installed F41: ... sudo dnf upgrade
Breaks with:
transaction failed: Rpm transaction failed. - file /usr/lib64/libtesseract.so.5.4.1 from install of tesseract-libs-5.4.1-4.fc41.x86_64 conflicts with file from package tesseract-5.4.1-2.fc41.x86_64
Anybody could solve this problem??
Kind regards
Joachim Backes
On Sun, 6 Oct 2024 12:55:08 +0200, Joachim Backes wrote:
Having a problem when upgrading an installed F41: ... sudo dnf upgrade
Breaks with:
transaction failed: Rpm transaction failed. - file /usr/lib64/libtesseract.so.5.4.1 from install of tesseract-libs-5.4.1-4.fc41.x86_64 conflicts with file from package tesseract-5.4.1-2.fc41.x86_64
Anybody could solve this problem??
You ought to see release 4 for tesseract not only release 4 for tesseract-libs. Which packages of tesseract* are installed prior to this upgrade attempt?
rpm -qa tesseract*
?
Also, there's some odd activity in the tesseract.spec file related to a package split:
https://src.fedoraproject.org/rpms/tesseract/c/85fd62953a661694f5ce930006611...
92 %package libs 93 Summary: Shared libraries for %{name} 94 + Conflicts: %{name} < 5.4.1-4
Why?! The package builds both "tesseract" and "tesseract-libs", and since the tesseract executables depend on the shared libs implicitly, an upgrade would pull in this new -libs subpackage _and_ upgrade the main tesseract package at the same time.
No need to explicit "Conflits"!
On Sun, Oct 6, 2024 at 7:39 AM Michael Schwendt mschwendt@gmail.com wrote:
On Sun, 6 Oct 2024 12:55:08 +0200, Joachim Backes wrote:
Having a problem when upgrading an installed F41: ... sudo dnf upgrade
Breaks with:
transaction failed: Rpm transaction failed.
- file /usr/lib64/libtesseract.so.5.4.1 from install of
tesseract-libs-5.4.1-4.fc41.x86_64 conflicts with file from package tesseract-5.4.1-2.fc41.x86_64
Anybody could solve this problem??
You ought to see release 4 for tesseract not only release 4 for tesseract-libs. Which packages of tesseract* are installed prior to this upgrade attempt?
rpm -qa tesseract*
?
Also, there's some odd activity in the tesseract.spec file related to a package split:
https://src.fedoraproject.org/rpms/tesseract/c/85fd62953a661694f5ce930006611...
92 %package libs 93 Summary: Shared libraries for %{name} 94 + Conflicts: %{name} < 5.4.1-4
Why?! The package builds both "tesseract" and "tesseract-libs", and since the tesseract executables depend on the shared libs implicitly, an upgrade would pull in this new -libs subpackage _and_ upgrade the main tesseract package at the same time.
No need to explicit "Conflits"!
It is necessary, or otherwise rpm doesn't know that an upgrade requires the old package to be uninstalled first. It will do it out of order and fail like the original poster stated.
Unfortunately, mingw-gcc is broken in F41 and I need to fix that first to fix this.
-- 真実はいつも一つ!/ Always, there's only one truth!
On Sun, Oct 6, 2024 at 7:46 AM Neal Gompa ngompa13@gmail.com wrote:
On Sun, Oct 6, 2024 at 7:39 AM Michael Schwendt mschwendt@gmail.com wrote:
On Sun, 6 Oct 2024 12:55:08 +0200, Joachim Backes wrote:
Having a problem when upgrading an installed F41: ... sudo dnf upgrade
Breaks with:
transaction failed: Rpm transaction failed.
- file /usr/lib64/libtesseract.so.5.4.1 from install of
tesseract-libs-5.4.1-4.fc41.x86_64 conflicts with file from package tesseract-5.4.1-2.fc41.x86_64
Anybody could solve this problem??
You ought to see release 4 for tesseract not only release 4 for tesseract-libs. Which packages of tesseract* are installed prior to this upgrade attempt?
rpm -qa tesseract*
?
Also, there's some odd activity in the tesseract.spec file related to a package split:
https://src.fedoraproject.org/rpms/tesseract/c/85fd62953a661694f5ce930006611...
92 %package libs 93 Summary: Shared libraries for %{name} 94 + Conflicts: %{name} < 5.4.1-4
Why?! The package builds both "tesseract" and "tesseract-libs", and since the tesseract executables depend on the shared libs implicitly, an upgrade would pull in this new -libs subpackage _and_ upgrade the main tesseract package at the same time.
No need to explicit "Conflits"!
It is necessary, or otherwise rpm doesn't know that an upgrade requires the old package to be uninstalled first. It will do it out of order and fail like the original poster stated.
Unfortunately, mingw-gcc is broken in F41 and I need to fix that first to fix this.
Update submitted: https://bodhi.fedoraproject.org/updates/FEDORA-2024-d100358a50
On Sun, 6 Oct 2024 07:46:12 -0400, Neal Gompa wrote:
It is necessary, or otherwise rpm doesn't know that an upgrade requires the old package to be uninstalled first. It will do it out of order and fail like the original poster stated.
Originally, it would be avoided with explicit
Requires: tesseract-libs%{?_isa} = %{version}-%{release}
in package "tesseract".
Within the packaging guidelines, there's a section added in 2013 [!] that only comments on an acceptable use scenario of "Conflicts".
If it were a MUST to avoid implicit conflicts during a system update, then the guidelines ought to fix the wording and make it a MUST.
On 06.10.24 13:39, Michael Schwendt wrote:
On Sun, 6 Oct 2024 12:55:08 +0200, Joachim Backes wrote:
Having a problem when upgrading an installed F41: ... sudo dnf upgrade
Breaks with:
transaction failed: Rpm transaction failed. - file /usr/lib64/libtesseract.so.5.4.1 from install of tesseract-libs-5.4.1-4.fc41.x86_64 conflicts with file from package tesseract-5.4.1-2.fc41.x86_64
Anybody could solve this problem??
You ought to see release 4 for tesseract not only release 4 for tesseract-libs. Which packages of tesseract* are installed prior to this upgrade attempt?
rpm -qa tesseract*
?
rpm -qa tesseract* tesseract-tessdata-doc-4.1.0-8.fc41.noarch tesseract-langpack-deu-4.1.0-8.fc41.noarch tesseract-langpack-eng-4.1.0-8.fc41.noarch tesseract-5.4.1-2.fc41.x86_64
Kind regards
Joachim Backes
Also, there's some odd activity in the tesseract.spec file related to a package split:
https://src.fedoraproject.org/rpms/tesseract/c/85fd62953a661694f5ce930006611...
92 %package libs 93 Summary: Shared libraries for %{name} 94 + Conflicts: %{name} < 5.4.1-4
Why?! The package builds both "tesseract" and "tesseract-libs", and since the tesseract executables depend on the shared libs implicitly, an upgrade would pull in this new -libs subpackage _and_ upgrade the main tesseract package at the same time.
No need to explicit "Conflits"!