Hello, Kalev. It would've been nice if you had contacted the maintainers of affected packages before renaming the python subpackages of libgexiv2:
* Mon Aug 15 2016 Kalev Lember klember@redhat.com - 0.10.4-1 [...] - Rename python2 and python3 subpackages are per latest guidelines
I started getting broken dep nag-mails on August 20th: === lazygal has broken dependencies in the rawhide tree: On x86_64: lazygal-0.8.8-1.fc26.noarch requires libgexiv2-python2 On i386: lazygal-0.8.8-1.fc26.noarch requires libgexiv2-python2 On armhfp: lazygal-0.8.8-1.fc26.noarch requires libgexiv2-python2 Please resolve this as soon as possible. ===
I didn't see any notification from you about this beforehand.
Regards, Dominik
Dominik 'Rathann' Mierzejewski wrote:
Hello, Kalev. It would've been nice if you had contacted the maintainers of affected packages before renaming the python subpackages of libgexiv2:
- Mon Aug 15 2016 Kalev Lember klember@redhat.com - 0.10.4-1
[...]
- Rename python2 and python3 subpackages are per latest guidelines
I started getting broken dep nag-mails on August 20th:
lazygal has broken dependencies in the rawhide tree: On x86_64: lazygal-0.8.8-1.fc26.noarch requires libgexiv2-python2
Or implement the rename in a backward-compatible way, adding Provides: libgexiv2-python2 = %{version}-%{release} under the .spec snippet for the Obsoletes: # For upgrade path from F24 Obsoletes: libgexiv2-python2 < 0.10.4 ...
-- Rex
On 08/22/2016 01:56 PM, Dominik 'Rathann' Mierzejewski wrote:
Hello, Kalev. It would've been nice if you had contacted the maintainers of affected packages before renaming the python subpackages of libgexiv2:
Sorry, I didn't find anything using them when I checked. My bad. Thanks for fixing it up!
On Mon, Aug 22, 2016 at 3:39 PM, Kalev Lember kalevlember@gmail.com wrote:
On 08/22/2016 01:56 PM, Dominik 'Rathann' Mierzejewski wrote:
Hello, Kalev. It would've been nice if you had contacted the maintainers of affected packages before renaming the python subpackages of libgexiv2:
Sorry, I didn't find anything using them when I checked. My bad. Thanks for fixing it up!
A good strategy for changes like this is to not even try to find out if anything's using something. Fedora != the world, and we have a documented process for changes like this that not only stuff in Fedora, but things outside of Fedora that build on it should be able to rely on. Just add the Provides, and remove it later: https://fedoraproject.org/wiki/Packaging:Guidelines#Renaming.2FReplacing_Exi...