-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updates to Python 3.7 on Buster for package building for securedrop-client #89
Conversation
5e1d551
to
5352cb0
Compare
steps: | ||
- checkout | ||
- *installdeps | ||
- *fetchwheels | ||
- *clonesecuredropclient | ||
- *getlatestreleasedversion | ||
- *getnightlyversion |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
for background. we're building the latest release to make sure that we can build the current released version of each project with whatever logic is in this repo. can you expand on the motivation for this change?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ahh you said this in the PR description. how about we tag a new version of the client?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
heyyo, I prepared this over in freedomofpress/securedrop-client#625
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
let's add a buster build job, since we're going to be building on both stretch and buster until everyone is migrated over to buster (otherwise devs will stop getting nightlies), see e.g. 65cc0a7
@@ -4,7 +4,7 @@ | |||
dh $@ --with python-virtualenv | |||
|
|||
override_dh_virtualenv: | |||
dh_virtualenv --python /usr/bin/python3.5 --setuptools -S --index-url https://dev-bin.ops.securedrop.org/simple --requirements build-requirements.txt | |||
dh_virtualenv --python /usr/bin/python3.7 --setuptools -S --index-url https://dev-bin.ops.securedrop.org/simple --requirements build-requirements.txt |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this will break stretch builds, so let's make this python3, also there's another hardcoded python3.5 in securedrop-client.triggers
so we'll need to update there too
? |
freedomofpress/securedrop-client#616 is that PR. |
c363fb5
to
db287dd
Compare
I made these changes in a branch (only because I wanted to lazily test the build in freedomofpress/securedrop-client#625 on both platforms), next steps here are:
|
41943cc
to
acbad97
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK I think this is good to go, @kushaldas I'll let you review the changes I added here, but approving from my side
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
wait just kidding, we need to add the +stretch or +buster to the version strings
this branch in the LFS repo has debs I built and tested on stretch and buster respectively (pointing to them in case anyone wants to test). Once we add |
c2ffac4
to
d8aaaea
Compare
Will this PR resolve #88? |
yep it will resolve #88 |
I will review the changes. |
Yep this is ready for review now, the corresponding packages built using this logic are in freedomofpress/securedrop-apt-test#24 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
approving on the latest so that I'm not blocking merge
Released version of client can not be build as it is only for Debian 9.0. We can bring back stable release builds after next release of client.
d8aaaea
to
886914e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I did a rebase and everything worked as they should.
Resolves #88
To test the same, you will have to build the package in a Debian Buster VM or container.
For the CI, I have also updated the per PR build job to build nightly client, as the last release of the securedrop-client (0.0.9) can not be built on Buster (due to wheel dependency).
I am going to update the CI for
securedrop-client
in the next PR.