Re: [viewvc-users] CVSDB

Michael, 
Yet another question...

what if I dont populate the ViewVC db and rely on the hook scripts both for cvs and svn. I mean this way if the users wont wish to use the query feature i will not use disc space. Of course on the other hand the first commit with the loginfohandler script will take some time.

So will the hooks work if there is empty database? I mean will they added old commits to the database?

Rgs,

Tair.

On 3/30/07, Tair Assimov <Tair@xxxxxxxxxxx> wrote:

Hi!

Thanks for the help. I have fixed this.

The problem is that we have repositories under chroot jail. But the viewvc web root is out of jail. So when the trigger script logs the info to db from the jail, it uses the path relative to jail root. Which is of course not shown in Viewvc interface because it uses the real paths.

Rgs,

Tair.

On 3/29/07, Tair Assimov < Tair@xxxxxxxxxxx> wrote:

Hello!

On 3/28/07, C. Michael Pilato < cmpilato@xxxxxxxxxx> wrote:

Tair Assimov wrote:
> Thanks for reply...
> What I wanted to verify is which options I have to use in hooks so that
> the script makes less operations and brings less overhead. As far as I
> understood from the document:
>
> svndbadmin update -> Updates only the non logged commits
> svndbadmin rebuild -> Rebuilds all the information related to provided REPO

In 1.0.x:

   svndbadmin rebuild -> updates all commits
   svndbadmin rebuild REV -> updates a specific commit
   svndbadmin update -> updates only the non-logged commits
   svndbadmin update REV -> updates only a specific non-logged commit

In trunk/1.1.x:

   svndbadmin rebuild -> updates all commits
   svndbadmin rebuild REV -> [ERROR, with suggestion to use update --force]
   svndbadmin update -> updates only the non-logged commits
   svndbadmin update REV -> updates only a specific non-logged commit
   svndbadmin update REV --force -> updates a specific commit

As you can see, in the 1.0.x line, there's really no reason to use
'svndbadmin update' at all.  You can use 'rebuild' the first time you setup
your repository, and then use 'rebuild REV' in your post-commit and
post-revprop-change hooks.

Got it; We use 1.0.x, so we should be using the svndbadmin update REV in the hook.
 

In 1.1.x, though, you still use rebuild to get your initial revisions into
the database.  But in your hooks you use 'update' and/or 'update --force'.

> What could be the problem in this situation:
>
> I am running CVS repositories from CHROOT jail. So I had to tweak mysql
> to make it work in there by using MySQL network connection. Though I had
> also to symlink the socket as ViewVC uses it. So when I do the commit,
> the loginfo-handler script successfully executes and I can see all the
> information about commit in the database. So, when I do the query in the
> web browser, the ViewVC says that there were no changes, even though all
> the info is in db. When I issue "cvsdbadmin update" everything is
> displayed (of course it should as it parses the CVS history). Do you
> know what causes the ViewVC query interface not to notice the
> information from the db? What cvsdbamin makes different to loginfo-handler?
>
> I would be very greatful if anyone could help on this issue,

It it a cache problem?  I mean, are you sure ViewVC isn't seeing the commits
upon asking, or is it not asking because your browser has cached the page of
empty results?

I dont think its a cache problem, as I even close the browser and do the query again. What is the way to debug in this case?
 

--
C. Michael Pilato < cmpilato@xxxxxxxxxx >
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand

Thanks,

Tair.