Bug#928164: backports work
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
Bug#928164: backports work
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). cheers, Frederic
Bug#928164: backports work
Hi Frederic, >> 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. Thanks, Thijs signature.asc Description: OpenPGP digital signature
Bug#928164: backports work
Hi, > 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. Frederic
Bug#928164: backports work
On Mon, 29 Apr 2019, Frederic Peters wrote: Harald Hannelius wrote: I forgot to mention that installing of liblasso3 from stretch backports also fixes the problem and I can operate as an SP and sign requests. Good to know as there's an important diff between 2.5.0 and 2.6.0, and cherrypicking a specific commit may be difficult; I'll still look at bisecting but it may take some time. I don't know how this happened, but there doesn't seem to be a liblasso3 in backports. Somehow the other server worked, but after a reboot I started getting signal 11 on that one too. It worked for a week. I disabled signing och all of the sites through creating static SP Metadata, and now the sites are up again. 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 -- Harald Hannelius | har...@iki.fi | +358505941020
Bug#928164: backports work
fixed 928164 2.6.0-2 thanks Hi, Harald Hannelius wrote: > > I forgot to mention that installing of liblasso3 from stretch backports also > fixes the problem and I can operate as an SP and sign requests. Good to know as there's an important diff between 2.5.0 and 2.6.0, and cherrypicking a specific commit may be difficult; I'll still look at bisecting but it may take some time. Fred
Bug#928164: backports work
Harald Hannelius wrote: > > > On Mon, 29 Apr 2019, Frederic Peters wrote: > > > fixed 928164 2.6.0-2 > > thanks > > Will this dribble down to Debian Stretch? Not automatically; to get it into stretch we first need to isolate a specific commit and propose it as an update. Fred
Bug#928164: backports work
On Mon, 29 Apr 2019, Frederic Peters wrote: fixed 928164 2.6.0-2 thanks Will this dribble down to Debian Stretch? -- Harald Hannelius | har...@iki.fi | +358505941020
Bug#928164: backports work
I forgot to mention that installing of liblasso3 from stretch backports also fixes the problem and I can operate as an SP and sign requests. -- Harald Hannelius | har...@iki.fi | +358505941020
