[tor-bugs] #20643 [Internal Services/Service - deb.tpo]: make and maintain a registry of what debs are on deb.tp.o and why

[Tor Bug Tracker & Wiki]

#20643: make and maintain a registry of what debs are on deb.tp.o and why
-------------------------------------------------+-------------------------
 Reporter:  arma                                 |          Owner:  irl
     Type:  task                                 |         Status:
                                                 |  needs_revision
 Priority:  Medium                               |      Milestone:
Component:  Internal Services/Service - deb.tpo  |        Version:
 Severity:  Normal                               |     Resolution:
 Keywords:                                       |  Actual Points:
Parent ID:                                       |         Points:
 Reviewer:  arma                                 |        Sponsor:
-------------------------------------------------+-------------------------
Changes (by arma):

 * status:  needs_review => needs_revision


Comment:

 Great! I looked at the wiki page.

 The wiki page lists these packages as being available on deb.tp.o:
 deb.torproject.org-keyring, tor, obfsproxy, pyptlib, obfs4proxy.

 But I see other debs, like python-klein:
 http://deb.torproject.org/torproject.org/pool/main/k/klein/
 and ooniprobe:
 http://deb.torproject.org/torproject.org/pool/main/o/ooniprobe/
 python-certifi:
 http://deb.torproject.org/torproject.org/pool/main/p/python-certifi/
 and txtorcon:
 http://deb.torproject.org/torproject.org/pool/main/t/txtorcon/

 So it seems like this list on the wiki is incomplete?

 Also, I didn't find the obfsproxy package in the pool/ directory. (Maybe
 it was removed in the past 7 months, when wheezy went away?)

 Are these extra debs somehow not "really" on deb.tpo, since they're not in
 the Releases files that you mentioned? If that is so, should we delete
 them?

 But I have a memory of Arturo thinking that the ooniprobe deb was still in
 use? (It appears to still be referenced directly from
 https://ooni.torproject.org/docs/ so I would guess yes it is.)

 In the example command line on the wiki there is this typo,
 "$PACKCAGETOREMOVE"

 To satisfy the "and maintain" part of this ticket, we should figure out
 some way to make sure that a pointer to the wiki page is in the critical
 path to adding or removing a package from deb.tpo, so people know to go
 update the wiki page. An alternative option would be that we run some sort
 of nagios cron that automatically enumerates the available packages, and
 notifies somebody when they differ from the entries on the wiki?

 And lastly, for the "and why" part of the ticket, it would be nice to have
 a short explanation of why we have each package on deb.tpo. Such an
 explanation would primarily help it stay easy to notice when that reason
 no longer applies and it's time to reconsider having a separate copy here.

 Thanks!

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/20643#comment:12>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online