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

Closed (moved)
Open
Opened Nov 08, 2017 by boklm@boklm

Tor Browser nightly builds include an old https-everywhere version

In projects/https-everywhere/config we are using the master branch for nightly builds, from the git repository https://git.torproject.org/https-everywhere.git

However the master branch on this repository is currently 12 months old.

To fix that, I think we could either:

  • use the master branch from https://github.com/EFForg/https-everywhere instead of https://git.torproject.org/https-everywhere.git, which seems to be updated frequently
  • ask legind to update the master branch on https://git.torproject.org/https-everywhere.git more frequently
  • not use the master branch in nightly builds but instead use the same tag as in the alpha. We can also update this tag manually when a new https-everywhere version is released, even when we don't plan to release a new Tor Browser soon, to include it in the nightly.
To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#24179