Guido Günther writes:
> On Tue, May 19, 2009 at 08:48:00AM +1200, Paul Collins wrote:
>> > It checks for it to get the binary paths.
>> I'm sorry, but that's really silly. Why doesn't it build-dep on kvm,
>> for example, to make sure it still lives in /usr/bin/kvm?
> It checks for several (iscsi
On Tue, May 19, 2009 at 08:48:00AM +1200, Paul Collins wrote:
> > It checks for it to get the binary paths.
>
> I'm sorry, but that's really silly. Why doesn't it build-dep on kvm,
> for example, to make sure it still lives in /usr/bin/kvm?
It checks for several (iscsiadm, parted, ...) but not al
> It checks for it to get the binary paths.
I'm sorry, but that's really silly. Why doesn't it build-dep on kvm,
for example, to make sure it still lives in /usr/bin/kvm?
> A package not being installable is a bad excuse to remove the build-dep.
It's not so much an excuse to remove the build-de
> It checks for it to get the binary paths.
I'm sorry, but that's really silly. Why doesn't it build-dep on kvm,
for example, to make sure it still lives in /usr/bin/kvm?
> A package not being installable is a bad excuse to remove the build-dep.
It's not so much an excuse to remove the build-de
Package: libvirt
Version: 0.6.3-2
This package checks for iscsiadm at build-time, but makes no attempt to
ensure it is available at runtime. This seems backwards to me, and with
open-iscsi being currently uninstallable on vanilla systems (#529280)
right now it is challenging to rebuild libvirt on
5 matches
Mail list logo
