Hey Frank, Those packages have no dependencies on cloudstack-management, so that should be alright.
Is the cloud-daemonize only installed with the agent? I seem to remember that it was also required to install it with the management server? If that is the case we should move the obsolete to the cloudstack-common package. That way it is properly removed when either the agent or the management server is installed. Cheers, Hugo > -----Original Message----- > From: Frank Zhang [mailto:[email protected]] > Sent: dinsdag 13 augustus 2013 0:14 > To: Hugo Trippaers ([email protected]) > Cc: [email protected] > Subject: make cloud-daemonize obsolete using cloudstack-agent instead of > cloudstack-management > > Hi Hugo: > I have an issue needing to double confirm with you. > https://issues.apache.org/jira/browse/CLOUDSTACK-4149 > In short, we used to make old cloud-daemonize obsolete using > cloudstack-management that makes it unnecessarily installed during > upgrading KVM agent(cloud-agent) on host. > I make a simple fix that moves "Obsoletes: cloud-daemonize < 4.1.0" > to cloudstack-agent. Just want to double check with you there is no side- > effect. > Now upgrading old cloud-agent will only install cloudstack-agent and > cloudstack-common, I hope these two packages have no dependency on > cloudstack-management
