https://bugzilla.redhat.com/show_bug.cgi?id=974145 Don Zickus <dzickus@xxxxxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(kevin@tigcc.tical | |c.org) --- Comment #15 from Don Zickus <dzickus@xxxxxxxxxx> --- (In reply to Kevin Kofler from comment #14) > Use Obsoletes for that. How would you obsolete packages that use bluez4? Isn't that a rough guess at best? My understanding is that the API change will break all the bluez4 apps. How do you manage that from a packaging perspective? You need to block the upgrade if any package depends on bluez4 and does _not_ have a bluez5 component to migrate too. Having a separate bluez5 package makes that simpler to handle. I am not sure what rpm magic we can add to keep it inside one package. But I defer to those who have been here before. Perhaps obsoletes can work, I just can't see how. Cheers, Don -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=0plngVwhtK&a=cc_unsubscribe _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review