-
Notifications
You must be signed in to change notification settings - Fork 687
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
Use cron-apt instead of apt upgrade molecule upgrade testing scenario #5214
Conversation
This is required if local grsecurity metapackages are present locally
I am testing this one. |
@emkll
|
@kushaldas has made a commitment to do continued (4 hour) time-boxed worked on this PR, w/ goal to resolve above issue & others encountered in testing, as part of 5/6-5/20 sprint. |
Deferring from the 5/20-6/3 sprint in favor of another improvement we're hoping to land to ease QA burden, #4216. |
Closing as we are considering unattended-upgrades as we migrate to Focal #5295 |
Status
Work in progress
The challenge here will be mostly to deal with packages on the apt server that are not tracked locally: the kernel images, tor packages, and now ossec dependencies.
For these reasons, introduced a commit to append apt-test.freedom.press to
security.list
prior to running cron-apt, to ensure kernel images referred to my the metapackage are pulled in during the upgrade.Feedback is welcome, as I am not sure this is the best approach (though it seems like an easy/quick fix that will help prevent future regressions when it comes to apt dependencies).
Description of Changes
Fixes #4659
Changes proposed in this pull request:
Testing
Local packages
make upgrade-start
upgrade-test-local
completes successfullyApt-test packages
make upgrade-qa-start
make upgrade-test-qa
Deployment
Test only
Checklist
If you made non-trivial code changes: