On Fri, Sep 27, 2013 at 01:05:32AM +0800, Thomas Goirand wrote: > On 09/26/2013 10:56 PM, Bill Allombert wrote: > > reopen 718822 > > thanks > > On Thu, Sep 26, 2013 at 01:58:16PM +0800, Thomas Goirand wrote: > >> No reply from the original submitter, so I'm closing the bug. > > > > Strange, I was sure I replied. > > > > I do not see why nova-compute-kvm need to depend on nova-compute in the > > first > > place, since it only contains a single config file. > > > Nothing will break if it is installed without nova-compute. > > If you really want, you can have nova-compute-kvm Recommends: nova-compute, > > but there is not need for a Depends. > > Yes, there's the need for a Depends:, as we really want to have at least > one hypervisor selected.
Hello Thomas, This is a rationale for nova-compute to Depends: nova-compute-kvm, yes, but not for the other way round, rather the opposite. If nova-compute-kvm were not Depending on nova-compute, then dpkg would ensure that nova-compute-kvm is configured before nova-compute. But with the circular dependency, it will happen that nova-compute is configured before nova-compute-kvm, so before any hypervisor is selected. The only other reverse dependency of nova-compute-kvm is openstack-compute-node which also depends on nova-compute anyway. So clearly setting nova-compute-kvm not to Depends: nova-compute will only make things more reliable. Cheers, -- Bill. <ballo...@debian.org> Imagine a large red swirl here. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
