Package repository now available

[Fabian A. Santiago]

December 27, 2017 11:06 AM, "Fabian A. Santiago" <fsantiago at garbage-juice.com> wrote:

> December 27, 2017 10:53 AM, aki.tuomi at dovecot.fi wrote:
> 
>> Small amendment...
>> 
>> if you ran
>> 
>> gpg --export > /etc/apt/trusted.gpg.d/dovecot.gpg
>> 
>> please run
>> 
>> gpg --export ED409DA1 > /etc/apt/trusted.gpg.d/dovecot.gpg
>> 
>> Aki
>> 
>>> On December 27, 2017 at 5:00 PM aki.tuomi at dovecot.fi wrote:
>>> 
>>> Dovecot now has package repository for Debian, CentOS and Ubuntu available at
>>> https://repo.dovecot.org
>>> 
>>> Packages are provided for 2.3 series and forward. Please let us know if you run into any trouble
>>> with these.
>>> 
>>> ---
>>> Aki Tuomi
>>> Dovecot oy
>>> _______________________________________________
>>> Dovecot-news mailing list
>>> Dovecot-news at dovecot.org
>>> https://dovecot.org/mailman/listinfo/dovecot-news
> 
> so i received this (centos 7.4):
> 
> Retrieving key from https://repo.dovecot.org/DOVECOT-REPO-GPG
> Importing GPG key 0xED409DA1:
> Userid : "Dovecot Community Edition <dovecot-ce at dovecot.org>"
> Fingerprint: 2be7 4aab 3ee7 54df b9c8 0d33 18a3 48ae ed40 9da1
> From : https://repo.dovecot.org/DOVECOT-REPO-GPG
> Is this ok [y/N]: y
> warning: /var/cache/yum/x86_64/7/dovecot-2.3-latest/packages/dovecot-pgsql-2.3.0-2.x86_64.rpm:
> Header V3 DSA/SHA256 Signature, key ID eed949f0: NOKEY
> Retrieving key from https://repo.dovecot.org/DOVECOT-REPO-GPG
> 
> The GPG keys listed for the "RHEL 7 - x86_64" repository are already installed but they are not
> correct for this package.
> Check that the correct key URLs are configured for this repository.
> 
> Failing package is: 2:dovecot-pgsql-2.3.0-2.x86_64
> GPG Keys are configured as: https://repo.dovecot.org/DOVECOT-REPO-GPG
> 
> upgrading from dovecot 2.2.x.
> 
> is this related to what you just mentioned with the gpg key?
> 
> --
> 
> Thanks,
> 
> Fabian S.
> 
> OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC

probably not; i did a manual rpm --import of the key and still received same error. is there an issue with the package signatures and the available key not matching? 

--

Thanks,

Fabian S.

OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC