Bug 363521 – sys-fs/cryptsetup-1.4.1 bump request

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Attila Jecs 2011-04-14 00:35:52 UTC]

cryptsetup 1.3.0 available
bump?

Reproducible: Always

Steps to Reproduce:
1. emerge sys-fs/cryptsetup -pv

Actual Results:  
[ebuild  N    ] sys-fs/cryptsetup-1.2.0-r1  USE="nls (-selinux) -static" 512 kB


Expected Results:  
[ebuild  N    ] sys-fs/cryptsetup-1.3.0  USE="nls (-selinux) -static" 512 kB

[Comment 1 Rafał Mużyło 2011-04-14 01:16:57 UTC]

Patience recommended.

[Comment 2 ScytheMan 2011-06-03 16:37:26 UTC]

1.3.1 has been released 

http://code.google.com/p/cryptsetup/wiki/Cryptsetup131

[Comment 3 ScytheMan 2011-10-22 23:59:30 UTC]

1.4.0_rc1

http://code.google.com/p/cryptsetup/wiki/Cryptsetup140

[Comment 4 Mike Auty (RETIRED) 2011-10-25 10:26:16 UTC]

cryptsetup 1.4.0_rc1 includes support for dm-crypt discard (along with the 3.1 linux kernel), so it might be worth getting to this when 1.4.0 goes stable...

[Comment 5 ScytheMan 2011-11-06 01:43:32 UTC]

1.4.0 final released

[Comment 6 matthias.grobarek 2011-11-07 15:07:06 UTC]

Just tried building cryptsetup 1.4.0 using the 1.2.0-r1 ebuild file (just renamed it). It compiles properly with or without the 'static' USE flag. cryptsetup 1.4.0 works on my system (which uses a LUKS partition for the root fs), also with the 'allow_discards' option. I consider this stable for my purposes.

[Comment 7 SpanKY 2011-11-13 04:18:15 UTC]

1.4.1 now in the tree

[Comment 8 Sergiy Borodych 2011-11-13 09:58:30 UTC]

make[1]: Leaving directory `/var/tmp/portage/sys-fs/cryptsetup-1.4.1/work/cryptsetup-1.4.1'
!!! newinitd: /usr/portage/sys-fs/cryptsetup/files/dmcrypt.initd does not exist
 * ERROR: sys-fs/cryptsetup-1.4.1 failed (install phase):

please fix it
maybe you mean here
/usr/portage/sys-fs/cryptsetup/files/dmcrypt.rc

[Comment 9 SpanKY 2011-11-13 18:52:47 UTC]

file new bugs for new issues in the future