-
-
Notifications
You must be signed in to change notification settings - Fork 372
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
Enable the ability to set a custom Codename when publishing #892
Conversation
While testing out Aptly, the `apt-get` client complains with the following error, since the `codename` was switched from the InRelease files that are baked out by Aptly: ``` E: Repository 'http://debianrepo.example.com/bionic testing InRelease' changed its 'Codename' value from '' to 'testing' ```
Codecov Report
@@ Coverage Diff @@
## master #892 +/- ##
==========================================
- Coverage 63.79% 63.78% -0.02%
==========================================
Files 54 54
Lines 6674 6682 +8
==========================================
+ Hits 4258 4262 +4
- Misses 1890 1893 +3
- Partials 526 527 +1
Continue to review full report at Codecov.
|
Hello @smira, is it possible to get this reviewed? Thanks for your time. |
Ubuntu 18.04 performs strict checking of the Codename and Label when performing an apt-get update. The snapshots published by aptly do not set these parameters in a way that apt-get likes. This change explicitly sets the codename and label based on the values from the upstream repo being mirrored. Note: this relies on a currently unmerged pull request/ aptly-dev/aptly#892 Change-Id: I011862dcf9efbb8b1f9757c65f3d58da49a496d7
* Update openstack-helm-images from branch 'master' - mini-mirror: Preserve codename and label Ubuntu 18.04 performs strict checking of the Codename and Label when performing an apt-get update. The snapshots published by aptly do not set these parameters in a way that apt-get likes. This change explicitly sets the codename and label based on the values from the upstream repo being mirrored. Note: this relies on a currently unmerged pull request/ aptly-dev/aptly#892 Change-Id: I011862dcf9efbb8b1f9757c65f3d58da49a496d7
I wanted to bump this - we are having the same issue. This pull request resolves it; is it possible to get this merged @smira ? |
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.
It looks good to me.
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.
Looks good to me!
@smstone if you are still interested in this change, would you mind rebasing and have a look at why the tests are failing now that we moved the new github actions pipeline 🎉
I will close this as there seems to be a lack of interest for this change, feel free to leave a comment if you want this reopened |
Description of the Change
This change will allow users to set a custom
Codename
in the release files when publishing.This PR is inspired/guided by #874
Why this change is important?
While testing out Aptly, our test
apt-get
clients were exiting with non-zero status sinceCodename
was changed in the release files that are baked out by Aptly:I attempted to update system tests / man pages, apologies if something was missed. I can also split these out into separate commits, if that is preferable.
Checklist
AUTHORS