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
  • #15864

Closed (moved)
Open
Opened Apr 30, 2015 by Mike Perry@mikeperry

Differentiate between build and release sha256sums.txt

Windows users on our blog and elsewhere are being confused by the fact that the sha256sums for our exes don't match the downloaded files. This problem will probably get worse once we sign the Mac packages..

We might be able to communicate this to them indirectly by providing two sets of sha256sums.txt files: build-sha256sums.txt and release-sha256sums.txt. Or maybe build-sha256sums.txt and sha256sums.txt...

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