[jira] [Closed] (SVN-3062) svnmerge doesn't warn when permission is denied for a path

["Daniel Sahlberg (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SVN-3062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel Sahlberg closed SVN-3062.
--------------------------------
    Resolution: Won't Fix

Described in dev@ by Johan Corveleyn ([https://lists.apache.org/thread/2w1o5dzqbpbg5rjbbwltcnf7m535zmg2):]

 

[close as "invalid"], or as "won't fix", because svnmerge.py is part of contrib, and
contrib is not supported anymore (not by the Subversion community
anyway) – and in any case svnmerge.py is deprecated I think. IIRC,
svnmerge.py was a script that did some form of merge tracking, before
the core implementation arrived in Subverison 1.5.

Out of curiosity I've taken a quick look in its documentation: the
README ([https://svn.apache.org/repos/asf/subversion/trunk/contrib/client-side/svnmerge/svnmerge.README])
refers to a wiki page that still exists:
[https://www.orcaware.com/svn/wiki/Svnmerge.py]. That page contains a
FAQ entry:
[[[
How do I migrate from svnmerge.py to Subversion 1.5's Merge Tracking?
Use svnmerge-migrate-history.py to convert the merge history written
by svnmerge.py into Subversion 1.5's format.
]]]

In any case I think it's pretty OK to close all outstanding issues
about svnmerge.py.

> svnmerge doesn't warn when permission is denied for a path
> ----------------------------------------------------------
>
>                 Key: SVN-3062
>                 URL: https://issues.apache.org/jira/browse/SVN-3062
>             Project: Subversion
>          Issue Type: Bug
>          Components: contrib/svnmerge.py
>    Affects Versions: 1.4.x
>            Reporter: Subversion Importer
>            Assignee: Blair Zajac
>            Priority: Major
>             Fix For: nonblocking
>
>
> {noformat:nopanel=true}
> svnmerge doesn't warn/throw-error when we try to merge a branch (source) for
> which the user has no read permission. In my case, a subdirectory of the
> "branch" being merged didn't have read permission and svnmerge didn't complain
> anything. In fact, svnmerge silently ignored that "subdirectory" and merged the
> rest. It looked like the merge was successful.
> I feel that svnmerge should throw an error in this case and stop proceeding
> further (It should be considered FATAL). Currently the only way to find out that
> this has happened is to search the svnmerge-commit-message.txt for "no author"
> pattern.
> eg.
> ........
>   r4455 | (no author) | (no date) | 1 line
> ........
> Version Information:
> svnmerge r21994
>   modified: 2006-10-17 06:52:10 +0000 (Tue, 17 Oct 2006)
> Copyright (C) 2004,2005 Awarix Inc.
> Copyright (C) 2005, Giovanni Bajo
> ---
> svn, version 1.4.3 (r23084)
>    compiled Oct 15 2007, 08:39:54
> Copyright (C) 2000-2006 CollabNet.
> {noformat}
> Original issue reported by *santhoshmani*



--
This message was sent by Atlassian Jira
(v8.20.1#820001)