On September 24, 2016 1:00:21 PM EDT, Matthias Klumpp <matth...@tenstral.net> wrote: >2016-09-24 18:36 GMT+02:00 Ximo Baldó <espinda...@gmail.com>: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA512 >> >> No. Precisely, the bug I'm reporting is that the package manager, >plasma-discover, does not warn user about his intention to do that >removing operation. So, the user never has notice about these changes >and as far I know this situation can be considered as grave bug as it >can lead to an unusable system. > >Discover is meant for users who have no idea what a "package" is, so >prompting them with questions they don't understand will highly likely >not happen (they would just klick "yes" anyway). I wonder though if we >could add some safeguard, like "ask for re-confirmation if more than >50 packages are going to be removed". >In any case, this is not a grave bug since it only ever happens on >development suites, which no end-user sees. It's normal/important at >max.
Developers are users too. If your position is that Discover isn't suitable for use in testing/unstable then what that means is Discover gets released untested. That's not a recipe for success. If it breaks a system without warning, that's a grave bug. Nothing about bug severities says that they only apply to stable. What I think you want is for developers and advanced users to use Discover, at least occasionally, during development so we know it's well integrated with Debian prior to release. That's not going to happen if it silently breaks systems. Scott K
