Re: [LogiLogi-list] another hint please

I have posted this response to the LogiLogi list also, as it's better 
to do these issues through the mailing-list, because then other people 
that might run into the same thing, they can get help from it. Would 
you please join the list if not already on there and post questions to
there: http://lists.sourceforge.net/mailman/listinfo/logilogi-list

> Hi Wybo,
>
> If you have a little more time, a clue would be most appreciated.

I looked into it, but 

> 1) I have changed the config.rb to match the template that goes with the  
> latest update, as instructed (in fact as there is a template per  
> version, I check them all and they are not that different)

There should be only one.

> 2) I had svn update
> 3) I drop the db

rake db:initialize also drops the database.

> 4) I then ran
> rake db:initialize RAILS_ENV=production
>
> 5) I counted the number of users (=2), the number of logis (=6)
> So this shows that the db is initialise with basic information

It is then indeed.

> 6) when I go to htpp://logilogi.lirmm.fr
> I get a dump (see attached pdf)

This error is very strange, as it supposes there is no context set.

> 7) I tryed to restart the server by doing  rake server:daemons:restart
> but it failed.  So maybe the new config.rb has not been taken into account.
>
> root@logilogi:/var/www/logilogi/fr/current/lib/tasks# rake  
> server:daemons:restart
> (in /var/www/logilogi/fr/releases/20091021101933)
> cap global:daemons:restart -S stage=production
> rake aborted!
> Command failed with status (127): [cap global:daemons:restart -S  
> stage=produc...]
>
> (See full trace by running task with --trace)
> root@logilogi:/var/www/logilogi/fr/current/lib/tasks# cd ..
> root@logilogi:/var/www/logilogi/fr/current/lib# cd ..
> root@logilogi:/var/www/logilogi/fr/current# svn update
> svn: Expected 'log' to be a directory but found a file
>
> 8)I can see that there is a synchronisation problem but I do not know  
> what version to use to avoid it.

If you want SVN to get the last version for a file, the most sure way
to know you have the latest is deleting all versions, and then do svn
update again. This will restore the file using the newest version.

But it should be noted that getting synchronisation problems with SVN
should not happen unless someone has been editing/updating files on
the server, and it might be a good idea to find out why this was done,
and whether you want to maintain or commit the changes.

So I suggest you do this, then try again, and let me know how it went.
As it is working here.

> Any clues ?

Not beyond this, but I'm happy to help.

Wybo

> Martine

-- 

::Student:
- MA in Digital Humanities at King's College London
- 3 BAs 1st cl. hons in Humanities Computing, History and Philosophy

::Secretary of the Members Council of Goodenough College:
- Room 2150, Goodenough College, Mecklenburgh Square, London WC1N 2AB, UK

::Free Software and Open Source Developer:
- http://www.LogiLogi.org, Cumulative, shared commenting, publication and
                           idea sharing: Philosophy beyond the Book...