Bug #16809

Track tor-experimental-0.4.0.x-buster

Added by anonym 2019-06-13 12:22:32 . Updated 2019-06-14 08:42:44 .

Status:
Rejected
Priority:
Normal
Assignee:
Category:
Build system
Target version:
Start date:
Due date:
% Done:

0%

Feature Branch:
Type of work:
Sysadmin
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

I just tried to merge devel into feature/buster and got a conflict in config/chroot_sources/torproject.chroot because of Feature #16687. The solution should be:

deb http://deb.torproject.org/torproject.org buster main
deb http://deb.torproject.org/torproject.org tor-experimental-0.4.0.x-buster main

but we don’t track tor-experimental-0.4.0.x-buster so this FTBFS. So I’m refraining from this merge in hope that it can be quickly added.

If tor 0.4.x finally is moved into the stable archives (so buster) this ticket can be rejected.

Subtasks

History

#1 Updated by anonym 2019-06-13 12:24:55

BTW, who has access to do this vs know how to do this?

#2 Updated by intrigeri 2019-06-14 08:41:35

  • Status changed from Confirmed to Rejected

Let’s use tor-experimental-0.4.0.x-stretch on Buster if it works there, and only if it doesn’t let’s do what this ticket requests (I don’t think it’s worth the hassle given we’ll go back to non-experimental suites soon).

#3 Updated by intrigeri 2019-06-14 08:42:44

> BTW, who has access to do this vs know how to do this?

This stuff is configured in templates/reprepro/snapshots/time_based/*/* in https://git-tails.immerda.ch/puppet-tails/. Anyone can send a patch but only sysadmins can deploy it in production.