Re: [fossil-users] fossil proxy web browser
It solves part of the problem; I'm just getting a 502 bad gateway now. I'll
find a way to see what's happening with it...
On Thu, Apr 30, 2015 at 8:35 PM, Richard Boehme rboe...@gmail.com wrote:
I've made it a configurable option in the setting call user-config; diff
below. I've compiled it, but I'm unsure if it's 32 or 64 bit - my home
computer is 64 bit, but where I need to run it is 32 bit.
Thanks for the help!
Would this be useful as an option for a future version?
Thanks.
Richard
C:\Users\rboehme\nonCloud\OpenSource\fossil\srcfossil diff
Index: src/db.c
==
--- src/db.c
+++ src/db.c
@@ -2385,10 +2385,11 @@
#ifdef FOSSIL_ENABLE_TH1_HOOKS
{ th1-hooks,0, 0, 0, 0, off },
#endif
{ th1-setup,0, 40, 1, 1, },
{ th1-uri-regexp, 0, 40, 1, 0, },
+ { user-agent, 0,100, 0, 0, },
{ web-browser, 0, 32, 0, 0, },
{ 0,0,0,0,0,0 }
};
/*
Index: src/main.c
==
--- src/main.c
+++ src/main.c
@@ -968,11 +968,11 @@
** use in HTTP(S) requests.
*/
const char *get_user_agent(){
static const char version[] = Fossil/ RELEASE_VERSION (
MANIFEST_DATE
MANIFEST_VERSION );
- return version;
+ return db_get(user-agent, version);
}
/*
** COMMAND: version
**
On Mon, Apr 27, 2015 at 9:07 PM, Andy Bradford amb-fos...@bradfords.org
wrote:
Thus said Richard Boehme on Mon, 27 Apr 2015 09:07:54 -0400:
They are distinct, but I needed some way to see what my proxy's
response was, and it looks like it needs to look like a certain web
browser - it looks like the proxy rejects anything that isn't
Internext Explorer 9. When I try to connect using Fossil, it simply
hangs.
You may be able to get the proxy's response using --httptrace; e.g,
fossil clone --httptrace ...
It will write a series of request/reply files in your current directory
that record the HTTP transactions.
Thanks,
Andy
--
TAI64 timestamp: 4000553edd65
--
Thank you.
Richard Boehme
Email: rboe...@gmail.com
Phone: 443-739-8502
Work Phone: 410-966-6606 (Mon - Thu 6 AM - 4:30 PM)
--
Thank you.
Richard Boehme
Email: rboe...@gmail.com
Phone: 443-739-8502
Work Phone: 410-966-6606 (Mon - Thu 6 AM - 4:30 PM)
___
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] fossil proxy web browser
I've made it a configurable option in the setting call user-config; diff
below. I've compiled it, but I'm unsure if it's 32 or 64 bit - my home
computer is 64 bit, but where I need to run it is 32 bit.
Thanks for the help!
Would this be useful as an option for a future version?
Thanks.
Richard
C:\Users\rboehme\nonCloud\OpenSource\fossil\srcfossil diff
Index: src/db.c
==
--- src/db.c
+++ src/db.c
@@ -2385,10 +2385,11 @@
#ifdef FOSSIL_ENABLE_TH1_HOOKS
{ th1-hooks,0, 0, 0, 0, off },
#endif
{ th1-setup,0, 40, 1, 1, },
{ th1-uri-regexp, 0, 40, 1, 0, },
+ { user-agent, 0,100, 0, 0, },
{ web-browser, 0, 32, 0, 0, },
{ 0,0,0,0,0,0 }
};
/*
Index: src/main.c
==
--- src/main.c
+++ src/main.c
@@ -968,11 +968,11 @@
** use in HTTP(S) requests.
*/
const char *get_user_agent(){
static const char version[] = Fossil/ RELEASE_VERSION (
MANIFEST_DATE
MANIFEST_VERSION );
- return version;
+ return db_get(user-agent, version);
}
/*
** COMMAND: version
**
On Mon, Apr 27, 2015 at 9:07 PM, Andy Bradford amb-fos...@bradfords.org
wrote:
Thus said Richard Boehme on Mon, 27 Apr 2015 09:07:54 -0400:
They are distinct, but I needed some way to see what my proxy's
response was, and it looks like it needs to look like a certain web
browser - it looks like the proxy rejects anything that isn't
Internext Explorer 9. When I try to connect using Fossil, it simply
hangs.
You may be able to get the proxy's response using --httptrace; e.g,
fossil clone --httptrace ...
It will write a series of request/reply files in your current directory
that record the HTTP transactions.
Thanks,
Andy
--
TAI64 timestamp: 4000553edd65
--
Thank you.
Richard Boehme
Email: rboe...@gmail.com
Phone: 443-739-8502
Work Phone: 410-966-6606 (Mon - Thu 6 AM - 4:30 PM)
___
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] fossil proxy web browser
Tried again and it didn't hang: SSL: proxy connect failed with HTTP status code 403 Sync done, sent: 0 received: 0 ip: On Mon, Apr 27, 2015 at 12:57 PM, Ron W ronw.m...@gmail.com wrote: On Mon, Apr 27, 2015 at 9:07 AM, Richard Boehme rboe...@gmail.com wrote: They are distinct, but I needed some way to see what my proxy's response was, and it looks like it needs to look like a certain web browser - it looks like the proxy rejects anything that isn't Internext Explorer 9. When I try to connect using Fossil, it simply hangs. If the proxy server was returning a not supported browser, I would expect Fossil to exit with an error, not hang. Do you have admin privs on your PC? If so, you could try running WireShark to see what response the proxy server is sending to Fossil. Alternately, you could use a cheap ethernet hub between your PC and the network jack so you can monitor the conversation with a second PC using WireShark. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- Thank you. Richard Boehme Email: rboe...@gmail.com Phone: 443-739-8502 Work Phone: 410-966-6606 (Mon - Thu 6 AM - 4:30 PM) ___ 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] fossil proxy web browser
They are distinct, but I needed some way to see what my proxy's response was, and it looks like it needs to look like a certain web browser - it looks like the proxy rejects anything that isn't Internext Explorer 9. When I try to connect using Fossil, it simply hangs. On 4/27/15, Richard Hipp d...@sqlite.org wrote: On 4/27/15, Richard Boehme rboe...@gmail.com wrote: Is there any way to set the browser fossil identifies itself as when communicating by proxy? Trying to connect via PuTTY to my server gives 403 NotSupportedBrowser, so I figure something similar is happening with Fossil when it tries to connect and can't. I don't quite understand what you are trying to do. Proxies come into play when you use http: and PuTTY is used for ssh:. Those two connection methods are distinct. -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- Thank you. Richard Boehme Email: rboe...@gmail.com Phone: 443-739-8502 Work Phone: 410-966-6606 (Mon - Thu 6 AM - 4:30 PM) ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] fossil proxy web browser
Is there any way to set the browser fossil identifies itself as when communicating by proxy? Trying to connect via PuTTY to my server gives 403 NotSupportedBrowser, so I figure something similar is happening with Fossil when it tries to connect and can't. -- Thank you. Richard Boehme Email: rboe...@gmail.com Phone: 443-739-8502 Work Phone: 410-966-6606 (Mon - Thu 6 AM - 4:30 PM) ___ 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] fossil proxy web browser
Unfortunately, I can't install WireShark, so I'm left guessing. . Does fossil have a setting to change the user-agent string? On Mon, Apr 27, 2015 at 4:29 PM, Ron W ronw.m...@gmail.com wrote: On Mon, Apr 27, 2015 at 4:04 PM, Richard Boehme rboe...@gmail.com wrote: Tried again and it didn't hang: SSL: proxy connect failed with HTTP status code 403 Sync done, sent: 0 received: 0 ip: HTTP 403 is a general forbidden response. Further explanation by the server sending this response is optional. You said that PuTTY was reporting 403 NotSupportedBrowser. This suggests that the server doesn't like the value PuTTY supplies for the HTTP User-agent field. While this might be what is happening when Fossil is trying to go through the proxy, it would be better to confirm it, if possible. I am not sure how much of the server's negative response is practical for Fossil to display. But, as I previously said, this can be confirmed using a tool like WireShark. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- Thank you. Richard Boehme Email: rboe...@gmail.com Phone: 443-739-8502 Work Phone: 410-966-6606 (Mon - Thu 6 AM - 4:30 PM) ___ 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] Veracity Version control
I would be strongly in favor of presets in Fossil as everyone has outlined open source - everyone can read corporate - only registered users can read, and new users have minimal permissions private - I'm unsure what this means. Comments? Thanks. Richard On 3/11/15, Ron W ronw.m...@gmail.com wrote: On Wed, Mar 11, 2015 at 1:49 AM, Graeme Pietersz gra...@pietersz.net wrote: On 11/03/15 00:45, Ron W wrote: I'm thinking he wants 2 sets of default settings: The existing one (which he perceives as being open source oriented) and another set that are more appropriate for use by software teams within a corporate environment. It would be nice to have, and not just for corporate teams. It is bit of a pain to set up a repo that has nothing publicly accessible - i.e. only logged in users see anything. It is not a huge problem, but it is a mild annoyance for those of us who regularly set up new repos. It would be nice to just click a button or run a command that sets sensible defaults for a private repo. I just remembered 2 things that partially mitigate the absence of this: 1. fossil new has a --template option to obtain settings from. It claims to require a path to the repo file. 2. fossil config has export, import, merge and other commands to save/load settings to/from a file or even another Fossil server. -- Thank you. Richard Boehme Email: rboe...@gmail.com Phone: 443-739-8502 Work Phone: 410-966-6606 (Mon - Thu 6 AM - 4:30 PM) ___ 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] Fossil 2.1: Scaling
One question that arises is: how do I define what a server is? Can I get the complete repository history for everything else but get a more limited history for files that are larger than a certain size, or that have certain extensions? How would this work with sub-repositories (sorry, not versed very well in fossil, but I understand that there can be sub respositories that are nested under the main one (for instance for a directory which contains a lot of videos or images)) Thanks. Richard On 3/2/15, Richard Hipp d...@sqlite.org wrote: Ben Pollack's essay at http://bitquabit.com/post/unorthodocs-abandon-your-dvcs-and-return-to-sanity/ succinctly points up some of the problems with DVCS versus centralized VCS (like subversion). Much further discussion occurs on the various news aggregator sites. So I was thinking, could Fossil 2.0 be enhanced in ways to support scaling to the point where it works on really massive projects? The key idea would be to relax the requirement that each client load the entire history of the project. Instead, a clone would only load a limited amount of history (a month, a year, perhaps even just the most recent check-in). This would make cloning much faster and the resulting clone much smaller. Missing content could be downloaded from the server on an as-needed basis. So, for example, if the user does fossil update trunk:2010-01-01 then the local client would first have to go back to the server to fetch content from 2010. The additional content would be added to the local repository. And so the repository would still grow. But it grows only on an as-needed basis rather than starting out at full size. And in the common case where the developer never needs to look at any content over a few months old, the growth is limited. By downloading the meta-data that is currently computed locally by rebuild, many operations on older content, such as timelines or search, could be performed even without having the data present. In the bsd-src.fossil repository, the content is 78% of the repository file and the meta-data is the other 22%. So a clone that stored only the most recent content together with all metadata might be about 1/4th the size of a full clone. For even greater savings, perhaps the metadata could be time-limited, though not as severely as the content. So perhaps the clone would only initialize to the last month of content and the last five years of metadata. For wide repositories (such as bsd-src) that hold many thousands of files in a single check-out, Fossil could be enhanced to allow cloning, checkout, and commit of just a small slice of the entire tree. So, for example, a clone might hold just the bin/ subdirectory of bsd-src containing just 56 files, rather than all 147720 files of a complete check-out. Fossil should be able to do everything it normally does with just this subset, including commit changes, except that on new manifests generated by the commit, the R-card would have to be omitted since the entire tree is necessary to compute the R-card. But the R-card is optional already, controlled by the repo-cksum setting, which is turned off in bsd-src, so there would be no loss in functionality. Tickets and wiki in a clone might be similarly limited to (say) the previous 12 months of content, or the most recent change, whichever is larger. With these kinds of changes, it seems like Fossil might be made to scale to arbitrarily massive repositories on the client side. On the server side, the current design would work until the repository grew too big to fit into a single disk file, at which point the server would need to be redesigned to use a client/server database like, PostgreSQL, that can scale to sizes larger than the 140 terabyte limit of SQLite. But that would be a really big repo. 22 years of BSD history fits in 7.2 GB, or 61 GB uncompressed. So it would take a rather larger project to get into the terabyte range. The sync protocol would need to be greatly enhanced to support this functionality. Also, the schema for the meta-data, which currently is an implementation detail, would need to become part of the interface. Exposing the meta-data as interface would have been unthinkable a few years ago, but at this point we have accumulated enough experience about what is needed in the meta-data to perhaps make exposing its design a reasonable alternative. These are just thoughts to elicit comments and discussion. I have several unrelated and much higher-priority tasks to keep me busy at the moment, so this is not something that would happen right away, unless somebody else steps up to do a lot of the implementation work. -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- Thank you. Richard Boehme
Re: [fossil-users] New search features
Does anyone have a Windows binary of the latest fossil with search? I don't have the ability to compile it from where I am at the moment. Thanks. Richard On Tue, Feb 3, 2015 at 1:41 AM, jungle Boogie jungleboog...@gmail.com wrote: Dr. Hipp, On 2 February 2015 at 22:11, Richard Hipp d...@sqlite.org wrote: On 2/3/15, jungle Boogie jungleboog...@gmail.com wrote: Something recently has changed that doesn't allow the clicked result to be viewed. http://fossil-scm.org/index.html/tktsrch?s=windows The main Fossil repo (and the main SQLite repo) are now running on a full-text index, rather than do a full scan of all documents for each search. This is faster, but considerably trickier to implement. I expect it to be a bountiful source of errors over the next few days. Not a problem with me, I'll report them as I encounter them! The problem with hyperlinks is now fixed, I think. Please try again. Yes, that corrected it and results are now clickable. -- D. Richard Hipp d...@sqlite.org Thanks! -- --- inum: 883510009027723 sip: jungleboo...@sip2sip.info xmpp: jungle-boo...@jit.si ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- Thank you. Richard Boehme Email: rboe...@gmail.com Phone: 443-739-8502 Work Phone: 410-966-6606 (Mon - Thu 6 AM - 4:30 PM) ___ 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] Fossil DB Corruption
Good thoughts. I'm not using Cygwin (this is straight Windows command line stuff), but I'll locate my fossil stuff outside of the Google Drive tree and backup into it (maybe a windows cron utility - though I have to look into that). I had to remove my local repo and clone off the remote, but that worked like a charm. Thanks for the help! Richard On Fri, Jan 9, 2015 at 11:28 PM, Warren Young w...@etr-usa.com wrote: On Jan 9, 2015, at 6:51 PM, Richard Boehme rboe...@gmail.com wrote: I host elsewhere - a private sever (Linode). I'm the only one who accesses that Google Drive folder, so it's unlikely to be updated by anyone else. Wrong. There are two things that can access it at once: the Google Drive background updater, and fossil.exe. How can this happen, you ask? Because you’re using Cygwin Fossil: C:\Users\rboehme\Google Drive\user\Richard\Projects\CSharp\ShardGalaxyfossil version This is fossil version 1.29 [3e5ebe2b90] 2014-06-12 17:25:56 UTC The thing about Cygwin SQLite — which Cygwin fossil uses — is that it defaults to BSD advisory locks, so that it will cooperate properly with other Cygwin programs which are expecting advisory locking semantics. Native Windows programs, though, expect mandatory locking semantics. If the background Google Drive updater tries updating one of the two (!) SQLite DB files while fossil.exe is trying to update it, Windows won’t stop it. The obvious SQLite DB file is the one you get from “fossil clone” but even if you’re cloning outside the GDrive tree, you also get a _FOSSIL_ SQLite DB file at the root of a “fossil open” tree on Windows. Back when I was maintaining Cygwin SQLite, you could make it use native mandatory locks by setting a certain environment variable, but when Jan Nijtmans took over, he changed it to use SQLite’s VFS mechanism instead. I don’t know how to make Fossil use a different SQLite VFS. While it would be nice to know how to do that, I’d recommend not putting any actively-used Fossil files in your GDrive tree. Not only do you put the precious _FOSSIL_ DB file there, your build system probably also puts all the build products (*.obj, *.dll, *.exe, *.pdb…) there, too. If you want the Fossil repo backed up to the Google Cloud, I’d “fossil clone” and “fossil open” outside that tree, then back it up to your GDrive as a separate step. Since you’re using Cygwin anyway, you can create a crontab entry that does something like this: sqlite3 myrepo.fossil .dump | xz ~/GDrive/myrepo.sql.xz You should get a tiny bit better compression this way, too. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- Thank you. Richard Boehme Email: rboe...@gmail.com Phone: 443-739-8502 Work Phone: 410-966-6606 (Mon - Thu 6 AM - 4:30 PM) ___ 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] Fossil DB Corruption
I host elsewhere - a private sever (Linode). I'm the only one who accesses that Google Drive folder, so it's unlikely to be updated by anyone else. Thanks for all the responses; I'll try cloning from the Linode repo and recopying any changed files. On Fri, Jan 9, 2015 at 8:44 PM, Andy Bradford amb-fos...@bradfords.org wrote: Thus said Warren Young on Fri, 09 Jan 2015 18:32:16 -0700: Mr Boehme, have you considered hosting your Fossil repository either on ChiselApp or your own cheap VPS? Then you're not relying on the cloud disk syncing mechanism to do the right thing with the Fossil blobs. You're allowing Fossil to do intelligent syncing. From the URLs in the last-sync-url the output he provided, it would appear that he is already hosting it elsewhere. From what I can tell from the output, he has done ``fossil open'' into a Google Drive (and possibly even cloned into the Google Drive). Andy -- TAI64 timestamp: 400054b08426 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- Thank you. Richard Boehme Email: rboe...@gmail.com Phone: 443-739-8502 Work Phone: 410-966-6606 (Mon - Thu 6 AM - 4:30 PM) ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Fossil DB Corruption
Good evening. I have a small fossil repository that I've been committing
into for a couple of weeks now, and when I tried to commit a bunch of
files, it indicated the repository is corrupt.
Can anyone recommend how I can fix this?
I also have my command list below.
Thanks.
Richard
C:\Users\rboehme\Google
Drive\user\Richard\Projects\CSharp\ShardGalaxyfossil update
Autosync: https://rboe...@quietwisp.com:8420/qw_shardgalaxy/
Round-trips: 1 Artifacts sent: 0 received: 0
SQLITE_CORRUPT: database corruption at line 56528 of [b1ed4f2a34]
SQLITE_CORRUPT: statement aborts at 26: [REPLACE INTO
config(name,value,mtime)VALUES('ckout:C:/Users/rboehme/Google
Drive/user/Richard/Projects/CSharp/ShardGala
xy/',1,now())]
Pull finished with 363 bytes sent, 2309 bytes received
---
checkout: e0e69dddec5888fbc55b8806eacd6405754808c2
leaf: open
changes: None. Already up-to-date
C:\Users\rboehme\Google Drive\user\Richard\Projects\CSharp\ShardGalaxy
C:\Users\rboehme\Google Drive\user\Richard\Projects\CSharp\ShardGalaxy
C:\Users\rboehme\Google Drive\user\Richard\Projects\CSharp\ShardGalaxy
C:\Users\rboehme\Google
Drive\user\Richard\Projects\CSharp\ShardGalaxyfossil com -m Added log4net
SQLITE_CORRUPT: database corruption at line 56528 of [b1ed4f2a34]
SQLITE_CORRUPT: statement aborts at 26: [REPLACE INTO
config(name,value,mtime) VALUES('last-sync-url','
https://rboe...@quietwisp.com:8420/qw_shardgalaxy/',now()
)]
fossil: database disk image is malformed: {REPLACE INTO
config(name,value,mtime) VALUES('last-sync-url','
https://rboe...@quietwisp.com:8420/qw_shardgalaxy/',now
())}
If you have recently updated your fossil executable, you might
need to run fossil all rebuild to bring the repository
schemas up to date.
C:\Users\rboehme\Google
Drive\user\Richard\Projects\CSharp\ShardGalaxyfossil all rebuild
C:\Users\rboehme\Google Drive\user\Richard\apps\bin\fossil.exe rebuild
C:/Users/rboehme/Google Drive/user/Richard/fossil/RFBPersonal_home.fossil
100.0% complete...
C:\Users\rboehme\Google Drive\user\Richard\apps\bin\fossil.exe rebuild
C:/Users/rboehme/Google Drive/user/Richard/fossil/qw_shardgalaxy.fossil
0.0% complete...
SQLITE_CORRUPT: database corruption at line 56528 of [b1ed4f2a34]
SQLITE_CORRUPT: statement aborts at 19: [DROP TABLE 'filename']
C:\Users\rboehme\Google Drive\user\Richard\apps\bin\fossil.exe: database
disk image is malformed: {DROP TABLE 'filename'}
If you have recently updated your fossil executable, you might
need to run fossil all rebuild to bring the repository
schemas up to date.
C:\Users\rboehme\Google
Drive\user\Richard\Projects\CSharp\ShardGalaxyfossil version
This is fossil version 1.29 [3e5ebe2b90] 2014-06-12 17:25:56 UTC
C:\Users\rboehme\Google Drive\user\Richard\Projects\CSharp\ShardGalaxy
--
Thank you.
Richard Boehme
Email: rboe...@gmail.com
Phone: 443-739-8502
Work Phone: 410-966-6606 (Mon - Thu 6 AM - 4:30 PM)
___
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] Internal Server Error on files page after push
It's fixed now; I don't know why it works, but it does work. I did the following: 1. Delete the local fossil repository 2. Remove the _FOSSIL_ file from the local checked out directory. 3. fossil clone the server repository 4. fossil open into the local checked out directory 5. fossil add * all of the files 6. fossil commit 7. check the local repo - it has the added files 8. fossil push with the URL of the server 9. Check the server repo - it has the changed files. Thanks. Richard On Fri, Nov 11, 2011 at 1:20 PM, Richard Boehme rboe...@gmail.com wrote: The directory containing the repo is also writable; I had set it to worls-readable and writable for a short time just to make sure. Thanks. Richard On Fri, Nov 11, 2011 at 12:38 PM, Stephan Beal sgb...@googlemail.com wrote: On Fri, Nov 11, 2011 at 6:31 PM, Ron Wilson ronw.m...@gmail.com wrote: On Fri, Nov 11, 2011 at 11:08 AM, Richard Boehme rboe...@gmail.com wrote: My local fossil copy is at C:\Users\Richard Boehme\Dropbox\apps\bin Are you using Dropbox to backup your repository? Is it possible Dropbox is doing something that interferes with Fossil? FWIW: i use fossil-in-dropbox for several small repos and have had no problems with it to-date. Dropbox won't merge conflicting repo files (it will instead create two copies, one of them named something like filename (conflict)). Nonetheless, to keep dropbox from trying to copy the short-lived journal files, i tend to (but don't always) disable dropbox while i'm working with such a repo. -- - stephan beal http://wanderinghorse.net/home/stephan/ ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- Thank you. Richard Boehme Email: rboe...@gmail.com Phone: 443-739-8502 Blog: http://www.inexperiencetalking.com/ -- Thank you. Richard Boehme Email: rboe...@gmail.com Phone: 443-739-8502 Blog: http://www.inexperiencetalking.com/ ___ 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] Internal Server Error on files page after push
They are all readable and writeable by the user apache runs as (inthis case www-data). When I go to the main wiki page, I am able to addwiki content just fine; any other page but the files page works. -- Thank you. Richard Boehme Email: rboe...@gmail.com Phone: 443-739-8502 Blog: http://www.inexperiencetalking.com/ ___ 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] Internal Server Error on files page after push
Thanks. That worked for seeing the file without crashing the files section, but the push from the client side still doesn't work. My local fossil copy is at C:\Users\Richard Boehme\Dropbox\apps\bin; my push fails. I've checked the permissions on the fossil.exe; I have full access control to it (and my account is an administrator account). On the server, I've set the repository to world-readable and writable to make sure that there aren't permission problems; the same error occurs: This is fossil version 1.20 [a75e2d2504] 2011-10-21 12:52:53 UTC C:\Users\Richard Boehme\Dropbox\Projects\QuietConflict.GSfossil push Server:http://192.168.1.15:32080/cgi-bin/repos/GameServer/ Bytes Cards Artifacts Deltas Sent: 14850321 0 0 Error: not authorized to writex\apps\bin\fossil.exe: Received: 65 1 0 0 Total network traffic: 8225 bytes sent, 305 bytes received Thank you for the help. Richard On Fri, Nov 11, 2011 at 10:34 AM, Richard Hipp d...@sqlite.org wrote: On Thu, Nov 10, 2011 at 9:07 AM, Richard Boehme rboe...@gmail.com wrote: When I looked into the server's fossil repository, I could get into the repository itself, but the files tab gave me an internal server error. There was once a bug (now fixed) in Fossil where it was dividing by the number of files. So if you haven't checked in any files yet, it is dividing by zero, and crashing. Either update to the latest Fossil code (from the source tree) or else add a single file to the repo. -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- Thank you. Richard Boehme Email: rboe...@gmail.com Phone: 443-739-8502 Blog: http://www.inexperiencetalking.com/ ___ 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] Internal Server Error on files page after push
The directory containing the repo is also writable; I had set it to worls-readable and writable for a short time just to make sure. Thanks. Richard On Fri, Nov 11, 2011 at 12:38 PM, Stephan Beal sgb...@googlemail.com wrote: On Fri, Nov 11, 2011 at 6:31 PM, Ron Wilson ronw.m...@gmail.com wrote: On Fri, Nov 11, 2011 at 11:08 AM, Richard Boehme rboe...@gmail.com wrote: My local fossil copy is at C:\Users\Richard Boehme\Dropbox\apps\bin Are you using Dropbox to backup your repository? Is it possible Dropbox is doing something that interferes with Fossil? FWIW: i use fossil-in-dropbox for several small repos and have had no problems with it to-date. Dropbox won't merge conflicting repo files (it will instead create two copies, one of them named something like filename (conflict)). Nonetheless, to keep dropbox from trying to copy the short-lived journal files, i tend to (but don't always) disable dropbox while i'm working with such a repo. -- - stephan beal http://wanderinghorse.net/home/stephan/ ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- Thank you. Richard Boehme Email: rboe...@gmail.com Phone: 443-739-8502 Blog: http://www.inexperiencetalking.com/ ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Internal Server Error on files page after push
Hi there. I'm having a bit of trouble with fossil push. I have one local machine (Win 7) that I originally created the fossil repository on (just a blank repository). I copied it to my linux server and ran it with Apache over CGI. I also made sure that the same version of fossil was on my local machine and the server. At this time, the project's files page showed no files (as expected). I added files with fossil add and fossil commit (and could see the files in the local fossil instance), and then tried to push to the server's URL. The client complained that it didn't have permission to write to the local fossil executable (no permission for xapps/bin/fossil.exe - I don't know where it got the x in there). When I looked into the server's fossil repository, I could get into the repository itself, but the files tab gave me an internal server error. My initial fossil commit on my local machine asked about crlf style, but the local repository files look file. It's only the server file page that is screwed up. I tried doing a fossil rebuild on the server - that didn't help; neither did creating another repository from scratch on the server. Any thoughts on why fossil push would end up with my server's files page giving me an internal server error? If needed, I can get exact wording once I'm back in range of my computers at home. -- Thank you. Richard Boehme Email: rboe...@gmail.com Phone: 443-739-8502 Blog: http://www.inexperiencetalking.com/ ___ 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] Internal Server Error on files page after push
Thanks for the quick reply. I'll check on that when I get back tonight. Richard On Thu, Nov 10, 2011 at 9:13 AM, Richard Hipp d...@sqlite.org wrote: On Thu, Nov 10, 2011 at 9:07 AM, Richard Boehme rboe...@gmail.com wrote: Any thoughts on why fossil push would end up with my server's files page giving me an internal server error? The repository file, the directory that contains the repository file and /tmp all need to be readable and writable by whatever user CGI is running under. -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- Thank you. Richard Boehme Email: rboe...@gmail.com Phone: 443-739-8502 Blog: http://www.inexperiencetalking.com/ ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
