Hi, On Fri, 23 Apr 2010, Josselin Mouette wrote: > Now if you run “dpkg -i bar_2.0_all.deb foo_2.0_hurd-i386.deb”, the > packages will refuse to upgrade, just as if there were conflicts.
And with dpkg -B -i ? > And similarly to conflicts, APT will have to deconfigure one of the two > before upgrading the other. That's expected, the policy says about Breaks: When one binary package declares that it breaks another, dpkg will refuse to allow the package which declares Breaks be installed unless the broken package is deconfigured first, and it will refuse to allow the broken package to be reconfigured. > I think the correct behavior is to not look at Breaks: at all at the > unpack phase, and to only do it at the configure phase. If a package for > which a Breaks has been set has not been upgraded, dpkg should refuse to > configure just as if there were a missing dependency. I have not tested but APT uses --auto-deconfigure (aka -B) by default IIRC and it might simply make sense to have this option activated by default in dpkg since it's required for many common operations anyway. Cheers, -- Raphaël Hertzog Like what I do? Sponsor me: http://ouaza.com/wp/2010/01/05/5-years-of-freexian/ My Debian goals: http://ouaza.com/wp/2010/01/09/debian-related-goals-for-2010/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
