infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Ivanov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-16420) Apache Ignite Bintray repositories
Date Sat, 28 Apr 2018 06:36:00 GMT

    [ https://issues.apache.org/jira/browse/INFRA-16420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16457395#comment-16457395
] 

Peter Ivanov commented on INFRA-16420:
--------------------------------------

That's not the thing we require.
We do not want to sign packages themselves (they are signed before upload), we want to have
uploaded GPG key for the whole repository (and not the user key, but organization's one -
apache) so that METADATA of the repositories was signed properly.

> Apache Ignite Bintray repositories
> ----------------------------------
>
>                 Key: INFRA-16420
>                 URL: https://issues.apache.org/jira/browse/INFRA-16420
>             Project: Infrastructure
>          Issue Type: Improvement
>          Components: Other/Misc
>            Reporter: Peter Ivanov
>            Assignee: Chris Thistlethwaite
>            Priority: Major
>
> After INFRA-16400 everything is back, but now we have signing issues.
> Does ignite-rpm and ignite-deb repositories configured for autosign and if the are --
can they autosign with Organization Key?
> Currently adding ignite-deb to list of repositories and running "apt update" fails with
"E: The repository 'https://apache.bintray.com/ignite-deb apache-ignite Release' is not signed."



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message