Am Sonntag, dem 09.04.2023 um 22:28 +0200 schrieb Paul Gevers: > > [ Risks ] > This is a new upstream release. This is not a small change. And while > typing this unblock request, I'm getting uncomfortable and wonder if > we want this. But as it's all prepared, let's discuss and pull Markus > in to elaborate a bit too.
I am in favor of shipping rhino 1.7.14 in Bookworm for all the reasons Paul has mentioned. I believe at this point in the release cycle we don't want to make arbitrary changes but we also want to deliver the best possible software package to our users. I'm not confident to find a different fix to address #1026639 and the broken web application in openrefine. It clearly works with 1.7.14 but not with the current version in testing. Since I only had to patch one reverse-dependency, the orphaned package closure-compiler, and everything else appears to work as expected, I believe the risks are very manageable. Worst case would be to rebuild another package. We also get the latest upstream version and don't have to ship a six year old version again. Markus
signature.asc
Description: This is a digitally signed message part
