Return-Path: X-Original-To: apmail-incubator-cloudstack-issues-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-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 56BF4E7BC for ; Sun, 10 Mar 2013 13:39:14 +0000 (UTC) Received: (qmail 93358 invoked by uid 500); 10 Mar 2013 13:39:14 -0000 Delivered-To: apmail-incubator-cloudstack-issues-archive@incubator.apache.org Received: (qmail 93251 invoked by uid 500); 10 Mar 2013 13:39:13 -0000 Mailing-List: contact cloudstack-issues-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-issues@incubator.apache.org Received: (qmail 93227 invoked by uid 99); 10 Mar 2013 13:39:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 10 Mar 2013 13:39:13 +0000 Date: Sun, 10 Mar 2013 13:39:13 +0000 (UTC) From: =?utf-8?Q?Youri_Bonnaff=C3=A9_=28JIRA=29?= To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CLOUDSTACK-1415) .deb packaging merge MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CLOUDSTACK-1415?page=3Dcom.atla= ssian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId= =3D13598250#comment-13598250 ]=20 Youri Bonnaff=C3=A9 commented on CLOUDSTACK-1415: -------------------------------------------- Ok, I encountered several issues, if there is work in progress I will just = write down the issues I had to help people already working on it. - The mysql jdbc driver was missing, I added libmysql-java as a dependency = for cloudstack-management=20 - The classpath.conf.in file is using "build-classpath" I don't know where = it is coming from but I had to tweak the classpath to include jars from /us= r/share/java and /usr/share/cloudstack/management/lib/lib to make it work - in cloud-management.in MSENVIRON is replaced by /usr/share/cloud/.... whe= re now it seems that /usr/share/cloudstack is used - if the user does not exist, the .ssh folder is non existing and the ssh k= eys are not created - many errors with log folders/file access (permissions, non existing) - had to add setup folder to folder so scripts (db upgrade sql scripts) can= be found =20 > .deb packaging merge > -------------------- > > Key: CLOUDSTACK-1415 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-141= 5 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the defa= ult.)=20 > Reporter: Noa Resare > Assignee: Noa Resare > > This ticket tracks the merge of the packaging work that me and [~widodh] = has been working on in a separate branch. > The diff is kind of large, but most of the lines are the package delimita= tions moving around resulting in a lot of file moves. The changes should be= orthogonal to non-packaging related developments and the target is both th= e 4.1 and master branches. Since the current state of packaging is very bro= ken, at least it will be an improvement. > Concepts included in the diff: > * the replace.properties location used by maven is parameterized to allow= for a build that does not modify the currently git tracked files > * package naming is updated along the lines of what was discussed on the = -dev mailing list and between committers at the Build a Cloud Day in Belgiu= m. > * package version pattern is updated (since we redo all package names, we= might as well drop the epoch) > This commit is not very well tested, and most likely broken in a few ways= , but since should be pretty safe regression-wise and it is a good starting= point to get to a broader user base for the last fixes to 4.1 packaging. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrato= rs For more information on JIRA, see: http://www.atlassian.com/software/jira