https://bugzilla.redhat.com/show_bug.cgi?id=1970619 --- Comment #7 from Major Hayden 🤠 <mhayden@xxxxxxxxxx> --- (In reply to Ben Beasley from comment #6) > I think the other missing piece for a reviewer is understanding how you plan > to handle conflicts with python-azure-sdk while you are creating these > fine-grained packages. That seemed like it was still an open question in > https://bugzilla.redhat.com/show_bug.cgi?id=1953789. Originally, I thought the only path forward was to build all of these little components, obsolete the python-azure-sdk package, and then the little components would go on to live forever. Then I read a bunch of documentation, looked through more specs, and asked people a few more questions. Then I re-read Mohamed's comments in https://bugzilla.redhat.com/show_bug.cgi?id=1953789 and it all clicked. (I am a bit of a slow learner at times.) 😞 The python-azure-sdk package has lots of little "Provides:" added automatically for the Azure SDK components by the Python RPM macros. Since Azure stopped releasing all of the SDK components together in January 2021, the version numbers of all of the little components (in the automatic "Provides:") went stagnant. The little components kept releasing from the main repository and their version numbers increased. As an example, this review is for python-azure-common-1.1.27, but the python-azure-common from python-azure-sdk (in the automatic provides) is less than python-azure-common-1.1.27, so this package should supersede it if I understand everything correctly now. The goal is to keep python-azure-sdk as the thing that ties all of these little packages together so someone could install "the whole SDK" using just the python-azure-sdk package and it would bring in all of the small SDK dependencies, like this one. Does this plan make any sense? I'd like to accomplish this without "Obsoletes:" if possible, and people keep telling me it's definitely possible. -- 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 _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/package-review@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
