You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Anders Hammar (JIRA)" <ji...@apache.org> on 2010/05/17 11:58:41 UTC

[jira] Created: (GERONIMO-5309) Invalid signature for org.apache.geronimo.genesis:genesis:pom:1.2 at central

Invalid signature for  org.apache.geronimo.genesis:genesis:pom:1.2 at central
-----------------------------------------------------------------------------

                 Key: GERONIMO-5309
                 URL: https://issues.apache.org/jira/browse/GERONIMO-5309
             Project: Geronimo
          Issue Type: Bug
      Security Level: public (Regular issues)
            Reporter: Anders Hammar


The signature of org.apache.geronimo.genesis:genesis:pom:1.2 (http://repo1.maven.org/maven2/org/apache/geronimo/genesis/genesis/1.2/genesis-1.2.pom) at Maven central is invalid. This is most likely because that the signature att the Apache repo is invalid. Using signature procurement will then block this making, for example the JMS spec implementation of Geronimo not usable in Maven.

Suggested action:
1. Verify the pom at the Apache repo (against the one in svn)
2. Resign and deploy to the Apache repo
3. It should now be synced to central

You will most likely need help handling the repo in Apache's Nexus instance. Try contacting Brian Fox (Apache Maven PMC) and he should be able to help.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (GERONIMO-5309) Invalid signature for org.apache.geronimo.genesis:genesis:pom:1.2 at central

Posted by "Matt Hogstrom (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/GERONIMO-5309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12869682#action_12869682 ] 

Matt Hogstrom commented on GERONIMO-5309:
-----------------------------------------

Here are the list of artifacts in quesition:

genesis-1.2-site.xml                               31-Jul-2007 22:24                 757
genesis-1.2-site.xml.md5                           31-Jul-2007 22:24                  32
genesis-1.2-site.xml.sha1                          31-Jul-2007 22:24                  40
genesis-1.2.pom                                    31-Jul-2007 22:16               11097
genesis-1.2.pom.asc                                31-Jul-2007 22:24                 186
genesis-1.2.pom.asc.asc                            31-Jul-2007 22:24                 186
genesis-1.2.pom.asc.asc.md5                        31-Jul-2007 22:24                  32
genesis-1.2.pom.asc.asc.sha1                       31-Jul-2007 22:24                  40
genesis-1.2.pom.asc.md5                            31-Jul-2007 22:24                  32
genesis-1.2.pom.asc.sha1                           31-Jul-2007 22:24                  40
genesis-1.2.pom.md5                                31-Jul-2007 22:16                  32
genesis-1.2.pom.sha1                               31-Jul-2007 22:16                  40


It looks like the tool used to generate the signatures ran a little awry and signed signatures and basically didn't work correctly.  Also, I don't think these artifacts need to be signed.  I'll drop a note to Brian to ask for them to be removed.

> Invalid signature for  org.apache.geronimo.genesis:genesis:pom:1.2 at central
> -----------------------------------------------------------------------------
>
>                 Key: GERONIMO-5309
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-5309
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>            Reporter: Anders Hammar
>            Assignee: Matt Hogstrom
>
> The signature of org.apache.geronimo.genesis:genesis:pom:1.2 (http://repo1.maven.org/maven2/org/apache/geronimo/genesis/genesis/1.2/genesis-1.2.pom) at Maven central is invalid. This is most likely because that the signature att the Apache repo is invalid. Using signature procurement will then block this making, for example the JMS spec implementation of Geronimo not usable in Maven.
> Suggested action:
> 1. Verify the pom at the Apache repo (against the one in svn)
> 2. Resign and deploy to the Apache repo
> 3. It should now be synced to central
> You will most likely need help handling the repo in Apache's Nexus instance. Try contacting Brian Fox (Apache Maven PMC) and he should be able to help.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Assigned: (GERONIMO-5309) Invalid signature for org.apache.geronimo.genesis:genesis:pom:1.2 at central

Posted by "Matt Hogstrom (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/GERONIMO-5309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Hogstrom reassigned GERONIMO-5309:
---------------------------------------

    Assignee: Matt Hogstrom

> Invalid signature for  org.apache.geronimo.genesis:genesis:pom:1.2 at central
> -----------------------------------------------------------------------------
>
>                 Key: GERONIMO-5309
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-5309
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>            Reporter: Anders Hammar
>            Assignee: Matt Hogstrom
>
> The signature of org.apache.geronimo.genesis:genesis:pom:1.2 (http://repo1.maven.org/maven2/org/apache/geronimo/genesis/genesis/1.2/genesis-1.2.pom) at Maven central is invalid. This is most likely because that the signature att the Apache repo is invalid. Using signature procurement will then block this making, for example the JMS spec implementation of Geronimo not usable in Maven.
> Suggested action:
> 1. Verify the pom at the Apache repo (against the one in svn)
> 2. Resign and deploy to the Apache repo
> 3. It should now be synced to central
> You will most likely need help handling the repo in Apache's Nexus instance. Try contacting Brian Fox (Apache Maven PMC) and he should be able to help.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.