Bug#691784: [Pkg-libvirt-maintainers] Bug#691784: [virt-manager] make spice optional (on !linux-{i386, amd64})

2013-09-26 Thread Hilko Bengen
* Guido Günther: >> Why is spice only available for amd64 and i386 in the first place? I >> have a vague recollection about x86-only assembly language snippets >> that reeked of micro-optimization -- is that still the problem? > > Yes, for locking primitives I think, Lets better ask the maintainer

Bug#691784: [Pkg-libvirt-maintainers] Bug#691784: [virt-manager] make spice optional (on !linux-{i386, amd64})

2013-09-23 Thread Guido Günther
On Fri, Sep 20, 2013 at 12:17:53PM +0200, Hilko Bengen wrote: > * Guido Günther: > > >> Well, what about this then: > >> > >> Subject: [PATCH] spice is only available on i386 and amd64 > >> > >> so don't depend on it on other architectures > > > > ...won't work since it's arch all - sorry for th

Bug#691784: [Pkg-libvirt-maintainers] Bug#691784: [virt-manager] make spice optional (on !linux-{i386, amd64})

2013-09-20 Thread Hilko Bengen
* Guido Günther: >> Well, what about this then: >> >> Subject: [PATCH] spice is only available on i386 and amd64 >> >> so don't depend on it on other architectures > > ...won't work since it's arch all - sorry for the noise. We'll use the > recommends then. > Cheers, > -- Guido Why is spice on

Bug#691784: [virt-manager] make spice optional (on !linux-{i386, amd64})

2013-09-20 Thread Guido Günther
On Fri, Sep 20, 2013 at 11:16:37AM +0200, Guido Günther wrote: > On Wed, Sep 18, 2013 at 06:30:09PM -0700, Vagrant Cascadian wrote: > > On Tue, Sep 03, 2013 at 10:44:08PM +0200, Guido Günther wrote: > > > On Tue, Sep 03, 2013 at 01:18:39PM -0700, Vagrant Cascadian wrote: > > > > Would it be feasibl

Bug#691784: [virt-manager] make spice optional (on !linux-{i386, amd64})

2013-09-20 Thread Guido Günther
On Wed, Sep 18, 2013 at 06:30:09PM -0700, Vagrant Cascadian wrote: > On Tue, Sep 03, 2013 at 10:44:08PM +0200, Guido Günther wrote: > > On Tue, Sep 03, 2013 at 01:18:39PM -0700, Vagrant Cascadian wrote: > > > Would it be feasible to upload this fix to wheezy-proposed-updates, since > > > the > > >

Bug#691784: [virt-manager] make spice optional (on !linux-{i386, amd64})

2013-09-18 Thread Vagrant Cascadian
On Tue, Sep 03, 2013 at 10:44:08PM +0200, Guido Günther wrote: > On Tue, Sep 03, 2013 at 01:18:39PM -0700, Vagrant Cascadian wrote: > > Would it be feasible to upload this fix to wheezy-proposed-updates, since > > the > > package is uninstallable on non-x86 arches? Is it a simple change in the > >

Bug#691784: [Pkg-libvirt-maintainers] Bug#691784: [virt-manager] make spice optional (on !linux-{i386, amd64})

2013-09-03 Thread Guido Günther
On Tue, Sep 03, 2013 at 01:18:39PM -0700, Vagrant Cascadian wrote: > Would it be feasible to upload this fix to wheezy-proposed-updates, since the > package is uninstallable on non-x86 arches? Is it a simple change in the > Depends/Recommends, or does it require code changes that would be too invas

Bug#691784: [virt-manager] make spice optional (on !linux-{i386,amd64})

2013-09-03 Thread Vagrant Cascadian
Would it be feasible to upload this fix to wheezy-proposed-updates, since the package is uninstallable on non-x86 arches? Is it a simple change in the Depends/Recommends, or does it require code changes that would be too invasive for wheezy? Thanks for maintaining virt-manager! live well, vagra

Bug#691784: [virt-manager] make spice optional (on !linux-{i386,amd64})

2012-10-29 Thread Christoph Egger
Package: virt-manager Version: 0.9.1-4 Severity: wishlist Hi! I have virt-manager working here perfectly fine on kfreebsd-amd64 after removing the hard dependency on python-spice-client-gtk which is uninstallable on architecutres other than linux-{amd64,i386}. Would be cool to relax the depende