Opened 7 years ago

Closed 2 years ago

#1873 closed task (wontfix)

Allow osgeo-post-commit-hook SVN script to receive TRAC name by relative path

Reported by: strk Owned by: strk
Priority: normal Milestone:
Component: SysAdmin/Trac Keywords:

Description (last modified by strk)

As trac env location path changed (#1684) all SVN hooks broke (#1872). Letting the osgeo-post-commit-hook SVN script accept relative trac env names would reduce the risk of this happening in the future, and would remove an hard-coded path in the script (which could be replaced by basename $1, already used by some scripts which are likely broken at the moment).

Change History (7)

comment:1 by strk, 7 years ago

Description: modified (diff)

comment:2 by strk, 7 years ago

Description: modified (diff)

comment:3 by strk, 7 years ago

Description: modified (diff)

comment:4 by strk, 7 years ago

For the record: the hooks using relative project name (assuming SVN repo name == trac env name) are currently:


If I'm right (hadn't checked) those 3 would not be showing in Trac any SVN changes.

comment:5 by jimk, 7 years ago

While geomoose has history in trac and svn, all active development is on github. So we would not expect any changes in svn or trac.

Last edited 7 years ago by jimk (previous) (diff)

comment:6 by jimk, 7 years ago

For clarity:

GeoMoose would like its OSGeo Trac and SVN archived/preserved from a historical perspective. GeoMoose does not expect we will be updating either in the future. (Which makes things like update hooks irrelevant.)

All current development is happening with github (repositories and issues) but history was not migrated when we moved active development from svn to git and from trac to github issues.

comment:7 by strk, 2 years ago

Resolution: wontfix
Status: newclosed

Moot as nobody should still be using SVN in 2022 :)

Note: See TracTickets for help on using tickets.