SVN-Server

---

BoxMatrix >> Development >> SVN-Server

@ BoxMatrix   -   IRC-Chat   -   Translate: de es fr it nl pl

News

Selectors

Models

Accessories

Components

Environment

Config

Commands

System

Webif

Software

Develop

Lexicon

Community

Project

Media

---

Tarballs

GPL-Browser

FW-Probes

FW-History

FW-News

Supportdata

Hardware

SVN

Trac

Freetz-News

Freetz-Timeline

Freetz-Releases

Freetz-Mirror

OpenWRT

Research

---

Everyone who ever checked out Freetz from its repository now has dead builds which could not be updated any more since the Freetz team switched off the SVN master. For all users with existing builds we created a backup server which could be used to update your builds to the moment when Freetz turned a Github-only fork of itself, disposing all of its prior pride. One advantage of Github is that everybody can fork a project with a few clicks, and start working independently, and it already happened. Now we have multiple forks of Freetz, the freetz-org fork which owns the domain, and the freetz-ng fork which intends to be more open for collaborative development. Both use the last snapshot of the SVN master to start their fork. Not finished yet but you will be able to choose which fork of the former master to follow. See the Freetz-News for details about ongoing development.

---

The freetz-ng fork moved from Github to BoxMatrix, the first fork master here. freetz-ng is intended to be open for collaborative development. A good chance for a return of an actively maintained community driven and up to date Freetz is now here. If you are a coder please help to let the old pride of Freetz return. The master on our SVN-Server is working and our Trac-Server is now open for registration, so independency of 3rd party services completely returned here. You can either checkout the latest revision of freetz-ng here or relocate all your old SVN based Freetz builds. The ticket system is up and running and bug reports, patches or feature requests are welcome.

---

BoxMatrix SVN-Server

The BoxMatrix SVN-Server is a replacement server for the former Freetz master and its forks. It uses the same structure as before just the base URL changed:

• Old base URL: http://svn.freetz.org/
• New base URL: Choose one:

3-hourly updated index of recent activity on our svn repositories, most active fork listed first. Last update: 2024-12-24 02:16 GMT.
The Freetz-org fork is unmaintained since 2021-05-26. Its last maintainer Er13 recommends using Freetz-ng.

	Repository base URL	Rev	Com	Project Info	Status	Log	Master	Date / GMT
	http://svn.boxmatrix.info/freetz-ng/	20037	5023	Active master of to the freetz-ng fork	working	Log	here	2018-12-02 22:01
	http://svn.boxmatrix.info/freetz-org/	15442	428	3-hourly bridge to the freetz-org fork	work in progess	Log	Github	2021-05-26 20:13
	http://svn.boxmatrix.info/freetz-dhu/	15437	423	3-hourly bridge to the freetz-dhu fork	work in progess	Log	Github	2020-10-08 19:07
	http://svn.boxmatrix.info/freetz/	15014	0	Frozen copy of the passed Freetz SVN	working	Log	gone	2018-12-02 22:01
4 SVN repositories (once finished)

Legend:   = hosted here.   -   = dead link.   -   The Com column shows the amount of commits since the fork of the freetz SVN master.

Once finished you can relocate to the fork of your choice. All repositories are currently read only. This may change.
If you are a developer consider contributing to one of the forks, but use the respective Master then to check out, or create your own fork.
If you want another fork hosted or bridged here then get in touch.

Checking out

To build freetz from scratch you need the svn checkout command:

$ umask 0022 && svn co http://svn.boxmatrix.info/freetz-ng/trunk freetz-ng

If you have an existing build you need to relocate:

Relocate your build

The svn client permits to relocate the remote project URL of a build. This is a step by step howto:

Get the svn Version

The method to relocate depends on the version of the svn client so you first have to check it:

$ svn --version
svn, version 1.6.17 (r1128011)
...

If the version is below 1.7 you need to use the old method, as of 1.7 the new method is your friend.

Get the Project URL

Next cd to your build and find out the current project URL:

$ svn info
Path: .
URL: http://svn.freetz.org/trunk
Repository Root: http://svn.freetz.org
Repository UUID: 149334a1-2f27-0410-a3b9-fc62619ac1e6
...

In this example the URL shows that you checked out the trunk. Now let's relocate this URL:

Relocate: old Method

For the example above pre 1.7 clients relocate your trunk like this:

$ svn switch --relocate http://svn.freetz.org/trunk http://svn.boxmatrix.info/freetz-ng/trunk

Relocate: new Method

As of version 1.7 switch --relocate has been deprecated and replaced by the relocate command:

$ svn relocate http://svn.boxmatrix.info/freetz-ng/trunk

Update your build

Now you can simply update your build as you are used to:

$ svn up
...
Updated to revision 15014.

This method also works for all tags and branches and checkouts for specific revisions, even for old dsmod builds which used the SVN.

Choose a fork

Once implemented you can choose one of the forks hosted or bridged here, which you can easily relocate to as explained.

Change the fork

You needn't stay with a specific fork, you can switch it any time by relocating it. Since all forks here are checked into a clone of the frozen SVN master they are compatible up to the revision of the frozen master.

Just checkout revision 15014 (or 15000) and switch the fork by relocating it. Of course this requires cleaning your build to not mix up projects.

• To be explained here

Using HTTPS

The BoxMatrix SVN-Server supports HTTPS, thanks to Let's Encrypt. Using HTTPS has quite some advantages, but may also have disadvantages.

The Freetz SVN never had working HTTPS support, which is an advantage now that it's gone. People who have hundreds of builds could mass relocate a HTTP checkout on DNS level, instead of relocating build for build. The new target just needs the same path structure and a virtual host for the prior hostname.

Since the author of BoxMatrix is one of those people with hundreds of (mostly modified) builds there will be support for DNS based mass relocation for svn.freetz.org in future (by your hosts file or using dnsmasq). However, this is not implemented yet.

So if you plan to have masses of checkouts you should stay with HTTP to stay mass relocatable and independent of a working certificate.

Credits

Big thanks to Cuma for providing the latest backup of the passed SVN server and for spending one night to check it into an empty repository!