Hi Vincent, Here's the rest:
1) Recommends line moved back to where it should be 2) There is no doxygen-built documentation distributed with this package; I discussed it with #debian-mentors and they seemed to think that the Doxyfile in the upstream tarball is only there for development purposes and its output wouldn't be necessary in a binary distribution. (The plugin interface is documented separately, and already included in hexchat-common.) 3) I turned on verbose building and -D_FORTIFY_SOURCE=2 is indeed being used when python.so is being compiled, so that would make this an upstream issue, correct? Anything in particular I should mention when I report it to them? 4) The weird debian/rules targets were because I referred to the xchat package for examples, and its debian/rules may have been written originally before dh overrides were available/widely known. What I did worked, so I accepted it and moved on. I have switched the format to override_dh_* targets now. 5) debian/watch updated. Let me know your thoughts on the license exception, as well as point 2 in this email, and then I'll re-upload with the final decision. sney -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org