Ubuntu/devel#303
Conversation
|
Where are we keeping the list of cherry picks? I wonder if we should have that as a file in the release branch. Otherwise someone repeating your steps might get that wrong? |
|
OK. I've reproduced your branch with: |
|
ERROR: Failure: ImportError (No module named 'pytest') Do we need a debian dep updated here? |
4c614d3 to
74995dc
Compare
We determined that Travis CI doesn't apply patches from debian/patches directory when determining build-deps, so our cherry-picked unit tests that import pytest can't find the pytest because we also have another cherry-pick which adds pytest to the test-requirements.txt, but that patch it not yet applied by |
|
Just added a final cherry-pick for PR #306. And added steps which manually add another quilt patch which can drop netbsd and openbsd from the tests/unittests/test_render_cloudcfg.py because that render support is only present in upstream until our next |
24746d0 to
5cb4246
Compare
LP: #1866930
LP: #1867029
LP: #1868327
LP: #1868232
|
OK. I can reproduce your branch, I've source built and sbuild the output successfully. +1 |
This branch is created for release of 3 feature/bug fixes into focal.
In order to release, we need to re-apply the already released cherry-pick for ec2 full networking because we droppped to fix daily recipe builds. Then we add our other new cherry-picks to that list for this second cherry pick release.
We can't use
new-upstream-snapshot --update-patches-onlybecause that presupposes that our next release will be performing a full new-upstream-snapshot, which is untrue during feature freeze.Instead we manually perform the following: