>
>
> Posts found on Google suggested that doing an 'svnadmin dump' with an
> older version of svn, and 'svnadmin load'-ing that on a new svn system,
> essentially recreating the repostory from scratch, helps recover from
> this situation which is indeed true.
> This is all nice if a repo has a few
Hello Johan,
Thank you so much for your response! It was incredibly helpful and clear.
You were correct in the fact that my "tar" command was not preserving the
correct modified timestamps. It turns out that the default tar format is GNU,
which only supports timestamp up to a granularity of se
Hello Doug,
On Thu, Jun 16, 2016 at 8:51 PM, Doug Robinson
wrote:
>
> Folks:
>
> Does anyone know if (or when) svnbook.red-bean.com is going to update/support
> SVN 1.9 ? It is still listing SVN 1.7 as "current", SVN 1.8 as "nightly" and
> SVN 1.9 is nowhere to be seen.
We've been working on
On Thu, Jun 16, 2016 at 7:42 PM, Doug Robinson
wrote:
>
> One thing to remember: if revision properties are being changed (i.e. the
> pre-revprop-change hook allows them) then those changes will need to be
> captured and replayed into the loaded repository "somehow" or changes to
> revisions pr
On Jun 16, 2016, at 6:05 AM, Somashekarappa, Anup (CWM-NR) wrote:
> Is the pkgconfig related to apr or apr-util or it is independent of it?
>
> [USER@server subversion-1.9.4]$ make install
> /usr/bin/install -c -d /usr/local/lib /usr/local/share/pkgconfig
> /usr/bin/install: cannot change permi
On Thu, Jun 16, 2016 at 01:51:08PM -0400, Doug Robinson wrote:
> Folks:
>
> Does anyone know if (or when) svnbook.red-bean.com is going to
> update/support SVN 1.9 ? It is still listing SVN 1.7 as "current", SVN 1.8
> as "nightly" and SVN 1.9 is nowhere to be seen.
>
> Thank you.
>
> Doug
> --
Folks:
Does anyone know if (or when) svnbook.red-bean.com is going to
update/support SVN 1.9 ? It is still listing SVN 1.7 as "current", SVN 1.8
as "nightly" and SVN 1.9 is nowhere to be seen.
Thank you.
Doug
--
*DOUGLAS B. ROBINSON* SENIOR PRODUCT MANAGER
*T *925-396-1125
*E* doug.robin...@w
One thing to remember: if revision properties are being changed (i.e. the
pre-revprop-change hook allows them) then those changes will need to be
captured and replayed into the loaded repository "somehow" or changes to
revisions prior to -rNEXTREV will be lost.
On Thu, Jun 16, 2016 at 6:49 AM, Joh
On 6/16/2016 1:05 PM, Somashekarappa, Anup (CWM-NR) wrote:
Hello,
Is the pkgconfig related to apr or apr-util or it is independent of it?
Maybe someone else who's more familiar with building SVN on Linux can
provide you some more details on this. From the install doc it's
suggested that pkg-
Quoting Johan Corveleyn (jcor...@gmail.com):
> > 2) svnadmin dump -M 1024 OLDREPOS | svnadmin load -M 1024 NEWREPOS
> I forgot that you might have to use the "old svnadmin" from the old
> svn version that can still read your repository, on the 'svnadmin
> dump' side, to fix your corruption problem
Hello,
Is the pkgconfig related to apr or apr-util or it is independent of it?
[USER@server subversion-1.9.4]$ make install
/usr/bin/install -c -d /usr/local/lib /usr/local/share/pkgconfig
/usr/bin/install: cannot change permissions of `/usr/local/share/pkgconfig': No
such file or directory
mak
On Thu, Jun 16, 2016 at 12:49 PM, Johan Corveleyn wrote:
...
> To be precise, your commands might be:
>
> 1) svnadmin create NEWREPOS
> (maybe create it on a ramdisk)
> 2) svnadmin dump -M 1024 OLDREPOS | svnadmin load -M 1024 NEWREPOS
> (initial dump+load; you might want to pass -q to dum
>> You should rather let the computer spend some time dealing with the dump
>> and load process, instead of spending your own time working around problems
>> and not even knowing if the result of your workarounds will be OK.
>
> Will have to plan a maintenance window then.
> Gah. :)
You can do thi
On Thu, Jun 16, 2016 at 01:08:37PM +0300, Evgeny Kotkov wrote:
> Sander Smeenk writes:
>
> >> Can you run 'svnadmin info' (exists as of 1.9) on the old (non-upgraded)
> >> repository and show the output? That will give us details about its format.
> >
> > The output is as follows:
> >
> > | % svn
Sander Smeenk writes:
>> Can you run 'svnadmin info' (exists as of 1.9) on the old (non-upgraded)
>> repository and show the output? That will give us details about its format.
>
> The output is as follows:
>
> | % svnadmin info foo
> | Path: foo
> | UUID: d7ac1088-da18-0410-849e-888fbd42cb43
> |
On Thu, Jun 16, 2016 at 11:49:32AM +0200, Sander Smeenk wrote:
> Quoting Stefan Sperling (s...@elego.de):
> > Can you run 'svnadmin info' (exists as of 1.9) on the old (non-upgraded)
> > repository and show the output? That will give us details about its format.
>
> The output is as follows:
>
>
Quoting Stefan Sperling (s...@elego.de):
> > I fear that running 'svnadmin upgrade' on the repositories will break
> > compatibiltiy with older (though not 2006-old) SVN-clients
> No, it won't. As long as older clients access the repository over the
> network (i.e. not via file:// URLs) there will
On Thu, Jun 16, 2016 at 10:51:27AM +0200, Sander Smeenk wrote:
> Trying to do a new checkout of the old repository also results in this error
> message:
> | % svn co file:///svnroot/foo newcheckout
> | svn: E125012: Invalid character in hex checksum
>
> The issue 'thus' lies in the repository its
Hi,
I'm having a challenge with subversion and old(er) repositories.
I'm currently running svn 1.9.3 (r1718519) but the repositories were
created back in june 2006, i'm not sure what the svn version was back
then.
I had an old local checkout which i had to 'upgrade':
| % svn up
| svn: E155036: Pl
Hi,
Brandon Eusebio wrote:
> I am trying to move/copy a Subversion (version 1.8.10) working copy
> from one linux machine to another.
[...]
> however the performance of svn operations becomes drastically slower.
Are the machines software identical w.r.t. svn and it's dependencies?
In particular,
On Wed, Jun 15, 2016 at 11:36 PM, Brandon Eusebio wrote:
> Hello,
>
>
>
> I am trying to move/copy a Subversion (version 1.8.10) working copy from one
> linux machine to another. From researching similar questions/answers, this
> seems possible by simply moving the entire folder (along with the .s
21 matches
Mail list logo
