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

Clean up metadata files on publish #1257

Open
andrewshadura opened this issue Mar 14, 2024 · 1 comment
Open

Clean up metadata files on publish #1257

andrewshadura opened this issue Mar 14, 2024 · 1 comment
Assignees
Labels

Comments

@andrewshadura
Copy link
Contributor

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.

@neolynx neolynx self-assigned this Apr 17, 2024
@neolynx
Copy link
Member

neolynx commented Apr 17, 2024

That would help with the consistency, indeed. Do you think an implementation which removes i.e. *.bz2 if -skip-bz2 is provided would be enough ?

@neolynx neolynx added the bug label Aug 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants
@andrewshadura @neolynx and others