You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Petra Langebroek <Pe...@awi.de> on 2010/09/01 10:31:17 UTC

edit log message after commit

Hello,

I am using an relatively old version of subversion (1.3.1) and would like to edit a log file that I already committed to the main repository.
The normal solutions of changing the properties

svn propedit -r N --revprop svn:log URL 

or

svnadmin setlog -r <Rev. Nr> --bypass-hooks <File with log-message> 

dont work, because this version had no "hooks" directory.

Any help is greatly appreciated!

Petra Langebroek

Re: edit log message after commit

Posted by Andy Levy <an...@gmail.com>.
On Wed, Sep 1, 2010 at 11:00, Petra Langebroek <Pe...@awi.de> wrote:
>
> On 1 Sep 2010, at 4:22 PM, Andy Levy wrote:
>
>> Please don't reply directly to me. Use Reply to All to reply to the
>> mailing list.
>>
>> On Wed, Sep 1, 2010 at 09:38, Petra Langebroek <Pe...@awi.de> wrote:
>>>
>>> On 1 Sep 2010, at 3:27 PM, Andy Levy wrote:
>>>
>>> On Wed, Sep 1, 2010 at 06:31, Petra Langebroek <Pe...@awi.de>
>>> wrote:
>>>
>>> Hello,
>>>
>>> I am using an relatively old version of subversion (1.3.1) and would like to
>>> edit a log file that I already committed to the main repository.
>>>
>>> The normal solutions of changing the properties
>>>
>>> svn propedit -r N --revprop svn:log URL
>>>
>>> or
>>>
>>> svnadmin setlog -r <Rev. Nr> --bypass-hooks <File with log-message>
>>>
>>> dont work, because this version had no "hooks" directory.
>>>
>>> Any help is greatly appreciated!
>>>
>>> Subversion has had hook scripts since before 1.3. Why does your
>>> repository not have a "hooks" directory at all? Did you delete it?
>>> What is the *actual* error message you get - please don't just say "it
>>> doesn't work" - there should be a useful error message returned.
>>>
>>>
>>> I have no clue why I don't have this hooks directory, I never deleted it.
>>> Maybe because I did not set up the initial project, only joined an already
>>> existing project, and just "checkout" the project?
>>
>> Hooks are on the server, not in your working copy. They reside in the
>> same directory as the repository.
>
> Ok, maybe that is the problem: my repository is at a website.
>
>>
>>> If I type:
>>> svn propset svn:log "Added wisosw_d as input file" -r65 --revprop
>>> Error:
>>> svn: DAV request failed; it's possible that the repository's
>>> pre-revprop-change hook either failed or is non-existent
>>> svn: At least one property change failed; repository is unchanged
>>> If I type:
>>> svnadmin setlog -r 65 --bypass-hooks newlog.txt
>>> (Where newlog.txt is "Added wisosw_d as input file".)
>>> Error:
>>> svnadmin: Exactly one file argument required
>>
>> What does svnadmin setlog take for parameters (I haven't had 1.3
>> around for years, so I don't recall)? svnadmin help setlog
>
> svnadmin help setlog:
>
> setlog: usage: svnadmin setlog REPOS_PATH -r REVISION FILE
>
> Set the log-message on revision REVISION to the contents of FILE.  Use
> --bypass-hooks to avoid triggering the revision-property-related hooks
> (for example, if you do not want an email notification sent
> from your post-revprop-change hook, or because the modification of
> revision properties has not been enabled in the pre-revprop-change
> hook).
>
> NOTE: revision properties are not historied, so this command
> will permanently overwrite the previous log message.
>
> Valid options:
>  -r [--revision] arg      : specify revision number ARG (or X:Y range)
>  --bypass-hooks           : bypass the repository hook system
>
>
> I tried:
> svnadmin setlog http://aforge.awi.de/svn/echam5iso -r 65 --bypass-hooks newlog.txt
>
> Error:
> svnadmin: 'http://aforge.awi.de/svn/echam5iso' is an URL when it should be a path
>
> Indeed it is an ULR, but I never used a path.

svnadmin can only be used with a local file path. It cannot take URLs.
If you do not have shell access to the server, you can't use svnadmin.

Or you could install a pre-revprop-change hook to allow you to do it
via svn propset --revprop

Re: edit log message after commit

Posted by Petra Langebroek <Pe...@awi.de>.
On 1 Sep 2010, at 4:22 PM, Andy Levy wrote:

> Please don't reply directly to me. Use Reply to All to reply to the
> mailing list.
> 
> On Wed, Sep 1, 2010 at 09:38, Petra Langebroek <Pe...@awi.de> wrote:
>> 
>> On 1 Sep 2010, at 3:27 PM, Andy Levy wrote:
>> 
>> On Wed, Sep 1, 2010 at 06:31, Petra Langebroek <Pe...@awi.de>
>> wrote:
>> 
>> Hello,
>> 
>> I am using an relatively old version of subversion (1.3.1) and would like to
>> edit a log file that I already committed to the main repository.
>> 
>> The normal solutions of changing the properties
>> 
>> svn propedit -r N --revprop svn:log URL
>> 
>> or
>> 
>> svnadmin setlog -r <Rev. Nr> --bypass-hooks <File with log-message>
>> 
>> dont work, because this version had no "hooks" directory.
>> 
>> Any help is greatly appreciated!
>> 
>> Subversion has had hook scripts since before 1.3. Why does your
>> repository not have a "hooks" directory at all? Did you delete it?
>> What is the *actual* error message you get - please don't just say "it
>> doesn't work" - there should be a useful error message returned.
>> 
>> 
>> I have no clue why I don't have this hooks directory, I never deleted it.
>> Maybe because I did not set up the initial project, only joined an already
>> existing project, and just "checkout" the project?
> 
> Hooks are on the server, not in your working copy. They reside in the
> same directory as the repository.

Ok, maybe that is the problem: my repository is at a website.

> 
>> If I type:
>> svn propset svn:log "Added wisosw_d as input file" -r65 --revprop
>> Error:
>> svn: DAV request failed; it's possible that the repository's
>> pre-revprop-change hook either failed or is non-existent
>> svn: At least one property change failed; repository is unchanged
>> If I type:
>> svnadmin setlog -r 65 --bypass-hooks newlog.txt
>> (Where newlog.txt is "Added wisosw_d as input file".)
>> Error:
>> svnadmin: Exactly one file argument required
> 
> What does svnadmin setlog take for parameters (I haven't had 1.3
> around for years, so I don't recall)? svnadmin help setlog

svnadmin help setlog:

setlog: usage: svnadmin setlog REPOS_PATH -r REVISION FILE

Set the log-message on revision REVISION to the contents of FILE.  Use
--bypass-hooks to avoid triggering the revision-property-related hooks
(for example, if you do not want an email notification sent
from your post-revprop-change hook, or because the modification of
revision properties has not been enabled in the pre-revprop-change
hook).

NOTE: revision properties are not historied, so this command
will permanently overwrite the previous log message.

Valid options:
  -r [--revision] arg      : specify revision number ARG (or X:Y range)
  --bypass-hooks           : bypass the repository hook system


I tried:
svnadmin setlog http://aforge.awi.de/svn/echam5iso -r 65 --bypass-hooks newlog.txt

Error:
svnadmin: 'http://aforge.awi.de/svn/echam5iso' is an URL when it should be a path

Indeed it is an ULR, but I never used a path.

"svn info" gives:

Path: .
URL: http://aforge.awi.de/svn/echam5iso
Repository Root: http://aforge.awi.de/svn/echam5iso
etc.



Re: edit log message after commit

Posted by Andy Levy <an...@gmail.com>.
Please don't reply directly to me. Use Reply to All to reply to the
mailing list.

On Wed, Sep 1, 2010 at 09:38, Petra Langebroek <Pe...@awi.de> wrote:
>
> On 1 Sep 2010, at 3:27 PM, Andy Levy wrote:
>
> On Wed, Sep 1, 2010 at 06:31, Petra Langebroek <Pe...@awi.de>
> wrote:
>
> Hello,
>
> I am using an relatively old version of subversion (1.3.1) and would like to
> edit a log file that I already committed to the main repository.
>
> The normal solutions of changing the properties
>
> svn propedit -r N --revprop svn:log URL
>
> or
>
> svnadmin setlog -r <Rev. Nr> --bypass-hooks <File with log-message>
>
> dont work, because this version had no "hooks" directory.
>
> Any help is greatly appreciated!
>
> Subversion has had hook scripts since before 1.3. Why does your
> repository not have a "hooks" directory at all? Did you delete it?
> What is the *actual* error message you get - please don't just say "it
> doesn't work" - there should be a useful error message returned.
>
>
> I have no clue why I don't have this hooks directory, I never deleted it.
> Maybe because I did not set up the initial project, only joined an already
> existing project, and just "checkout" the project?

Hooks are on the server, not in your working copy. They reside in the
same directory as the repository.

> If I type:
> svn propset svn:log "Added wisosw_d as input file" -r65 --revprop
> Error:
> svn: DAV request failed; it's possible that the repository's
> pre-revprop-change hook either failed or is non-existent
> svn: At least one property change failed; repository is unchanged
> If I type:
> svnadmin setlog -r 65 --bypass-hooks newlog.txt
> (Where newlog.txt is "Added wisosw_d as input file".)
> Error:
> svnadmin: Exactly one file argument required

What does svnadmin setlog take for parameters (I haven't had 1.3
around for years, so I don't recall)? svnadmin help setlog

Re: edit log message after commit

Posted by Andy Levy <an...@gmail.com>.
On Wed, Sep 1, 2010 at 06:31, Petra Langebroek <Pe...@awi.de> wrote:
> Hello,
>
> I am using an relatively old version of subversion (1.3.1) and would like to edit a log file that I already committed to the main repository.
> The normal solutions of changing the properties
>
> svn propedit -r N --revprop svn:log URL
>
> or
>
> svnadmin setlog -r <Rev. Nr> --bypass-hooks <File with log-message>
>
> dont work, because this version had no "hooks" directory.
>
> Any help is greatly appreciated!

Subversion has had hook scripts since before 1.3. Why does your
repository not have a "hooks" directory at all? Did you delete it?
What is the *actual* error message you get - please don't just say "it
doesn't work" - there should be a useful error message returned.