You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@marmotta.apache.org by "Sergio Fernández (JIRA)" <ji...@apache.org> on 2014/04/10 09:44:15 UTC

[jira] [Updated] (MARMOTTA-485) Signatures are not automatically generated for ldpath tarballs

     [ https://issues.apache.org/jira/browse/MARMOTTA-485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sergio Fernández updated MARMOTTA-485:
--------------------------------------

    Summary: Signatures are not automatically generated for ldpath tarballs  (was: Signatures are not automatically generated for ldpath binary tarballs)

> Signatures are not automatically generated for ldpath tarballs
> --------------------------------------------------------------
>
>                 Key: MARMOTTA-485
>                 URL: https://issues.apache.org/jira/browse/MARMOTTA-485
>             Project: Marmotta
>          Issue Type: Bug
>          Components: Build Environment
>    Affects Versions: 3.2.0
>            Reporter: Sergio Fernández
>            Assignee: Jakob Frank
>            Priority: Critical
>              Labels: gpg, maven
>             Fix For: 3.3
>
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> Checking the 3.2.0 release we have realized that the work performed for solving MARMOTTA-339 did not completely solved the issue. It looks that detaching those binaries for the assembly makes them not eligible for signing.
> The quick fix for now is to manually generate those signatures, see r5011 at dist.apache.org 



--
This message was sent by Atlassian JIRA
(v6.2#6252)