PR#5: Add explicit conflicts - rpms/python-lesscpy

rpms / python-lesscpy

#5 Add explicit conflicts

Merged 6 years ago by mrunge. Opened 6 years ago by churchyard.

rpms/ churchyard/python-lesscpy conflicts into master

Add explicit conflicts

Miro Hrončok • 6 years ago

52d9a74

python-lesscpy.spec

file modified

+7 -1

		`@@ -9,7 +9,7 @@`

		`Name: python-%{pypi_name}`
		`Version: 0.13.0`
		`- Release: 3%{?dist}`
		`+ Release: 4%{?dist}`
		`Summary: Lesscss compiler`

		`License: MIT`
		`@@ -58,6 +58,9 @@`
		`BuildRequires: python3-six`
		`%{?python_provide:%python_provide python3-lesscpy}`

		`+ # executable moved to py3 package`
		`+ Conflicts: python2-lesscpy < 0.13.0-2`
		`+`
		`%description -n python3-lesscpy`
		`A compiler written in python 3 for the lesscss language. For those of us not`
		`willing/able to have node.js installed in our environment. Not all features`
		`@@ -108,6 +111,9 @@`


		`%changelog`
		`+ * Wed Jun 13 2018 Miro Hrončok <mhroncok@redhat.com> - 0.13.0-4`
		`+ - Add explicit conflicts`
		`+`
		`* Tue Jun 12 2018 Miro Hrončok <mhroncok@redhat.com> - 0.13.0-3`
		`- General spec cleanup`
		`- Add missing dependency on six`

churchyard commented 6 years ago

file /usr/bin/lesscpy from install of python3-lesscpy-0.13.0-3.fc28.noarch conflicts with file from package python2-lesscpy-0.10.1-13.fc28.noarch

churchyard commented 6 years ago

The message is from a COPR build of the F29 package for F28

mrunge commented 6 years ago

Hmm, packaging guidelines state

As a general rule, Fedora packages must NOT contain any usage of the Conflicts: field.

https://fedoraproject.org/wiki/Packaging:Conflicts#Acceptable_Uses_of_Conflicts:

churchyard commented 6 years ago

Splitting Packages subsection in that section:

If contents from one package are split into a separate package the new package usually contains files that also appear in the original package which might lead to a implicit conflict between the files in the new package and the original package. ... If the new package should be installable independently of whether the original package is installed, a versioned conflict is allowed. ... The Conflicts are only there to resolve the case where the new package is installed and the older version of the original package was already installed.