well, no.
because eventually there will be a host that does not have keys in
/etc/apt/trusted.gpg/* that can verify bionic (when the 2018-archive
signing key is retired).
essentially all you'd be doing there is changing this the keyring
maintained here to be 'obsolete-signing-keys'.
Possibly the right thing to do would be to have a package called
'ubuntu-keyring-retired'. Then if that package got updated correctly
mfdiff and other things could just rely on the fact that the
combination of keyrings provided by 'ubuntu-keyring' and
'ubuntu-keyring-retired' would be able to verify all things.
well, no. trusted. gpg/* that can verify bionic (when the 2018-archive
because eventually there will be a host that does not have keys in
/etc/apt/
signing key is retired).
essentially all you'd be doing there is changing this the keyring signing- keys'.
maintained here to be 'obsolete-
Possibly the right thing to do would be to have a package called keyring- retired' . Then if that package got updated correctly keyring- retired' would be able to verify all things.
'ubuntu-
mfdiff and other things could just rely on the fact that the
combination of keyrings provided by 'ubuntu-keyring' and
'ubuntu-
On Tue, Dec 11, 2018 at 3:15 PM Dan Watkins trusted. gpg* in to the cache and then adding this keyring.gpg to cache_dir/ etc/apt/ trusted. gpg.d save us from having to do the maintenance in future? /code.launchpad .net/~smoser/ vmbuilder/ mfdiff- apt-key- transition/ +merge/ 313797
<email address hidden> wrote:
>
> Would copying /etc/apt/
> --
> https:/
> You are the owner of lp:~smoser/vmbuilder/mfdiff-apt-key-transition.