On Thu, 18 Mar 2010, Michael Tokarev <m...@tls.msk.ru> wrote: > I see 3 issues here: > > 1) bad error message _text_. It's fixed (only partially, -- I've looked > at the thing again and see more cases where it'll throw as useful > error messages as this one -- I'll add/send more patches for this). > At least this does not need to be discussed further, I think.
Great! > 2) destination of error/warning messages. I disagree with your position > here, it is for this very reason we've separate stderr and stdout. If OK, there are other ways of getting the type of results I desire. > 3) -Werror mode. I somehow missed your second email in this bug#, where > you said: > > " > I think that this particular error should result in aborting the attempt > to run kvm. When I specifically instruct the program to do a particular > action and it's unable to do so that's a good cause for aborting with an > error. IMHO work-arounds should be implemented by humans not software. > " > > Valid points, and it's the same as with -enable-kvm and inability to > use /dev/kvm for some reason (#574063). > > And this is where the real question is, and what is this bug about, or > at least I will treat it this way. > > Does it sound right? Yes, that's fine. If you make it always do what I tell it to do then there would not be much need for error messages about failure modes. > But for 3), and #574063, I think the two bugs should be merged together. > There are other cases like this, and before trying to deal with the > issues, there should be general consensus about how to solve similar > problems. Sure. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
