Bug#987213: pypy-stem: fails to upgrade from buster: prerm uses pypy in unconfigured state

Control: clone -1 -2 Control: reassign -1 pypy 7.3.3+dfsg-1 Control: retitle -1 pypy: ${shlibs:Depends} must move to Pre-Depends Control: affects -1 pypy-stem Control: reassign -2 pypy3 7.3.3+dfsg-3 Control: retitle -2 pypy3: ${shlibs:Depends} must move to Pre-Depends On Fri, Apr 30, 2021 at

Bug#987213: pypy-stem: fails to upgrade from buster: prerm uses pypy in unconfigured state

On Mon, Apr 19, 2021 at 08:41:14PM +0200, Andreas Beckmann wrote: >... > Preparing to unpack .../pypy-stem_1.8.0-3_all.deb ... > /usr/bin/pypy: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not > found (required by /usr/lib/pypy/bin/libpypy-c.so) > dpkg: warning: old pypy-stem

Bug#987213: pypy-stem: fails to upgrade from buster: prerm uses pypy in unconfigured state

Followup-For: Bug #987213 Control: tag -1 patch Hi, a possible solution would be to move the libc6 dependency in pypy to pre-depends s.t. pypy will not be unpacked before libc6 providing new (and required) symbols. Andreas diff -Nru pypy-7.3.3+dfsg/debian/changelog

Bug#987213: pypy-stem: fails to upgrade from buster: prerm uses pypy in unconfigured state

Package: pypy-stem Version: 1.8.0-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'buster'. It installed fine in 'buster', then the upgrade to 'bullseye' fails. >From the attached log (scroll to