14.04.2014 04:26, Christian Balzer wrote: > On Sun, 13 Apr 2014 19:04:45 +0400 Michael Tokarev wrote: [] >> I just removed librbd support in qemu once again, because the same old >> issue - lack of library/symbol versioning - which prevented ceph from >> going into wheezy - is _still_ not fixed. Because once I uploaded rbd- >> enabled qemu, I received a new grave bugreport against qemu-system which >> tells me that running qemu-system binary results in dynamic linker not >> finding symbol rbd_aio_flush or some other. >> > Where is that NEW bug report? Would that be the OLD:
The new bugreport against qemu is #744364, which is the same as very old #680307 which started all this stuff. > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679686 > > you merged things with? I didn't merge anything with #679686. But that one is messy due to my actions, but is still valid. >> And now I need _really_ good reason to re-enable it again, because, well, >> guys, this is not funny at all. >> > Firstly I am running 1.7.0+dfsg-6 under Jessie and it works just fine. > As did source build versions with RBD enabled in the past, either by using > the inktank Ceph packages or since 0.72.x entered sid and then jessie. > > Secondly, Bug 679686 is about something that is not true in Jessie, as it > contains Ceph 0.72.2 (at this time). > That version is not in wheezy-backports yet and for that particular case > it would be true. > However for Jessie it most emphatically isn't. It is the still present issue which pops up any time someone ends up with half- updated system, for whatever reason, because dpkg/apt does not tell user about the correct dependencies. And this time, the new bugreport was filed against qemu right when I was waiting for the 2-day "urgent" package upload to migrate to testing, to fix an important security hole. The new bug prevents the testing migration. Thanks, /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
