Jonas Meurer schrieb: > The problem here is, that nobody with the required skills steps in and > fixes the bugs. > The people who maintained the code in the past seem to be rather busy > with other things, and you should acknowledge that they did their job > voluntarily. I do acknowledge that. I didn't know the maintainers were inactive now, that is sad to hear. > So the real problem is, that cryptsetup becomes more and more popular, > while no new developers seem to be interested in participating. > > I have to admit that this applies to me as well. I maintain cryptsetup > in debian, but i've neither skills nor time to do upstream tasks on a > regular basis. I usually fix stuff myself if I can. A simple compile error, or little problems in userspace applications. But when it comes to kernel things like this, I simply don't have the knowledge. All I could find out is that the problem is most likely in the device-mapper, not in cryptsetup. > You could at least file bugreports against cryptsetup in your favourite > distribution. That documents the issue, and maybe the maintainer who is > responsible for the package cares enough to find a fix. That won't help. I AM the maintainer of cryptsetup in my favorite distribution and I am (co)maintaining the kernel package as well (when it comes to device-mapper related stuff, the bug is assigned to me). Until today, I feared that it was something in the Archlinux kernel that caused the problem, but now that I've found someone who had this problem on Debian, I know that is not the case. Without the knowledge to fix the kernel myself, with no patch available on the internet, with no idea what may cause the problem, my last resort is to turn to people who know _something_ about the topic. I was expecting to find these people on the dm-crypt mailing list. --------------------------------------------------------------------- dm-crypt mailing list - http://www.saout.de/misc/dm-crypt/ To unsubscribe, e-mail: dm-crypt-unsubscribe@xxxxxxxx For additional commands, e-mail: dm-crypt-help@xxxxxxxx
