On Tue, Jan 7, 2025 at 10:48 AM Bo Berglund <bo.bergl...@gmail.com> wrote: ... > I have also checked the commit emails for this repo and those show another set > of commits done for revs 4519 to 4528 between 2024-08-14-2024-12-01, which is > where the mirror should be now. But isn't.... > > > Command svn info on the *main server* shows this: > > Repository Root: https://agiengineering/svn/pc > Repository UUID: 1e489663-c639-2248-90da-e976bc628839 > Revision: 4518 > Node Kind: directory > Last Changed Author: bosse > Last Changed Rev: 4518 > Last Changed Date: 2023-12-05 04:12:11 -0600 (Tue, 05 Dec 2023)
Shouldn't this be at revision 4528 by now (given your explanation above), with a Last Changed Date somewhere in 2024? So your main server is also (a year) behind? Where did those revisions between 4519 and 4528 land then? > And the same mirror repo that should have been synced to the mirror server > many > time during the fall: > > Repository Root: https://svn.mydomain.com/svn/pc > Repository UUID: e8e82d8e-9267-4f7b-8f11-ddd3f99e352f > Revision: 4498 > Node Kind: directory > Last Changed Author: bosse > Last Changed Rev: 4498 > Last Changed Date: 2023-03-28 20:59:05 +0200 (Tue, 28 Mar 2023) Strange indeed. Now, to eliminate all possible confusion of whether you are looking at a working copy (which might not be fully up to date) instead of the repository, I would suggest running 'svnadmin info $REPOS_PATH' or 'svnlook youngest $REPOS_PATH' on the server, instead of 'svn info $URL'. Probably will give you the same information, but can't hurt to doublecheck that way. -- Johan
