On Wed, May 22, 2019 17:21, Frederic Peters wrote:
> Hi Thijs,
>
>> >> I would have been OK to have 2.6.0 of liblasso3 in stretch backports,
>> >> and I was in the believe that I had installed it. But when checking,
>> >> I'm still running 2.5.0-5+b1. Spooky
>>
>> > I'll see about uploading 2.6.0 to backports.
>>
>> That would be great. I have a backport of libapache2-mod-auth-mellon in
>> stretch, to allow to use SHA256 with mellon. But the signatures fail
>> because of https://dev.entrouvert.org/issues/10019
>>
>> That is fixed in lasso 2.5.1. So having a lasso >= 2.5.1 in backports
>> would really help us aswell.
>>
>> I can help out with the backport work if needed.
>
> Per https://backports.debian.org/Contribute/#index3h3 I asked to be
> added to the ACL but no news yet; as you are already in I'd suggest you
> go ahead and upload lasso (afaik there are no technical difficulties
> and I'm using a local backport at $dayjob).

FYI, I have done this yesterday and it's now queued for review:
https://ftp-master.debian.org/backports-new.html


Cheers,
Thijs

Reply via email to