Hi!
On Wed, 2023-03-08 at 14:26:13 +0100, Guilhem Moulin wrote:
> On Wed, 08 Mar 2023 at 14:11:05 +0100, Christoph Anton Mitterer wrote:
> > On Wed, 2023-03-08 at 14:04 +0100, Guilhem Moulin wrote:
> >> No please don't, #-1 is RC so that would block transitioning into
> >> Bookworm which only
Control: notfound -1 cryptsetup/2:2.6.1-1
This is not an issue in testing because the argon2/cryptsetup combination is
okay there.
The migration excuses did not catch the grave bugs' changes in time for the
migration to happen.
I do not think that the changes justify an unblock request, so I
On Thu, 2023-03-09 at 01:14 +0100, Guilhem Moulin wrote:
> so please confirm :-)
hehe,... just that very minute I've written a dummy hook script that
simply includes libgcc so that I can upgrade my kernel ;-)
Applied your patch, and at least it causes libgcc to be included. So
I'd call that
Control: tag -1 pending
On Wed, 08 Mar 2023 at 14:04:42 +0100, Guilhem Moulin wrote:
> On Wed, 08 Mar 2023 at 13:42:53 +0100, Christoph Anton Mitterer wrote:
>> @Guilhem, I'm reopening this for now.
>
> No please don't, #-1 is RC so that would block transitioning into
> Bookworm which only
On Wed, 08 Mar 2023 at 14:11:05 +0100, Christoph Anton Mitterer wrote:
> On Wed, 2023-03-08 at 14:04 +0100, Guilhem Moulin wrote:
>> No please don't, #-1 is RC so that would block transitioning into
>> Bookworm which only supports merged-usr… Will fix that later during
>> the
>> freeze, but ATM
On Wed, 2023-03-08 at 14:04 +0100, Guilhem Moulin wrote:
> No please don't, #-1 is RC so that would block transitioning into
> Bookworm which only supports merged-usr… Will fix that later during
> the
> freeze, but ATM the priority is to get -2 into Bookworm ASAP, not
> further delay the
Control: clone -1 -2
Control: severity -2 important
Control: done -1 2:2.6.1-2
On Wed, 08 Mar 2023 at 13:42:53 +0100, Christoph Anton Mitterer wrote:
> @Guilhem, I'm reopening this for now.
No please don't, #-1 is RC so that would block transitioning into
Bookworm which only supports merged-usr…
Control: reopen -1
On Wed, 2023-03-08 at 08:16 +0100, Milan Broz wrote:
> Just upstream is no longer responding here...
Seems upstream is dead... I also have some minor PRs open against
argon2, but no response. Tried to get directly in contact with some of
them, but the same.
@Guilhem, I'm
Just FYI - I think that the whole problem can be avoided by merging this patch
https://github.com/P-H-C/phc-winner-argon2/pull/331
(we have the patch applied in cryptsetup for embedded libargon already).
Just upstream is no longer responding here...
Milan
Hey Guilhem.
Is it possible that your fix doesn't work on not-yet-usr-merged
systems?
I get here:
$ env --unset=LD_PRELOAD ldd /sbin/cryptsetup | sed -nr
'/.*=>\s*(\S+)\/libargon2\.so\..*/ {s//\1/p;q}'
/usr/lib/x86_64-linux-gnu
but:
$ dpkg -L libgcc-s1
/lib/x86_64-linux-gnu
Booting an older kernel/initrd and then downgrading libargon2-1 to the
version in Testing and updating the initrd resolves the situation for
now. Thanks to Kai and Guilhem.
Regards, Daniel
signature.asc
Description: This is a digitally signed message part
As a workaround I created a file /etc/initramfs-tools/hooks/libgcc:
. /usr/share/initramfs-tools/hook-functions
copy_file library /lib/x86_64-linux-gnu/libgcc_s.so.1
/lib/x86_64-linux-gnu/libgcc_s.so.1
With this hook the lib is copied an I am able to provide a password at
login.
Package: cryptsetup
Version: 2:2.6.1-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: kai.weber+deb...@glorybox.de
Dear Maintainer,
Today's upgrade triggered a rebuild of the initramfs. After a reboot I
can no longer login to my system. Using an older kernel worked. This
13 matches
Mail list logo
