Return-Path: X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 561CF974D for ; Fri, 24 Feb 2012 02:16:10 +0000 (UTC) Received: (qmail 69878 invoked by uid 500); 24 Feb 2012 02:16:10 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 69822 invoked by uid 500); 24 Feb 2012 02:16:10 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 69761 invoked by uid 99); 24 Feb 2012 02:16:09 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Feb 2012 02:16:09 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Feb 2012 02:16:08 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id E2617337116 for ; Fri, 24 Feb 2012 02:15:48 +0000 (UTC) Date: Fri, 24 Feb 2012 02:15:48 +0000 (UTC) From: "Hadoop QA (Commented) (JIRA)" To: common-issues@hadoop.apache.org Message-ID: <47312776.13388.1330049748928.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <151448256.13139.1330048308799.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (HADOOP-8109) Using the default rpms of hadoop, /usr/etc/hadoop symlink gets removed on upgrade MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HADOOP-8109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13215314#comment-13215314 ] Hadoop QA commented on HADOOP-8109: ----------------------------------- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12515865/HADOOP-8109.trunk.patch against trunk revision . +1 @author. The patch does not contain any @author tags. -1 tests included. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 eclipse:eclipse. The patch built with eclipse:eclipse. +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed unit tests in . +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/627//testReport/ Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/627//console This message is automatically generated. > Using the default rpms of hadoop, /usr/etc/hadoop symlink gets removed on upgrade > ---------------------------------------------------------------------------------- > > Key: HADOOP-8109 > URL: https://issues.apache.org/jira/browse/HADOOP-8109 > Project: Hadoop Common > Issue Type: Bug > Affects Versions: 0.23.0, 1.0.0 > Reporter: Hitesh Shah > Assignee: Hitesh Shah > Priority: Minor > Attachments: HADOOP-8109.trunk.patch > > > Given that for rpms, the pre-uninstall scripts for the older version run after the post-install scripts of the package being installed, the symlink created from /usr/etc/hadoop to /etc/hadoop gets deleted. This breaks running /usr/bin/hadoop without providing --config. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira