Hi,
On Tue, Sep 15, 2015 at 05:26:38PM -0700, Eric Johnson wrote:
>I just checked, and there aren't any open bugs about this.
>Interrupting svnrdump can result in a dump file with not all the files of
>the last commit in the dump record. Accidentally use that dump file to
>load int
> Branko Čibej writes:
>
> > capabilities somewhere in the code. In any case, the documentation (and
> > the implementation) clearly states we should be seeing client
> > capabilities here, so it looks like a bug at first glance.
> It is deliberate: http://svn.haxx.se/dev/archive-2007-11/0347.sht
I just checked, and there aren't any open bugs about this.
Interrupting svnrdump can result in a dump file with not all the files of
the last commit in the dump record. Accidentally use that dump file to load
into a new repository, and the resulting repository will not be a copy of
the original.
Incidentally, I wish there were a "--depth N" parameter to make all that
easier. intermediates and files was not enough from root, and infinity as
too far.
(following on from my message from 16 hrs ago)
I'd make a Jenkins job that ran ...
svn up -q
repoRoot=$(svn info | grep "^URL: " | sed "s/URL: //")
rm -f .branch_mappings
for f in *; do
svn ls "$repoRoot/$f" --depth immediates > .immediates
while read p; do
svn -q log --verbose --stop-on-
Hi all,
I'd like to file a bug in Subversion 1.9.1 and 1.9.0, but I'm not sure if it's
a deliberate behavior.
The problem was not encountered in Subversion 1.7.6, which we used for a long
time.
I didn't find anything concerning this issue in the change log.
Summary:
--
The "svn swit
Hi Bert,
The files that made it into the dump file were complete. It is just that
the last commit in the dump file didn't have all of the files it was
supposed to have.
This may be a deliberate design of the dump file format, but it does mean
that svnrdump is badly broken. Svnrdump should not be
On Tue, Sep 15, 2015 at 10:11:47AM +, Grierson, David wrote:
> > From: wolfgang.zt...@web.de [mailto:wolfgang.zt...@web.de]
> >
> > http://subversion.apache.org/download.cgi#supported-releases:
> > subversion-1.9.1.tar.bz2 2ba78f59b3669e461ef6f56326426918100e2073
> >
> > but sha1sum gives:
> From: wolfgang.zt...@web.de [mailto:wolfgang.zt...@web.de]
>
> http://subversion.apache.org/download.cgi#supported-releases:
> subversion-1.9.1.tar.bz2 2ba78f59b3669e461ef6f56326426918100e2073
>
> but sha1sum gives: 1244a741dbcf24f2b1d165225f0159a0c994e37a subversion-
> 1.9.1.tar.bz2
>
> a
On Tue, Sep 15, 2015 at 11:59:20AM +0200, wolfgang.zt...@web.de wrote:
> Hi,
>
> http://subversion.apache.org/download.cgi#supported-releases:
> subversion-1.9.1.tar.bz2 2ba78f59b3669e461ef6f56326426918100e2073
>
> but sha1sum gives: 1244a741dbcf24f2b1d165225f0159a0c994e37a
> subversion-1
Hi,
http://subversion.apache.org/download.cgi#supported-releases:
subversion-1.9.1.tar.bz22ba78f59b3669e461ef6f56326426918100e2073
but sha1sum gives: 1244a741dbcf24f2b1d165225f0159a0c994e37a
subversion-1.9.1.tar.bz2
all 1.9.1 files, different mirrors checked, yesterday and now.
nobod
Hi,
Paul Hammant wrote:
> If I expand on what you did, I can get the branch mapping like so:
> svn log --verbose --stop-on-copy branchtwo/test.txt | grep " (from "
> Gives:
>
> A /branchtwo (from /branchone:1)
You'll want...
-r1:HEAD -l1
to limit to one log message and...
> Close enough
If I expand on what you did, I can get the branch mapping like so:
svn log --verbose --stop-on-copy branchtwo/test.txt | grep " (from "
Gives:
A /branchtwo (from /branchone:1)
Close enough, but I fear it's not robust.
On Tue, Sep 15, 2015 at 5:21 AM, Stefan Sperling wrote:
> On Tue, Se
On Tue, Sep 15, 2015 at 05:10:30AM -0400, Paul Hammant wrote:
> OK, 'svn copy' makes branches. Most would follow the standard
> trunk/tags/branches model. If you don't though, if you dip your toe into
> the world of creative/arbitrary branch designs, it is not clear how you
> catalog your branch ma
OK, 'svn copy' makes branches. Most would follow the standard
trunk/tags/branches model. If you don't though, if you dip your toe into
the world of creative/arbitrary branch designs, it is not clear how you
catalog your branch mappings. By comparison, Perforce has branch-specs
(which are not perfec
In what way was the dump file incomplete?
Was it broken halfway through a file? (That should have been caught via the
checksums in the file). If a whole node edit is missing it is still a complete
dumpfile and there is no way the current dump doesn’t know when a revision is
done. (This allows e
Branko Čibej writes:
> capabilities somewhere in the code. In any case, the documentation (and
> the implementation) clearly states we should be seeing client
> capabilities here, so it looks like a bug at first glance.
It is deliberate: http://svn.haxx.se/dev/archive-2007-11/0347.shtml
The revi
17 matches
Mail list logo
