[immodule-qt] svn repository malfunction
yamaken at bp.iij4u.or.jp
Wed Sep 8 18:49:15 EEST 2004
I've completed the recovery of our svn repository! The database
is cleanly restored from svn dump. Both svn+ssh and http access
are now available. Let's restart active development.
I'll release new unified patch once some issues have been
The next release involves some API change to make plugins source
compatible with Qt4. The changes are already committed. See
qinputcontext.h and commit log. Developers, commit your changes
for next release.
Cougar, please denote following info when you commit a code to
share development status, in GNU ChangeLog style or your
favorite. I'm using a variant of GNU style because pure GNU
style is hard to read for me.
- which file is modified
- which function is modified
At Wed, 08 Sep 2004 03:34:11 +0900,
yamaken at bp.iij4u.or.jp wrote:
> At Wed, 08 Sep 2004 01:55:30 +0900,
> yamaken at bp.iij4u.or.jp wrote:
> > At Wed, 08 Sep 2004 00:41:18 +0900,
> > yamaken at bp.iij4u.or.jp wrote:
> > > I'm monitoring the repository status since after Daniel had
> > > killed the blocking apache2 processes. Once required information
> > > has been acquired from the monitoring, I'll do next step to
> > > resurrect our repository.
> > I've finished the monitoring. In fact, our repository database
> > requires a improper surgery.
> > I had seen no processes are accessing to /svn/immqt/db/__db.001
> > just a few minutes ago by fuser(1), but I couldn't access the
> > database by neither svn nor db_deadlock. It indicates that the
> > locker of the mutex in the file is already died without freeing
> > the mutex. There is no way to free the mutex in proper way, at
> > least in my knowledge.
> > I'll try the surgery to dump our repository data from a live
> > copy of the repository database.
> Successfully done!
> Developers, please back up following file. This is lifeline of
> Wait for repository reconstruction.
YamaKen yamaken at bp.iij4u.or.jp
More information about the immodule-qt