Return-Path: X-Original-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 357C39126 for ; Thu, 6 Sep 2012 18:07:09 +0000 (UTC) Received: (qmail 26362 invoked by uid 500); 6 Sep 2012 18:07:08 -0000 Delivered-To: apmail-incubator-cloudstack-dev-archive@incubator.apache.org Received: (qmail 26315 invoked by uid 500); 6 Sep 2012 18:07:08 -0000 Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cloudstack-dev@incubator.apache.org Delivered-To: mailing list cloudstack-dev@incubator.apache.org Received: (qmail 26260 invoked by uid 99); 6 Sep 2012 18:07:08 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Sep 2012 18:07:08 +0000 Date: Fri, 7 Sep 2012 05:07:08 +1100 (NCT) From: "David Nalley (JIRA)" To: cloudstack-dev@incubator.apache.org Message-ID: <467011026.45674.1346954828827.JavaMail.jiratomcat@arcas> Subject: [jira] [Created] (CLOUDSTACK-31) xt_checksum kernel object (binary and license problems) is present in source tree MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 David Nalley created CLOUDSTACK-31: -------------------------------------- Summary: xt_checksum kernel object (binary and license problems) is present in source tree Key: CLOUDSTACK-31 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-31 Project: CloudStack Issue Type: Bug Components: Network Controller Affects Versions: pre-4.0.0 Reporter: David Nalley Priority: Blocker Fix For: 4.0.0 patches/systemvm/debian/xt_CHECKSUM.ko is a GPL-licensed kernel object, that is also a binary, both of which are verboten. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira