Add conflicts/replaces for the obsolete packages
Bug #1420175 reported by
Timo Jyrinki
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mir |
Invalid
|
Undecided
|
Unassigned | ||
mir (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Archive admin (infinity) recommends adding Conflicts:
As the new packages did not have the same files this was not a fatal error preventing release of Mir 0.11, but it should be fixed so that people upgrading get rid of the obsolete packages properly.
Changed in mir: | |
status: | New → Invalid |
To post a comment you must log in.
Hmm, cjwatson disagrees though:
< cjwatson> infinity,Mirv: We don't normally use C/R for library transitions, surely; I'd be concerned that for this kind of thing it would make the upgrade unresolvable?
< cjwatson> or at least over-complex
I don't think it'd make it unresolvable, but yes it'd add to complexity. One can argue the apt-get autoremove would eventually at some point take care of this...
So, marking as Invalid for now, can be reopened if considered valid.