build for 1 is locally ok (gbp buildpackage --git-debian-branch=debian/unstable-swh --git-builder='sbuild -As --force-orig-source').
I'm heading towards the jenkins debian build pipeline to build and deploy it.
build for 2 is on hold as it depends on 1. to be deployed first.
has been built, packaged through our debian jenkins build machinery
i've locally something that built for unstable (using gpb like jenkins)
It's still on hold as i need to discuss further with olasd the change required for building external packages (with our jenkins tool chain) the right way.
It's still on hold as i need to discuss further with olasd the change required for building external packages (with our jenkins tool chain) the right way.
Discussion, toolchain [1], and manual updated accordingly [2]
I restarted the work on pytest-postgresql following the guidelines (initial work help though).
The joke is that pytest-postgresql built fine on unstable (after mirakuru packaging work).
Not for stretch backport though as another dependency was not there (port-for).
After packaging it, jenkins was finally able to build pytest-postgresql.
Antoine R. Dumontchanged title from debian package pytest fixture pytest-postgresql to debian: update toolchain/manual to allow build of external dependency (use pytest-postgresql need as a test)
changed title from debian package pytest fixture pytest-postgresql to debian: update toolchain/manual to allow build of external dependency (use pytest-postgresql need as a test)