On 16-May-2017, Boyuan Yang wrote: > I would like to summerize problems found when packaging pagure in > May 2017. This is a useful list of issues! > * Every version needs py-bcrypt, which exists in fedora but long > superceded by python-bcrypt. > > Patches in pagure source code available. Do you mean that the Debian packaging could just take those patches, and apply them to the existing Pagure version? > * Some strange unittest errors for v2.6+dfsg. Thanks for the build logs to show those errors. > * Unittest needs a functional database when using "local" auth > method but that database never exists during dh_auto_test. Perhaps a change to the unit tests, so that they don't rely on an actual database. (Unit tests should be isolated from external dependencies that are not reliably available at test time.) Would this be worthwhile? > * Specific to v2.14.2: pep8-compat testing would invoke pyflake8, > which is python3 version in Debian. (Fixed in upstream trunk). Another patch that can just be taken from upstream and applied in the packaging? -- \ “I have yet to see any problem, however complicated, which, | `\ when you looked at it in the right way, did not become still | _o__) more complicated.” —Paul Anderson | Ben Finney <bignose@debian.org>
Attachment:
signature.asc
Description: PGP signature