Opened 12 years ago

Last modified 7 years ago

#475 closed defect (Fixed)

version comparison

Reported by: weasel Owned by: nickm
Priority: Low Milestone: 0.2.0.x-final
Component: Core Tor/Tor Version: 0.1.0.18
Severity: Keywords:
Cc: weasel, nickm Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

changed recommendedversions on tor26 to only recommend 0.1.2.16 and 0.2.0.4:

Fri 00:06:31 <weasel> it made tor's notice message change too:
Fri 00:06:41 <weasel> from: Aug 02 07:08:58.368 [notice] This version of Tor (0.2.0.3-alpha-dev) is newer than any recommended version, according to

3/3 version-listing network statuses. Versions recommended by more than 1 authority are: 0.1.1.26, 0.1.2.13, 0.1.2.14, 0.1.2.15,
0.2.0.2-alpha, 0.2.0.3-alpha

Fri 00:07:00 <weasel> to Aug 02 19:41:32.354 [warn] Please upgrade! This version of Tor (0.2.0.3-alpha-dev) is not recommended, according to 3/3

version-listing network statuses. Versions recommended by at least 1 authority are: 0.1.1.26, 0.1.2.13, 0.1.2.14, 0.1.2.15,
0.2.0.2-alpha, 0.2.0.3-alpha

Fri 00:07:22 <weasel> which was kinda funny. please upgrade: here is a list of older versions that are recommended

[Automatically added by flyspray2trac: Operating System: All]

Child Tickets

Change History (4)

comment:1 Changed 12 years ago by nickm

I'm pretty sure this is an artefact of the way that Tor currently decides how to describe versions: it decides
how to describe your old version independently from deciding what the recommended list _is_. This should get fixed
as we switch clients to use consensus networkstatus docs.

comment:2 Changed 12 years ago by nickm

Should be fixed by new v3 directory code in r11957.

comment:3 Changed 12 years ago by nickm

flyspray2trac: bug closed.

comment:4 Changed 7 years ago by nickm

Component: Tor ClientTor
Note: See TracTickets for help on using tickets.