Description of problem: can't update lvm2 due to udisks? needing lower version. sudo yum update [sudo] password for xxxx Loaded plugins: auto-update-debuginfo, downloadonly, fastestmirror, langpacks, local, presto, protectbase, refresh-packagekit, remove-with- : leaves, security Adding en_IE to language list Loading mirror speeds from cached hostfile * fedora: mirror.sov.uk.goscomb.net * updates: mirror.ox.ac.uk * updates-testing: mirror.ox.ac.uk 0 packages excluded due to repository protections Setting up Update Process Resolving Dependencies --> Running transaction check ---> Package lvm2.x86_64 0:2.02.72-4.fc13 set to be updated --> Processing Dependency: liblvm2app.so.2.1()(64bit) for package: udisks-1.0.1-1.fc13.x86_64 --> Processing Dependency: liblvm2app.so.2.1(Base)(64bit) for package: udisks-1.0.1-1.fc13.x86_64 ---> Package lvm2-libs.x86_64 0:2.02.72-4.fc13 set to be updated --> Finished Dependency Resolution --> Running transaction check ---> Package lvm2-libs.x86_64 0:2.02.72-4.fc13 set to be updated --> Processing Dependency: lvm2-libs = 2.02.72-4.fc13 for package: lvm2-2.02.72-4.fc13.x86_64 --> Finished Dependency Resolution Packages skipped because of dependency problems: lvm2-2.02.72-4.fc13.x86_64 from updates-testing lvm2-libs-2.02.72-4.fc13.x86_64 from updates-testing
grrrrr. lvm2app API/ABI changed. two possible solutions - revert abi change in lvm2app - upgrade also udisks in F13 (which is only user of it)
David, is it possible to rebuild udisks in F13 with the lvm2app patch from rawhide? This lvm2 update fixes also https://bugzilla.redhat.com/CVE-2010-2526 so we should try to push update asap - and udisks rebuild seems to be easy (and it is already built for F14).
Waiting for rebuild of udisks per email conversation with David Zeuthen.
OK, I've committed the patch on f13/master http://pkgs.fedoraproject.org/gitweb/?p=udisks.git;a=shortlog;h=refs/heads/f13/master along with other changes (autoreconf, added BRs etc.). However, since the latest lvm2 packages are not in buildroot, the build fails with the expected error configure: error: lvm2 support requested but libraries not found since we want lvmapp >= 2.2 (pkgconfig version). See http://koji.fedoraproject.org/koji/taskinfo?taskID=2389658 for more information. To resolve this, please ask releng to put your latest lvm2 packages in the buildroot and then rebuild udisks. Thanks.
Ok - will do. Thanks for the update David!
*** Bug 622810 has been marked as a duplicate of this bug. ***
*** Bug 622816 has been marked as a duplicate of this bug. ***
Still not there yet but making progress. I filed this releng ticket and Bill Nottingham worked on it: https://fedorahosted.org/rel-eng/ticket/3946 I resubmitted the udisks build in koji but now it is failing because of a udev dependency on device mapper. So I guess I need another releng ticket - having issues getting to koji / fedroahosted though at the moment - not sure what is going on.
Ok new udisks build is now green, after Bill taggged new udev as well. Task id in koji was 2392140. This issue should be resolved though I'm told there may be another issue related to udev / lvm2 that peter (prajnoha) is investigating. We need to push lvm2, dm, udev, and udisks all as one update.
!!!IMPORTANT!!! Unfortunately, I've just found a very annoying bug in dm udev rules. It's related to a recent change where we make use of DM_UDEV_PRIMARY_SOURCE_FLAG to help support synthesized events (just like the one used at boot when calling "udevadm trigger --action=add" in udev init script). Having *old* dm rules+libdevmapper in initrd and having *new* dm rules+libdevmapper used in the system itself after pivot root causes problems. The DM_UDEV_PRIMARY_SOURCE_FLAG is not stored in udev db from initrd and so we can't identify the synthesized ADD events generated by udev init script. We try to ignore any spurious ADD events (except the ones where DM_UDEV_PRIMARY_SOURCE_FLAG is in udev db already and so we know the device has already been activated properly before). But without that flag and ignoring the event results in the symlinks for those devices to be removed... rc.sysinit script the can't find the symlinks and so it fails. I'll try to come up with a fix for this. (the obvious fix is to rebuild the initrd so new udev rules+libdevmapper will get there, but it I can't expect that to happen, of course...) Please, wait with the update!
I fixed the rules so there shouldn't be a problem with combining old and new libdevmapper/udev rules in initrd and system itself now: http://sourceware.org/git/?p=lvm2.git;a=commit;h=f3645e3f4ba4d3c9b42eebd9a9db0b050ba9a03b We need to attach this patch to the lvm2 build...
Dave, how it is with that update? I think compatibility patch is ready.
Sorry very late reply. My F13 boxes are sorted
Fixed in udisks update: http://lists.fedoraproject.org/pipermail/package-announce/2010-September/047498.html and lvm2 update: http://lists.fedoraproject.org/pipermail/package-announce/2010-September/047499.html