id	summary	reporter	owner	description	type	status	priority	milestone	component	version	severity	resolution	keywords	cc
1250	Misleading svn output from `make psVersionDefinition.h`	Sebastian Jester	Paul Price	"While trying to diagnose some compile problems in psLib, we found this output just before the end of the compile log that looked like there was a problem with svn:
{{{
make psVersionDefinitions.h
rm -f psVersionDefinitions.h
/usr/bin/sed -e ""s|@PSLIB_VERSION@|\""`/usr/bin/svnversion ../..`\""|"" -e ""s|@PSLIB_BRANCH@|\""`/usr/bin/svn info ../.. | /usr/bin/sed -n -e '/URL:/ h' -e '/Repository Root:/ { x; H; x; s|Repository Root: \(.*\)\nURL: \1\(.*\)|\2| ; s|^/|| ; s|/[a-zA-Z]*/src.*|| ; p }'`\""|"" -e ""s|@PSLIB_SOURCE@|\""`/usr/bin/svn info | /usr/bin/sed -n -e 's/Repository UUID: // p'`\""|"" psVersionDefinitions.h.in > psVersionDefinitions.h
svn: Path '../..' ends in '..', which is unsupported for this operation
svn: '.' is not a working copy
}}}
However, the svn messages are in fact a feature of that version mechanism when you compile and exported copy of IPP. Having them in the compile output mislead us into thinking that they were the source of the problem, when in fact the problem was elsewhere. You're free to blame us, of course, but that output from svn could be suppressed, couldn't it?"	enhancement	assigned	low		psconfig	current	trivial