On 10/07/2014 09:56 AM, Johan Van de Wauw wrote: > Hello everyone, > > I've updated the pycsw package and I think it is almost ready for > jessie. Please review if you have some time!
Can you push your pristine-tar branch, it's missing the commit for 1.10.0+dfsg? > There are some remaining issues for which I'm not sure what would be > the best solution: > * the package contains some precompiled docs. I don't use these docs > but recompile on the fly (removing google analytics and using jquery > and underscore from debian packages). Should I remove this > documentation or should I add a a lintian override saying that the > precompiled javascript files are not used? You seem to have solved this nicely. > *I'm not entirely sure I handle my postinst correctly. In fact lintian > complains that there is no error handling. Anyone knows a good example > I could use? Should I enable cgi in my postinst? In fact I'm wondering > if it would not be better to use WSGI. I used cgi because that was how > the original packaging was done. The maintainer scripts weren't limited to the appropriate targets. I've pushed a change to address this. As discussed elsewhere in this thread, moving from CGI to WSGI is a good idea. I've also added the copyright and license for the OGC schemas. Addressing the remaining extra-license-file lintian issue, and the possible-documentation-but-no-doc-base-registration issue, are still TODO. I'm not sure if it's desirable to have so much stuff web accessible under /var/www/html. The python-pycsw package contains the ./debian/python-pycsw/usr/lib directory structure which it shouldn't. > Regards, > Johan Kind Regards, Bas -- GPG Key ID: 4096R/E88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/[email protected]
