hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vijay Bhat (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-9329) document native build dependencies in BUILDING.txt
Date Fri, 13 Mar 2015 23:13:39 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-9329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14361286#comment-14361286

Vijay Bhat commented on HADOOP-9329:

[~cmccabe] , I have a question - I'm trying to submit the documentation patch with the changes
you mentioned, but Jenkins seems to keep failing to apply the patch. The error I see is:

Your branch is behind 'origin/trunk' by 16 commits, and can be fast-forwarded.
  (use "git pull" to update your local branch)
First, rewinding head to replay your work on top of it...
Fast-forwarded trunk to 30c428a858c179645d6dc82b7027f6b7e871b439.
HADOOP-9329 patch is being downloaded at Wed Mar 11 19:32:38 UTC 2015 from
cp: cannot stat '/home/jenkins/buildSupport/lib/*': No such file or directory
The patch does not appear to apply with p0 to p2

It looks like Jenkins is applying the patch to the head of trunk even though this JIRA was
reported for branch-2.1.0-beta. I generated the patch as a diff against branch-2.1.0-beta.
Is this what I should be doing? Please let me know!

> document native build dependencies in BUILDING.txt
> --------------------------------------------------
>                 Key: HADOOP-9329
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9329
>             Project: Hadoop Common
>          Issue Type: Task
>          Components: documentation
>    Affects Versions: 2.1.0-beta
>            Reporter: Colin Patrick McCabe
>            Assignee: Vijay Bhat
>            Priority: Trivial
>         Attachments: HADOOP-9329.001.patch, HADOOP-9329.002.patch, HADOOP-9329.003.patch,
> {{BUILDING.txt}} describes {{-Pnative}}, but it does not specify what native libraries
are needed for the build.  We should address this.

This message was sent by Atlassian JIRA

View raw message