"Adam M." <[EMAIL PROTECTED]> writes: > Anthony DeRobertis wrote: > >>Klaus Ethgen wrote: >> >> >> >>>The according bug is #306608. >>> >>> >> >>This is a bug, though possibly not in the libwxgtk2.4-python package. If >>the relevant maintainers (libwxgtk2.4-python, wxpython2.5.3) and bug >>sumitters can't work out a solution, then ask the Technical Comittee to >>do so. That's what they're there for. >> >> > > I haven't read the bug report, but when a newer package replaces an > older one, you need to have add a > Conflicts: <old version> > Replaces: <old version> > To the new package. I think apt-get, dselect and others have been set up > in this manner. > > It is not correct to put Conflicts in the 2.4 package because it is 2.5 > that *caused* the conflict. It came on the scene AFTER 2.4, right? > > - Adam
No, as I read there first was 2.4 then 2.5 came and then the 2.4 package got a new version uploaded after 2.5 causing the problem on upgrade. So 2.5 is broken for having a replaces without conflicts and for not coordinating an update with 2.4. And the new 2.4 is broken for not having a conflict to clean up the broken mess 2.5 creates. It looks like 2.5 misused the Replaces field to manage a common file both 2.4 and 2.5 have. The right procedure would have been to split that file out of both packages into it's own package and have a conflicts, replaces and provides between the two (assuming the 2.5 version works for 2.4 too). The question is: Is it the job of 2.4 to clean up the mess 2.5 made? My opinion: yes, if you are doing an upload anyway then add the conflicts. Doesn't hurt you. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]