Re: [fossil-users] About to merge the forum-v2 branch
El 03/08/2018 a las 11:13, Warren Young escribió: > The vast majority of mail users *do* go out and specifically pull emails, > either via IMAP or by visiting a web mail interface of some kind. Is there a reason why you exclude POP3 from the "pulling"? ___ 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] Checkin [a9578f7870] freezes Windows server
El 01/08/2018 a las 21:17, Joe Mistachkin escribió: > Richie Adler wrote: >> Compiling checkin a9578f7870 in Windows 7 freezes the server; whatever > task is >> running, it never ends, and the timeline does not update, neither does the >> files list. > I'm unable to reproduce the issue here (also Windows 7). Do you have any > further > details on how to see the problem? Does it (eventually) stop after 120 > seconds? At 120 seconds it goes to the intended page, yes. When I try to open any of the main selections on the menu (Timeline, Files, Branches...), it shows only the title or it remain frozen to the previously open until the 120 seconds end and the page refreshes. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Checkin [a9578f7870] freezes Windows server
Compiling checkin a9578f7870 in Windows 7 freezes the server; whatever task is running, it never ends, and the timeline does not update, neither does the files list. Going back to d5c41263af restores functionality. -- o-=< Marcelo >=-o ___ 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] Unnable to merge: Cannot find a common ancestor between the current checkout and ID
Richard, I'm having now the same problem in my repository at https://chiselapp.com/user/richieadler/repository/axxoneval/ I'm trying to merge the branch "mejorasilus" into trunk. For "fossil stat" I get [...] checkout: 4541a5d4ba186d49dbc8e2f31ab91796fee90de3 2018-05-30 22:43:54 UTC parent: 0fa7991da7a851e7ab69c8b11217db666d467ef3 2018-05-26 00:20:26 UTC child:6f2cb868897367ce42ef2aeb5283e876bb8fd6eb 2018-06-03 17:30:43 UTC tags: trunk comment: Bugfix: modified_on=request.now al poner a cero las evaluaciones (user: Kilroy) >f merge mejorasilus Autosync: http://richiead...@chiselapp.com/user/richieadler/repository/axxoneval Round-trips: 1 Artifacts sent: 0 received: 0 Pull done, sent: 405 received: 2377 ip: 74.208.146.128 cannot find a common ancestor between the current checkout and mejorasilus >f merge 82494c4441 Autosync: http://richiead...@chiselapp.com/user/richieadler/repository/axxoneval Round-trips: 1 Artifacts sent: 0 received: 0 Pull done, sent: 407 received: 2378 ip: 74.208.146.128 cannot find a common ancestor between the current checkout and 82494c4441 You should be able to access anonymously to the repository... any ideas? Compiled in Windows 7 with MinGW. This is fossil version 2.6 [f39d0a7290] 2018-06-04 19:52:53 UTC ___ 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] Error compiling Fossil in Windows for 396513fa
El 19/01/2018 a las 16:12, Richard Hipp escribió: > I moved the offending check-in onto a branch. Please do "fossil up > trunk" and then try again. [6b41a7e803] compiles perfectly. Thank you. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Error compiling Fossil in Windows for 396513fa
I get the following warning in compilation: src/checkin.c: In function 'status_cmd': src/checkin.c:477:7: warning: implicit declaration of function 'getuid' [-Wimplicit-function-declaration] if( getuid()==0 ){ ^ and then on link: wbld/checkin.o:checkin_.c:(.text+0xea9): undefined reference to `getuid' collect2.exe: error: ld returned 1 exit status make: *** [fossil.exe] Error 1 Version [4f90d591aa] compiles perfectly. Compiled under Windows 7, gcc version 5.3.0 (x86_64-posix-seh-rev0, Built by MinGW-W64 project) ___ 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] Errors in current trunk (24c2b99d) related to TIMESPEC
El 09/01/2018 a las 18:27, The Tick escribió: > Zero errors or warnings. Very nice. Thank you. I concur, same result on my end. Thank you very much. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Errors in current trunk (24c2b99d) related to TIMESPEC
Compiling current trunk (24c2b99d) under Windows 7, I get these errors (maybe even with the spaces the lines are considered proper #define directives?) src/shell.c:2074:0: warning: "stat" redefined # define stat _stat ^ In file included from src/shell.c:108:0: c:/Prog/mingw-w64/x86_64-5.3.0-win32-seh-rt_v4-rev0/mingw64/x86_64-w64-mingw32/include/sys/stat.h:268:0: note: this is the location of the previous definition #define stat _stat64 ^ src/shell.c:2073:20: warning: 'struct TIMESPEC' declared inside parameter list # define timespec TIMESPEC ^ src/shell.c:2073:20: warning: its scope is only this definition or declaration, which is probably not what you want src/shell.c:2073:20: warning: 'struct TIMESPEC' declared inside parameter list # define timespec TIMESPEC ^ src/shell.c:2073:20: warning: 'struct TIMESPEC' declared inside parameter list # define timespec TIMESPEC ^ src/shell.c:2073:20: warning: 'struct TIMESPEC' declared inside parameter list # define timespec TIMESPEC ^ src/shell.c:2073:20: warning: 'struct TIMESPEC' declared inside parameter list # define timespec TIMESPEC ^ src/shell.c: In function 'writefileFunc': src/shell.c:2327:9: warning: implicit declaration of function 'S_ISLNK' [-Wimplicit-function-declaration] if( S_ISLNK(mode) ){ ^ src/shell.c: At top level: src/shell.c:2346:3: error: unknown type name 'DIR' DIR *pDir; /* From opendir() */ ^ src/shell.c: In function 'fsdirResetCursor': src/shell.c:2422:22: warning: implicit declaration of function 'closedir' [-Wimplicit-function-declaration] if( pLvl->pDir ) closedir(pLvl->pDir); ^ src/shell.c: In function 'fsdirNext': src/shell.c:2484:18: warning: implicit declaration of function 'opendir' [-Wimplicit-function-declaration] pLvl->pDir = opendir(pLvl->zDir); ^ src/shell.c:2484:16: warning: assignment makes pointer from integer without a cast [-Wint-conversion] pLvl->pDir = opendir(pLvl->zDir); ^ src/shell.c:2493:29: warning: implicit declaration of function 'readdir' [-Wimplicit-function-declaration] struct dirent *pEntry = readdir(pLvl->pDir); ^ src/shell.c:2493:29: warning: initialization makes pointer from integer without a cast [-Wint-conversion] src/shell.c:2495:17: error: dereferencing pointer to incomplete type 'struct DIRENT' if( pEntry->d_name[0]=='.' ){ ^ make: *** [wbld/shell.o] Error 1 ___ 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 with IPv6 support on Windows XP
El 03/01/2018 a las 16:38, Olivier Mascia escribió: > Merely replacing "127.0.0.1" with "::1". In my Windows 7 x64 installation, updating to 96dcb7e7 and making the indicated change DOES NOT restore the --localauth functionality. ___ 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 with IPv6 support on Windows XP
Florian Balmer decía, en el mensaje "Re: [fossil-users] Fossil with IPv6 support on Windows XP" del 3/1/2018 14:59:05: > Re: Fossil with IPv6 support on Windows XP > > I have several physical and virtual XP machines around, and `fossil > ui' doesn't work any more with the new patch. I can add that starting with 21d5038f, for "fossil server", localhost access without login stops working even when the --localauth is passed on invocation, at least in my Windows 7 installation. I use this to access all my local repos without login so I reverted to 6b5cfc86. ___ 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] Load customized skin from subdirectory on Windows
El 26/05/2017 a las 09:44, Florian Balmer escribió: > I would highly appreciate a configuration option (similar to > `index-page') to set custom default timeline query parameters. +1 ___ 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] Issue with crlf-glob *
Thomas decía, en el mensaje "[fossil-users] Issue with crlf-glob *" del 8/4/2017 17:46:14: > Does anyone know how to unveil the secret of getting the mentioned > asterisk into the crlf-glob setting without consulting the web interface? For me, it works if I enter the asterisk as '*'. I'm on Windows 7 Ultimate Build 7601 SP 1. This is fossil version 2.2 [9612d43f93] 2017-03-18 14:10:13 UTC Compiled on Mar 18 2017 13:48:53 using mingw32 (64-bit) ___ 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] [PROPOSED FEATURE] Fossil commands output sent through a pager
Sergei Gavrikov decía, en el mensaje "Re: [fossil-users] [PROPOSED FEATURE] Fossil commands output sent through a pager" del 25/3/2017 14:09:57: > My 2 cents. Many of us use f-alias to deal with fossil in a terminal, > right? Then why not f-function? Maybe because not everybody uses Unix-like operating systems? ___ 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] Problem with Fossil compilation on Windows
Jan Nijtmans decía, en el mensaje "Re: [fossil-users] Problem with Fossil compilation on Windows" del 23/1/2017 08:02:41: > Did you do a full clean before re-building? If not, the earlier built > libz.a will not be built again. I had, but just in case I did it again just now. Same errors. ___ 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] Problem with Fossil compilation on Windows
> Jan Nijtmans Thu, 19 Jan 2017 01:57:05 -0800 > > 2017-01-19 0:13 GMT+01:00 Richie Adler: >> Windows 7 Ultimate 64 bit >> gcc (x86_64-win32-seh-rev0, Built by MinGW-W64 project) 5.3.0 >> >> Running this: >> >> C:\Prog\MinGW\msys\1.0\bin\make.exe -e -f win\Makefile.mingw clean >> SET FOSSIL_ENABLE_JSON=1 >> C:\Prog\MinGW\msys\1.0\bin\make.exe -e -f win\Makefile.mingw >> >> Generates these errors: >> >> src/../compat/zlib/libz.a(deflate.o):deflate.c:(.text+0x745): undefined >> reference to `longest_match' > ... > > > Try: > C:\Prog\MinGW\msys\1.0\bin\make.exe -e -f win\Makefile.mingw X64=1 > FOSSIL_ENABLE_JSON=1 > > Just have a look at comment line #16 of win\Makefile.mingw, you'll see why. > Sadly, that didn't solve the issue. Same errors. > If you want a full 64-bit (with openssl-1.1.0c and more, json too), > have a look at: > <https://sourceforge.net/projects/cyqlite/files/fossil/> I may try that, but I really enjoyed being able to compile my own Fossil. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Problem with Fossil compilation on Windows
Windows 7 Ultimate 64 bit gcc (x86_64-win32-seh-rev0, Built by MinGW-W64 project) 5.3.0 Running this: C:\Prog\MinGW\msys\1.0\bin\make.exe -e -f win\Makefile.mingw clean SET FOSSIL_ENABLE_JSON=1 C:\Prog\MinGW\msys\1.0\bin\make.exe -e -f win\Makefile.mingw Generates these errors: src/../compat/zlib/libz.a(deflate.o):deflate.c:(.text+0x745): undefined reference to `longest_match' src/../compat/zlib/libz.a(deflate.o):deflate.c:(.text+0x1414): undefined reference to `longest_match' src/../compat/zlib/libz.a(deflate.o):deflate.c:(.text+0x1cb0): undefined reference to `match_init' src/../compat/zlib/libz.a(deflate.o):deflate.c:(.text+0x3fdd): undefined reference to `match_init' src/../compat/zlib/libz.a(deflate.o):deflate.c:(.text+0x43e9): undefined reference to `match_init' src/../compat/zlib/libz.a(inflate.o):inflate.c:(.text+0x2093): undefined reference to `inflate_fast' collect2.exe: error: ld returned 1 exit status make: *** [fossil.exe] Error 1 ___ 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] OT: Why we should NEVER use inetd/xinetd
Nathaniel Reindl decía, en el mensaje "Re: [fossil-users] OT: Why we should NEVER use inetd/xinetd" del 28/10/2016 08:23:28: > From my perspective, this thread has far outlasted its usefulness and has > become an exercise in self-satisfaction for those who prefer to write words > instead of writing code. Can we perhaps refrain from offering > attention-addicted individuals the attention they so desperately crave? Apparently I did something like that previously; the OP is in my blocklist. I would encourage others to do the same. ___ 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] features I'd like to have in fossil
> * suggestions on what could be improved to make Fossil easier to use for me As a mere reader of the list, I have to ask: why should *the Fossil team* consider this important? You haven't presented any compelling reason to change significatively the way Fossil operates, besides that it would be nice for you. Am I missing something? ___ 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 on HN
Lonnie Abelbeck decía, en el mensaje "Re: [fossil-users] Fossil on HN" del 10/10/2016 09:46:54: > > On Oct 9, 2016, at 8:31 PM, Richard Hippwrote: > >> https://news.ycombinator.com/item?id=12673229 > > Our project uses Fossil to track configuration files for various open source > packages, git was a non-starter for our small, embedded 50 MB image. > > Fossil's small footprint and efficiency with built-in web tools makes it > apples vs. oranges to most other VCS. Your case is a very nice "success story". Fossil is a perfect example of an excuse that has to die. *Nobody* has the excuse that version control is costly or complicated anymore. You don't even need to create an account in Github. You can keep it all in house and the configuration couldn't be easier... ___ 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] Unversioned files.
Adam Jensen decía, en el mensaje "Re: [fossil-users] Unversioned files." del 3/9/2016 09:27:05: > a next step might be to track, > manage, and share items in the file-system that are not actually stored > in the repository database file; an example might be media files or HDF5 > dataset files. -1 > And not to be too overwhelmingly far out, but at this point one might > begin to imagine that the sync function could be extended with > torrent-like capabilities. (Too much?) -inf ___ 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 quote
Konstantin Khomoutov decía, en el mensaje "Re: [fossil-users] git quote" del 8/6/2016 13:01:48: > Some people appear to feel the necessity to fetishize their hatred for > certain things, no matter how bizzare it is. On the other hand, as there are many people eager to propose ways in which Fossil can be more and more similar to Git, even asking it to contravene the ideas leading to its creation, I guess there is enough balance. ___ 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] Quotes
> Not sure it's fair to include my quote when I've never once actually used > git, but I appreciate your vote. You don't need to drill your own head to know that the practice is deadly :) ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Quotes (was: git rebase, and what it looks like in Fossil)
El 18/05/2016 a las 10:56, Andy Goth escribió: > [...] the git model may have compromised its users' thought processes to > the point where they don't realize they're missing anything, basically a > combination of Sapir-Whorf and Stockholm Syndrome. I vote this to be added to the list of quotes about Git :) ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Rewrite of fossil-v-git.wiki. Was: Fossil mentioned on HN
Scott Robison decía, en el mensaje "Re: [fossil-users] Rewrite of fossil-v-git.wiki. Was: Fossil mentioned on HN" del 17/12/2015 21:12:09: > Microsoft software has been exporting and importing CSV files for multiple > decades. The CSV "standard" is just over one decade old. There are plenty of > reasons to object to Microsoft, but this doesn't seem like one of them, > really. Please, read 1.1 at http://www.pg-versus-ms.com/ in full if you haven't done so. I think the argument they make there is compelling. Microsoft has also been creating operating systems for many years now. That doesn't seem to make them particularly good at it, though. But if you think that might makes right and that a de facto standard trumps a better designed one, by all means, say so explicitly so I can adjust my e-mail filters accordingly. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Rewrite of fossil-v-git.wiki. Was: Fossil mentioned on HN
El 17/12/2015 a las 17:28, Ross Berteig escribió: > On 12/16/2015 6:42 PM, Ron W wrote: >> Would be nice if there was a "fossil ticket export" command that would >> produce a "proper" CSV file. While "proper" is still something of a >> debate, most spread sheet apps (Excel, LibreCalc, GnomeCalc, etc) seem to >> adequately digest CSV files where fields that contain comas or newlines >> are enclosed in double quotes, with any contained double quote escaped (I >> think by doubling - ie. like "has ""quote"" inside"). > > A problem with CSV is that there really isn't a clear definition of it at > its edge cases other than testing what Excel will import correctly. Which is a sorry state of things, in itself. Reading an article about support of CSV files in PostgreSQL (at http://www.pg-versus-ms.com/), I learned that there is somewhat of a standard of CSV defined as a RFC at http://tools.ietf.org/html/rfc4180; I also learned that no Microsoft product (including MSSQL Server, Excel and Access) can import the standards-compliant file linked in the article. So apparently your use of JSON was the safest course of action. ___ 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] Linux compilation problem (Ubuntu v14) and is rebuild needed?
Martin Gagnon decía, en el mensaje Re: [fossil-users] Linux compilation problem (Ubuntu v14) and is rebuild needed? del 23/5/2015 10:53:25: May be I'm a bit too parano, but every time I build from source after an update I do a make clean and a ./configure. $ fossil up $ make clean $ ./configure $ make Paranoid or not, re-running configure solved the issue for me. A mere make clean didn't do the trick. ___ 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] Missing timeline graph above 36 timeline items (?!)
Andy Bradford decía, en el mensaje Re: [fossil-users] Missing timeline graph above 36 timeline items (?!) del 17/3/2015 1:48:13: Disabled NoScript and for more security restarted Firefox with no extensions enabled. Same thing. I wonder if perhaps some cross-site scripting blocking tool is blocking it? The only one was NoScript and it was disabled in safe mode. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Missing timeline graph above 36 timeline items (?!)
After the latest upgrades, I've been unable to see the timeline graphs if I have more than 36 items in the timeline. The space for the graph remains, but nothing is drawn. The weirdest thing is that I have reverted to old versions and I'm still unable to see the full graph! I can see it in the Fossil site which is running the same version, though... This is fossil version 1.32 [127ee1f572] 2015-03-16 14:25:03 UTC Compiled on Mar 16 2015 12:48:12 using mingw32-3.20-gcc-4.7.2 (32-bit) SQLite 3.8.8 2015-02-25 14:25:31 6d132e7a22 Schema version 2015-01-24 zlib 1.2.8, loaded 1.2.8 JSON (API 20120713) MBCS_COMMAND_LINE Running on Windows 7. ___ 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] Missing timeline graph above 36 timeline items (?!)
El 16/03/2015 a las 17:10, Tontyna escibió: The weirdest thing is that I have reverted to old versions and I'm still unable to see the full graph! First idea: cached stylesheet? Cleared the cache to no avail. Although that wouldn't explain why you can see 36 items on the Fossil site but not on localhost. That stumped me too. Can't imagine that the HTML served by fossil.exe is sooo different from the HTML produced on fossil-scm.org -- what's the skin of your repo? I tried all of them -- no skin shows the arrows for a timeline 36 now. JavaScript issue? Disabled NoScript and for more security restarted Firefox with no extensions enabled. Same thing. Only the arrows and boxes of the timeline are missing? The whole graph is absent. The Footer is present? Hum. Not in the timeline, no. When I click other pages it shows, though. When you hover the empty timeline space: does the mouse pointer change? No. Does clicking on two different positions bring you to the Check-in-Differences page? No. ___ 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 repolist argument with winsrv
Petr Ferdus decía, en el mensaje Re: [fossil-users] fossil repolist argument with winsrv del 3/3/2015 17:13:44: Is it correct/intentional? My hopes were that I would have Available Repositories: displayed in any directory/subdirectory I browse into. Could be fossil repositories enumerated in any directory? My question would be: why should it? The winsvr subcommand is just a mechanism to create a service which will invoke fossil server with the passed parameters. The server subcommand only automatically serves those repositories contained in the named repository. Why should fossil winsvr include other repositories when fossil server doesn't? (Also, the list of open repositories is a per-user setting saved in a user directory. The service would not have access to those by default except if the service is started with the normal user login, and that user may not have permissions to start services if the computer is part of a domain with security policies applied.) ___ 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 repolist argument with winsrv
Petr Ferdus decía, en el mensaje Re: [fossil-users] fossil repolist argument with winsrv del 3/3/2015 18:15:56: BTW fossil server could serve *.fossil files from any subdirectory of directory it was invoked with. In order to do what you want, fossil server should iterate all the directories under the one specified to search for *.fossil files. I don't know if that's a generally needed/desired feature, of if Dr. Hipp is willing to entertain the notion. The list of repositories is generated, I understand, when the user requests the / directory of the host where fossil server is running, and not before, so this can take a very long time if it has to recurse a whole file system. I think a better solution is create a structure where all repositories reside in the same directory. The source have no such limitation, after all, and the _FOSSIL_ file contains the path to the repo so there's no need of having them in several places. For what is worth, -1 from me for your suggested feature, in any case. ___ 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 repolist argument with winsrv
Joe Mistachkin decía, en el mensaje Re: [fossil-users] fossil repolist argument with winsrv del 2/3/2015 18:42:42: Petr Ferdus wrote: I just realized that fossil winsrv command does not recognize --repolist argument. Could winsrv honors this argument as well? Fixed on trunk. This passes the --repolist parameter to the fossil server command recorded in the registry, but I get a Not found page when I run the service installed or even when I run fossil server --repolist --port 8080 D:\path\to\repo-directory and I try to access localhost:8080 Can somebody else test in Windows the server command with the --repolist parameter? My configuration: fossil version 1.31 [a0b33ab4d4] 2015-03-02 21:41:52 UTC gcc (GCC) 4.7.2 Windows 7 Ultimate SP1 ___ 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 repolist argument with winsrv
Joe Mistachkin decía, en el mensaje Re: [fossil-users] fossil repolist argument with winsrv del 2/3/2015 19:48:22: Sorry, minor oversight. It was not setting the right flag bit prior to calling into the Win32 HTTP server. Should work on trunk now. Confirmed: it does. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Problem with /dev/random and /dev/null in latest versions?
I've found this problem in my fossil: accessing the Admin page shows the following messages: WARNING: Device /dev/null is not available for reading and writing. WARNING: Device /dev/urandom is not available for reading. This means that the pseudo-random number generator used by SQLite will be poorly seeded. Version data: This is fossil version 1.31 [04e6a82ed7] 2015-02-09 12:18:00 UTC Linux selene 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:12 UTC 2014 i686 athlon i686 GNU/Linux cc (Ubuntu 4.8.2-19ubuntu1) 4.8.2 -- o-= Marcelo =-o ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Error in Windows with Makefile.mingw
After many builds working properly, this happens: C:/Prog/MinGW/bin/mingw32-make -C src/../compat/zlib PREFIX= LOC=-DASMV -DASMINF OBJA=inffas86.o match.o -f win32/Makefile.gcc libz.a C:\Prog\MinGW\bin\mingw32-make: invalid option -- A C:\Prog\MinGW\bin\mingw32-make: invalid option -- M Usage: mingw32-make [options] [target] ... Options: -b, -m Ignored for compatibility. -B, --always-make Unconditionally make all targets. -C DIRECTORY, --directory=DIRECTORY Change to DIRECTORY before doing anything. -d Print lots of debugging information. --debug[=FLAGS] Print various types of debugging information. -e, --environment-overrides Environment variables override makefiles. --eval=STRING Evaluate STRING as a makefile statement. -f FILE, --file=FILE, --makefile=FILE Read FILE as a makefile. -h, --help Print this message and exit. -i, --ignore-errors Ignore errors from recipes. -I DIRECTORY, --include-dir=DIRECTORY Search DIRECTORY for included makefiles. -j [N], --jobs[=N] Allow N jobs at once; infinite jobs with no arg. -k, --keep-goingKeep going when some targets can't be made. -l [N], --load-average[=N], --max-load[=N] Don't start multiple jobs unless load is below N. -L, --check-symlink-times Use the latest mtime between symlinks and target. -n, --just-print, --dry-run, --recon Don't actually run any recipe; just print them. -o FILE, --old-file=FILE, --assume-old=FILE Consider FILE to be very old and don't remake it. -p, --print-data-base Print make's internal database. -q, --question Run no recipe; exit status says if up to date. -r, --no-builtin-rules Disable the built-in implicit rules. -R, --no-builtin-variables Disable the built-in variable settings. -s, --silent, --quiet Don't echo recipes. -S, --no-keep-going, --stop Turns off -k. -t, --touch Touch targets instead of remaking them. --trace Print tracing information. -v, --version Print the version number of make and exit. -w, --print-directory Print the current directory. --no-print-directoryTurn off -w, even if it was turned on implicitly. -W FILE, --what-if=FILE, --new-file=FILE, --assume-new=FILE Consider FILE to be infinitely new. --warn-undefined-variables Warn when an undefined variable is referenced. This program built for i686-pc-mingw32 Report bugs to bug-m...@gnu.org win\Makefile.mingw:818: recipe for target 'zlib' failed mingw32-make: *** [zlib] Error 2 I'm thinking maybe checkins 270897a301 and/or 3616b7489b may be related? I think the variables passed to Make are not being read properly. checkout: 156ef9ec06a069f3791c4fba8e3972a1099bad7b 2014-11-26 14:53:41 UTC Windows 7 Ultimate build 7601 SP1 GNU Make 3.82.90 Built for i686-pc-mingw32 Makefile ran from CMD. ___ 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] Pessimism about CommonMark in fossil
Stephan Beal decía, en el mensaje Re: [fossil-users] Pessimism about CommonMark in fossil del domingo, 28 de septiembre de 2014 13:45:58: On Sun, Sep 28, 2014 at 6:39 PM, Natacha Porté nata...@instinctive.eu mailto:nata...@instinctive.eu wrote: But this is still about disambiguating Markdown, without looking at any other wiki or markup format. If it is incompatible with _any_ existing Markdown dialects, then it is effectively a competing format. If there are over 2 dozen slightly different implementations, what are the real chances of getting those two dozen projects to consolidate on one standard? And then what are the chances that all of them will change their parsers to all work identically (which seems like quite a waste of effort, to have 20+ implementations which all work identically). i still predict utter failure ;). My 0.02 Credits: didn't the name CommonMark (and not *Markdown) had to be created because the creator of Markdown himself disowned the effort and DEMANDED that the name Markdown wasn't used? More reason to agree with Stephan's prediction. ___ 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] break in fossil sync, between versions [9b30c01e8b] and [f62bedf1ef]
Confirmed. This should now be fixed on trunk: https://www.fossil-scm.org/index.html/info/1f8a4ecdb7 Thanks for the report. I'm getting the following error compiling this in MinGW: wbld/translate.exe src/add.c wbld/add_.c 0 [main] us 0 init_cheap: VirtualAlloc pointer is null, Win32 error 487 AllocationBase 0x0, BaseAddress 0x60E9, RegionSize 0x1A, State 0x1 C:\Prog\MinGW\msys\1.0\bin\sh.exe: *** Couldn't reserve space for cygwin's heap, Win32 error 0 make: *** [wbld/add_.c] Error 1 Running Windows 7 SP1 ___ 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] Problem with compilation under MINGW
Joe Mistachkin escribió: A clean build from Fossil trunk compiles fine here. Can you please run make clean and try again? That did the trick. I'll make sure to include this in my troubleshooting before reporting a problem again -- sorry for the noise. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Problem with compilation under MINGW
After checkin [bd1151126a], compilation under MINGW produces the following error: wbld/sqlite3.o:sqlite3.c:(.text+0xe244): undefined reference to `_fossil_localtime' Previous checkins from trunk work properly. -- o-= Marcelo =-o ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Problems with Fossil 1.26 for Windows
Trying to run the Windows version in Windows XP SP3 gives the error Not a valid Win32 application. -- o-= Marcelo =-o ___ 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] Noted a chiselapp status update - positive news
Andreas Kupries decía, en el mensaje [fossil-users] Noted a chiselapp status update - positive news del Martes, 23 de Abril de 2013 13:17:18: Update: Chiselapp found a new home. Starting May 1ish Chiselapp will be transfered to it's new owner (a member of the Tcl community). Andreas, I'm assuming you're the member of the Tcl community mentioned in the update? If so, many thanks for making the effort to keep this useful resource for the community of Fossil users. -- o-= Marcelo =-o ___ 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] Why do we need a fossil hosting service?
Matt Welland decía, en el mensaje Re: [fossil-users] Why do we need a fossil hosting service? del Viernes, 29 de Marzo de 2013 14:38:25: Ability for loosely coupled collaboration (i.e. fork). Not exactly what Fossil was designed for, I believe... Community and the momentum that can come with it. And as far as Hg/Git lovers keep telling everybody how awful Fossil is because is different from their pet tools, it will never happen... ... which I don't think is entirely unintended. Project life beyond the initial developer. Consequence of the one before. -- o-= Marcelo =-o ___ 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 vs. Git/Mercurial/etc.?
Michael Richter decía, en el mensaje Re: [fossil-users] Fossil vs. Git/Mercurial/etc.? del Domingo, 30 de Diciembre de 2012 02:11:46: There's use cases for every bizarre feature in every bizarre SCM (distributed or otherwise) out there. Let's not turn Fossil into the C++ of DSCMs, shall we? If you *really, positively, /absolutely/* must have rebase, Git is that-a-way. Insisting that Fossil should turn into Git is not a viable argument. *standing ovation* -- o-= Marcelo =-o ___ 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] why does `fossil rm' not do the real thing?
Chad Perrin decía, en el mensaje Re: [fossil-users] why does `fossil rm' not do the real thing? del Miércoles, 12 de Diciembre de 2012 18:22:53: I rather suspect that, if Fossil continues to grow in usage over time, and if it fails to implement sane defaults and options like what you just described as a general policy, there will probably be either a fork or a wrapper that arrives to solve the problem. If that happens, please make sure to include git in the new name. That's what all the naysayers are trying to convert Fossil into, anyway. -- o-= Marcelo =-o ___ 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 version 1.25 scheduled.
fossil-m...@h-rd.org decía, en el mensaje Re: [fossil-users] Fossil version 1.25 scheduled. del Martes, 04 de Diciembre de 2012 07:26:32: Why not fossil allow only to serve files from a specific and specified directory (in settings). I think thats better than filtering on mime types etc. An advantage is that it allows you to serve whatever file you want, maybe including fossil repos or whatever custom files you have. +1 ___ 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 version 1.25 scheduled.
Dmitry Chestnykh decía, en el mensaje Re: [fossil-users] Fossil version 1.25 scheduled. del Sábado, 01 de Diciembre de 2012 09:44:27: On a related note, I think you should consider making the previous behaviour (not serving static files) the default one, and serve static files only when --static-files or similar flag is supplied. I'm worried that this change may be surprising to some people who currently may store sensitive information along with their repositories. When they upgrade to the new version, suddenly their files become exposed to the world. Or when a hosting site updates Fossil (Chisel comes to mind). Proposal seconded. -- o-= Marcelo =-o ___ 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] [1.24/Win] Adding files through *.html?
Gilles decía, en el mensaje Re: [fossil-users] [1.24/Win] Adding files through *.html? del Jueves, 29 de Noviembre de 2012 14:08:32: On Thu, 29 Nov 2012 17:43:34 +0100, Peter Spjuth peter.spj...@gmail.com wrote: You can also do: for %x in (*.html) do fossil add %x Thanks for the tip, but it's much more involved than simply fossil add *.html. Peter's solution is much more involved but compiling your own fossil executable is acceptable?! Weird :) -- o-= Marcelo =-o ___ 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] status of TODO list (was Re: comparison with Git)
Richard Hipp escribió: On Sat, Oct 13, 2012 at 4:06 AM, Gour g...@atmarama.net mailto:g...@atmarama.net wrote: Now, I'm curious about some of the items from the TODO list (http://www.fossil-scm.org/index.html/wiki?name=To+Do+List) and their status: * Uncommit All what I need is simple mechanism to quickly 'fix' some wrong commits without tinkering deep into the commit history. ... The idea is when one creates short-lived feature branch, experiment with it a bit, and when it's ready simply commits to the 'main' branch not wanting to keep it any longer. Deleting content from a repository is scary. A bug in the delete logic could easily cause loss of information. I'm mostly an outsider (and very, very happy user of Fossil in its current state), so take my coment with a pinch of salt, but: Doesn't strike you as odd this sudden influx of requests of make Fossil more like Git!? It's almost as if disgruntled users of Git want to have a Git-like program, even importing their defects (or, let's be generous, differences in design philosophy), but with a more friendly interface. No matter if this bothers or causes some worry or complication to current Fossil users or even to its implementors: we want our Git-lite program so we can have all the things we like and not have the Git manual tattooed to our inner eyelids! That's the generous hypothesis. The paranoid one is that Git promoters really want to nullify all differences between Git and Fossil and then say: See? Fossil does the same that Git does! And we have Github! And the community! And etcetera!. I like Richard's attitude of Fossil is there to scratch my own itches and it's doing fine like it is now. I wouldn't like to have its CLI turned into a unmanageable monstrosity (at the very least) or to compromise the integrity of the Fossil file format because of people in love Fossil's simplicity but who don't want to get rid of their old Git thinking habits. -- o-= Marcelo =-o ___ 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] The future of markdown-in-fossil
Michal Suchanek escribió: Note there are JavaScript hacks for interpreting random wiki syntax so you can have markdown interpreted without any direct support in fossil. Note there are good wiki engines out there, so no need for one in Fossil too. But once we set the scope to include something, please don't keep it half-hearted... And it has been said that markdown is out of the scope of Fossil. I am not to decide that but I have to agree. Once you let in markdown people used to some other wiki syntax would argue they have needlessly hard time and there would be no end to the stream of requests to include yet another. Wholeheartedly agreed. Let's stop with the wiki markup discussions and keep the list DSCM related... PLEASE. -- o-= Marcelo =-o ___ 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] The future of markdown-in-fossil
Remigiusz Modrzejewski decía, en el mensaje Re: [fossil-users] The future of markdown-in-fossil del Viernes, 03 de Agosto de 2012 07:26:27: I've read the we'll have requests for all the markups in the world argument many times. I can't remember anyone actually coming and asking for *anything* else than markdown. I was going to wait until the whole Markup brouhaha was ended, but I for one would like support for reStructuredText :) -- o-= Marcelo =-o ___ 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] Problem with fossil winsrv (alternative name problem solved; minor issue not working?; typo in error messages)
Richard Hipp decía, en el mensaje Re: [fossil-users] Problem with fossil winsrv (cont'd) del Jueves, 07 de Junio de 2012 07:39:35: You can download a complete development environment from http://www.mingw.org/ - I did this just the other day on the Windows 8 RC and it works great. Thank you, Richard. I followed your suggestion and I tested the winsrv branch. The changes seem to be working, the name specified in the command line is honored and properly used on creation. One thing I noticed is that on removal (fossil winsrv delete), when I used the current official version, removal of the default Fossil-DSCM service ocurred immediately (the service disappeared from the Services console when I refreshed the window), while the current just sets the service as Disabled until the next reboot; then is really removed. I don't see anything in the code which causes that, however, so I'm willing to chalk it out to the way I compiled my test version. I also noticed that all the error messages about arguments were consistenly misspelled (from before this change, may I add) as to much arguments for XXX method. I'm inclined to say that it should be too much, but I'm not an English native speaker and maybe the correct form is too many? Anyway, I'm happy to report that the main problem is solved. And that I'm now able to test cutting-edge versions of fossil if I'm so inclined! Wow! :) Thank you for all your help. -- o-= Marcelo =-o ___ 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] Problem with fossil winsrv (cont'd)
Thomas Schnurrenberger decía, en el mensaje Re: [fossil-users] Problem with fossil winsrv (cont'd) del Miércoles, 06 de Junio de 2012 17:35:59: On 06.06.2012 20:59, Marcelo wrote: What do you think of my proposed change? I have committed a fix to the Fossil repository. It can be found in the branch winsrv. Please try it out. No development enviroment here, but I'll see what I can do. -- o-= Marcelo =-o ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Problem with fossil winsrv
When creating a new Fossil service, the command fossil winsrv create Tickets ... doesn't create a service called Tickets, but a service called Fossil-DSCM. There's no way to change the low-level service name. This is not the documented behaviour, when the service name is supposed to be the one specified in the command line. Tested in Win2000 and WinXP. -- o-= Marcelo =-o ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users