Helmut Grohne <hel...@subdivi.de> writes: > I incline to agreeing with the scenario you depict. This can reasonably > happen. I also think that David made a good case for it being unlikely > to manage oneself into the buggy situation that way. And then the > consequence is that you lost some possibly important files. If you ended > up fiddling with dpkg in a failed upgrade, would it be too much to ask > for running dpkg --verify? In the event you see missing files, you may > reinstall affected packages and thus have cured the symptoms for your > installation. > > Say we extended release-notes saying that you should dpkg --verify after > the upgrade and more so if you happened to use dpkg directly in the > process and review the output. Would that address your concern?
Perhaps release-notes should suggest to run dpkg --verify after a dist-upgrade anyway - i assume it doesnt hurt to do so? Happy to suggest and edit text for release notes: i would want to know: - how do i know if the system is fine? i was assuming that it would output nothing if everything is fine, but that seems to be far from the case. I get huge amounts of output that is very hard to interpret, i assume it's showing a 'c' for every single changed conffile, and 'missing' where i deleted conffiles. But why are some lines contain question marks? we would need a lot of explanation here to make this useful for users (unfortunately, the dpkg man page is very confusing about this option, and doesnt have any of this, as far as i can understand) - if something went wrong: a) how do i know? would there be an obvious error message? do i need to check the exit status? b) what would i do?: reinstall some packages? reinstall the whole system? (maybe this should be in a bug against release-notes)
