This is expected behavior; if you hadn't modified a config file, it updates it with the new version, if you had, it asks you what you want to do with it.

I believe paul is correct; is there any reason to keep this bug open?

I think the only way this is possible is if you modified capsd-configuration.xml but didn't modify datacollection-config.xml or snmp-graph.properties.

From http://www.debian.org/doc/debian-policy/ap-pkg-conffiles.html#sE.1
"If neither the user nor the package maintainer has changed the file, it is left alone. If one or the other has changed their version, then the changed version is preferred - i.e., if the user edits their file, but the package maintainer doesn't ship a different version, the user's changes will stay, silently, but if the maintainer ships a new version and the user hasn't edited it the new version will be installed (with an informative message). If both have changed their version the user is prompted about the problem and must resolve the differences themselves."

So, I think what you're seeing is simply the "informative messages" saying that the maintainer shipped a new version of those files, and the new versions were being automatically installed since you hadn't edited your copies.