[fossil-users] SSH commands run as user nobody
Dear List, All of the remote ssh commands that I execute (pull/push/sync/clone) try to run as the user nobody. This is a big problem, because I need to make sure that other users on my machine cannot login to the web interface, (eg. I want nobody and anonymous to have no capabilities) and I want to use my named username of beyert. After performing the clone over sshfs, which works fine (although sshfs gives database errors for pull/push/sync), I set the remote-url command as follows: ssh://beyert@[my-domain]:[my-port]//the/remote/path/scripts.fossil I have tried every variation of the password notation that I know of, namely: ssh://beyert@[my-domain]:[my-port]//the/remote/path/scripts.fossil ssh://beyert:*@[my-domain]:[my-port]//the/remote/path/scripts.fossil ssh://beyert:[my-password]@[my-domain]:[my-port]//the/remote/path/scripts.fossil With my secure settings for nobody with no capabilities, I get the following error: Error: not authorized to read I only was able to get the pull/push/sync to work once I gave nobody gio capabilities, which allowed other users on my machine to see the repository. When I looked at the usage logs, that sync operation was recorded as belonging to user nobody, whereas all of my other repository commands belong to beyert. I don't understand why it isn't using the user beyert, which has s capabilities? I also tried setting the environment variable REMOTE_USER to beyert, which didn't help. On both sides, the command fossil user default gives beyert, and my UNIX user on both machines is beyert. I'm using FreeBSD 9.0-RELEASE on both machines, with a snapshot from 2012-03-17. Should I use a newer snapshot? Regards, Tim ___ 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] SSH commands run as user nobody
Le 2012-05-07 à 05:22, Timothy Beyer bey...@fastmail.net a écrit : Dear List, All of the remote ssh commands that I execute (pull/push/sync/clone) try to run as the user nobody. This is a big problem, because I need to make sure that other users on my machine cannot login to the web interface, (eg. I want nobody and anonymous to have no capabilities) and I want to use my named username of beyert. After performing the clone over sshfs, which works fine (although sshfs gives database errors for pull/push/sync), I set the remote-url command as follows: ssh://beyert@[my-domain]:[my-port]//the/remote/path/scripts.fossil I have tried every variation of the password notation that I know of, namely: ssh://beyert@[my-domain]:[my-port]//the/remote/path/scripts.fossil ssh://beyert:*@[my-domain]:[my-port]//the/remote/path/scripts.fossil ssh://beyert:[my-password]@[my-domain]:[my-port]//the/remote/path/scripts.fossil With my secure settings for nobody with no capabilities, I get the following error: Error: not authorized to read I only was able to get the pull/push/sync to work once I gave nobody gio capabilities, which allowed other users on my machine to see the repository. When I looked at the usage logs, that sync operation was recorded as belonging to user nobody, whereas all of my other repository commands belong to beyert. I don't understand why it isn't using the user beyert, which has s capabilities? I also tried setting the environment variable REMOTE_USER to beyert, which didn't help. On both sides, the command fossil user default gives beyert, and my UNIX user on both machines is beyert. I'm using FreeBSD 9.0-RELEASE on both machines, with a snapshot from 2012-03-17. Should I use a newer snapshot? Yes, this as been resolve recently. Now you have all capabilities via ssh, since one which have ssh access can do whatever he want with the .fossil file. -- Martin G. ___ 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] SSH commands run as user nobody
At Mon, 7 May 2012 05:48:54 -0400, Martin Gagnon wrote: I'm using FreeBSD 9.0-RELEASE on both machines, with a snapshot from 2012-03-17. Should I use a newer snapshot? Yes, this as been resolve recently. Now you have all capabilities via ssh, since one which have ssh access can do whatever he want with the .fossil file. -- Martin G. Thanks! I'll update fossil right away. Tim ___ 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] SSH commands run as user nobody
At Mon, 7 May 2012 05:48:54 -0400, Martin Gagnon wrote: Yes, this as been resolve recently. Now you have all capabilities via ssh, since one which have ssh access can do whatever he want with the .fossil file. -- Martin G. I just tried the version from fossil (2012-05-05 13:53:37 UTC), re-cloned via sshfs due to the same issues, and then set the remote-url to the appropriate ssh path, and the Error: not authorized to read remains. I also did a rebuild on the repository. Tim ___ 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] SSH commands run as user nobody
Le 2012-05-07 à 06:20, Timothy Beyer bey...@fastmail.net a écrit : At Mon, 7 May 2012 05:48:54 -0400, Martin Gagnon wrote: Yes, this as been resolve recently. Now you have all capabilities via ssh, since one which have ssh access can do whatever he want with the .fossil file. -- Martin G. I just tried the version from fossil (2012-05-05 13:53:37 UTC), re-cloned via sshfs due to the same issues, and then set the remote-url to the appropriate ssh path, and the Error: not authorized to read remains. I also did a rebuild on the repository. Have you update server side as well? -- Martin G. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] HOWTO delete a Wiki page?
Hi, I made a typo in Wiki page. Can I rename Wiki page or delete a Wiki page? Thx, Jiri -- Jiri Navratil, http://www.navratil.cz, +420 777 224 245 ___ 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] HOWTO delete a Wiki page?
On Mon, 7 May 2012 14:16:59 +0200 Jiri Navratil j...@navratil.cz wrote: I made a typo in Wiki page. Can I rename Wiki page or delete a Wiki page? In one sense, no. Artifacts are forever (though you can shun them). However, if you delete all the text from a page, it'll vanish from the list of wiki pages. mike -- Mike Meyer m...@mired.org http://www.mired.org/ Independent Software developer/SCM consultant, email for more information. O ascii ribbon campaign - stop html mail - www.asciiribbon.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Wysiwyg wiki editing. Was: Side-by-side wiki editing?
What if we were to provide full WYSIWYG editing of wiki pages in Fossil? I've been experimenting with the code at https://developer.mozilla.org/en/Rich-Text_Editing_in_Mozilla (with the bug on line 140 fixed, as well as other enhancements). The basic code seems to work pretty well on Firefox, Chrome, Safari, Opera, and IE, so it seems to be sufficiently cross-platform. If we extend the wiki generator to allow style= attributes on span tags, and if we surround the HTML text that comes back from this wysiwyg editor with nowiki../nowiki, then I think it might work. Another option is to translate the HTML that comes back from javascript back into the Fossil wiki format. The latter option would be trickier and more prone to error, but it would also enable the same wiki page to be edited as plain text or as wysiwyg. (The HTML that comes back from javascript is directly editable, in theory, but it is not pleasing to look at.) Unfortunately, I'm very busy with other things right now and have not had an opportunity to prototype this yet. But I'd be interested in hearing thoughts from the community on the idea, at least. On Mon, Apr 23, 2012 at 12:25 PM, Cunningham, Robert rcunning...@nsmsurveillance.com wrote: I’m evaluating Trac vs. Fossil for use within our small engineering department (2 CEs, 2 EEs, 2 MEs). I have some experience with Trac and none at all with Fossil (I’ve been using SVN + Bugzilla for way too long). We need version control, bug tracking and documentation tools, and getting them rolled into a single integrated system is highly desired, even if compromises must be made.I have both systems running in parallel, and the other engineers are playing with each as time permits. ** ** So far, Fossil is winning quite handily on all the key technical features and issues we care about. But usability issues, especially for non-software folks, provide some stumbling blocks. ** ** One feature many enjoy is the side-by-side wiki editing capability of Trac (http://trac.edgewall.org/wiki/TracWiki), especially those who have little or no experience with wiki markup or HTML, or folks like me who have used way too many wiki markup systems and keeps getting them confused. The side-by-side approach provides a very nice, possibly ideal, compromise between full (and heavy) WYSIWYG editing vs. the tedious edit/preview cycle. ** ** Is side-by-side wiki editing available in Fossil? Ideally, this mode would be available wherever any kind of markup is allowed to be entered, such as within tickets. ** ** FWIW, while searching for other implementations of similar capabilities I stumbled across Wiky (http://goessner.net/articles/wiky/), which could permit such a feature to be implemented using only client-side code. (Not that that’s an issue for Fossil, where the entire local UI server is “client side”!) ** ** ** ** TIA, ** ** -BobC ** ** ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- 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
[fossil-users] what device is full?
Hello,
Here is a suggestion. When issuing the following error message, write
the full pathname of the file on which the error occured.
[pjb@kuiper :0 src]$ fossil commit -m 'Tested with Lispworks.'
generate-application.lisp
fossil: SQLITE_FULL: statement aborts at 27: [UPDATE blob SET content=:data
WHERE rid=387]
fossil: SQL error: database or disk is full
If you have recently updated your fossil executable, you might
need to run fossil all rebuild to bring the repository
schemas up to date.
[pjb@kuiper :0 src]$
(In this case it was /tmp/something).
--
__Pascal Bourguignon__ http://www.informatimago.com/
A bad day in () is better than a good day in {}.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] A draft of ranges contribution
Dear Richard, All,
Finally, I've found a bit of time to implement the first draft of the
ranges functionality I was posting a couple of months ago
(http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg07419.html).
This is my first contribution to the project so apologize if anything
is not that clean and tidy as it should be.
From a user point of view the patch changes the way users can do
commits. First 'fossil changes' lists changes with additional column
indicating the row number, e.g.:
1 EDITED src/checkin.c
2 EDITED src/main.mk
3 EDITED src/makemake.tcl
4 ADDED src/ranges.c
5 EDITED win/Makefile.dmc
6 EDITED win/Makefile.mingw
7 EDITED win/Makefile.msc
Then using 'fossil commit --range|-r RANGE_LIST' the user can easily
pick only these files they want to check-in, e.g. 'fossil commit -r
1,3-4 -m added an extension to...' is equivalent to 'fossil commit
-m added an extension to... src/checkin.c src/makemake.tcl
src/ranges.c'
Internally, 'fossil changes' creates a temporary table in _FOSSIL_
where it stores row numbers, vfile.id and pathname. This is enough to
restore the proper file ids during 'fossil commit -r ...' and also
detect some circumstances which prevent from safe commit using
ranges. For example, if after above 'fossil changes' the user issues
'fossil rm src/main.mk' and then 'fossil commit -r 2', the code will
complain and guide the user to refresh the changes list.
I'd be glad if anyone can have a look on this and exercise the code to
see if the approach is reasonable.
If you like it, the next target might be 'fossil rm' and then 'fossil
extra' and 'fossil add'.
P.S. After patching the code please issue 'tclsh makemake.tcl' in the
'src' directory to regenerate src/main.mk and win makefiles.
Cheers,
Jacek
ranges.patch
Description: Binary data
#include config.h
#include ranges.h
#include errno.h
/*
**
**
*/
static int parse_file_range_token(const char* rangeString, int* range, int startIndex) {
char* endptr;
errno = 0;
range[startIndex] = strtol(rangeString, endptr, 10);
if (errno != 0 || range[startIndex] = 0) {
fossil_fatal(error parsing ranges);
} else if (*endptr == '-') {
char* upper = endptr;
range[startIndex + 1] = strtol(upper, endptr, 10);
if (errno != 0 || *endptr != '\0' || range[startIndex + 1] == 0) {
fossil_fatal(error parsing ranges);
}
return 2;
} else if (*endptr != '\0') {
fossil_fatal(error parsing ranges);
}
return 1;
}
/*
** Parses a string into an array of integers denoting value ranges.
** The acceptable input string is in form: \d+((-\d+)?(,\d+)?)*
** For example: '1', '1,2', '1-5,7', '1-3,20-25,9' are all acceptable.
**
** The returned array is zero-terminated and allocated on the heap.
** Negative values indicate an upper bound of a range and must be preceded by
** a positive value -- the lower bound.
**
** For the above examples the function will return following arrays:
** [1], [1, 2], [1, -5, 7], [1, -3, 20, -25, 9]
**
*/
int* parse_file_range(const char* rangeString) {
/* An arbitraty initial value; must be larger than 2. */
int reallocLimit = 20;
char *comma;
int *range = fossil_malloc(sizeof(int) * reallocLimit);
int n = 0;
while ((comma = strchr(rangeString, ',')) != NULL) {
*comma = 0;
n += parse_file_range_token(rangeString, range, n);
*comma = ',';
rangeString = comma + 1;
if (n = reallocLimit - 2) {
reallocLimit *= 2;
range = realloc(range, sizeof(int) * reallocLimit);
}
}
n += parse_file_range_token(rangeString, range, n);
range[n] = 0;
return range;
}
/*
** This is a helper function that prints contents of an integer range on
** standard output.
**
*/
void print_file_range(int* range) {
int i = 0;
printf(Range: );
while (range[i] != 0) {
printf(%d , range[i++]);
}
printf(\n);
}
___
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] HOWTO delete a Wiki page?
Didn't know the empty page heuristic - will need to add that to the json api. - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal On May 7, 2012 2:23 PM, Mike Meyer m...@mired.org wrote: On Mon, 7 May 2012 14:16:59 +0200 Jiri Navratil j...@navratil.cz wrote: I made a typo in Wiki page. Can I rename Wiki page or delete a Wiki page? In one sense, no. Artifacts are forever (though you can shun them). However, if you delete all the text from a page, it'll vanish from the list of wiki pages. mike -- Mike Meyer m...@mired.org http://www.mired.org/ Independent Software developer/SCM consultant, email for more information. O ascii ribbon campaign - stop html mail - www.asciiribbon.org ___ 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
Re: [fossil-users] Wysiwyg wiki editing. Was: Side-by-side wiki editing?
Wow, that rocks. I really should learn more about this web stuff someday. The js library and demo at kevinroth.com/rte is simple and convincing. The only major lack in that library seems to be the ability to change fonts inline (such as to show a function name in a monospaced serif font): Font changes presently apply to entire paragraphs. This limitation does not apply to the Yahoo YUI3, CKEditor, TinyMCE or goog.editor libraries, and they may be better (but heavier, though more Open) choices. My general thoughts surrounding WYSIWYG editing are: 1. Some (many? most?) non-engineer users may want to click rather than type to get their desire formatting, meaning effort may be needed to maintain GUI elements and their actions, when such effort may have greater benefits applied elsewhere within Fossil. If a library can't be found that meets 100% of Fossil's needs, it may be better to postpone full WYSIWYG support until it exists. 2. Side-by-side editing serves as a context-sensitive tutorial, where users would quickly learn the markup commands they most want to use. But this may not be something we should force users accustomed to word-processing programs to endure. It's a good, but partial, step to more universal usability. 3. WYSIWYG editing over congested or slow links could suffer unless the solution were 100% client-side, and perhaps even then if per-keystroke updates are sent to the remote server. And a pure client-side solution could mean unsaved edits could be lost. (Which may be the current situation - I haven't checked.) 4. Would slow clients suffer? Or those with older browsers? What about the increasing use of tablets? (Gotta ride that wave!) Phones? Fossil viewing is already thoroughly cross-platform: Making user input and interaction just as universal is very attractive. 5. Would WYSIWIG editing be inherently compatible with the existing markup? Or would the current markup have to be abandoned after conversion to native HTML? I'm not at all attached to the current Fossil markup (it's one of many similar systems that get the job done), but I'd make a single markup system a priority over multiple competing systems. While I am greatly in favor of improving Fossil usability to make it more useful to (and usable by) non-programmers, non-engineers and the general public, I would not want to see bend-over-backwards usability become an entangling issue that hurts Fossil as a whole. KISS applies. But if that's not a major concern, then now may be the time try some simple-to-implement ideas and see what works/feels best. I have access to some non-engineer Fossil testers who are willing to be guinea pigs... An aside: My main motivation is to avoid having to select Trac in the near term merely because of Fossil usability issues. If I do have to temporarily select Trac while Fossil usability matures, it would be a massive benefit if there would one day also be a way to import a Trac system into Fossil (code, comments, bugs, wiki, etc.) with a single (well, a few) reliable commands. That feature alone could help Fossil to better compete with Trac's installed base, and could also persuade some experienced Trac developers to support Fossil (especially to port some powerful Trac plugin functionality). -BobC From: fossil-users-boun...@lists.fossil-scm.org [mailto:fossil-users-boun...@lists.fossil-scm.org] On Behalf Of Richard Hipp Sent: Monday, May 07, 2012 7:06 AM To: Fossil SCM user's discussion Subject: [fossil-users] Wysiwyg wiki editing. Was: Side-by-side wiki editing? What if we were to provide full WYSIWYG editing of wiki pages in Fossil? I've been experimenting with the code at https://developer.mozilla.org/en/Rich-Text_Editing_in_Mozilla (with the bug on line 140 fixed, as well as other enhancements). The basic code seems to work pretty well on Firefox, Chrome, Safari, Opera, and IE, so it seems to be sufficiently cross-platform. If we extend the wiki generator to allow style= attributes on span tags, and if we surround the HTML text that comes back from this wysiwyg editor with nowiki../nowiki, then I think it might work. Another option is to translate the HTML that comes back from javascript back into the Fossil wiki format. The latter option would be trickier and more prone to error, but it would also enable the same wiki page to be edited as plain text or as wysiwyg. (The HTML that comes back from javascript is directly editable, in theory, but it is not pleasing to look at.) Unfortunately, I'm very busy with other things right now and have not had an opportunity to prototype this yet. But I'd be interested in hearing thoughts from the community on the idea, at least. On Mon, Apr 23, 2012 at 12:25 PM, Cunningham, Robert rcunning...@nsmsurveillance.commailto:rcunning...@nsmsurveillance.com wrote: I'm evaluating Trac vs. Fossil for use within our small engineering
[fossil-users] fossil push doesn't show up on the server
[pjb@kuiper :0 patchwork]$ fossil push
Server:http://fossil.informatimago.com:8002/patchwork
Bytes Cards Artifacts Deltas
Sent: 268 4 0 0
Error: not authorized to write
Received: 65 1 0 0
Total network traffic: 386 bytes sent, 276 bytes received
[pjb@kuiper :0 patchwork]$ fossil pull
Server:http://fossil.informatimago.com:8002/patchwork
Bytes Cards Artifacts Deltas
Sent: 146 2 0 0
Received: 78 2 0 0
Total network traffic: 324 bytes sent, 285 bytes received
[pjb@kuiper :0 patchwork]$ fossil push
Server:http://fossil.informatimago.com:8002/patchwork
Bytes Cards Artifacts Deltas
Sent: 268 4 0 0
Error: not authorized to write
Received: 65 1 0 0
Total network traffic: 387 bytes sent, 276 bytes received
[pjb@kuiper :0 patchwork]$ fossil status
repository: /home/pjb/works/patchwork/patchwork/../patchwork.fossil
local-root: /home/pjb/works/patchwork/patchwork/
checkout: 6d88e9d9e206b3fe641e3050c1c321e0e98e0872 2012-05-07 15:00:19 UTC
parent: 19efd2e28b33dd1acd93f603bd0c95edb1b42b27 2012-05-07 14:11:19 UTC
tags: trunk
comment: Added Makefile. (user: pjb)
[pjb@kuiper :0 patchwork]$ fossil timeline
=== 2012-05-07 ===
15:00:19 [6d88e9d9e2] *CURRENT* Added Makefile. (user: pjb tags: trunk)
14:46:48 [13d579f58a] Changes to wiki page [PatchWork/MacOSX] (user: pjb)
14:45:24 [4a7ddd781d] Changes to wiki page [PatchWork/MacOSX] (user: pjb)
14:45:00 [52a205b51a] Changes to wiki page [PatchWork/MacOSX] (user: pjb)
14:44:34 [2c5ba740a6] Changes to wiki page [PatchWork/MacOSX] (user: pjb)
But when I clone and open http://fossil.informatimago.com:8002/patchwork
or just watch it on the web server, the last commit doesn't appear:
[pjb@kuiper :0 p]$ fossil status
repository: /tmp/p/../patchwork.fossil
local-root: /tmp/p/
checkout: 19efd2e28b33dd1acd93f603bd0c95edb1b42b27 2012-05-07 14:11:19 UTC
parent: cba26aa1935252fbf017d2bf4e7d96d5ca447a66 2012-05-07 14:11:09 UTC
tags: trunk
comment: Changed license to GPL3; added header comments. (user: pjb)
What's wrong? What should I do to push my commits?
--
__Pascal Bourguignon__ http://www.informatimago.com/
A bad day in () is better than a good day in {}.
___
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 push doesn't show up on the server
On Mon, May 07, 2012 at 06:23:53PM +0200, Pascal J. Bourguignon wrote: What's wrong? What should I do to push my commits? Your answer is in the output of your failed fossil push: Error: not authorized to write -- James Turner ja...@calminferno.net ___ 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] Wysiwyg wiki editing. Was: Side-by-side wiki editing?
On Mon, May 7, 2012 at 11:44 AM, Cunningham, Robert rcunning...@nsmsurveillance.com wrote: Wow, that rocks. I really should learn more about this web stuff someday. ** ** The js library and demo at kevinroth.com/rte is simple and convincing. The only major lack in that library seems to be the ability to change fonts inline (such as to show a function name in a monospaced serif font): Font changes presently apply to entire paragraphs. This limitation does not apply to the Yahoo YUI3, CKEditor, TinyMCE or goog.editor libraries, and they may be better (but heavier, though more Open) choices. ** ** My general thoughts surrounding WYSIWYG editing are: ** ** **1. **Some (many? most?) non-engineer users may want to click rather than type to get their desire formatting, meaning effort may be needed to maintain GUI elements and their actions, when such effort may have greater benefits applied elsewhere within Fossil. If a library can’t be found that meets 100% of Fossil’s needs, it may be better to postpone full WYSIWYG support until it exists. ** ** **2. **Side-by-side editing serves as a context-sensitive tutorial, where users would quickly learn the markup commands they most want to use. But this may not be something we should force users accustomed to word-processing programs to endure. It’s a good, but partial, step to more universal usability. ** ** **3. **WYSIWYG editing over congested or slow links could suffer unless the solution were 100% client-side, and perhaps even then if per-keystroke updates are sent to the remote server. And a pure client-side solution could mean unsaved edits could be lost. (Which may be the current situation – I haven’t checked.) All editing is on the client side. The server only gets involved when the user presses the Apply button. ** ** **4. **Would slow clients suffer? Or those with older browsers? What about the increasing use of tablets? (Gotta ride that wave!) Phones? Fossil viewing is already thoroughly cross-platform: Making user input and interaction just as universal is very attractive. ** ** **5. **Would WYSIWIG editing be inherently compatible with the existing markup? Or would the current markup have to be abandoned after conversion to native HTML? I’m not at all attached to the current Fossil markup (it’s one of many similar systems that get the job done), but I’d make a single markup system a priority over multiple competing systems. The current markup is very close to HTML. Think of the current markup as HTML + extensions (blank line means paragraph, etc). The nowiki.../nowiki tags on wiki mean that all markup is 100% HTML. Note, however, that for security reasons certain HTML tags are disallowed. (e.g.: script). And certain attributes too, such as style= in span. The latter is used by Firefox for client-side WYSIWYG so we'd have to relax the constraint and allow it, or else backtranslate the span tags generated by Firefox to biu and s. ** ** While I am *greatly* in favor of improving Fossil usability to make it more useful to (and usable by) non-programmers, non-engineers and the general public, I would not want to see bend-over-backwards usability become an entangling issue that hurts Fossil as a whole. KISS applies. But if that’s not a major concern, then now may be the time try some simple-to-implement ideas and see what works/feels best. I have access to some non-engineer Fossil testers who are willing to be guinea pigs… ** ** An aside: My main motivation is to avoid having to select Trac in the near term merely because of Fossil usability issues. If I do have to temporarily select Trac while Fossil usability matures, it would be a massive benefit if there would one day also be a way to import a Trac system into Fossil (code, comments, bugs, wiki, etc.) with a single (well, a few) reliable commands. That feature alone could help Fossil to better compete with Trac’s installed base, and could also persuade some experienced Trac developers to support Fossil (especially to port some powerful Trac plugin functionality). ** ** ** ** -BobC ** ** ** ** ** ** *From:* fossil-users-boun...@lists.fossil-scm.org [mailto: fossil-users-boun...@lists.fossil-scm.org] *On Behalf Of *Richard Hipp *Sent:* Monday, May 07, 2012 7:06 AM *To:* Fossil SCM user's discussion *Subject:* [fossil-users] Wysiwyg wiki editing. Was: Side-by-side wiki editing? ** ** What if we were to provide full WYSIWYG editing of wiki pages in Fossil? I've been experimenting with the code at https://developer.mozilla.org/en/Rich-Text_Editing_in_Mozilla (with the bug on line 140 fixed, as well as other enhancements). The basic code seems to work pretty well on Firefox, Chrome, Safari, Opera, and IE, so it seems to be sufficiently cross-platform. If we extend the wiki generator to allow
Re: [fossil-users] fossil push doesn't show up on the server
James Turner ja...@calminferno.net writes:
On Mon, May 07, 2012 at 06:23:53PM +0200, Pascal J. Bourguignon wrote:
What's wrong? What should I do to push my commits?
Your answer is in the output of your failed fossil push:
Error: not authorized to write
Why am I not?
I created the remote by copying it with scp from a local repo I was
obviously authorized to modify.
I can login on the remote web with my usual login/password.
I re-cloned the local from the remote.
--
__Pascal Bourguignon__ http://www.informatimago.com/
A bad day in () is better than a good day in {}.
___
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 push doesn't show up on the server
On Mon, May 7, 2012 at 7:02 PM, Pascal J. Bourguignon p...@informatimago.com wrote: I re-cloned the local from the remote. When you cloned it, did you add username:password to the URL? If not, try cloning with that. It doesn't look like you did because the Server: line does not show your name, like this: stephan@tiny:~/cvs/fossil/cpdo$ f push Server:http://step...@fossil.wanderinghorse.net/repos/cpdo/index.cgi Bytes Cards Artifacts Deltas Sent: 636 12 0 0 Received: 32 1 0 0 Total network traffic: 640 bytes sent, 286 bytes received -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ 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 push doesn't show up on the server
I think this is a good illustration of how noisy output makes it hard for new users to see problems occurring. I would prefer to see most of the sync output suppressed unless a verbose switch is flipped. Most of the time people really only need to know that the sync succeeded or failed. At the very least make the error messages stand out more with an all upper case ERROR: prefix. On Mon, May 7, 2012 at 9:29 AM, James Turner ja...@calminferno.net wrote: On Mon, May 07, 2012 at 06:23:53PM +0200, Pascal J. Bourguignon wrote: What's wrong? What should I do to push my commits? Your answer is in the output of your failed fossil push: Error: not authorized to write -- James Turner ja...@calminferno.net ___ 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
Re: [fossil-users] fossil push doesn't show up on the server
Stephan Beal sgb...@googlemail.com writes:
On Mon, May 7, 2012 at 7:02 PM, Pascal J. Bourguignon
p...@informatimago.com wrote:
I re-cloned the local from the remote.
When you cloned it, did you add username:password to the URL? If not,
try cloning with that. It doesn't look like you did because the
Server: line does not show your name, like this:
No, indeed, I did not.
It works better if I clone it adding the user:password to the url.
Thank you.
--
__Pascal Bourguignon__ http://www.informatimago.com/
A bad day in () is better than a good day in {}.
___
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 push doesn't show up on the server
Matt Welland estifo...@gmail.com writes:
I think this is a good illustration of how noisy output makes it hard
for new users to see problems occurring. I would prefer to see most of
the sync output suppressed unless a verbose switch is flipped. Most
of the time people really only need to know that the sync succeeded or
failed. At the very least make the error messages stand out more with
an all upper case ERROR: prefix.
Definitely.
Also it's better of the error message is last in the output.
And in the case of cloning without a user:password, it might be good to
issue a warning that an anonymous clone has been done.
Alternatively, there could be a way to change the remote user:password
after cloning.
--
__Pascal Bourguignon__ http://www.informatimago.com/
A bad day in () is better than a good day in {}.
___
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] Bug - Pictures not loaded consistently in wiki
Confirmed on Google Chrome under Win7, except I never saw both images displayed simultaneously (top, bottom or neither, never both). -BobC From: fossil-users-boun...@lists.fossil-scm.org [mailto:fossil-users-boun...@lists.fossil-scm.org] On Behalf Of Bjorn Madsen Sent: Monday, May 07, 2012 12:56 PM To: fossil-users@lists.fossil-scm.org Subject: [fossil-users] Bug - Pictures not loaded consistently in wiki First of all thanks for a great piece of software, and all the constructive dialogue on the mailing list. It is quite educative! Whilst reading the wiki I noticed a minor bug - that pictures are not loaded consistently when reading pages. I have taken 4 screenshots from http://www.fossil-scm.org/index.html/doc/trunk/www/branching.wiki by re-loading (F5) the pages a few times, to illustrate the inconsistency. (All attached). I hope it may help? Kind Regards -- Bjorn ___ 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] Bug - Pictures not loaded consistently in wiki
On Mon, May 7, 2012 at 9:56 PM, Bjorn Madsen bjorn.h.mad...@googlemail.comwrote: org/index.html/doc/trunk/www/branching.wikihttp://www.fossil-scm.org/index.html/doc/trunk/www/branching.wiki by re-loading (F5) the pages a few times, to illustrate the inconsistency. (All attached). My _guess_ is that it's a locking issue when the IMG requests are sent off and contend for fossil. Maybe we can convince one of the developers better versed in sqlite3 locking handling than i to take a look at it. -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ 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] SSH commands run as user nobody
At Mon, 7 May 2012 06:51:19 -0400, Martin Gagnon wrote: Have you update server side as well? Here is the output of fossil version on the server: This is fossil version 1.22 [7fb59a67dc] 2012-05-05 13:53:37 UTC Here is the output of fossil version on the client: This is fossil version 1.22 [7fb59a67dc] 2012-05-05 13:53:37 UTC I just issued another fossil all rebuild on both the client and the server to make sure that I didn't miss anything. I am still getting the Error: not authorized to read error. First I tried just rebuilding on the client side, then trying the sync, which didn't work, giving the same error. Then I tried closing the repository on the client side, re-cloning under sshfs again, changing the remote-url (where it prompted me for the password as normally, then issuing the fossil sync command. Basically, it displays the Sent: packets as it should, then it gives the Error: not authorized to read, then it prints the received packets. In my testing, the sync never actually updated the repository until I gave nobody expanded permissions, in which the latest revisions were updated on the timeline command. Maybe the fix is in a branch other than trunk? Should I try another branch when installing from the fossil repository? Possibly unrelated: Maybe my issue is specific to FreeBSD? I am testing this under /bin/sh shell (I have my shell even changed to /bin/sh at the moment on the server side to ensure the proper behavior) because the ssh commands do not work under tcsh at all... Tim ___ 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] SSH commands run as user nobody
Regarding ssh transport for fossil: I've been trying to get ssh to work with fsecure and on Linux (openssh) and I have never had any luck. If someone using fossil ssh for clone, sync etc. with different user(s) or different hosts at either end of the pipe could post their exact setup and settings I will try again as I really need this to work. On Mon, May 7, 2012 at 1:29 PM, Timothy Beyer bey...@fastmail.net wrote: At Mon, 7 May 2012 06:51:19 -0400, Martin Gagnon wrote: Have you update server side as well? Here is the output of fossil version on the server: This is fossil version 1.22 [7fb59a67dc] 2012-05-05 13:53:37 UTC Here is the output of fossil version on the client: This is fossil version 1.22 [7fb59a67dc] 2012-05-05 13:53:37 UTC I just issued another fossil all rebuild on both the client and the server to make sure that I didn't miss anything. I am still getting the Error: not authorized to read error. First I tried just rebuilding on the client side, then trying the sync, which didn't work, giving the same error. Then I tried closing the repository on the client side, re-cloning under sshfs again, changing the remote-url (where it prompted me for the password as normally, then issuing the fossil sync command. Basically, it displays the Sent: packets as it should, then it gives the Error: not authorized to read, then it prints the received packets. In my testing, the sync never actually updated the repository until I gave nobody expanded permissions, in which the latest revisions were updated on the timeline command. Maybe the fix is in a branch other than trunk? Should I try another branch when installing from the fossil repository? Possibly unrelated: Maybe my issue is specific to FreeBSD? I am testing this under /bin/sh shell (I have my shell even changed to /bin/sh at the moment on the server side to ensure the proper behavior) because the ssh commands do not work under tcsh at all... Tim ___ 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
Re: [fossil-users] SSH commands run as user nobody
On Mon, May 07, 2012 at 01:37:39PM -0700, Matt Welland wrote: Regarding ssh transport for fossil: I've been trying to get ssh to work with fsecure and on Linux (openssh) and I have never had any luck. If someone using fossil ssh for clone, sync etc. with different user(s) or different hosts at either end of the pipe could post their exact setup and settings I will try again as I really need this to work. iirc, fossil can work bad if you have a .bashrc or .bash_profile that outputs text or things like that. I remember having troubles with this. On Mon, May 7, 2012 at 1:29 PM, Timothy Beyer bey...@fastmail.net wrote: At Mon, 7 May 2012 06:51:19 -0400, Martin Gagnon wrote: Have you update server side as well? Here is the output of fossil version on the server: This is fossil version 1.22 [7fb59a67dc] 2012-05-05 13:53:37 UTC Here is the output of fossil version on the client: This is fossil version 1.22 [7fb59a67dc] 2012-05-05 13:53:37 UTC I just issued another fossil all rebuild on both the client and the server to make sure that I didn't miss anything. I am still getting the Error: not authorized to read error. First I tried just rebuilding on the client side, then trying the sync, which didn't work, giving the same error. Then I tried closing the repository on the client side, re-cloning under sshfs again, changing the remote-url (where it prompted me for the password as normally, then issuing the fossil sync command. Basically, it displays the Sent: packets as it should, then it gives the Error: not authorized to read, then it prints the received packets. In my testing, the sync never actually updated the repository until I gave nobody expanded permissions, in which the latest revisions were updated on the timeline command. Maybe the fix is in a branch other than trunk? Should I try another branch when installing from the fossil repository? Possibly unrelated: Maybe my issue is specific to FreeBSD? I am testing this under /bin/sh shell (I have my shell even changed to /bin/sh at the moment on the server side to ensure the proper behavior) because the ssh commands do not work under tcsh at all... Tim ___ 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 mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Bug - Pictures not loaded consistently in wiki
On Mon, May 7, 2012 at 3:56 PM, Bjorn Madsen bjorn.h.mad...@googlemail.comwrote: First of all thanks for a great piece of software, and all the constructive dialogue on the mailing list. It is quite educative! Whilst reading the wiki I noticed a minor bug - that pictures are not loaded consistently when reading pages. I have taken 4 screenshots from http://www.fossil-scm.org/index.html/doc/trunk/www/branching.wiki by re-loading (F5) the pages a few times, to illustrate the inconsistency. (All attached). Please try this again now. I hope it may help? Kind Regards -- Bjorn * * ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- 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
Re: [fossil-users] SSH commands run as user nobody
I tried a number of approaches to implementing ssh:. I finally settled on the following: (1) Run the ssh command using system() to get a shell on the remote system. (2) Send an echo command and get the reply. Hopefully this will move past the welcome banner. (3) Run fossil http on the remote side. (4) Start sending HTTP requests from the local side to the remote, and accepting replies back. (5) After the last reply is received, shut down the SSH pipe. All of the above is pretty fragile based on what flavor of SSH you are running locally and on the remote, what kind of banner messages are issued by the remote, how the various SSH implementations handle password management and authentication, quirks and idiosyncrasies of both systems and their SSH implementation, etc. It works in many instances, but it is brittle and there are still issues. If you have a non-working scenario and can suggest changes to make the system more robust, then please contribute. -- 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
