Comment 3 for bug 506985

Revision history for this message
Soren Hansen (soren) wrote :

In other words, this is expected, yet highly unfortunate behaviour.

We have a few options:

1. Version the binary packages and specify a Breaks: relationship between them.
2. Show a great big warning that this is going to happen.
3. Somehow pursuade upstream to provide a proper upgrade path.