Andrey,Thank you for your comments. This being my fist debian submission, I want to make sure there are not too many cooks in the kitchen before uploading a new version. Back at the beginning of May, Stephen Kitt had offered to co-maintain and sponsor the project. However, nothing has happened since. Stephen, what you you like me to do?
Assuming that I'm uploading a new version, some comments and questions.1) I will create a debian directory that exists solely for the debian submission (i.e. not PPA, not OBS). This should clean things up. 2) IIRC, I was forced to increment the Debian release by debain-mentors. A failed submission "used up" a debian release number and blocked a corrected submission with the same release number. Is there some way around this? 3) I will eliminate packages libddcutil0 and libddcutil-dev. The shared library does not (yet) implement all the functionality needed by the command line application, which is why ddcutil is not linked against libddcutil0, and it is subject to change from user feedback and as the Python API is implemented. Those wishing to experiment the the API can get the shared library from my site or OBS.
Sanford On 07/24/2017 03:11 PM, Andrey Rahmatullin wrote:
Control: tags -1 + moreinfo Please remove all unneeded files from debian/. Please remove commented out sample lines from debian/rules. You shouldn't "Bump Debian release for debian-mentors". Please remove all changelog entries (both old upstream ones and recent bumps) and add oe correct entry. Please switch to the debhelper compat level 10. B-D: libglib2.0-0 looks wrong. Please update to the current Standards-Version version. Please fix and uncomment Vcs-Browser. Adding explicit Depends: on library packages is usually wrong. Please remove unneeded comments from debian/control. Please drop debian/menu. Consider adding the symbols file. Please don't ship .la. I'd expect ddcutil to be linked against libddcutil0.