Skip to content
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

Closed
wants to merge 4 commits into from

Conversation

smstone
Copy link
Contributor

@smstone smstone commented Oct 30, 2019

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 since Codename was changed in the release files that are baked out by Aptly:

E: Repository 'http://debianrepo.example.com/bionic unstable InRelease' changed its 'Codename' value from '' to 'unstable'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.

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

  • unit-test added (if change is algorithm)
  • functional test added/updated (if change is functional)
  • man page updated (if applicable)
  • bash completion updated (if applicable)
  • documentation updated
  • author name in AUTHORS

Steven Stone added 2 commits October 30, 2019 19:04
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
Copy link

codecov bot commented Oct 31, 2019

Codecov Report

Merging #892 (b7211fe) into master (3266aa3) will decrease coverage by 0.01%.
The diff coverage is 71.42%.

❗ Current head b7211fe differs from pull request most recent head 453e712. Consider uploading reports for the commit 453e712 to get more accurate results
Impacted file tree graph

@@            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     
Impacted Files Coverage Δ
deb/publish.go 62.93% <55.55%> (-0.16%) ⬇️
pgp/gnupg_finder.go 68.65% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f93bc6e...453e712. Read the comment docs.

@smstone
Copy link
Contributor Author

smstone commented Nov 1, 2019

Hello @smira, is it possible to get this reviewed? Thanks for your time.

openstack-gerrit pushed a commit to openstack/openstack-helm-images that referenced this pull request Dec 27, 2019
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
openstack-gerrit pushed a commit to openstack/openstack that referenced this pull request Dec 27, 2019
* 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
@mattmceuen
Copy link

I wanted to bump this - we are having the same issue. This pull request resolves it; is it possible to get this merged @smira ?

Copy link
Contributor

@lbolla lbolla left a 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.

@lbolla lbolla self-assigned this Jan 28, 2022
Copy link
Contributor

@randombenj randombenj left a 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 🎉

@randombenj
Copy link
Contributor

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

@randombenj randombenj closed this Apr 13, 2022
@jbayfield jbayfield mentioned this pull request Aug 18, 2022
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants