Oh, my error: I misread, you did indeed use incomplete. My apologies.
To expand on my answer: it is not clearly documented in Debian, but lintian is correct in that symlinking the changelog file to another package is treated as a bug in Debian: a changelog is a required part of each package, and symlinking doesn't mean the file is in the package. It's possible to get into a situation where the symlink target isn't installed, and then the changelog isn't available at all for that package.
Ubuntu does not have a problem with this, and Ubuntu's build daemons replace identical copies of changelogs with symlinks to one.
Oh, my error: I misread, you did indeed use incomplete. My apologies.
To expand on my answer: it is not clearly documented in Debian, but lintian is correct in that symlinking the changelog file to another package is treated as a bug in Debian: a changelog is a required part of each package, and symlinking doesn't mean the file is in the package. It's possible to get into a situation where the symlink target isn't installed, and then the changelog isn't available at all for that package.
Ubuntu does not have a problem with this, and Ubuntu's build daemons replace identical copies of changelogs with symlinks to one.