Haven't read the whole thread, but the problem here has to do with r81.
r80 moved fine and I expect `svnlook youngest dest` = 80.
If the source repos has authz set up or has undergone history surgeries
that's likely related.
You could try running:
% svnserve --log-file=foo.log -dr.
% svnsync sync
- Original Message -
From: Giulio Troccoli
> Why is it showing files in trunk when you're log command is for
> branches/working ? Or have you just pasted the wrong command?
Nope, that's the command. I mean, it *is* the log, so... shouldn't it?
The commands for trunk and
On 02/04/12 13:16, Gary wrote:
- Original Message -
From: Giulio Troccoli
On 02/04/12 11:51, Gary wrote:
- Original Message -
From: Giulio Troccoli
On 02/04/12 11:10, Gary wrote:
- Original Message -
From: Giulio Troccoli
On 02/04/12 10:24, Gary wrote:
that still doesn
- Original Message -
From: Giulio Troccoli
On 02/04/12 11:51, Gary wrote:
> - Original Message -
> From: Giulio Troccoli
> On 02/04/12 11:10, Gary wrote:
>> - Original Message -
>> From: Giulio Troccoli
>>> On 02/04/12 10:24, Gary wrote:
> that still doesn't explain to m
On 02/04/12 11:51, Gary wrote:
- Original Message -
From: Giulio Troccoli
On 02/04/12 11:10, Gary wrote:
- Original Message -
From: Giulio Troccoli
On 02/04/12 10:24, Gary wrote:
that still doesn't explain to me why svnsync barfs on those (not)
missing revisions. Looking at t
- Original Message -
From: Giulio Troccoli
On 02/04/12 11:10, Gary wrote:
> - Original Message -
> From: Giulio Troccoli
>> On 02/04/12 10:24, Gary wrote:
that still doesn't explain to me why svnsync barfs on those (not)
missing revisions. Looking at the command line histo
On 02/04/12 11:10, Gary wrote:
- Original Message -
From: Giulio Troccoli
On 02/04/12 10:24, Gary wrote:
This is perhaps better:
$ svn log svn://devel.//
[snip]
r84 | gpspbu | 2011-06-24 12:52:16 +0200 (Fri, 24 Ju
- Original Message -
From: Giulio Troccoli
> On 02/04/12 10:24, Gary wrote:
>> This is perhaps better:
>>
>> $ svn log svn://devel.//
>> [snip]
>>
>> r84 | gpspbu | 2011-06-24 12:52:16 +0200 (Fri, 24 Jun 2011) | 1 lin
Am 02.04.2012 11:39, schrieb Gary:
> See my other email, I got the svn log command wrong, and the branch
> *is* still available, just can't be modified any more. The question
> is, why svnsync gets its knickers into a twist about that. The
> revisions *are* available (and can be checked out, I chec
From: Ulrich Eckhardt
>> I imagine they are/were in a branch, which AFAIK is no longer
>> available. Is there any way to get around this? Assuming that's
>> the problem, of course.
>
> Do you know more about this branch and how it was removed? Just "svn
> delete"ing a branch doesn't cause revision
On 02/04/12 10:24, Gary wrote:
From: Giulio Troccoli
On 02/04/12 08:27, Gary wrote:
- Original Message -
From: Henrik Sundberg
Do you have a precommit hook now that was not there when revs 81-82
were committed?
There are no hooks as far as I know. (I'm not an admin, and the admin is
From: Giulio Troccoli
On 02/04/12 08:27, Gary wrote:
>> - Original Message -
>> From: Henrik Sundberg
>>
>>> Do you have a precommit hook now that was not there when revs 81-82
>> were committed?
>> There are no hooks as far as I know. (I'm not an admin, and the admin is not
>> very forthc
Am 30.03.2012 15:25, schrieb Gary:
> I see a lot of reports of this error, but little in the way of
> clear information as to what it might mean, or how to fix it:
>
> $ svnsync sync file://`pwd`/dest
> Committed revision 1.
> Copied properties for revision 1.
> Transmitting file data
On 02/04/12 08:27, Gary wrote:
- Original Message -
From: Henrik Sundberg
Do you have a precommit hook now that was not there when revs 81-82
were committed?
There are no hooks as far as I know. (I'm not an admin, and the admin is not
very forthcoming on.. well, anything, really).
- Original Message -
From: Henrik Sundberg
> Do you have a precommit hook now that was not there when revs 81-82
were committed?
There are no hooks as far as I know. (I'm not an admin, and the admin is not
very forthcoming on.. well, anything, really).
> Svn log will show the revisions
Do you have a precommit hook now that was not there when revs 81-82
were committed?
Svn log will show the revisions whereever in the repository they were
made. Are they missing for real?
/$
On Fri, Mar 30, 2012 at 15:25, Gary wrote:
> I see a lot of reports of this error, but little in the way of
16 matches
Mail list logo
