Home | Docs | Forums | Lists | Bugs | Planet | Store | GMN | Get Gentoo!
View Bug Activity | Format For Printing | XML | Clone This Bug
Requesting the arch teams to stabilize cryptsetup-0.1-r3. This is a minor change to fix Bug #120802 and has been in the tree for a month with no bugs.
Stable on ppc
stable on ppc64
Checking whether I can stabilize it for x86...
Works fine with current x86 stable device-mapper. Now checking with device-mapper 1.02.02...
Works fine with the (now stable) device-mapper 1.02.02. Stable for x86.
sparc stable.
bump, in particular for amd64
is it intentional that the ebuild doesn't die when the needed kernel configuration isn't present? >>> md5 src_uri ;-) cryptsetup-0.1.tar.bz2 * Determining the location of the kernel source code * Found kernel source directory: * /usr/src/linux * Found sources for kernel version: * 2.6.15-gentoo-r7 * Checking for dm-crypt support ... [ !! ] * cryptsetup requires dm-crypt support! * Please enable dm-crypt support in your kernel config, found at: * (for 2.6 kernels) * * Device Drivers * Multi-Device Support * Device mapper support * [*] Crypt Target Support * * and recompile your kernel if you want this package to work with this kernel >>> Unpacking source...
bleh, somebody please kill my mouse
yes its intentional. I got shouted at by people who wanted to compile it on one machine with different kernels to roll out to other machines etc etc. It doesn't NEED the kernel option to function hence its only a warning.
stabilize please amd, this is holding up other bugs now.
Stable on mips.
come on amd ....
stable on amd64 sorry for the delay!
alpha ... whats the hold up? If there is a problem then let me know, if not then please stabilize this ebuild ~3 months should be enough time.
alpha stable.
Benjamin, please close this bug, if you think it's done
finished