Code review comment for lp://qastaging/~smoser/vmbuilder/mfdiff-apt-key-transition

Revision history for this message
Scott Moser (smoser) wrote :

of course. At said later date, you can just add a key to the keyring
and commit it.

The change that is in place currently relies on the host to provide
the keys, and quite simply no host will *ever* provide historical and
future keys in /etc/apt/trusted.gpg.d .

So yes, this change does add maintenance on the order of once per N
years (N=6?) that is in some cases provided "for free" by using the
content from ubuntu-keyring.

On Tue, Dec 11, 2018 at 2:40 PM Dan Watkins
<email address hidden> wrote:
>
> My concern is that, unless I'm misunderstanding something, this change effectively freezes the keyring we use to xenial's keyring. So at some point in the future, this keyring will become outdated regardless of the underlying release (so I won't be able to just use bionic).
>
> Is my understanding off?
> --
> https://code.launchpad.net/~smoser/vmbuilder/mfdiff-apt-key-transition/+merge/313797
> You are the owner of lp:~smoser/vmbuilder/mfdiff-apt-key-transition.

« Back to merge proposal