[
https://issues.apache.org/jira/browse/CLOUDSTACK-580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Brockmeier resolved CLOUDSTACK-580.
---------------------------------------
Resolution: Fixed
Sudha,
David made changes to the debian/rules and changelog files, which seems to have
fixed this. Please let us know if you see any other versioning issues.
> Packages are named with 4.0 with 4.0.1 build
> ---------------------------------------------
>
> Key: CLOUDSTACK-580
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-580
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Install and Setup
> Affects Versions: 4.0.1
> Reporter: Sailaja Mada
> Assignee: Joe Brockmeier
> Priority: Blocker
> Fix For: 4.0.1
>
>
> Steps:
> Tried to use Ubutnu build available @
> http://jenkins.cloudstack.org/job/build-4.0.1-nonoss-ubuntu/lastSuccessfulBuild/artifact/CloudStack-non-OSS-4.0.1-1.tar.bz2
> .
> Cloudstack packages are built with 4.0.0 version name. These has to be named
> with 4.0.1 to do upgrade from 4.0 to 4.0.1.
> root@asf401:~# cd CloudStack-non-OSS-4.0.1-1/
> root@asf401:~/CloudStack-non-OSS-4.0.1-1# ls
> cloud-agent_4.0.0-incubating_amd64.deb
> cloud-cli_4.0.0-incubating_amd64.deb
> cloud-deps_4.0.0-incubating_amd64.deb
> cloud-setup_4.0.0-incubating_amd64.deb install.sh
> cloud-agent-deps_4.0.0-incubating_amd64.deb
> cloud-client_4.0.0-incubating_amd64.deb
> cloud-python_4.0.0-incubating_amd64.deb
> cloud-system-iso_4.0.0-incubating_amd64.deb Packages.gz
> cloud-agent-libs_4.0.0-incubating_amd64.deb
> cloud-client-ui_4.0.0-incubating_amd64.deb
> cloud-scripts_4.0.0-incubating_amd64.deb
> cloud-usage_4.0.0-incubating_amd64.deb
> cloud-awsapi_4.0.0-incubating_amd64.deb
> cloud-core_4.0.0-incubating_amd64.deb
> cloud-server_4.0.0-incubating_amd64.deb
> cloud-utils_4.0.0-incubating_amd64.deb
> root@asf401:~/CloudStack-non-OSS-4.0.1-1#
--
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
