On 1/31/22 04:44 PM, Stephen Gallagher wrote:
On Mon, Jan 31, 2022 at 3:45 PM Steven A. Falco
<stevenfalco(a)gmail.com> wrote:
>
> When updating from KiCad 5 to KiCad 6, a few files have moved from the kicad-doc
package to the main kicad package.
>
> If someone has KiCad 5 and its documentation package installed, and then tries to
just upgrade the main package to KiCad 6 (without also updating the docs), they get an
error message like:
>
> Error: Transaction test error:
> file /usr/share/doc/kicad/scripts/lib_convert.py from install of
kicad-1:6.0.1-1.fc35.x86_64 conflicts with file from package
kicad-doc-1:5.1.12-1.fc35.noarch
> file /usr/share/doc/kicad/scripts/test_kicad_plugin.py from install of
kicad-1:6.0.1-1.fc35.x86_64 conflicts with file from package
kicad-doc-1:5.1.12-1.fc35.noarch
>
> I think the correct solution is to put this into the main package:
>
> Obsoletes: kicad-docs < 6.0.0
>
> Is that correct, or is there a better way to handle it?
No, that will remove kicad-docs entirely from user systems.
What you want is:
Conflicts: kicad-doc < %{epoch}:%{version}-{release}
If you forget the epoch in this comparison, it won't work properly,
since the existing kicad-doc package will resolve as higher.
Also, I recommend using the version and release macros instead of a
static value, because it will ensure that the docs are always updated
to match the binary.
Thanks for the info. In this case, I don't think it matters too much about the
version/release. It is just that a few files moved from the kicad-doc-5.1.12 package into
the kicad-6.0.0 main package. It shouldn't be a problem going from 6.0.0 to 6.0.1,
for example. A plain "dnf update" should handle that case.
But I'll definitely remember about the epoch - good tip!
Steve