Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-13T16:59:31Zhttps://gitlab.torproject.org/legacy/trac/-/issues/32346What is proper release name at Tor Debian Repository for Ubuntu Bionic 18.04?2020-06-13T16:59:31ZTracWhat is proper release name at Tor Debian Repository for Ubuntu Bionic 18.04?/etc/debian_version came up with buster/sid.
I also tried strectch, stable and jessie.
apt-get install tor came up with:
----
The following packages have unmet dependencies:
tor : Depends: libevent-2.0-5 (>= 2.0.10-stable) but it is no.../etc/debian_version came up with buster/sid.
I also tried strectch, stable and jessie.
apt-get install tor came up with:
----
The following packages have unmet dependencies:
tor : Depends: libevent-2.0-5 (>= 2.0.10-stable) but it is not installable
E: Unable to correct problems, you have held broken packages.
---
it also complained about libc version.
**Trac**:
**Username**: sectua1weasel (Peter Palfrader)weasel (Peter Palfrader)https://gitlab.torproject.org/legacy/trac/-/issues/32179retire orestis2020-06-13T16:59:19Zweasel (Peter Palfrader)retire orestisthis is an (old-style) onionoo frontend going only to the old backends. cf. #31659.
onionoo-frontend-0[12] are perfectly able to handle the current load. We can retire this instance.this is an (old-style) onionoo frontend going only to the old backends. cf. #31659.
onionoo-frontend-0[12] are perfectly able to handle the current load. We can retire this instance.weasel (Peter Palfrader)weasel (Peter Palfrader)https://gitlab.torproject.org/legacy/trac/-/issues/32045Add Jenkins builders for 0.4.22020-06-13T16:59:14ZNick MathewsonAdd Jenkins builders for 0.4.2Hooray! Tor 0.4.2 is now a separate branch, and deserves its own Jenkins builders. (The branch is named maint-0.4.2, as usual.)Hooray! Tor 0.4.2 is now a separate branch, and deserves its own Jenkins builders. (The branch is named maint-0.4.2, as usual.)Tor: 0.4.2.x-finalweasel (Peter Palfrader)weasel (Peter Palfrader)https://gitlab.torproject.org/legacy/trac/-/issues/31883Please remove metrics-lib-master job2020-06-13T16:59:06ZKarsten LoesingPlease remove metrics-lib-master jobWe moved this job over to GitLab, so we don't need the Jenkins job anymore. Please remove it at your convenience. Thanks!We moved this job over to GitLab, so we don't need the Jenkins job anymore. Please remove it at your convenience. Thanks!weasel (Peter Palfrader)weasel (Peter Palfrader)https://gitlab.torproject.org/legacy/trac/-/issues/31784move majus off of moly2020-06-13T16:59:02Zanarcatmove majus off of molyas part of an effort to reduce our dependence on an old server (moly), we should move majus (a non-redundant server) to a different host, probably the FSN* cluster.as part of an effort to reduce our dependence on an old server (moly), we should move majus (a non-redundant server) to a different host, probably the FSN* cluster.weasel (Peter Palfrader)weasel (Peter Palfrader)https://gitlab.torproject.org/legacy/trac/-/issues/31676decommission togashii2020-06-13T16:58:52Zweasel (Peter Palfrader)decommission togashiiI chatted with dgoulet, and we can retire togashii.
We can always set up a new VM for testnet services if they are useful again in the future. But for now, this setup is not in use.
This is part of the "retire textile" drive.I chatted with dgoulet, and we can retire togashii.
We can always set up a new VM for testnet services if they are useful again in the future. But for now, this setup is not in use.
This is part of the "retire textile" drive.weasel (Peter Palfrader)weasel (Peter Palfrader)https://gitlab.torproject.org/legacy/trac/-/issues/31659new onionoo hosts2020-06-13T16:58:51Zweasel (Peter Palfrader)new onionoo hostsRight now we have two onionoo backends (that run the java stuff) and also serve users, and two additional frontend-only hosts (that only serve users and ask the backends if they don't have a cached answer). So we have 4 hosts in total, t...Right now we have two onionoo backends (that run the java stuff) and also serve users, and two additional frontend-only hosts (that only serve users and ask the backends if they don't have a cached answer). So we have 4 hosts in total, two of which serve a double role.
To make the setup easier to monitor, scale, and maintain we should split these roles. For communications between frontends and backends we'll switch to using ipsec rather than the stunnels.
As a first step, we'll set up a new backend-only host (on Debian 10/buster) and Iain will set up the service there.weasel (Peter Palfrader)weasel (Peter Palfrader)https://gitlab.torproject.org/legacy/trac/-/issues/312150.3.5.8-1~xenial packages no longer available?2020-06-13T16:58:23Zcypherpunks0.3.5.8-1~xenial packages no longer available?Is it intentional that the main 0.3.5.8-1~xenial packages are no longer available?
I'm looking at:
https://deb.torproject.org/torproject.org/pool/main/t/tor/
It appears only nightly builds (*-dev-$date-*) packages for the 0.3.5.x rel...Is it intentional that the main 0.3.5.8-1~xenial packages are no longer available?
I'm looking at:
https://deb.torproject.org/torproject.org/pool/main/t/tor/
It appears only nightly builds (*-dev-$date-*) packages for the 0.3.5.x release series are available.weasel (Peter Palfrader)weasel (Peter Palfrader)https://gitlab.torproject.org/legacy/trac/-/issues/31143Add cohosh to ldap group snowflake2020-06-13T16:58:16ZArlo BreaultAdd cohosh to ldap group snowflakeThis is to give them permission to update snowflake.tpo as in #25724This is to give them permission to update snowflake.tpo as in #25724weasel (Peter Palfrader)weasel (Peter Palfrader)https://gitlab.torproject.org/legacy/trac/-/issues/31032Use narrowly-scoped signing keys in instructions for using torproject apt rep...2020-06-13T16:58:10ZdkgUse narrowly-scoped signing keys in instructions for using torproject apt repositoryhttps://2019.www.torproject.org/docs/debian.html.en engages in a number of suboptimal practices. In particular, it should not encourage users to use `apt-key add` with an OpenPGP certificate that is not expected to certify all repositor...https://2019.www.torproject.org/docs/debian.html.en engages in a number of suboptimal practices. In particular, it should not encourage users to use `apt-key add` with an OpenPGP certificate that is not expected to certify all repositories on the machine.
See https://wiki.debian.org/DebianRepository/UseThirdParty for reasonable guidance on setting up third party APT repositories.
(at the very least: place the key someplace like `/usr/local/share/keyrings/tor-project-arhcive.gpg` and then use a `signed-by` directive in the apt repository configuration)weasel (Peter Palfrader)weasel (Peter Palfrader)https://gitlab.torproject.org/legacy/trac/-/issues/30997Rust/Cargo problem on Jenkins sid-armhf?2020-06-13T16:58:09ZTaylor YuRust/Cargo problem on Jenkins sid-armhf?Looks like maybe Cargo or rustc is broken on sid-armhf?
```
17:28:51 ( cd "/srv/jenkins-workspace/workspace/tor-ci-linux-master-rust-arm/ARCHITECTURE/armhf/SUITE/sid/build-tree-tor/src/rust" ; \
17:28:51 CARGO_TARGET_DIR="/srv/jenkins-w...Looks like maybe Cargo or rustc is broken on sid-armhf?
```
17:28:51 ( cd "/srv/jenkins-workspace/workspace/tor-ci-linux-master-rust-arm/ARCHITECTURE/armhf/SUITE/sid/build-tree-tor/src/rust" ; \
17:28:51 CARGO_TARGET_DIR="/srv/jenkins-workspace/workspace/tor-ci-linux-master-rust-arm/ARCHITECTURE/armhf/SUITE/sid/build-tree-tor/src/rust/target" \
17:28:51 cargo build --release \
17:28:51 --frozen \
17:28:51 --manifest-path "/srv/jenkins-workspace/workspace/tor-ci-linux-master-rust-arm/ARCHITECTURE/armhf/SUITE/sid/build-tree-tor/../tor/src/rust/tor_rust/Cargo.toml" )
17:28:53 error: process didn't exit successfully: `rustc -vV` (exit code: 1)
17:28:53 --- stdout
17:28:53 rustc 1.34.2
17:28:53 binary: rustc
17:28:53 commit-hash: unknown
17:28:53 commit-date: unknown
17:28:53 host: armv7-unknown-linux-gnueabihf
17:28:53 release: 1.34.2
17:28:53
17:28:53 --- stderr
17:28:53 : CommandLine Error: Option '' registered more than once!
17:28:53 LLVM ERROR: inconsistency in registered CommandLine options
17:28:53
17:28:53 make[1]: *** [Makefile:23235: src/rust/target/release/libtor_rust.a] Error 101
17:28:53 make[1]: Leaving directory '/srv/jenkins-workspace/workspace/tor-ci-linux-master-rust-arm/ARCHITECTURE/armhf/SUITE/sid/build-tree-tor'
17:28:53 make: *** [Makefile:6668: all] Error 2
17:28:53 + true
17:28:53 + exit 2
17:28:53 + rc=2
17:28:53 + echo '=== [build-wrapper] end ==='
17:28:53
### [build-wrapper] end
```
I think we didn't make any changes to Tor that could have caused that.weasel (Peter Palfrader)weasel (Peter Palfrader)https://gitlab.torproject.org/legacy/trac/-/issues/30989intermittent jenkins failures for tor-ci2020-06-13T16:58:08ZTaylor Yuintermittent jenkins failures for tor-ciThere seem to be intermittent Jenkins failures for some tor-ci-linux-master builds, related to timeouts retrieving packages. Some examples are below. network-team: please note additional similar failures on this ticket when they appear.
...There seem to be intermittent Jenkins failures for some tor-ci-linux-master builds, related to timeouts retrieving packages. Some examples are below. network-team: please note additional similar failures on this ticket when they appear.
https://jenkins.torproject.org/view/Failed+Unstable/job/tor-ci-linux-master/ARCHITECTURE=i386,SUITE=stretch/4022/console
```
16:24:13 E: Failed to fetch https://mirrors.wikimedia.org/debian/pool/main/p/python2.7/libpython2.7-stdlib_2.7.13-2+deb9u3_i386.deb Operation too slow. Less than 10 bytes/sec transferred the last 120 seconds
16:24:13 E: Some files failed to download
16:24:13 run-parts: /home/jenkins/jenkins-tools/slaves/linux/tor-ci-linux-master/setup/15-install-build-depends exited with return code 1
```
https://jenkins.torproject.org/view/Failed+Unstable/job/tor-ci-linux-master-expensive-hardening/ARCHITECTURE=amd64,SUITE=buster/2447/console
```
18:41:41 E: Failed to fetch https://mirrors.wikimedia.org/debian/pool/main/p/python2.7/libpython2.7-minimal_2.7.16-2_amd64.deb Could not wait for server fd - select (11: Resource temporarily unavailable) [IP: 2620:0:861:1:208:80:154:15 443]
18:41:41 E: Some files failed to download
18:41:41 run-parts: /home/jenkins/jenkins-tools/slaves/linux/tor-ci-linux-master-expensive-hardening/setup/15-install-build-depends exited with return code 1
```weasel (Peter Palfrader)weasel (Peter Palfrader)https://gitlab.torproject.org/legacy/trac/-/issues/30836Build debs for tor's 0.4.1 branch, and stop building tor's 0.3.4 and 0.3.3 br...2020-06-13T17:28:15ZteorBuild debs for tor's 0.4.1 branch, and stop building tor's 0.3.4 and 0.3.3 branchesWe've just created maint-0.4.1 and release-0.4.1.
As of 10 June, we deprecated maint-0.3.3, maint-0.3.4, release-0.3.3, and release-0.3.4:
https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CoreTorReleases#Endoflife
He...We've just created maint-0.4.1 and release-0.4.1.
As of 10 June, we deprecated maint-0.3.3, maint-0.3.4, release-0.3.3, and release-0.3.4:
https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CoreTorReleases#Endoflife
Here's the list of built versions:
https://deb.torproject.org/torproject.org/pool/main/t/tor/Tor: 0.4.1.x-finalweasel (Peter Palfrader)weasel (Peter Palfrader)https://gitlab.torproject.org/legacy/trac/-/issues/30824Add Jenkins builders for 0.4.0 and 0.4.12020-06-13T16:57:57ZNick MathewsonAdd Jenkins builders for 0.4.0 and 0.4.1There are now maint and release branches for 0.4.0 and 0.4.1. We should add them to Jenkins.There are now maint and release branches for 0.4.0 and 0.4.1. We should add them to Jenkins.weasel (Peter Palfrader)weasel (Peter Palfrader)https://gitlab.torproject.org/legacy/trac/-/issues/30823Stop building 0.3.3 and 0.3.4 in Jenkins2020-06-13T16:57:56ZNick MathewsonStop building 0.3.3 and 0.3.4 in JenkinsTor 0.3.3 and 0.3.4 have reached end of life; we no longer need builders for them.Tor 0.3.3 and 0.3.4 have reached end of life; we no longer need builders for them.weasel (Peter Palfrader)weasel (Peter Palfrader)https://gitlab.torproject.org/legacy/trac/-/issues/30590Ubuntu packages for 0.4.0.5 unavailable2020-06-13T16:57:42ZTracUbuntu packages for 0.4.0.5 unavailablePackages for Ubuntu 18.04 (bionic) not updated to current 0.4.0.5 release.
**Trac**:
**Username**: highflux7Packages for Ubuntu 18.04 (bionic) not updated to current 0.4.0.5 release.
**Trac**:
**Username**: highflux7weasel (Peter Palfrader)weasel (Peter Palfrader)https://gitlab.torproject.org/legacy/trac/-/issues/30547Install python cryptography for stem's Jenkins jobs2020-06-13T16:57:42ZteorInstall python cryptography for stem's Jenkins jobsWhat do I need to do to get the python cryptography library installed for the stem jobs in Jenkins?
https://trac.torproject.org/projects/tor/ticket/28909#comment:1
If we run "make test-stem" in Tor's Jenkins jobs, we'll also want crypto...What do I need to do to get the python cryptography library installed for the stem jobs in Jenkins?
https://trac.torproject.org/projects/tor/ticket/28909#comment:1
If we run "make test-stem" in Tor's Jenkins jobs, we'll also want cryptography installed for them.weasel (Peter Palfrader)weasel (Peter Palfrader)https://gitlab.torproject.org/legacy/trac/-/issues/30435Lektor builds in jenkins sometimes fail with templates problems2020-06-13T16:57:39ZemmapeelLektor builds in jenkins sometimes fail with templates problemsSome builds of lektor in jenkins fail with:
jinja2.exceptions.UndefinedError: '_' is undefined
But if you click on 'build now' on the jenkins web interface, they usually build.
It seems like if some machines had the software needed to...Some builds of lektor in jenkins fail with:
jinja2.exceptions.UndefinedError: '_' is undefined
But if you click on 'build now' on the jenkins web interface, they usually build.
It seems like if some machines had the software needed to compile, and some not. As in many other languages, _ is the shortened expression for i18n, so it could be that the lektor-i18n plugin is missing? It looks like it installs, though, even if there is an error about 'wheels':
09:16:52 Updating packages in /home/jenkins/.cache/lektor/packages/1b7e03f6dbb11eed7da0c1e12dd75608 for project
09:16:52 Obtaining file:///srv/jenkins-workspace/workspace/lektor-website-tpo-translation/website/packages/i18n
09:16:53 Installing collected packages: lektor-i18n
09:16:53 Running setup.py develop for lektor-i18n
09:16:53 Successfully installed lektor-i18n
09:16:53 /usr/lib/python3/dist-packages/pip/_internal/commands/install.py:222: UserWarning: Disabling all use of wheels due to the use of --build-options / --global-options / --install-options.
Example: https://jenkins.torproject.org/job/lektor-website-tpo-translation/448/consoleFull or most of failed builds at https://jenkins.torproject.org/job/lektor-website-tpo-translationweasel (Peter Palfrader)weasel (Peter Palfrader)https://gitlab.torproject.org/legacy/trac/-/issues/30277amd bionic tor builds fail with an apt-get dependency error2020-06-13T16:57:33Zteoramd bionic tor builds fail with an apt-get dependency errorMost tor builds have failed with an error like this:
```
01:40:04 Install dose3 build dependencies (apt-based resolver)
01:40:04 -----------------------------------------------------
01:40:04
01:40:04 Installing build dependencies
01:4...Most tor builds have failed with an error like this:
```
01:40:04 Install dose3 build dependencies (apt-based resolver)
01:40:04 -----------------------------------------------------
01:40:04
01:40:04 Installing build dependencies
01:40:04 Reading package lists...
01:40:04 Building dependency tree...
01:40:04 Reading state information...
01:40:05 Some packages could not be installed. This may mean that you have
01:40:05 requested an impossible situation or if you are using the unstable
01:40:05 distribution that some required packages have not yet been created
01:40:05 or been moved out of Incoming.
01:40:05 The following information may help to resolve the situation:
01:40:05
01:40:05 The following packages have unmet dependencies:
01:40:05 sbuild-build-depends-dose3-dummy : Depends: dose-distcheck but it is not installable
01:40:05 E: Unable to correct problems, you have held broken packages.
01:40:05 apt-get failed.
01:40:05 E: Package installation failed
01:40:05 Not removing build depends: cloned chroot in use
01:40:06 E: Failed to explain bd-uninstallable
```
https://jenkins.torproject.org/job/tor-debian-0.3.4-nightly-binaries/ARCHITECTURE=amd64,SUITE=bionic/358/consoleFull#-16059184715da2eb1d-1267-4376-8b22-f5f143383dc7
I don't know how to fix this issue.
If it's not a trivial fix, please move this ticket into Core Tor/Tor, and someone should deal with it soon.weasel (Peter Palfrader)weasel (Peter Palfrader)https://gitlab.torproject.org/legacy/trac/-/issues/29974move critical services off, and then replace, moly2020-06-13T17:00:20Zanarcatmove critical services off, and then replace, molyAs part of #29817, we found out that `moly.torproject.org` has vastly surpassed its shelf life, having been installed in 2011. It's a big machine with multiple KVM guests, so we can't simply retire it and redistribute its guests elsewher...As part of #29817, we found out that `moly.torproject.org` has vastly surpassed its shelf life, having been installed in 2011. It's a big machine with multiple KVM guests, so we can't simply retire it and redistribute its guests elsewhere, at least not without filling up the rest of the infrastructure.
So we probably need to find a replacement box for moly.weasel (Peter Palfrader)weasel (Peter Palfrader)