https://bugzilla.redhat.com/show_bug.cgi?id=2029677
--- Comment #5 from Petr Menšík <pemensik(a)redhat.com> ---
(In reply to Mattia Verga from comment #4)
So, both this new package and python-sep are going to provide
python3-sep...
I think it's wrong.
I think the only way to handle this is to bump this new package to a version
greater than python-sep and retire python-sep.
Of course, something like that is expected. This package can provide both
python and native library from single source. Moreover it does not use python
site to proxy releases, but uses what I believe is original author's
repository.
Because I am using %autorelease macro, raising release above current 3 would be
just matter of 3 commits. I think Obsoletes is not necessary if the new
python3-sep package has the same name, just is built from different source.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component
https://bugzilla.redhat.com/show_bug.cgi?id=2029677