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 4A2041771A for ; Tue, 28 Jul 2015 12:19:13 +0000 (UTC) Received: (qmail 71720 invoked by uid 500); 28 Jul 2015 12:19:13 -0000 Delivered-To: apmail-cloudstack-dev-archive@cloudstack.apache.org Received: (qmail 71664 invoked by uid 500); 28 Jul 2015 12:19:13 -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 71653 invoked by uid 99); 28 Jul 2015 12:19:12 -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, 28 Jul 2015 12:19:12 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 93540E00AA; Tue, 28 Jul 2015 12:19:12 +0000 (UTC) From: pdion891 To: dev@cloudstack.apache.org Reply-To: dev@cloudstack.apache.org References: In-Reply-To: Subject: [GitHub] cloudstack pull request: fix systemvm64template build, fix .deb pa... Content-Type: text/plain Message-Id: <20150728121912.93540E00AA@git1-us-west.apache.org> Date: Tue, 28 Jul 2015 12:19:12 +0000 (UTC) Github user pdion891 commented on the pull request: https://github.com/apache/cloudstack/pull/626#issuecomment-125581299 I will go ahead and apply this PR to fix builds, @rsafonseca can you create a PR with your line that does not look at line 22 ? @wilderrodrigues, I know! it's pretty weird, I'm under the impression the package dependency would have changed over the weekend on wheeze-upsteam ? Anyway, I guest you idea was to go on a more recent version of keepalived. Cheers, --- 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. ---