Re: [fossil-users] fossil - JIRA hooks
On Thu, Sep 11, 2014 at 10:02 PM, Ron W ronw.m...@gmail.com wrote:
No different than my TH1 code being my responsibility to make sure it
handles my custom fields correctly.
handles is the operative word. TH1 can _handle_ things, and JSON, by
itself, cannot.
The only expectations of the JSON API would be to limit the length of
strings delivered to the rest of Fossil and map queries/updates
appropriately (see below).
Any such limits cannot be imposed until the JSON is parsed in its entirety,
though. The JSON DOM (so to say) gets parsed at a lower level, and then
the Fossil side of that has to understand what those limits are and where
to apply them. e.g. it must not apply them in the Wiki APIs, where pages
can be arbitrarily long.
What, like this?
[odroid@host:~/fossil/cwal]$ f json query -sql 'select count(*) from
user'
{
Is this possible through the web interface? If so, can it be disabled?
It's enabled for admin/setup users only (which also means any CLI use,
since Fossil treats CLI users as a superuser), and there is no mechanism
for disabling individual calls.
It just means that any app (or other library) using libfossil to access
tickets will have to be held responsible for using the custom fields
correctly. libfossil would only provide the means to access the tickets and
their fields. No validation beyond limiting string lengths. Nor any mapping
of queries or updates.
Why are string length limits so important here - i don't get that part.
What if someone wants to add a rough draft of your most recent novel
field?
(From above) By appropriate mapping, I suggest something like:
Query JSON message: Payload is 2 lists: One of name/value pairs
designating the fields to search and describing the values to match. The
other a list of fields to return in the results.
Update/Add JSON message: Payload is a list of name value pairs designating
the fields and their values.
The response could be either just a string containing the raw response,
or a list of name/value pairs.
i'll need to see an example before that's clear to me, i think. Can you
compose some pseudo-json for such a request/response exchange?
--
- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
Freedom is sloppy. But since tyranny's the only guaranteed byproduct of
those who insist on a perfect world, freedom will have to do. -- Bigby Wolf
___
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] Manually deleting users
On Thu, Sep 11, 2014 at 11:05 PM, Philip Bennefall phi...@blastbay.com wrote: Ah, sweet. To be safe I am going to enable foreign key constraints before I do it, as well. If I do mess something up in the process, e.g. there is in fact some reference to that user somewhere even though I doubt it, how likely is Fossil to detect this and complain? To elaborate just a bit: users are a bit special in fossil in that they're only ever referenced by their string name, and if that name doesn't exist in the user table then (aside from _possibly_ some minor cosmetic bugs) no big deal. AFAIR Fossil never complains about missing users, but it can hypothetically do things like create a link to a name which no longer exists in the user table. Since your user never actually created any changes, that won't be a (hypothetical) problem for you. -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do. -- Bigby Wolf ___ 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] Getting configure to find openssl on FreeBSD
Bizarrely, I went back to this today and fossil compiled first time without me needing to specify any --with-openssl options. I've no idea why! On 2014-09-11T17:33:33 -0400 Eric Rubin-Smith eas@gmail.com wrote: A stripped shared library would not be worth much, since the whole point of a shared library is to provide symbols. Did you pass '-D'? Nope, didn't know -D existed. $ file /usr/lib/libssl.so.6 /usr/lib/libssl.so.6: ELF 64-bit LSB shared object, x86-64, version 1 (FreeBSD), dynamically linked, stripped $ nm /usr/lib/libssl.so.6 nm: /usr/lib/libssl.so.6: no symbols $ nm -D /usr/lib/libssl.so.6 | grep SSL_new 00034810 T SSL_new All binaries in the FreeBSD base are stripped (not sure I really see the utility of it, but...) On 2014-09-12T12:15:18 +1000 Steve Bennett ste...@workware.net.au wrote: ./configure --debug ... And then look at config.log Thanks, useful for future reference. M ___ 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] Getting configure to find openssl on FreeBSD
Hello, more likely than not this is not related, but perhaps it gives a hint in the right direction anyway: on NetBSD there is also an openssl in the base-system, and one in pkgsrc (NetBSD's equivalent of ports). In my case, fossil's ./configure could find openssl, but the resulting binary could not find the .so. This turned out to be a flaw/mismatch in pkg-config when queried for compiler-/linker-flags. This was posted here: https://mail-index.netbsd.org/pkgsrc-users/2014/05/31/msg019783.html The local hack here was to alter the libssl.pc pkg-config config file, but it was fixed here: http://gnats.netbsd.org/cgi-bin/query-pr-single.pl?number=48871 h2h, Michai On 11 September 2014 21:06, org.fossil-scm.fossil-us...@io7m.com wrote: 'Lo. The fossil build scripts seem to be unable to find openssl on FreeBSD 9.2. It has a choice of the version included with the base system (in /usr) or the version available from FreeBSD ports (/usr/local), but it can't seem to find either of them. Is there any way to get it to give more information about why it's failing to find them? $ ./configure --with-openssl=auto Host System...x86_64-unknown-freebsd9.2 Build System...x86_64-unknown-freebsd9.2 C compiler... cc -g -O2 C++ compiler... c++ -g -O2 Build C compiler...cc Checking for stdlib.h...ok Checking for uint32_t...ok Checking for uint16_t...ok Checking for int16_t...ok Checking for uint8_t...ok Checking for pread...ok Checking for tclsh...no Checking for system ssl...no Checking for ssl in /usr/sfw...no Checking for ssl in /usr/local/ssl...no Checking for ssl in /usr/lib/ssl...no Checking for ssl in /usr/ssl...no Checking for ssl in /usr/pkg...no Checking for ssl in /usr/local...no Checking for ssl in /usr...no Error: OpenSSL not found. Consider --with-openssl=none to disable HTTPS support Try: 'configure --help' for options $ ./configure --with-openssl=/usr ... Checking for ssl in /usr...no Error: OpenSSL not found. Consider --with-openssl=none to disable HTTPS support Try: 'configure --help' for options $ ./configure --with-openssl=/usr/lib ... Checking for ssl in /usr/lib...no Error: OpenSSL not found. Consider --with-openssl=none to disable HTTPS support Try: 'configure --help' for options $ ./configure --with-openssl=/usr/local ... Checking for ssl in /usr/local...no Error: OpenSSL not found. Consider --with-openssl=none to disable HTTPS support Try: 'configure --help' for options $ ./configure --with-openssl=/usr/local/lib ... Checking for ssl in /usr/local/lib...no Error: OpenSSL not found. Consider --with-openssl=none to disable HTTPS support Try: 'configure --help' for options $ ls /usr/local/lib/libssl.so* /usr/local/lib/libssl.so /usr/local/lib/libssl.so.8 $ ls /usr/lib/libssl.so* /usr/lib/libssl.so /usr/lib/libssl.so.6 ... and so on. M ___ 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] Files marked as missing after addremove
Hi all, I am running a build of Fossil that is newer than the last public release, though I cannot remember exactly what check-in it is. I am having a bit of trouble with addremove. I remove the files in question from the repository and then I run addremove, and get the expected output which says deleted something.xyz. Then I run fossil commit, but it fails with a complaint about missing files. If I then say revert, and then use fossil rm to get rid of the files manually, status reports the files as deleted rather than missing. I don't recall having any issues with this in prior versions of Fossil. Am I doing something wrong in my workflow or is this potentially a bug? Kind regards, Philip Bennefall ___ 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] Files marked as missing after addremove
I haven't had time to dig in, but that sounds like the ticket I opened this week. If it sounds like that to you too, kindly add any more relevant info you have: http://fossil-scm.org/index.html/tktview?name=94a1f83f9f On Sep 12, 2014 9:12 PM, Philip Bennefall phi...@blastbay.com wrote: Hi all, I am running a build of Fossil that is newer than the last public release, though I cannot remember exactly what check-in it is. I am having a bit of trouble with addremove. I remove the files in question from the repository and then I run addremove, and get the expected output which says deleted something.xyz. Then I run fossil commit, but it fails with a complaint about missing files. If I then say revert, and then use fossil rm to get rid of the files manually, status reports the files as deleted rather than missing. I don't recall having any issues with this in prior versions of Fossil. Am I doing something wrong in my workflow or is this potentially a bug? Kind regards, Philip Bennefall ___ 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] Files marked as missing after addremove
It sounds similar indeed. One thing that is perhaps worth mentioning is that rm works just fine if you do it before you delete the actual file. Another thing is that addremove did report that the file was deleted, but then it was still reported missing by status and commit. I'll update the ticket with that information in the morning. Kind regards, Philip Bennefall On 9/13/2014 6:17 AM, B Harder wrote: I haven't had time to dig in, but that sounds like the ticket I opened this week. If it sounds like that to you too, kindly add any more relevant info you have: http://fossil-scm.org/index.html/tktview?name=94a1f83f9f On Sep 12, 2014 9:12 PM, Philip Bennefall phi...@blastbay.com mailto:phi...@blastbay.com wrote: Hi all, I am running a build of Fossil that is newer than the last public release, though I cannot remember exactly what check-in it is. I am having a bit of trouble with addremove. I remove the files in question from the repository and then I run addremove, and get the expected output which says deleted something.xyz. Then I run fossil commit, but it fails with a complaint about missing files. If I then say revert, and then use fossil rm to get rid of the files manually, status reports the files as deleted rather than missing. I don't recall having any issues with this in prior versions of Fossil. Am I doing something wrong in my workflow or is this potentially a bug? Kind regards, Philip Bennefall ___ fossil-users mailing list fossil-users@lists.fossil-scm.org mailto: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
