I don't think so. That commit handles a very specific case. The new package has to set all three of Provides, Conflicts, and Replaces. Breaks isn't recognized, and I imagine that there are common churn situations in a development release where Provides is not specified.
cjwatson, as the author of that patch, can you comment on the above?
I don't think so. That commit handles a very specific case. The new package has to set all three of Provides, Conflicts, and Replaces. Breaks isn't recognized, and I imagine that there are common churn situations in a development release where Provides is not specified.
cjwatson, as the author of that patch, can you comment on the above?