Return-Path: X-Original-To: apmail-cloudstack-dev-archive@www.apache.org Delivered-To: apmail-cloudstack-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A3E7619BB4 for ; Tue, 26 Apr 2016 16:00:35 +0000 (UTC) Received: (qmail 86247 invoked by uid 500); 26 Apr 2016 16:00:35 -0000 Delivered-To: apmail-cloudstack-dev-archive@cloudstack.apache.org Received: (qmail 86194 invoked by uid 500); 26 Apr 2016 16:00:35 -0000 Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list dev@cloudstack.apache.org Received: (qmail 86182 invoked by uid 99); 26 Apr 2016 16:00:34 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Apr 2016 16:00:34 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 82537DFF93; Tue, 26 Apr 2016 16:00:34 +0000 (UTC) From: swill To: dev@cloudstack.apache.org Reply-To: dev@cloudstack.apache.org References: In-Reply-To: Subject: [GitHub] cloudstack pull request: CLOUDSTACK-9289:Automation for feature de... Content-Type: text/plain Message-Id: <20160426160034.82537DFF93@git1-us-west.apache.org> Date: Tue, 26 Apr 2016 16:00:34 +0000 (UTC) Github user swill commented on the pull request: https://github.com/apache/cloudstack/pull/1417#issuecomment-214793885 My CI runs the following command after it builds ACS, so it **should** be using an upgraded Marvin, but I did see some messages about `--allow-external` being deprecated, so I will review this in my setup. Thanks... `pip install --upgrade tools/marvin/dist/Marvin-*.tar.gz --allow-external mysql-connector-python` --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastructure@apache.org or file a JIRA ticket with INFRA. ---