Should you describe the problem? What did you do? What happened? What do you expect to occur?
Thanks. []'s kretcheu :x On Mon, 20 Apr 2020 18:14:53 +0200 strunz <strunzenol...@gmx.de> wrote: > Package: bruteforce-luks > Version: 1.3.1-1+b1 > Followup-For: Bug #958334 > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate *** > > * What led up to the situation? > * What exactly did you do (or not do) that was effective (or > ineffective)? > * What was the outcome of this action? > * What outcome did you expect instead? > > *** End of the template - remove these template lines *** > > > > -- System Information: > Debian Release: 10.3 > APT prefers stable-updates > APT policy: (500, 'stable-updates'), (500, 'stable') > Architecture: amd64 (x86_64) > > Kernel: Linux 4.19.0-8-amd64 (SMP w/4 CPU cores) > Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE > Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages bruteforce-luks depends on: > ii libc6 2.28-10 > ii libcryptsetup12 2:2.1.0-5+deb10u2 > > bruteforce-luks recommends no packages. > > bruteforce-luks suggests no packages. > > -- no debconf information > >
