Needed for bug 254616
i'll need to review the open bug list to see what is/isnt a regression
Any update on this? Newer udev would be great for stable, and it appears this is all that is blocking.
bug #245266 is a regression from -r1. Adding to depends.
Btw. looking into cryptsetup-1.0.6-r2 ebuild, it just depends on >=sys-fs/udev-124, so where is written, why this blocks stabling newer udev?
(In reply to comment #4) > Btw. looking into cryptsetup-1.0.6-r2 ebuild, it just depends on > >=sys-fs/udev-124, so where is written, why this blocks stabling newer udev? > Both cryptsetup 1.0.5* and =1.0.6(-r1 and -r2 are okay) block udev: !>=sys-fs/udev-126
Ah, so I did look at the wrong ebuild, my bad. Do you expect to have the bugs blocking stabling solved in finite time? If not, I suggest you take cryptsetup-1.0.5-r1 and the udevsettle patch, put it into cryptsetup-1.0.5-r2 and stable that.
*poke* Any news? The stable version of udev is quite aged, and this will block anything newer for ever updating. 135, which already tried to go stable, had this as the only blocker.
bug 243216 was fixed and afaik, that is the only remaining blocker. Keywords: cryptsetup-1.0.5-r1: alpha amd64 arm hppa ia64 ppc ppc64 s390 sh sparc x86 Keywords: cryptsetup-1.0.6-r2: ~alpha ~amd64 ~arm ~hppa ~ia64 ~mips ~ppc ~ppc64 ~s390 ~sh ~sparc ~x86
x86 stable
Stable for HPPA.
ppc64 stable
amd64 stable
Both already stabilized/keyworded. Wonder why we were still on CC.
Ah, now I get it. This bug is confusing. Stabilized sys-fs/cryptsetup-1.0.6-r2 on alpha.
ppc stable
arm/ia64/s390/sh/sparc stable, closing
Closing