[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: show log issue

From: Anto Marky <markysvn_at_gmail.com>
Date: Tue, 14 Oct 2008 20:27:40 +0530

Hi Karl,

Sorry to bother you again, I went through the two links you sent and some
other links got googling but still unable to get them.These are the things I
did

First I tried by just copying the pre-revprop-change.tmpl to
pre-revprop-change and assigned executable permission to the file and then I
did a commit and then then I tried svn log but still got the same out put

> ------------------------------
------------------------------------------
> > > r2 | (no author) | (no date) | 1 line
> > >
> > >
> > >
>
------------------------------------------------------------------------
> > > r1 | (no author) | (no date) | 1 line

Then I copied all the tmpl files to files without the tmpl extension and
tried a commit from TSVN there I got the error

Commit
D:\New Folder (3)\New Folder
Commit failed (details follow):
Commit blocked by start-commit hook (exit code 1) with output:
/home/svn/BLE_REPOS/hooks/start-commit: line 61: commit-allower.pl: command
not found

As it said an error in commit-allower.pl I added user to the script and the
path to the repository but still I got the same error.

Then I removed all other scripts from the hooks director except the
pre-revprop-change and added the svn path and users to it but still getting
no extra output than the

> > > r2 | (no author) | (no date) | 1 line
> > >
> > >
> > >
> ------------------------------
------------------------------------------
> > > r1 | (no author) | (no date) | 1 line

older log.

As I am zero in scripting I didn't know what to do.

Kindly help me sort this issue.

Thanks and Regards

Marky

On Tue, Oct 14, 2008 at 7:05 PM, Karl Fogel <kfogel_at_red-bean.com> wrote:

> "Anto Marky" <markysvn_at_gmail.com> writes:
> > This is the output for the command.
> >
> > [root_at_testmachine ~]# svn proplist -v --revprop -r1 svn://192.168.1.250/
> > BLE_REPOS/
> > Unversioned properties on revision 1:
> > [root_at_testmachine ~]# svn proplist -v --revprop -r2 svn://192.168.1.250/
> > BLE_REPOS/
> > Unversioned properties on revision 2:
>
> Well, that's the problem. To have an author, there must be an
> "svn:author" revision property (revprop); to have a log message, there
> must be an "svn:log" revprop; to have a date, there must be an
> "svn:date" revprop.
>
> You can set those revprops manually; the TortoiseSVN manual should say
> how, but note that the repository administrator may need to enable the
> 'pre-revprop-change' hook:
>
>
> http://svnbook.red-bean.com/nightly/en/svn.ref.reposhooks.pre-revprop-change.html
>
> To learn more about revprops in general, see
>
> http://svnbook.red-bean.com/nightly/en/svn.ref.properties.html
>
> ...which contrasts versioned (regular) properties with unversioned
> (revision) properties. I know that may sound confusing, but it makes
> more sense when you read the above URL :-).
>
> -Karl
>
> > Thanks for your support.
> >
> > Marky
> >
> > On Tue, Oct 14, 2008 at 6:35 PM, Karl Fogel <kfogel_at_red-bean.com> wrote:
> >
> > "Anto Marky" <markysvn_at_gmail.com> writes:
> > > The repository is not public, it is not possible for me to make it
> > > public even for testing at this point of time.Are you able to find
> any
> > > mistake I doing? If needed I can give my work around step by step.
> >
> > Well, if you can run the command-line client, please do this:
> >
> > svn proplist -v --revprop -r1 URL_TO_YOUR_REPOSITORY
> >
> > and
> >
> > svn proplist -v --revprop -r2 URL_TO_YOUR_REPOSITORY
> >
> > and show us the outputs.
> >
> > -Karl
> >
> > > On Tue, Oct 14, 2008 at 4:51 PM, Karl Fogel <kfogel_at_red-bean.com>
> wrote:
> > >
> > > "Anto Marky" <markysvn_at_gmail.com> writes:
> > > > When I try from my CLI i get this output
> > > >
> > > >
> >
> ------------------------------------------------------------------------
> > > > r2 | (no author) | (no date) | 1 line
> > > >
> > > >
> > > >
> >
> ------------------------------------------------------------------------
> > > > r1 | (no author) | (no date) | 1 line
> > > >
> > > > I am using svn://svn co to checkout.
> > > >
> > > > I am trying to figure this out for more than a week still not
> able
> > to
> > > solve
> > > > this issue.
> > >
> > > Is this repository public? Can you share the URL here?
> > >
> > > -Karl
> > >
> > > > On Tue, Oct 14, 2008 at 12:28 AM, Ryan Schmidt <
> > > subversion-2008c_at_ryandesign.com
> > > >> wrote:
> > > >
> > > > On Oct 13, 2008, at 04:17, Anto Marky wrote:
> > > >
> > > >
> > > > I have been posting requests to sort a log issue for
> couple
> > of
> > > week, My
> > > > problem is still not sorted out in my production
> box.But I
> > think
> > > I am
> > > > somwhere near in sorting the issue in my test box,
> when I
> > click
> > > show
> > > > log my log window shows some active changes like
> this.
> > > >
> > > > >From 1/1/1970 to 1/1/1970
> > > >
> > > > Revision: Actions Author:
> > Date:
> > > > Message:
> > > > 1
> > > (no
> > > > date)
> > > > 2
> > > (no
> > > > date)
> > > > 3
> > > (no
> > > > date)
> > > > 4
> > > (no
> > > > date)
> > > >
> > > > It dosent have any information other than the
> revision
> > number,
> > > ant date
> > > > from and to is a 1970 date, does somebody know what
> the
> > problem
> > > is?
> > > >
> > > >
> > > > When you say "click" that means you must be using a GUI,
> right?
> > > TortoiseSVN
> > > > perhaps, or some other GUI? This list is for the core
> > Subversion
> > > libraries
> > > > and the command-line client. Try "svn log
> your://repository/
> > url" and
> > > see if
> > > > you get the same problem. If so, show us the output, and
> tell
> > us what
> > > > version of Subversion you have and what repository access
> > protocol
> > > you're
> > > > using and how the server is set up; if not, ask on the
> mailing
> > list
> > > for
> > > > whatever GUI you're using.
>
Received on 2008-10-14 16:58:14 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.