Tor and unusual version numbers

[Salvatore Domenick Desiano]

In general, when we've ahd thi happen in the past, we just bump the rev.

I can, however, verify that 0.1.2.13 is not identified as newer than 
0.1.1.26. If anyone would like me to run any tests, I'm leaving my 
system in the outdated state so we can play with it.

-- Sal
smile.




--------------
  Salvatore Domenick Desiano
    Doctoral Candidate
      Robotics Institute
        Carnegie Mellon University

On Thu, 26 Apr 2007, Ryan Schmidt wrote:

o 
o On Apr 26, 2007, at 17:28, Sbranzo wrote:
o 
o > On 27/04/07 08:17, Boey Maun Suang wrote:
o > 
o > > The only thing that comes to my mind is that port outdated won't pick
o > > up that there's a new version of a port available until PortIndex is
o > > updated, and that happens every twelve hours on the MacPorts rsync
o > > repository.  In between such index updates, port sync will update the
o > > Portfiles to their latest state, but any port commands that run
o > > through PortIndex files (like port outdated) will be out of date.
o > 
o > I tought about it too, but in the last weeks IIRC I saw more that once
o > tor showing up when port -v sync'ing.
o > Today I just forced an upgrade, so I can't investigate more. Maybe
o > someone who installed tor a while ago can verify this behaviour, without
o > forcing the upgrade, in the next 12 hours or so.
o 
o None of those changes updated tor's version number or necessitated a rebuild
o of tor, until today. You can check that by looking in the repository:
o