Hello This will be needed in a near future for stabilizing Gnome 2.30, since it requires udisks, that needs a newer lvm2 (bug 324485) that needs: || ( >=sys-fs/udev-151-r2 =sys-fs/udev-146-r3 ) Then, since 149 is the current stable on, for example, amd64, would be nice to stabilize a newer udev version. For now, I am running 151-r4 without problems. Feel free to choose the version you prefer and add arches when you think it's ready Thanks a lot Reproducible: Always
Well, as I added STARTUP property to udev specifically for udev-151-r4 (see changelog and look for STARTUP in lvm2 rules), I think it could be better to stable udev-151-r4 but am not sure. In case still udev-151-r2 should be stabled, please check if it doesn't interact bad with new lvm2.
I think -r4 should be ok (I am using it without problems, but cannot check how does it work with lvm2 since I don't have any lvm partition :-( )
Are you ok with adding arches then?
Nothing blocking from me, +1 on stabilization.
Robin give us his ok on #gentoo-dev Arches, please test and mark stable
make --no-print-directory check-TESTS Must have root permissions to run properly. PASS: test/udev-test.pl ============= 1 test passed ============= Is this expected?
x86 stable Thanks Myckel, that's a good point. I don't think it should prevent stabilization though.
I get this : n22 /etc/portage # /etc/init.d/udev restart * Caching service dependencies ... [ ok ] * The udev init-script is written for baselayout-2! * Please do not use it with baselayout-1!. and now I'm wondering whether this message is wrong or whether baselayout-2 should be stabilized too .
(In reply to comment #8) > I get this : > > n22 /etc/portage # /etc/init.d/udev restart > * Caching service dependencies ... > [ ok ] > * The udev init-script is written for baselayout-2! > * Please do not use it with baselayout-1!. > > and now I'm wondering whether this message is wrong or whether baselayout-2 > should be stabilized too . > The message is right, and no, baselayout doesn't need to be stabilized for this. You simply shouldn't use that init script with baselayout-1... that's all.
Stable on alpha.
HPPA declines until a fixed glibc is keyworded (bug #294470).
amd64 stable
(In reply to comment #11) > HPPA declines until a fixed glibc is keyworded (bug #294470). >
It seems that #294470 doesn't solve all the issues we're having on hppa. We're running into a similar bug with inotify : #331119.
ppc64 stable
Marked ppc stable.
arm stable
ia64/m68k/s390/sh/sparc stable
Stable for HPPA and closing.