 |
Sounds reasonable. I'll have to add that to the automated repository generation process, so it might not be as easy as you think, but I'll see what I can do. |
|
|
right now, we're creating the Release.key with "--export --armor --output Release.key", so I guess you just need the key without the ASCII-armor. I can add another export using "--export --output Release.gpg", but I wonder how we should name the file. Release.gpg doesn't really cut it, as context is lost when you drop it into /etc/apt/trusted.gpg.d/ Then we could probably do bareos.gpg, however, during upgrade or testing you may want to have multiple gpg keys installed at once (i.e. for the current version and the version you're upgrading to). Does it make sense to have files like "bareos-<keyid>.gpg"? Or should we just provide a bareos.gpg that contains all our keys (I don't think that is a great idea, because you would trust older keys, too)? Any thoughts on this? |
|
|
In the meantime we overhauled repository setup and now provide a script that does it. Does your original issue still exist with the current repositories, or did we already fix your problem? |
|
|
As there was no feedback, I guess this problem doesn't exist with the newer repository format anymore. |
- Anonymous
