Santiago Vila <sanv...@unex.es> writes: > On Sat, Nov 03, 2018 at 03:42:20PM -0700, Russ Allbery wrote:
>> In a way, I don't think this goes far enough. Build-Conflicting with >> something installed by debhelper would be incredibly painful and would >> basically require the package be built in a chroot. > I'm not sure what do you mean by "painful" here. In this case, a > Build-Conflicts would have told sbuild to uninstall automake during > the "install build-dependencies stage", which is not painful at all. I certainly think it is! I would be extremely upset if trying to build a package uninstalled automake. This also makes the package effectively unbuildable outside of a chroot, which is also quite painful. I feel pretty strongly here that Build-Conflicts is not a correct solution to this problem, and therefore I'm not happy about the idea of adding a Policy rule that would imply that it was. The problem was that the package didn't tolerate having automake installed, and fixing *that* was the correct fix. But this seems fairly subtle to try to turn into a general Policy rule. -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
