[fossil-users] `fossil init --admin-user` not sufficient anymore
Hi, I used to create my fossil repositories (scripted with fossil init --admin-user $user $repo But I just noticed that with 1.24, this does not work anymore, instead, fossil will reply with: Cannot figure out who you are! Consider using the --user command line option, setting your USER environment variable, or setting a default user with fossil user default USER. fossil: cannot determine user I have to use: fossil init --user $user --admin-user $user $repo Though `fossil --help init` still only shows admin-user as the option to set the user. What is the right way to go? Regards, Julian ___ 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 editing
Hi, A sandbox repository with open permissions and with WYSIWYG editing turned on has been created at http://www.fossil-scm.org/sandbox - please experiment and provide feedback. I tried a bit, but I'm not really a guy who uses these things. I like to switch off JS in my browser, and often I am behind a very restrictive proxy which strips out JS things. I did some editing, had an unordered list, then an ordered list, and then was under that list and wanted to insert another unordered list, but then Opera (12.01 on NetBSD) crashed (as in Send problem report to Opera company). I used this version today the first day, maybe it's the browser, but in any case it shouldn't happen. Anyway, I would rather like small additions to the wiki syntax (or using another processor, like Markdown which was often proposed) than a wysiwyg editor. * imho the two most important things for documentation, but currently missing in wiki syntax are embedded images and tables. Both are not possible with the wysiwyg editor. * I don't see the point in undo/redo buttons - maybe there are people using it, I always use Ctrl+Z/Y for this. * so the alignment: Do people really use alignment stuff in documentation wikis (I assume this is fossil's most probable use case)? * what does the Remove formatting button do? * the indentation buttons have a reverted description * why is there a separate blockquote button, which does the same as indentation? * colouring doesn't work for me (Opera behind privoxy) * selecting text, then selecting the colour, etc. above demarks the text and only changes the current line * when doing a newline, all formatting of the foregoing line is lost. If I wanted to do e.g. the whole text in red, I would have to reset that with every paragraph I write. Regards, Julian ___ 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] URL recognition fails with unknown protocols?
Hi, But then, if you try [irc://servername.tld|#channel] as a link in the wiki, this will be treated as a wiki subpage, i.e. redirected to $site/wiki=$url. Is there a way to do this without using HTML? Did you try: [irc://servername.tld#channel] or [irc://servername.tld/#channel] The verticle bar in your example could be (part of) the problem. actually, there were more haches in the URL. The bar was used to divide url from link name, the link should show up like '#channelname'. Regards, Julian ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] URL recognition fails with unknown protocols?
Hi, a friend just tried to edit a wiki page, and add a link to an IRC server (most recent browsers can handle this). This means, the URL specified was irc://servername.tld. But then, if you try [irc://servername.tld|#channel] as a link in the wiki, this will be treated as a wiki subpage, i.e. redirected to $site/wiki=$url. Is there a way to do this without using HTML? Regards, Julian ___ 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] wiki full text search?
Hi, I would like to add that having full text search would be a huge step forward for those who use fossil for other things than its primary purpose. I've been using fossil as CMS for a website, it works great. Having a built-in way to search the content of wiki pages and tickets would be amazing. However, I understand that fossil is a SCM and I patiently wait while more important features are being implemented (I was happy with fossil stash because before it I used to commit partial work to a temporary branch and merge everytime). I just want to second that! Fossil is a very nice tool for an integrated project management, and an (optional, to be activated) wiki search engine would clearly be benefitial for that. Regards, Julian ___ 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 coredumping and reporting malformed manifest on sparc64
Hi, Compiling went fine, and after updating sqlite, it didn't even throw SQL errors anymore. ;-) So far, I can initialise a repository, add files, start a server, but whenever I want to commit, I get the message: fossil: manifest file (3) is malformed I'm sorry I waited until now, but the problem persists, though there was a change in 1.21 (at least there was an entry in the changelog). The second issue is about fossil 1.20: I configured it manually and built it, but whenever I want to commit with that version, it simply coredumps. The pkgsrc-1.18 does not patch anything, but just compile fossil, so I think this is rather a fossil issue. 1.21 compiled btw fine on my machine. :-) Regards, Julian ___ 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 coredumping and reporting malformed manifest on sparc64
Hi, so I'm sending this mail the fourth time... are mails from outside the mailing list dropped? I got so far no mail that mine is waiting for being approved, and it was sent three days ago (g...@komkon2.de). On my NetBSD sparc64 I installed fossil 1.18 (the most recent version on pkgsrc): NetBSD $HOSTNAME 5.99.55 NetBSD 5.99.55 (NETRAT1) #6: Thu Jul 28 15:14:56 CEST 2011 $BUILDCONFIG sparc64 Compiling went fine, and after updating sqlite, it didn't even throw SQL errors anymore. ;-) So far, I can initialise a repository, add files, start a server, but whenever I want to commit, I get the message: fossil: manifest file (3) is malformed No matter how much I add or what it is. A typical log: A typical log: $ fossil init blakopf project-id: 52d8d1d05ce6b474e88e19a19b8a9a54a800589a server-id: b374ce2c60b1f7849e050f724f7f37dbd046f98e admin-user: gnrp (initial password is 115ecd) $ fossil open blakopf $ touch distinfo $ fossil add distinfo ADDED distinfo $ fossil commit -m toll New_Version: 248065b1c79f682e5138ebccdaf2c6da0d4e9070 fossil: manifest file (3) is malformed $ Then I installed the binary file for sparc (32-bit), and tested it as well on my old SparcStation LX, and there it ran fine. This works for now, but I'd rather like to have the right and self-compiled version for my architecture. The second issue is about fossil 1.20: I configured it manually and built it, but whenever I want to commit with that version, it simply coredumps. The pkgsrc-1.18 does not patch anything, but just compile fossil, so I think this is rather a fossil issue. I can of course provide traces of the calls, if you want. Regards, Julian ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Providing fossil as a vcs, wiki or blog for 'users'
Hi, I'm somewhat new to fossil, but I'm absolutely astonished by the features it provides despite its simplicity. I'd like to provide fossil for our (ISPs) users because of its ease of automation: 1. fossil init 2. fossil user password 3. Generate DNS records, config and CGI for webserver Users would access the repository only via http or https, but they can also (though not automatically) get shell access. This way, we could simply provide an automated wiki and vcs creation. For people who dislike fossil as a wiki or vcs, there are still other solutions, but they're not automated, so that wouldn't stop me. So, my question: Do you think fossil is appropriate? As I said, I'm relatively new to fossil, and may not have tried out all features. Would you have security concerns about that? And do you have any suggestions what might help me with that? Are there standard settings you would suggest? Regards, Julian ___ 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 coredumping and reporting malformed manifest on sparc64
Hi, please excuse my overlengthy lines, it was easier to not-wrap this content. As best as i can tell that's your OS segfaulting, not fossil. It returns from a write() and then immediately throws a sigbus? sigbus is something i've only seen on sparc, and i've personally only seen it when linking to invalid system libs (e.g. those compiled for other platforms). A bit of googling shows sigbus to sometimes be alignment-related. The address being passed to write() is 0x40b16808 (dec=1085368328), which should be properly aligned for 32/64-bit. Though I wouldn't bet on it, I think I've already seen SIGBUS on x86 with FreeBSD. It should be quite tricky C code for a C compiler to generate bad-aligned accesses for a given platform. I'd like to know where is that bad access; I've not checked, but I'd imagine fossil has no tricky C code. Fossil doesn't have any tricky C code (or at least it shouldn't - if you find some we'll call it a bug.) But SQLite does definitely have tricky C code. We've had SIGBUS problems running SQLite on sparc before, but I thought we had fixed all those. On the other hand, I don't have sparc on which to test SQLite so I'm not really sure. You're right, seems to be sqlite. $ gdb fossil-src-20111021125253/fossil GNU gdb 6.5 Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as sparc64--netbsd... (gdb) run init blakopf Starting program: /home/gnrp/temp/fossil-src-20111021125253/fossil init blakopf Program received signal SIGBUS, Bus error. 0x001b7560 in sqlite3CreateIndex (pParse=0x40b03008, pName1=value optimized out, pName2=value optimized out, pTblName=0x0, pList=0x40b10288, onError=value optimized out, pStart=0x0, pEnd=0x0, sortOrder=0, ifNotExist=0) at ./src/sqlite3.c:82174 82174 pIndex-azColl[i] = zColl; (gdb) I used svn before which uses sqlite, too (at least it's the dependency), but it worked flawless. Regards, Julian ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
