-
Notifications
You must be signed in to change notification settings - Fork 365
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
Clean up metadata files on publish #1257
Comments
That would help with the consistency, indeed. Do you think an implementation which removes i.e. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When
aptly publish
is used e.g. with-skip-contents
or-skip-bz2
, it probably should make sure these files are actually removed if present on the disk.When this is important: For example, I needed to change the PGP signing key, and I regenerated the published repository by hand. Unfortunately, I forgot to pass the same options as usual, and created these extra files, which won’t be updated by our package building machinery later and will become stale. When apt uses these repositories, it may get confused or outright refuse to use them, especially if the PGP key changed after the files were mistakenly created. Of course, this is also the case when skip-contents is enabled after the repository is published for the first time.
The text was updated successfully, but these errors were encountered: