Hi Richard,
fossil version reports:
[d090292800] 2010-08-05 10:09:43 UTC
The strange thing is that if I use fossil at home (I am working on a
laptop), it works fine, but then it is not plugged into the network.
If I use fossil at work (with the laptop connected to the local
network), it
Hi Saul,
see my reply to Richard Hipp: it has something to do with the network
that the laptop I am using is connected to or not.
Regards,
Arjen
On 2010-08-23 17:56, saulgo...@flashingtwelve.brickfilms.com wrote:
Quoting Arjen Markus arjen.mar...@deltares.nl:
Hi,
some further
Hi,
some more information:
If I try to create a completely new repository, the repository itself
is created, but I get the same error message. That is, when the laptop
is connected to the local network.
I have seen another strange thing with this laptop that may be
related - it is unable to
Hi,
the problem has been solved, thanks to Sergey Sfeli in a private mail.
It turns out that the environment variables HOMEDRIVE and HOMEPATH are
pointing to an unuseable path. If I set them to a local disk and
directory, fossil does its job without complaints.
Regards,
Arjen
On 2010-08-24
Hello,
I have got an answer to my first question now (logging in as a different
user), but it turns out that my fossil database has been corrupted.
That is: whatever I do I get a message SQLITE_CANTOPEN (at line 31151)
from fossil.
I can see the Wiki, but I can not commit, add, open, ...
Any
Please run
sqlite3 repository-name.fossil 'pragma integrity_check'
on your repository database file and post the results.
On Mon, Aug 23, 2010 at 7:30 AM, Arjen Markus arjen.mar...@deltares.nlwrote:
Hello,
I have got an answer to my first question now (logging in as a different
user),
Hi Richard,
odd, sqlite3 reports ok, but fossil comes up with:
fossil: SQLITE_CANTOPEN: cannot open file at line 31151 of [fbe70e1106]
fossil: unable to open database file
If you have recently updated your fossil executable, you might
need to run fossil all rebuild to bring the repository
On Mon, 23 Aug 2010 15:21:41 +0200
Arjen Markus arjen.mar...@deltares.nl wrote:
Hi Richard,
odd, sqlite3 reports ok, but fossil comes up with:
fossil: SQLITE_CANTOPEN: cannot open file at line 31151 of
[fbe70e1106] fossil: unable to open database file
Check file chmod if you're under
Hi,
some further information: I am cooperating in this project with Torsten
Berg and he was able to handle the repository I was not. He made a few
changes, sent it back and ... I can not handle the new one either!
I have no idea what is going wrong. Maybe restart the computer and
try again?
Hi,
restarting the computer made no difference whatsoever.
Regards,
Arjen
On 2010-08-23 16:51, Arjen Markus wrote:
Hi,
some further information: I am cooperating in this project with Torsten
Berg and he was able to handle the repository I was not. He made a few
changes, sent it back and
Are you using the latest version of Fossil? What does fossil version tell
you?
On Mon, Aug 23, 2010 at 10:51 AM, Arjen Markus arjen.mar...@deltares.nlwrote:
Hi,
some further information: I am cooperating in this project with Torsten
Berg and he was able to handle the repository I was not.
Quoting Arjen Markus arjen.mar...@deltares.nl:
Hi,
some further information: I am cooperating in this project with Torsten
Berg and he was able to handle the repository I was not. He made a few
changes, sent it back and ... I can not handle the new one either!
I have no idea what is going
I was assuming (and my limited experience suggested) that the user
that starts the server needs to have write access to the repository if
commits are to be accepted (even if from syncing a clone). So if I
(saul) wanted to commit changes to a repository created by David, I
would have to
13 matches
Mail list logo
