I agree about Conflicts most likely not being required here. I felt it was conservative to add so as not to introduce a regression if both packages are installed. After some further looking into it, a regression is unlikely. The file in question is identical in both packages, unchanged upstream for 8 years, so it's safe to "overwrite" with the "newer" version: https://gitlab.com/accounts-sso/libsignon-glib/-/tree/master/pygobject So, in the end, the conservative thing to do is to allow anyone with the need to install both packages at the same time and do a Replaces only.
About the versioning, I also agree that in general it is a good idea to be more permissive and limit restrictions by versioning them. In this case, in essence the package name is already the versioning.
Bottom line: Can you drop the Conflicts line in the patch but otherwise upload as proposed here?
Thank you for your comment, Robie.
I agree about Conflicts most likely not being required here. I felt it was conservative to add so as not to introduce a regression if both packages are installed. After some further looking into it, a regression is unlikely. The file in question is identical in both packages, unchanged upstream for 8 years, so it's safe to "overwrite" with the "newer" version: https:/ /gitlab. com/accounts- sso/libsignon- glib/-/ tree/master/ pygobject So, in the end, the conservative thing to do is to allow anyone with the need to install both packages at the same time and do a Replaces only.
About the versioning, I also agree that in general it is a good idea to be more permissive and limit restrictions by versioning them. In this case, in essence the package name is already the versioning.
Bottom line: Can you drop the Conflicts line in the patch but otherwise upload as proposed here?