severity 428057 normal merge 428057 178735 thanks Hi,
On Fri, 2007-06-08 at 15:23:24 +0200, Wolfgang Karall wrote: > Package: dpkg > Version: 1.13.25 > Severity: grave > during a class explaining to the participants how important the > consistent state of a system is, dpkg happily installed a broken > Debian package, which was corrupted during transmission from a > mirror. Attached is a type script of the installation, the corrupt > package in question can be downloaded from http://scratch.spiney.org/ > for further investigation (the file with the .ok extension is the same > file without the corruption). The frontends are checking for the hash of the files and will prefent installing broken ones. I agree this should be fixed but it's not going to happen on normal conditions with users using a frontend, and as such I don't think it's grave. > Basically this seems to be the same as #178735 which is over 4 years old > and is still not fixed, hence I submit a new bugreport with severity > grave. There's no reason to file a new bug report for the same issue, if you want to discuss the severity of the old bug report or add new information (which is not the case here), you can of course send a mail to that existing bug report. regards, guillem -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
