在 2017年5月17日星期三 +08 上午9:18:42，Ben Finney 写道： > On 16-May-2017, Boyuan Yang wrote: > > * 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? Yes. There is a patch left from 2.6+dfsg debian/patches directory on collab- maint. Also there is an unmerged https://pagure.io/pagure/pull-request/2014. > > * 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? I'm not quite sure. The dh_auto_test has some different behaviour when compared with upstream "runtests.sh". More investigations are needed. > > > * 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? Upstream just released shiny new v2.15 so that would be unnecessary. There are some ongoing works to deal with dependency problems (such as python- bleach >= 2.0.0, see https://pagure.io/pagure/pull-request/2269) and make pagure suitable for Debian. However, we are still in lack of human power for testing and packaging. -- Boyuan Yang
Attachment:
signature.asc
Description: This is a digitally signed message part.