Opened 6 years ago

Closed 13 months ago

#697 closed change (fixed)

[trac] add mirror/backup repository for trac plugins

Reported by: philll Assignee:
Priority: P2 Milestone:
Module: Infrastructure Keywords:
Cc: matze Blocked By:
Blocking: Platform: Unknown
Ready: no Confidential: no
Tester: Unknown Verified working: no
Review URL(s):



We currently use a vast amount of trac plugins, mostly provided by Apparently, that website and its repositories respectively do not have a very good uptime and are sometimes unavailable for quite some time (several weeks last time), which prohibits deploying test or live instances of our Trac instance in the infrastructure.

What to change

Provide a backup mirror repository with all our Trac plugins used to ensure they are available in case of a downtime of our plugin providers.

Change History (9)

comment:1 Changed 6 years ago by matze

  • Cc mathias@… added
  • Platform set to Unknown

Since GitHub supports Subversion for quite a while now¹, and because all plug-ins from are fetched via SVN over HTTP², and because we already maintain an adblockplus organization at GitHub³, I like to recommend forking the plug-ins in use into GitHub repositories, in order to avoid maintenance overhead.

This, however, needs to be done by someone who actually has owner permissions there, and can import the following resources:

  • svn+
  • svn+
  • svn+
  • svn+
  • svn+
  • svn+
  • svn+
  • svn+

Afterwards I can update the puppet files.


Last edited 6 years ago by matze (previous) (diff)

comment:2 Changed 6 years ago by philll

  • Cc matze trev added; mathias@… removed

@trev: Your opinion on matze's suggestion?

comment:3 Changed 6 years ago by trev

GitHub is still a third-party website, the idea is to have these repositories on Import from SVN is pretty easy using the Convert extension.

comment:4 Changed 6 years ago by matze

Well, the ticket description only states uptime and similar issues in the background description. I hardly doubt that GitHub's availability ( would become an issue for us. (In contrast; we do not care about our own availability that much right now..) Furthermore, the effort required to use this option is almost node.

Although we can use Mercurial and our own server to host the mirror repos as well, the import and future updates are a bit more time consuming.

However, in fact is does not really matter where the mirrors are, as long as they're reliable.

@trev: It's up to you anyway. Please either import the modules to or (AFAIK we can't do that due to the lack of permissions in either case). thx

comment:5 Changed 6 years ago by matze

Speaking of availability: #167 ... ;-D

Last edited 6 years ago by matze (previous) (diff)

comment:6 Changed 6 years ago by trev

We should really have all dependencies on our infrastructure - then we only need to care about availability of our own infrastructure. Plus: we cannot have repositories on GitHub as subrepositories. Plus: our scripts don't need to consider multiple possible sources (and formats). Updating really isn't the issue.

comment:7 Changed 6 years ago by matze

Agreed. Still, I cannot import new repositories. In case you won't find the time; whom else can I address regarding this task?

comment:8 Changed 3 years ago by fhd

  • Cc trev removed

comment:9 Changed 13 months ago by matze

  • Resolution set to fixed
  • Status changed from new to closed
  • Tester set to Unknown

This one's obsolete by now.

Note: See TracTickets for help on using tickets.