Notes about issue uname_output_in_python_debugging_symbols_caused_by_sysconfig_getplatform in unstable
| Identifier: | uname_output_in_python_debugging_symbols_caused_by_sysconfig_getplatform |
|---|---|
| Suites: | unstable / trixie / bookworm / bullseye / experimental |
| URL: | https://bugs.debian.org/835805 |
| Description: |
encoded in tempfile. Affects building on i386 as it does not distinguish between userland vs kernel. . https://sources.debian.net/src/python2.7/latest/Lib/sysconfig.py/#L572-L584 https://sources.debian.net/src/python3.5/latest/Lib/sysconfig.py/#L646-L658 |
|
Packages in 'unstable' known to be affected by this issue: (the 1/4 most-popular ones (within this issue) are underlined) |
None |
|
Our notes about issues affecting packages are stored in notes.git and are targeted at packages in Debian in 'unstable/amd64' (unless they say otherwise). |
|
A package name displayed with a bold
font is an indication that this package has a note. Visited
packages are linked in green, those which have not been visited are
linked in blue.
A # sign after the name of a package
indicates that a bug is filed against it. Likewise, a
+ sign indicates there is a
patch available, a P means a
pending bug while # indicates a
closed bug. In cases of several bugs, the symbol is repeated.