Feature #5506

Split Git

Added by Tails 2013-07-18 07:42:03 . Updated 2014-08-02 16:59:49 .

Target version:
Start date:
Due date:
% Done:


Feature Branch:
Type of work:

Affected tool:
Deliverable for:




  • Git becomes sluggish, mainly due to binary and source Debian packages we’ve been storing in Git.
  • We’ve never taken advantage of mixing website with sources, so we only experience the disadvantages of it.

Our plan

New Git repositories

… with history imported and rewritten to filter out parts that were splitted out:

  • tails-live.git: the Tails source code we feed live-build with
  • tails-website.git: the source of this website (i.e. more or less what is currently in wiki/src

APT repository

Current state: implemented.

We have imported binary and source packages from our Git repository for past releases (completed on 2012-11-14).

Let’s say the not-merged-yet branches will see their packages imported as they are worked on.

.mrconfig or Git submodules

A few teams, such as the debian-installer and Debian Perl ones, that use many Git repositories (thousands, in case of the latter), have been successfully using mr to make an initial checkout easier for new contributors, and generally making it easier to deal with a lot of repositories (mass-update, etc.). We could do the same, starting with maintaining and publishing a .mrconfig file.

Additional custom repositories we use and may want to include in this .mrconfig: whisperback, live-boot, live-config, vidalia, htp, tails-greeter.

We probably should ship two mrconfig files: one that uses anonymous git:// read-only remotes, the other that uses ssh:// read-write remotes.

OTOH, Git submodules allow to do basically the same thing, but also to make it clear what version of these other repositories a given Git branch (in the main repo) needs.


Next things to do

Now that the APT repository (Feature #5351) is setup, and old packages imported, see sub-tickets for the next steps.


Feature #6276: Migrate the website to its own Git repository Rejected intrigeri


Related issues

Related to Tails - Feature #7036: Move custom software to our main Git repository In Progress


#1 Updated by intrigeri 2013-09-11 13:25:16

  • Category set to Infrastructure
  • Type of work changed from Website to Sysadmin
  • Starter set to No

#2 Updated by intrigeri 2014-04-07 08:41:44

  • Subject changed from split Git to Split Git
  • Assignee set to intrigeri

#3 Updated by intrigeri 2014-04-07 08:43:55

  • Description updated

#4 Updated by intrigeri 2014-04-07 08:44:11

  • related to Feature #7036: Move custom software to our main Git repository added

#5 Updated by intrigeri 2014-05-12 00:55:32

  • related to Bug #7220: Ignore jenkins-{build,fetch}-* tags when generating reprepro configuration added

#6 Updated by intrigeri 2014-05-12 01:14:56

  • related to deleted (Bug #7220: Ignore jenkins-{build,fetch}-* tags when generating reprepro configuration)

#7 Updated by intrigeri 2014-08-02 16:59:03

  • blocked by deleted (Feature #6051: Migrate master Git repository to immerda)

#8 Updated by intrigeri 2014-08-02 16:59:49

  • Status changed from Confirmed to Rejected

We’ve rejected Feature #6276, so this ticket doesn’t make sense anymore.