Updating the gitdb module is understandable, but changing the package name to "gitdb2" while actually installing modules named "gitdb" is confusing. Doing so without any hint that this module overhaps deployments of gitdb is dangerous: this showed up when I was trying to RPM building this software for AWX deployment and saw the conflicts.
Reactions are currently unavailable
Updating the gitdb module is understandable, but changing the package name to "gitdb2" while actually installing modules named "gitdb" is confusing. Doing so without any hint that this module overhaps deployments of gitdb is dangerous: this showed up when I was trying to RPM building this software for AWX deployment and saw the conflicts.