I'm trying to set up a clean upgrade path for celestia.
Previously there was a monolithic 'celestia' package with everything inside it,
now there will be a separate 'celestia-data' package (from a different source
repository), while the former 'celestia' package will be splitted in
'celestia-common', 'celestia-gtk' and 'celestia-qt'.
The plan is that when a user upgrade from pre 1.7, it should end up with
'celestia-gtk' as default interface, which requires both 'celestia-common'
and 'celestia-data'.
I have set the 'celestia' specfile as follows:
%package common
Obsoletes: %{name} < 1.6.3
%package gtk
Requires: %{name}-common%{?_isa} = %{version}-%{release}
Provides: %{name} = %{version}-%{release}
I have prepared a build at
https://copr.fedorainfracloud.org/coprs/mattia/Astronomy/build/5517618/
When running an upgrade coming from pre 1.7, I get:
# dnf upgrade celestia --refresh
...
==========================================================================================
Package Arch Version Repository
Size
==========================================================================================
Installing:
celestia-common x86_64 1.7.0~202302239c1c4e4-0.3.fc37
copr:copr.fedorainfracloud.org:mattia:Astronomy 2.0
M
sostituisce celestia.x86_64 1.6.2-0.8.beta3.fc37
Installazione dipendenze:
celestia-data noarch 1.7.0~20230223ffc806d-1.fc37
copr:copr.fedorainfracloud.org:mattia:Astronomy 281
M
celestia-gtk x86_64 1.7.0~202302239c1c4e4-0.3.fc37
copr:copr.fedorainfracloud.org:mattia:Astronomy 76
k
...
Errore: Errore test di transazione:
il file /usr/share/celestia/fonts dell'installazione di
celestia-common-1.7.0~202302239c1c4e4-0.3.fc37.x86_64 entra in conflitto con il file del
pacchetto celestia-1.6.2-0.8.beta3.fc37.x86_64
So, dnf correctly finds that celestia-common obsoletes celestia, still it complains about
conflicting files.... ?
Have I set up something wrong?