I view this bug as very high priority. I see more than a decade of documentation out there, and of user experience familiar with a process.
A process that changed for code correctness, and for absolutely no other reason. A process than in changing, broke the existing process. And when the process that breaks the existing method is used, the user wonders 'huh?!'.. and consults the man page. The doc dirs. And they see that what they did should be correct... and wonder 'What did I do wrong, I followed the docs?' A user that will spend countless hours trying to figure out what went wrong -- often without a network connection. A process that is essential, and used by a massive number of users, on a massive number of machines. Yet, when I install 7.2.0 -- the man page still reflects nothing of this severe, crippling, massive change in methodology to get --set-selections to work. And when I install 7.2.0, I see far more minor things being corrected. I guess the friendliest way to put this, is that it saddens me. And what I must add? Is that whatever reason or logic was employed in a decision to not update for 7.2.0? That reason or logic was WRONG. That thought process was WRONG. And, Debian needs to get its act together, because minor documentation changes for major problems should always, always make it into point releases. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
