Control: tag -1 - newcomer Hi Rafal,
On Tue, Feb 03, 2015 at 10:20:26AM +0100, Rafal Pietrak wrote: > My guess is that some limit on number of errors was taken into account > unneceserly during an upgrade - upgrades are expected to rise trancient > errors. Your report seems to error into the total opposite unfortunately by not mentioning a single error. Upgrading is a tricky business and basically different for everyone (as which packages you have installed can vary widely as you have ~30000 to choose from). Your report is hence as actionable as a weather report saying: "It is going to rain tomorrow somewhere on earth". That isn't really telling me much about if I should carry an umbrella around or not on my adventure around my little patch of dirt. For this, as well as here, we need "details, details, details" to actually do something about it. But my crystalball tells me that you might mean #776063 as dpkg shows in this context a "too many errors" message (litmus test: the word "dbus" was printed all over the place, right?). If not we need at the very least the actual error message(s). The current system state (/var/lib/dpkg/status) as well as the state before the upgrade (the /var/backups/dpkg.status* file dated before the update) could also be helpful. On a more general note: Try not to guess in bugreports. You are the eyewitness, you know the facts. I am the guy on jury duty who has to come up with a coherent story of what happened and why. I know its tempting to "add" evidence as a witness, but that can spoil the whole process. Best regards David Kalnischkies P.S.: The 'newcomer' tag is for maintainers to indicate "bitsized" bugs which a newcomer to the project/package can try to tackle to get started. I wouldn't recommend these sort of upgrade bugs as a starting point… and we certainly don't need to label bugs from newcomers as such (which I guess is what you meant it to mean) as a bug is a bug, it isn't worse just because a longtime contributor reported it.
signature.asc
Description: Digital signature
