Nico Kadel-Garcia wrote on Sat, Apr 28, 2012 at 21:38:59 -0400:
> On Sat, Apr 28, 2012 at 5:27 PM, Daniel Shahaf wrote:
>
> > Nico Kadel-Garcia wrote on Sat, Apr 28, 2012 at 16:56:54 -0400:
> > > If you're up for some testing, there are tools I've submitted to
> > Repoforge
> > > for building 1.6.
On Sat, Apr 28, 2012 at 5:27 PM, Daniel Shahaf wrote:
> Nico Kadel-Garcia wrote on Sat, Apr 28, 2012 at 16:56:54 -0400:
> > If you're up for some testing, there are tools I've submitted to
> Repoforge
> > for building 1.6.18 and 1.7.4 over at http://www.github.com/nkadel/ All
> the
> > patches and
Nico Kadel-Garcia wrote on Sat, Apr 28, 2012 at 16:56:54 -0400:
> If you're up for some testing, there are tools I've submitted to Repoforge
> for building 1.6.18 and 1.7.4 over at http://www.github.com/nkadel/ All the
> patches and .spec files for building the RPM's, compatble for RHEL 4, 5,
> and
If you're up for some testing, there are tools I've submitted to Repoforge
for building 1.6.18 and 1.7.4 over at http://www.github.com/nkadel/ All the
patches and .spec files for building the RPM's, compatble for RHEL 4, 5,
and 6. You could rsync the repository to a new environment, build and
insta
Can you post a transcript of your shell session, starting from a fresh
checkout, and including the `svn status` output both before and after
running 'svm delete'? What version of svn are you using? Have you
tried 'svn commit' without any other arguments?
nut wrote on Fri, Apr 27, 2012 at 11:36:5
As to "how could I know this" --- *_tests.py take a --help option,
which lists --bin in its output.
*_tests.py look by default for svn in ../../svn/svn --- i.e., build
outputs. Are you running from a built source tree? If not, pass
--bin=/usr/bin.
