[fossil-users] Unable to open database file
I am following quick start guide and did the following to setup fossil
server and accessing it from a different client machine.
My server setup...
OpenBSD apache(1.3) chrooted to /var/www
Fossil compiled with -static for self-contained executable.
Fossil version - This is fossil version [34c23c6fd4] 2011-03-10 02:39:51 UTC
/var/www/users/bob# fossil new foo.fossil
project-id: b20f07ffc2ef5e984a897140cdba4a7f24738dbc
server-id: 1fa3c53148d66df4fd0fd023a0bd14d24aba48d0
admin-user: root (initial password is faf36a)
/var/ww/users/bob# ls -la foo.fossil
-rw-rw-rw-- 1 root daemon 53248 Mar 10 05:34 foo.fossil
Fossil cgi-script...
#!/usr/local/bin/fossil
repository: /users/bob/foo.fossil
/var/www/users/bob# fossil ui foo.fossil
Enable check-in, developer previleges for Nobody
client setup...
~/repo fossil clone http://server/cgi-bin/fossil.cgi foo.fossil
Bytes Cards Artifacts Deltas
Sent: 53 1 0 0
Received: 342 4 1 0
Sent: 680 28 0 0
Received: 674 2 0 0
Total network traffic: 645 bytes sent, 0 bytes received
Rebuilding repository meta-data...
100.0% complete...
project-id: 2424ed10afd0e33e443f1e1ff6a03db57cf6ccaf
server-id: 3b1e2f3fac32ead5037c363ca8a862d734921110
~/foo fossil open ~/repo/foo.fossil
~/foo fossil add blah.c
ADDED blah.c
~/foo fossil commit
Autosync: http://server/cgi-bin/fossil.cgi
Bytes Cards Artifacts Deltas
Sent: 130 1 0 0
Received: 78 1 0 0
Total network traffic: 272 bytes sent, 0 bytes received
/usr/bin/vi /Users/bob/check2/ci-comment-8DA095CBF89A.txt
New_Version: 25499957d937adc4b05885dc2629e5e7324e69b6
Autosync: http://server/cgi-bin/fossil.cgi
Bytes Cards Artifacts Deltas
Sent: 809 7 2 0
**Error: Database error: unable to open database file**
INSERT INTO rcvfrom(uid, mtime, nonce, ipaddr)VALUES(3, julianday('now'), NULL,
'xxx.248.84.92')
Received: 163 1 0 0
Total network traffic: 533 bytes sent, 0 bytes received
fossil: Autosync failed
~/foofossil pull
Server:http://server/cgi-bin/fossil.cgi
Bytes Cards Artifacts Deltas
Sent: 146 2 0 0
Received: 94 2 0 0
Total network traffic: 288 bytes sent, 0 bytes received
Am I doing something wrong here. How come pull is sucessfull while
sync/commit/push fail (Database error: unable to open database file).
thanks,
Sunil.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] adding js to themes
Awesome I'll test it using adding the js to the header ! 2011/3/8 Ron Wilson ronw.m...@gmail.com On Tue, Mar 8, 2011 at 11:37 PM, Federico Ramallo frama...@gmail.com wrote: I've been trying to add a js file but the theme only consider CSS, header and footer... I added as a file on the on the code, but is just a workaround. I checked skins.c file, but couldn't understand how it works to add a javascript.js file in the config table any ideas? How hard would be to implement that? That way when we export / import a skin we include a javascript file I suppose that can have a few advantages, but putting the Javascript in as a file makes it much easier to handle revisioning of it. In a pinch, Javascript could be put in-line in the header, though that does make the header harder to edit. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Ticket reports doesn't sync
Hi, I'm modifying reports on the main fossil repo. This is the repo everybody syncs to. So I modified a report, and created a new one. But after I sync or pull the report doesn't show up on the local repo. Is this by design or there is an error? Thanks, Federico Ramallo ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Ticket reports doesn't sync
I can answer myself! :D fossil config pull ticket Notice that AREA can be one of: all email project shun skin ticket user it makes sense not sync it by default with the sync command 2011/3/10 Federico Ramallo frama...@gmail.com Hi, I'm modifying reports on the main fossil repo. This is the repo everybody syncs to. So I modified a report, and created a new one. But after I sync or pull the report doesn't show up on the local repo. Is this by design or there is an error? Thanks, Federico Ramallo ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] symlinks to directories are traversed by fossil extras?
What is the plan for handling symlinks for fossil? My preference would be for fossil to treat links as a file. Storing the pointer would be great. Just ignoring links would also be fine by me. But actually traversing the links is not a good idea IMHO and is a real fossil killer. It is also not easy to work around. Links are commonly used to point to large amounts of static data outside of a build area or to reference one piece of data in multiple places. In neither of these cases would I want my scm tool to traverse the links and add the data. A setting ignore-links would be an ok compromise. Just my $0.02, thanks! ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Work flow with fossil (understanding conflict resolution)
For a very nice (IMHO) model on how to handle forks take a look at monotone. Forking is natural, you just want to take precautions to keep your data safe. A fork is just a branch you haven't given a name to and didn't necessarily intentionally create. In the case of monotone it just lets you know you have a fork and you can just merge or keep on working, your choice. On Thu, Mar 10, 2011 at 11:29 AM, Eric Junkermann e...@deptj.eu wrote: On Thu, March 10, 2011 12:38 am, Ron Wilson wrote: On Wed, Mar 9, 2011 at 3:52 PM, Eric e...@deptj.eu wrote: Finally, I don't think there is any way to safely have automatic merging of forks. This I agree with and never intended to suggest that forks should ever be automatically merged. And, as Richard said, what is a fork? Something I want to avoid like the plague. Your workflow seems, strictly followed, should (somewhat) minimize the risk of an accidental fork, however, you imply that you do intentionally start forks. No, it's just that working that way means I will inevitably find myself on a fork from time to time. I suppose if you make sure to either close the fork by merging, or tag it as a branch, before pushing your changes, then that should be ok. Which is exactly what I think should be done. It seems to me that forks are something that are all too easy to loose. The leaves page in the web UI (no longer on the menu) is actually very useful for finding them, especially if you close them after dealing with them appropriately. I do not see any advantages to creating a fork rather than a branch. If anything, all this discussion just reinforces the advice (from some people) that creating a branch for each and every task/change package is the right thing to do - especially when using a DVCS. Task Branch, Feature Branch, Release Branch, Private Branch - which all look much the same, except which other branches they merge to and from, and when; also whether they get closed or not. You don't need to have a branch policy, but it's useful to know what your branch is for and how you plan to use it. If you create a fork on purpose it's meant to be a branch - put some hint of the purpose in the name of the branch. I do realise that accidental forks are inevitable, so anything that the tool does to help find forks will help the overall development process. Just for forks, I think it's enough to look at the timeline frequently (in Checkins Only mode), but some path stuff seems to be going into Fossil, so we shall see. Eric ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] git equivalent commands
Hi, I was wondering how to do git reset --hard on a fossil repository. Because fossil clean only clear extra files, but what about changed files? Also I was wondering about git grep, there is any plan on implementing the command? I think is really really usefull Also Today we found a bug on fossil sqlite3 command, How should I add it as a ticket? Do i need a user or I could add it as anonymous? Regards, Federico Ramallo ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] git equivalent commands
On Fri, Mar 11, 2011 at 01:27:39AM -0600, Federico Ramallo wrote: I was wondering how to do git reset --hard on a fossil repository. Because fossil clean only clear extra files, but what about changed files? Possibly you need `fossil revert`. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
