Gnome 2.30 *will* require udisks, and then, it will require a newer lvm2 version to become stable with it. On my setup, I am currently running the following: sys-fs/lvm2-2.02.67-r2 sys-fs/udev-151-r4 Feel free to add arches and stabilize the option you prefer when you like Thanks a lot Reproducible: Always
sys-fs/lvm2-2.02.67-r2 will be the stabilization target, just waiting on one bug first, and then probably another week to be closer to the normal 30 days. Not adding arches yet.
Thanks a lot
Can we proceed with this one? It would be nice to get udisks/upower to stable. Need arch's in CC also for bug 324507 and bug 327689.
Robin give us his ok on #gentoo-dev Arches, please test and mark stable
x86 stable
Stable on alpha.
No it's not. (For what it's worth, x86 here ... but this seems more like a bug or over site with documentation for upgrading encrypted volumes??) Requires baselayout-2 to run scripts. Also, using the updated =sys-fs/cryptsetup-1.1.2 version as it is required when upgrading to this version of lvm2, encrypted volumes fail to be able to be mounted. The basic error I get when trying to mount: # e2fsck -c /dev/mapper/crypt e2fsck 1.41.11 (14-Mar-2010) e2fsck: Superblock invalid, trying backup blocks... e2fsck: The ext2 superblock is corrupt while trying to open /dev/mapper/crypt The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> I have regressed back to =sys-fs/cryptsetup-1.0.6-r2 and =sys-fs/lvm2-2.02.56-r2 and the problem dissipated (or resolved).
You should then open separate bug reports for your issues and make them block this one. Thanks
(In reply to comment #7) > Also, using the updated =sys-fs/cryptsetup-1.1.2 version as it is required when > upgrading to this version of lvm2, encrypted volumes fail to be able to be > mounted. Please open a new bug. The crypt volumes on my laptop work fine with the new LVM.
I would rather see Gnome-3.0 stabilized (even though I use DWM) vs. opening a blocking bug. I use a crypt volume only every now and then. I can easily work around by using the older version, masking the recently stabilized lvm2/cryptsetup. Consider my above post FYI and don't be surprised to see other bug filings. ... might be an upstream issue.
rogerx: blocker or not, I need you to file a bug with all of the details so we can trace it. I think it shouldn't be a blocker for the moment, until we can confirm what's going on. arches: please proceed with stabilization for now, we just might need to stabilize newer cryptsetup soon as well.
Oops. Only posted e2fsck output above. But, still very similar error to stdout. As you wish... filing.
amd64 stable (bug 329991 shouldn't block this as talked with Robin)
> > arches: please proceed with stabilization for now, we just might need to > stabilize newer cryptsetup soon as well. > Arches: current crypsetup will fail to build if you stabilize this lvm2 version. So please stabilize lvm2 along with cryptsetup(bug 327689) else cryptsetup will break.
Marked ppc/ppc64 stable.
arm stable for version in bug #334087.
ia64/s390/sh/sparc stable
Er, so this bug is deprecated.
