www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tony Stevenson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-6236) r1362927: svn.us != svn.eu
Date Wed, 30 Jul 2014 15:07:39 GMT

    [ https://issues.apache.org/jira/browse/INFRA-6236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14079350#comment-14079350
] 

Tony Stevenson commented on INFRA-6236:
---------------------------------------

Via Philip Martin [~philipm]

On the master I see a text change to one file and an svn:mergeinfo 
change on one directory. The slave revision has the revision properties 
svn:log, svn:date and svn:author but does not have the versioned text or 
svn:mergeinfo change. I wonder how that happened? r1362927 is from 
2012-07-18, do you know which version of Subversion was in use at that 
time? 

To fix via svnsync there is no need to start from scratch, instead 
backdate the slave to a revision before r1362927 and resync: 

- stop apache from serving the slave repository 
- delete the revision files (or pack files) from r1362927 onward 
- use an editor to rewrite db/current 
- run "svnadmin recover" 
- use "svn ps --revprop -r0" to reset svn:sync-last-merged-rev 
- allow apache to serve the slave repository 
- run svnsync (about 250,000 revisions) 

The slave will be out-of-date until the sync completes so will not be 
much use to users. Perhaps it would be possible to redirect svn.eu to 
svn.us while this operation is in progress? 

It is possible to do the operation on a copy of the slave repository and 
keep the existing slave repository online but this requires doing 
somthing to ensure that revprop changes made on the master during the 
svnsync get to the copy. 



> r1362927: svn.us != svn.eu
> --------------------------
>
>                 Key: INFRA-6236
>                 URL: https://issues.apache.org/jira/browse/INFRA-6236
>             Project: Infrastructure
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Subversion
>            Reporter: Julian Reschke
>            Priority: Critical
>              Labels: #bugbash
>
> r1362927 is empty on svn.eu (not even a new root noderev) but not-empty on svn.us.  Investigate
why that happens, upstream to Subversion project, fix on our end.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message