Hi, Sebastian Ramacher <sramac...@debian.org> (2021-05-31): > Control: tags -1 confirmed d-i > > On 2021-05-31 01:07:11 +0200, Thorsten Glaser wrote: > > Package: release.debian.org > > Severity: normal > > User: release.debian....@packages.debian.org > > Usertags: unblock > > X-Debbugs-Cc: t...@mirbsd.de > > > > Please unblock package klibc > > > > [ Reason ] > > The NMU contains a fix for #943425 (save/restore correct set of > > registers across *{set,long}jmp) which is RC on s390x, which is > > a release architecture. > > > > [ Impact ] > > klibc-built binaries on s390x can malfunction. > > > > [ Tests ] > > The mksh testsuite catches this. Today’s mksh upload’s buildd log > > on s390x shows that the fix works. An S/390 expert provided the > > correct set of registers to save/restore. I’ve compared it to the > > glibc implementation afterwards, and it matches, so I believe it > > to be correct. > > > > [ Risks ] > > klibc is rather critical; it’s part of booting and installing (so > > this also needs an udeb unblock). The patch affects s390x only, > > as far as I can tell, but I believe it necessary there. > > > > [ Checklist ] > > [x] all changes are documented in the d/changelog > > [x] I reviewed all changes and I approve them > > [x] attach debdiff against the package in testing > > > > [ Other info ] > > This will need an udeb unblock; what do I need to do for this? > > By adding Cyril (as d-i RM) and debian-boot@l.d.o to CC. Done now.
Declaring myself incompetent regarding s390x, but as that seems highly targeted at that arch, and since other archs like amd64 I run tests on don't seem to regress: no objections. :) Cheers, -- Cyril Brulebois (k...@debian.org) <https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant
signature.asc
Description: PGP signature