Please tag releases and do not maintain debian/ dir here

[tillea]

Hi,
pydf came up in some QA initiative (Bug of the Day). I realised that you kept on working on the upstream as well as the Debian packaging code. This is a bit unfortunate for Debian users since the result is not available from the Debian mirrors. The drawback is that your repository does not include any NMU (like 12+nmu1). In general maintaining the debian/ dir is something else than maintaining upstream code. I would suggest the following:

1. Remove the debian/ dir from your master branch (at least) if not at all from github.
2. Tag releases of your upstream code
3. Do not (mis-)use debian/changelog to log changes in your upstream code. Its just for packaging changes.
4. Maintain the debian/ dir on Salsa (please note that the Debian version numbering you've choosen and the source format is wrong - pydf is not a native Debian package)

For your comfort I've created a repository on Salsa which modernises the packaging to latest standards and just includes your upstream code. Usually I would file an "Intend to salvage" bug report to upload this package but it seems some clarification with you here in the issue tracker is more fruitful since several items of the salvage procedure are not applicable due to the unusual way you are doing the package maintenance.

Kind regards, Andreas.

[tillea]

I'll file some ITS (Intend To Salvage) bug against pydf in Debian. This means another waiting period of 21 days. It would be great if you could answer either this ITS bug or here inside the issue.