On 15 Mar 2001, Gregory Stark wrote: > I hate it when "advocacy" comments appear on bugs but I'm going to do this > anyways. This isn't a minor bug, I wouldn't even consider this a wishlist bug,
*sigh* nonsense. People have been using it like this for 4 years, please try to keep your rhetoric under control. The problem and nuisance from it is soly focused on buggy packages, and in 99% of those cases the only complete way out is fairly manual user intervention, no matter what. > This is BS. You don't need any such feedback from Dpkg. All the information > you need is in the package's current status. The broken package won't be > configured and therefore will cause dependency problems as necessary with > subsequent packages. Nope, there are complex scenarios here where this simple method simply won't work. It cannot be solved in a robust and worthwhile way without extensive dpkg support. You are focusing on the least problematic problem of all, failing configures, there are many other possible failure modes. > This is basically equivalent to the same operation the user is performing by > repeatedly running APT and manually holding packages that are failing to > configure. 'hold' has no effect on configuration of already installed but unconfigured packages. apt and dpkg always force configure them. Jason
