Skip to content

Conversation

@unman
Copy link
Member

@unman unman commented Apr 10, 2022

@marmarek
Copy link
Member

Generally I like this change, but I worry about upgrade: if user modified the sources.list file (for example to enable testing updates), the new version will be saved in .dpkg-new, right? In that case, old file will be used, but the key in the old location will be gone. This will break installing any further updates.

Any ideas? Keep old keyring location (too) for the time being?

@DemiMarie
Copy link
Contributor

Generally I like this change, but I worry about upgrade: if user modified the sources.list file (for example to enable testing updates), the new version will be saved in .dpkg-new, right? In that case, old file will be used, but the key in the old location will be gone. This will break installing any further updates.

Any ideas? Keep old keyring location (too) for the time being?

What about doing the upgrade in two steps?

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.

Use signed-by= in sources.list files

3 participants