bwauths need to upgrade (to start measuring even non-Fast relays)

With the recent commit of #8435 (moved) to Tor, directory authorities will leave off the Fast flag from any non-measured relay.

I believe bwauths currently don't measure relays that don't have the Fast flag.

Bad cycle we're about to have here.

See https://trac.torproject.org/projects/tor/ticket/8273#comment:6 and comments below it for context. Aaron has a proposed patch.

added component::core tor/torflow owner::aagbsn priority::medium resolution::fixed severity::normal status::closed tor-dirauth type::enhancement labels

Trac:
Status: new to needs_review

aagbsn says this is already merged. So now it is just a matter of getting the active bwauths to upgrade.

moria1 has. Who else? :)

Trac:
Cc: nickm, aagbsn, mikeperry to nickm, aagbsn, mikeperry, ln5, sebastian

Trac:
Component: Torflow to Tor
Summary: bwauths need to start measuring even non-Fast relays to bwauths need to upgrade (to start measuring even non-Fast relays)
Status: needs_review to new

salsa (reporting to maatuska) is now running 2ce8f6d7 (Thu Mar 14 12:17:24 2013 +0100).

I heard about new upgrade instructions, did they make it anywhere? Is the upgrade process significantly different from what it used to be?

It shows that my bwauthority.py has been unhappy since the upgrade, see #8698 (moved).

BTW, I'm still running Tor v0.2.3.9-alpha-dev. Is that what y'all are using too? I'm under the impression that we should use the same Tor. Correct?

I'm on a somewhat-recent master

Replying to ln5:

It shows that my bwauthority.py has been unhappy since the upgrade, see #8698 (moved).

BTW, I'm still running Tor v0.2.3.9-alpha-dev. Is that what y'all are using too? I'm under the impression that we should use the same Tor. Correct?

Would that be v0.2.4.9-alpha-dev?

And, use: torflow: git-rw.torproject.org/torflow.git 2ce8f6d7875f3674c7d9d4fe7848b6d0bb92fa9c

pytorctl (submodule is in directory TorCtl, don't forget to update it too): git-rw.torproject.org/pytorctl.git 68bc5de84dc90e1292c6aa19abd95f660b5e3277

Replying to aagbsn:

Replying to ln5:

It shows that my bwauthority.py has been unhappy since the upgrade, see #8698 (moved).

BTW, I'm still running Tor v0.2.3.9-alpha-dev. Is that what y'all are using too? I'm under the impression that we should use the same Tor. Correct?

Would that be v0.2.4.9-alpha-dev?

Apr 14 12:55:26.738 [notice] Tor v0.2.3.9-alpha-dev (git-b7519dce98031c2a) running on NetBSD i386.

Trac:
Milestone: N/A to Tor: 0.2.4.x-final
Keywords: N/A deleted, tor-auth added

Who still has to upgrade, if anybody? Is there a better component for this than "Tor" ?

Trac:
Component: Tor to Torflow

Trac:
Status: new to assigned

Trac:
Milestone: Tor: 0.2.4.x-final to N/A

Turns out that tor-auth is for directory authority so make it clearer with tor-dirauth

Trac:
Keywords: tor-auth deleted, tor-dirauth added

This ticket is defunct: if operators haven't upgraded for 5 years...

Trac:
Severity: N/A to Blocker
Resolution: N/A to fixed
Status: assigned to closed
Reviewer: N/A to N/A
Sponsor: N/A to N/A

Trac:
Severity: Blocker to Normal

closed

mentioned in issue #9062 (moved)

mentioned in issue #9369 (moved)

mentioned in issue tpo/core/tor#9062 (closed)

moved to tpo/network-health/torflow#8688 (closed)

mentioned in issue tpo/network-health/torflow#9369 (closed)