https://bugzilla.novell.com/show_bug.cgi?id=737512 https://bugzilla.novell.com/show_bug.cgi?id=737512#c2 Christian Boltz changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |REOPENED CC| |aj@suse.com, | |suse-beta@cboltz.de Resolution|NORESPONSE | AssignedTo|bnc-team-screening@forge.pr |lnussel@suse.com |ovo.novell.com | Severity|Normal |Major --- Comment #2 from Christian Boltz 2012-03-09 14:01:34 CET --- (In reply to comment #1 by kk zhang):

Long time no response.So closed.Feel free to reopen it.Thanks.

I'm afraid you misunderstood the "NORESPONSE" resolution. It should only be used if the bugreporter fails to provide additionally requested information which makes it impossible to fix the bug. Typically this applies to a bug that was in NEEDINFO state for months. It is NOT meant for bugreports like this one which are not yet assigned to the correct package maintainer. For those bugreports, you have to - find out to which package they belong (which is quite easy in this case - rpm -qf'ing the filenames mentioned above give a clear hint to "cryptsetup".) - find out the maintainer of this package with osc maintainer openSUSE:Factory cryptsetup - reassign the bugreport to this person If you are unable to do this for whatever reason, please at least stop closing those reports with "NORESPONSE". And please go through the other bugreports you closed with NORESPONSE just because nobody moved them away from the screening team, reopen them and assign them to the package maintainer. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=737512 https://bugzilla.novell.com/show_bug.cgi?id=737512#c4 --- Comment #4 from Ludwig Nussel 2012-05-11 13:18:27 CEST --- ping! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=737512 https://bugzilla.novell.com/show_bug.cgi?id=737512#c6 --- Comment #6 from Ludwig Nussel 2012-05-21 17:15:49 CEST --- adding a key file argument changes the hashing behavior of cryptsetup which could break existing installations. cryptsetup reads from stdin just fine automatically. I just tried to reproduce but everything works fine for me: # tail -1 /etc/fstab /dev/mapper/secret /secret ext2 nofail 0 2 # cat /etc/crypttab secret /dev/vdb1 none keyscript=/root/bin/fff # cat /root/bin/fff echo 12345 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.