This bug was fixed in the package pypy - 5.1.2+dfsg-1~16.04
---
pypy (5.1.2+dfsg-1~16.04) xenial-proposed; urgency=medium
* SRU: LP: #1589268. Backport 5.2.1 to 16.04 LTS.
pypy (5.1.2+dfsg-1) unstable; urgency=medium
* New upstream release.
* Refresh s390x-march.
* Drop othe
package successfully built in xenial-proposed
** Changed in: pypy (Ubuntu)
Status: New => Fix Released
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Hello Matthias, or anyone else affected,
Accepted pypy into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/pypy/5.1.2+dfsg-1~16.04 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://w
5.1 release notes include
"""
We have released PyPy 5.1, about a month after PyPy 5.0.
We encourage all users of PyPy to update to this version. Apart from the usual
bug fixes, there is an ongoing effort to improve the warmup time and memory
usage of JIT-related metadata, and we now fully support
** Description changed:
SRU: backport pypy 5.1.2 to 16.04 LTS. 5.1.2 is a bug fix release
compared to 5.1.0 shipped with 16.04 LTS. It's a universe package, used
as a build dependency in some main packages. We'll test build every
package having pypy as a build dependency.
+
+ The followin
