Please stable udev-124-r1. udev-124-r1 was commited today (03 Aug 2008), but contains only one small fux compared to udev-124 commited 12 Jun 2008. This is stopping udev from autoclosing cdrom drive when user tries to eject the media. So please test udev-124-r1 and mark stable.
Some of the changes between udev-119 and udev-124-r1: Improved error handling of udev-start.sh (called by baselayout to start udev). Warn about too old kernel. Load unix-socket module in case of very modular kernel. Fixed permissions of rfcomm and ttyACM devices. Added some more elog texts about persistent-net framework.
@Arch-teams: Please stable udev-124-r1.
mips doesn't have a stable package set anymore. Only unstable. Removing CC.
ia64/sparc stable
Stable for HPPA.
ppc64 stable
amd64 stable
Aug 9 02:41:26 home udevd[2172]: add_to_rules: unknown key 'WAIT_FOR' in /etc/udev/rules.d/60-persistent-storage-tape.rules:16 Aug 9 02:41:26 home udevd[2172]: add_to_rules: unknown key 'WAIT_FOR' in /etc/udev/rules.d/60-persistent-storage-tape.rules:16 Aug 9 02:41:28 home udevd version 124 started still stable ?
x86 stable
(In reply to comment #8) > Aug 9 02:41:26 home udevd[2172]: add_to_rules: unknown key 'WAIT_FOR' in > /etc/udev/rules.d/60-persistent-storage-tape.rules:16 > Aug 9 02:41:26 home udevd[2172]: add_to_rules: unknown key 'WAIT_FOR' in > /etc/udev/rules.d/60-persistent-storage-tape.rules:16 > Aug 9 02:41:28 home udevd version 124 started > It looks like the older udev from before the update (maybe udev-119) does not know the key WAIT_FOR and so prints a message. After that warning udev-124 gets started. So everything is fine. > > still stable ? > Sure. As the messages are not from udev-124. Only new idea here: before installing the new rules to the system: A) stop udevd or B) stop udevd automatically looking for rule updates.
Stable on alpha.
ppc stable
Closing, as all but mips added their stable keywords
