... | ... | @@ -504,6 +504,15 @@ should be dropped in ` /etc/apt/trusted.gpg.d` or (preferably) into an |
|
|
outside directory (we typically use `/usr/share/keyrings`). It is
|
|
|
believed that we already do the correct thing here.
|
|
|
|
|
|
### Python 2
|
|
|
|
|
|
Python 2 is still in Debian bullseye, but severely diminished: almost
|
|
|
all packages outside of the standard library were removed. Most
|
|
|
scripts that use *anything* outside the stdlib will need to be ported.
|
|
|
|
|
|
We clarified our Python 2 policy in [TPA-RFC-27: Python 2 end of
|
|
|
life](policy/tpa-rfc-27-python2-eol).
|
|
|
|
|
|
# Issues
|
|
|
|
|
|
See also the official list of [known issues](https://www.debian.org/releases/bullseye/amd64/release-notes/ch-information.en.html).
|
... | ... | @@ -518,6 +527,23 @@ See also the official list of [known issues](https://www.debian.org/releases/bul |
|
|
* some config files should be updated in Puppet to reduce the diff
|
|
|
with bullseye, see [issue tpo/tpa/team#40723](https://gitlab.torproject.org/tpo/tpa/team/-/issues/40723)
|
|
|
|
|
|
* many hosts had issues with missing Python 2 packages, as most of
|
|
|
those were removed from bullseye, [TPA-RFC-27: Python 2 end of
|
|
|
life](policy/tpa-rfc-27-python2-eol) was written in response, and many scrips were ported to
|
|
|
Python 3 on the fly, more probably remain, examples:
|
|
|
|
|
|
* [tpo/tpa/team#40751](https://gitlab.torproject.org/tpo/tpa/team/-/issues/40751)
|
|
|
* [tpo/network-health/exitmap#38](https://gitlab.torproject.org/tpo/network-health/exitmap/-/issues/38)
|
|
|
* [tpo/network-health/metrics/exit-scanner#40004](https://gitlab.torproject.org/tpo/network-health/metrics/exit-scanner/-/issues/40004)
|
|
|
* [tpo/network-health/metrics/tor-check#40007](https://gitlab.torproject.org/tpo/network-health/metrics/tor-check/-/issues/40007)
|
|
|
|
|
|
* virtualenvs that have an hardcoded Python version
|
|
|
(e.g. `lib/python3.7`) must be rebuilt with the newer version
|
|
|
(3.9), see for example [tpo/anti-censorship/bridgedb#40049](https://gitlab.torproject.org/tpo/anti-censorship/bridgedb/-/issues/40049)
|
|
|
|
|
|
* there are concerns about performance regression in PostgreSQL, see
|
|
|
[materculae](https://gitlab.torproject.org/tpo/tpa/team/-/issues/40750), [rude](https://gitlab.torproject.org/tpo/tpa/team/-/issues/40761)
|
|
|
|
|
|
* The official list of [known issues][]
|
|
|
|
|
|
[known issues]: https://www.debian.org/releases/buster/amd64/release-notes/ch-information.en.html
|
... | ... | @@ -567,6 +593,13 @@ back to the `/srv` mount timeout: |
|
|
|
|
|
unbound -d -p &
|
|
|
|
|
|
## onionbalance backport
|
|
|
|
|
|
lavamind had to upload a backport of onionbalance because we had it
|
|
|
patched locally to follow an upstream fix that wasn't shipped in
|
|
|
bullseye. Specifically, he [uploaded](https://ftp-master.debian.org/new/onionbalance_0.2.2-1~bpo11+1.html) `onionbalance
|
|
|
0.2.2-1~bpo11+1` to `bullseye-backports`.
|
|
|
|
|
|
# Troubleshooting
|
|
|
|
|
|
## Upgrade failures
|
... | ... | |