binary vs "real debian" packages

I've built a few debian "binary" style packages [1] but the maintainer of my local repository is asking that I have all the "proper" debian files, like the .dsc, .orig, .diff, .changes, etc so some how he can sleep better at night or something. He likes dupload for putting packages into the repo an

custom package dependencies not installing

I have a binary style package that I've created. The control file has a large number of Depends entries in it which all install fine by themselves. When I attempt to install the package (via dpkg -i) , it lists all of the Depends and it helpfully tells me that they are not installed (which is true)

avoid conf file overwrite message?

I have a package that I made which does a dpkg-divert in the 'preinst' on a couple of config files and then installs replacements from them. However, even though the dpkg-divert has run (and I've verified it does move it to the name I specify), I still get a message that looks like this: (this is

control file Replaces: question

I want to manage the config files for several other packages centrally in one package that I'm going to maintain. According to the package maintainers guide, section 7.5.1 [1] , this is entirely possible and perfectly reasonable via the Replaces: option in the control file. My question is,