Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #9553

Closed (moved)
Open
Opened Aug 21, 2013 by Karsten Loesing@karsten

Please bump tor version in maint-* branches as part of the release process

I just spent an hour wondering why Shadow simulates tor-0.2.4.16-rc just fine, but aborts when simulating maint-0.2.4:

0:0:22:976412 [thread-0] 0:5:2:381227791 [scallion-error] [exit8-81.1.0.0] [scalliontor_logmsg_cb] int connection_cpu_process_inbuf(connection_t *)(): Bug: /home/ubuntu/src/shadow/build/tor/src/or/cpuworker.c:313: connection_cpu_process_inbuf: Assertion rpl.magic == CPUWORKER_REPLY_MAGIC failed; aborting.
        **aborting**

Turns out there's no bug in tor. The problem is that Shadow looks at Tor's version string in configure.ac to decide what code changes to apply. maint-0.2.4 says it's version 0.2.4.10-alpha-dev. Editing the version string in configure.ac to 0.2.4.16-rc-dev fixes the problem.

Would it be possible to bump the tor version in maint-* branches as part of the release process? Is there a document where this step should be mentioned, and do you mind me requesting an update if the version string doesn't get updated in the future?

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
Tor: 0.2.4.x-final
Milestone
Tor: 0.2.4.x-final
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#9553