You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Olaf Flebbe (JIRA)" <ji...@apache.org> on 2015/02/17 20:48:11 UTC

[jira] [Commented] (BIGTOP-1677) Tez packaging is still failing

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

Olaf Flebbe commented on BIGTOP-1677:
-------------------------------------

+1 : Yes indeed somehow the wrong version of the patch has been applied to git

> Tez packaging is still failing
> ------------------------------
>
>                 Key: BIGTOP-1677
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-1677
>             Project: Bigtop
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 0.8.0
>            Reporter: Evans Ye
>            Assignee: Evans Ye
>            Priority: Critical
>             Fix For: 0.9.0
>
>         Attachments: BIGTOP-1677.1.patch
>
>
> The tez rpm can not be built. After some self hacks I finally figured out the root cause:
> BIGTOP-1179 commit is weird. The commit message shows that it was [authored on 27 Nov 2014|https://github.com/apache/bigtop/commit/f506701c8e8cd1b9e596c3f728996c988705e7d0], which should be an old patch targeted on 0.5.2 instead of the new one authored by [~oflebbe]. The wired thing is that the tez version of that commit is 0.6.0, which is new, but the code in that commit looked the same as the old patch submitted on 27 Nov 2014.
> Anyhow, we need to sync up the code to the final reviewed version in BIGTOP-1179.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)