incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-1415) .deb packaging merge
Date Thu, 28 Feb 2013 11:33:13 GMT


ASF subversion and git services commented on CLOUDSTACK-1415:

Commit 6168f42c69e9af27865403444c35b885d15e399c in branch refs/heads/4.1packagetest from [~tsp]
[;h=6168f42 ]

Revert "CLOUDSTACK-1415: Debian & Ubuntu packaging work"

Testing by reverting

This reverts commit 78e8d184288fcde0a6ef6b6f126424407601e8ca.

> .deb packaging merge
> --------------------
>                 Key: CLOUDSTACK-1415
>                 URL:
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            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 delimitations moving
around resulting in a lot of file moves. The changes should be orthogonal to non-packaging
related developments and the target is both the 4.1 and master branches. Since the current
state of packaging is very broken, at least it will be an improvement.
> Concepts included in the diff:
> * the 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 Belgium.
> * 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 administrators
For more information on JIRA, see:

View raw message