Re: gpg errors NO_PUBKEY after aptitude update

To: debian-user@lists.debian.org
Subject: Re: gpg errors NO_PUBKEY after aptitude update
From: Lisi Reisz <lisi.reisz@gmail.com>
Date: Tue, 30 Sep 2014 11:24:28 +0100
Message-id: <[🔎] 201409301124.28411.lisi.reisz@gmail.com>
In-reply-to: <[🔎] CAHHq9NuqU6P-TWYagvmGvqe3t91d0ndGp_bB5ETWK+R5OK_3qg@mail.gmail.com>
References: <[🔎] CAHHq9NthK9GUpB6G_aeU8WpmHiUpk+EyhfQRSeWp4SxZs4ZRJQ@mail.gmail.com> <[🔎] CAHHq9NuqU6P-TWYagvmGvqe3t91d0ndGp_bB5ETWK+R5OK_3qg@mail.gmail.com>

On Tuesday 30 September 2014 11:14:52 Valery Mamonov wrote:
> Only "third-party" repositories are affected.

You have added the third party keys?

Lisi

Reply to:

Follow-Ups:
- Re: gpg errors NO_PUBKEY after aptitude update
  - From: Valery Mamonov <valerymamonov@gmail.com>

References:
- gpg errors NO_PUBKEY after aptitude update
  - From: Valery Mamonov <valerymamonov@gmail.com>
- Re: gpg errors NO_PUBKEY after aptitude update
  - From: Valery Mamonov <valerymamonov@gmail.com>

Prev by Date: Re: Let's have a vote!
Next by Date: Re: gpg errors NO_PUBKEY after aptitude update
Previous by thread: Re: gpg errors NO_PUBKEY after aptitude update
Next by thread: Re: gpg errors NO_PUBKEY after aptitude update
Index(es):
- Date
- Thread