2013/3/14 Christian Berendt <berendt@b1-systems.de>:
I don't like that we have to do things, because there are requirement of the SUSE Cloud. And I don't like that we can't simply provide a newer libvirt package because a requirement of the SUSE Cloud is to not overlay existing packages in SLE. Also I don't like it to add patches to the packages in C:O only to workaround issues in the SUSE Cloud existing because of some requirements of the SUSE Cloud.
Hi, I generally agree. However, also generally, we should be nice to the underlying platform. Be it because of SUSE Cloud or because of Cloud:OpenStack:Grizzly. For the same reason we wouldn't put a linux 3.9.rc4 kernel into C:O:G just because it fixes one particular problem we have with grizzly on the platform. If there is a specific problem, we need to find a specific solution. The specific solution might very well be "well, its not worth spending the effort fixing it in the old version of libvirt", and then the specific solution is to replace libvirt with a newer release. I'm very much fine with that and I'm very happy that you're spending time on doing that and discussing it here. The part I have resentiments with is that without _understanding_ the issue going with a newer version. If you understood the issue (aka can point out the missing patch in the old libvirt package or give a document/testcase/reproducer/problem description) then I'm fine with following the resolution of doing a version upgrade. I just didn't have the impression that we have reached that point yet, but maybe I'M the one missing the background information. Could you please help me out here? Is there a bugzilla report or anything that sheds further light on the problem that you fixed with the upgrade? Thanks, Dirk -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org