Sometimes files may become corrupt either by the user or other items. There could be a tool that identifies the files that don't match what was originally installed and present that to the user.
Clearing 2.0 milestone
rpm (rpm -Va) and dpkg (dpkg --verify) can do this, opkg can't yet.
Reassigning to opkg. Alejandro: rpm and dpkg both have a way to verify files on disk against the checksums in the package database. It would be useful if opkg could also do this.
*** Bug 8948 has been marked as a duplicate of this bug. ***
Implemented on 8f367b763246ebe2306a45f408ee7cbb872b30f6