On Mon, Oct 13, 2014 at 03:54:38AM +0200, Christoph Anton Mitterer wrote: > Guido Günther <a...@sigxcpu.org> wrote: > >It would if these are RC bugs like security issues or daemon crashes. > > Don't we have packages that explicitly exclude such support or that > simply never went from sid to testing? > If compiling the VMware driver doesn't change the rest of libvirt, then > one could possibly simply place it in it's own package, add a note for > debian-security-support to be displayed that it is not security > supported (like webkit, chromium and others), add a bug that basically > says "don't move to testing until someone is willing to support this" > and perhaps add some lines to have reportbug told that people should not > report issues when they use the vmware module. > > > >I'm not planning to install ESX for that at home[1]. > Hell,... who would ^^ But unfortunately I have to work with their LRZ > (lrz.de) infrastructure at work - and Germany's leading super computing > centre (well perhaps together with our friends in Jülich) put most of > their bets on proprietary software in recent years - "it's simply > better" - isn't it ;-) ... and you have million dollar contracts with > companies to give you support, whose people usually have no clue either > D:
I feel your pain and building ESX from a seprate source package should be possible. It's just that I don't have the time and energy to support this. I'm lagging on literally dozens of open issues and so I don't want to add any proprietary stuff to that set. As I said: if anybody wants to pick it up, you're very welcome and I'm happy to put this under pkg-libvirt and help out here and there. Cheers, -- Guido -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
