diff options
| author | Karel Kočí <cynerd@email.cz> | 2021-09-04 16:43:29 +0200 |
|---|---|---|
| committer | Karel Kočí <cynerd@email.cz> | 2021-09-04 16:43:29 +0200 |
| commit | 79ed6249ce3149eda1d895087c8665a41f6fb47e (patch) | |
| tree | fcd97da3473a5da157425f0b8beea946723b6b5c /dev-python/pyftdi | |
| parent | 0dedc589a05f16794e8a1228178c58aa22699de7 (diff) | |
| download | gentoo-personal-overlay-79ed6249ce3149eda1d895087c8665a41f6fb47e.tar.gz gentoo-personal-overlay-79ed6249ce3149eda1d895087c8665a41f6fb47e.tar.bz2 gentoo-personal-overlay-79ed6249ce3149eda1d895087c8665a41f6fb47e.zip | |
sys-boot/myinitramfs: revert changes
As it seems the issue is somewhere else. The lock is now in
/run/cryptsetup and /run is present. The code to include libgcc_s.so
does not work as there are two more levels to include and the biggest
issue is that it won't help anyway. I tested it by adding those files to
filesystem and chrooting to it. The error was same. I even copied whole
/usr and /lib and /lib64 and the error was same. This seems like there
is something rotten deep.
The root cause seems to be in the used algorithm. The default now is
argon2 but when I use pbkdf2 the issue is gone. The issue seems to be
with libargon2.so as it seems.
Diffstat (limited to 'dev-python/pyftdi')
0 files changed, 0 insertions, 0 deletions