Re: [fossil-users] cannot connect to host

2015-08-31 Thread Doug Currie
Is anyone else having trouble syncing with Chiselapp lately? None of
my Chiselapp local repos can sync, whereas my non-Chiselapp (lua.sqlite.org)
repo is syncing fine. [Note that I did `fossil configuration push all` on
only one of my local repos, so this isn't the cause of my problem, as I
speculated below.]

e


On Fri, Aug 28, 2015 at 11:29 PM, Doug Currie <doug.cur...@gmail.com> wrote:

> This "cannot connect to host" question has come up before, but earlier
> threads on this subject seem to lead to server credentials/certificate
> re-configuration or mis-configuration, and in this case I'm using
> chiselapp...
>
> Sync to chiselapp was working for me three days ago. The last sync that
> worked was a configuration push to update the wiki:
>
> e$ fossil configuration push all
> Round-trips: 1   Artifacts sent: 0  received: 0
> Push done, sent: 874  received: 260  ip: 216.250.117.7
>
> (Maybe I broke something by pushing 'all' from local to chiselapp?)
>
> Today I get:
>
> e$ fossil sync
> Sync with https://e...@chiselapp.com/user/e/repository/myrepo
> SSL: cannot connect to host chiselapp.com:443 ()
> Sync done, sent: 0  received: 0  ip:
>
> I can log onto chiselapp on https://chiselapp.com and access the repo, so
> the route is fine.
>
> I updated and rebuilt fossil and tried again to no avail.
>
> e$ fossil version
> This is fossil version 1.33 [d43847c968] 2015-08-27 14:24:09 UTC
>
> This is on Mac OS X 10.10.5
>
> Any ideas?
>
> Thanks.
>
> e
>
___
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] cannot connect to host

2015-08-31 Thread Doug Currie
Thanks, Goyo. My problem seems to be SSL

>> SSL: cannot connect to host chiselapp.com:443 ()

e

On Mon, Aug 31, 2015 at 12:17 PM, Goyo <goyod...@gmail.com> wrote:

> I can sync with chiselapp using http. My fossil is built without ssl
> so I can't try https.
>
> 2015-08-31 18:08 GMT+02:00 Doug Currie <doug.cur...@gmail.com>:
> > Is anyone else having trouble syncing with Chiselapp lately? None of my
> > Chiselapp local repos can sync, whereas my non-Chiselapp (lua.sqlite.org
> )
> > repo is syncing fine. [Note that I did `fossil configuration push all` on
> > only one of my local repos, so this isn't the cause of my problem, as I
> > speculated below.]
> >
> > e
> >
> >
> > On Fri, Aug 28, 2015 at 11:29 PM, Doug Currie <doug.cur...@gmail.com>
> wrote:
> >>
> >> This "cannot connect to host" question has come up before, but earlier
> >> threads on this subject seem to lead to server credentials/certificate
> >> re-configuration or mis-configuration, and in this case I'm using
> >> chiselapp...
> >>
> >> Sync to chiselapp was working for me three days ago. The last sync that
> >> worked was a configuration push to update the wiki:
> >>
> >> e$ fossil configuration push all
> >> Round-trips: 1   Artifacts sent: 0  received: 0
> >> Push done, sent: 874  received: 260  ip: 216.250.117.7
> >>
> >> (Maybe I broke something by pushing 'all' from local to chiselapp?)
> >>
> >> Today I get:
> >>
> >> e$ fossil sync
> >> Sync with https://e...@chiselapp.com/user/e/repository/myrepo
> >> SSL: cannot connect to host chiselapp.com:443 ()
> >> Sync done, sent: 0  received: 0  ip:
> >>
> >> I can log onto chiselapp on https://chiselapp.com and access the repo,
> so
> >> the route is fine.
> >>
> >> I updated and rebuilt fossil and tried again to no avail.
> >>
> >> e$ fossil version
> >> This is fossil version 1.33 [d43847c968] 2015-08-27 14:24:09 UTC
> >>
> >> This is on Mac OS X 10.10.5
> >>
> >> Any ideas?
> >>
> >> Thanks.
> >>
> >> e
> >
> >
> >
> > ___
> > 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] cannot connect to host

2015-08-31 Thread Doug Currie
On Mon, Aug 31, 2015 at 12:58 PM, jungle Boogie 
wrote:

> I can clone, over TLS, one of the many public repos, but I don't have
> access to any of them to sync.
>
>
So, I just tried cloning using https to no avail:

test e$ fossil clone https://chiselapp.com/user/e/repository/ldecNumber
ldecNumber.fossil
SSL: cannot connect to host chiselapp.com:443 ()
Clone done, sent: 0  received: 0  ip:
server returned an error - clone aborted

but it works with http:

test e$ fossil clone http://chiselapp.com/user/e/repository/ldecNumber
ldecNumber.fossil
Round-trips: 2   Artifacts sent: 0  received: 339
Clone done, sent: 523  received: 1281643  ip: 216.250.117.7

 e
___
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] cannot connect to host

2015-08-31 Thread Doug Currie
On Mon, Aug 31, 2015 at 2:21 PM, jungle Boogie <jungleboog...@gmail.com>
wrote:

> On 31 August 2015 at 10:51, Doug Currie <doug.cur...@gmail.com> wrote:
> > test e$ fossil clone https://chiselapp.com/user/e/repository/ldecNumber
> > ldecNumber.fossil
> > SSL: cannot connect to host chiselapp.com:443 ()
> > Clone done, sent: 0  received: 0  ip:
> > server returned an error - clone aborted
>
>
> % fossil clone https://chiselapp.com/user/e/repository/ldecNumber
> ldecNumber.fossil
> Round-trips: 2   Artifacts sent: 0  received: 0
> Error: not authorized to clone
> Round-trips: 2   Artifacts sent: 0  received: 0
> Clone done, sent: 533  received: 708  ip: 216.250.117.7
> server returned an error - clone aborted
>
>
> Give a repo we can clone and I'll test it.
>
>

Thanks; I just turned on clone permission for "nobody" in that repo.

e




> --
> ---
> inum: 883510009027723
> sip: jungleboo...@sip2sip.info
> xmpp: jungle-boo...@jit.si
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
___
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] cannot connect to host

2015-08-31 Thread Doug Currie
On Mon, Aug 31, 2015 at 3:32 PM, jungle Boogie 
wrote:

> % fossil version -v
> This is fossil version 1.33 [7febc31883] 2015-08-29 15:24:16 UTC
> Compiled on Aug 29 2015 16:15:07 using gcc-4.2.1 Compatible FreeBSD
> Clang 3.4.1 (tags/RELEASE_34/dot1-final 208032) (64-bit)
> SQLite 3.8.11.1 2015-07-29 20:00:57 cf538e2783
> Schema version 2015-01-24
> zlib 1.2.8, loaded 1.2.8
> SSL (LibreSSL 2.2.2)
> TH1_DOCS
> TCL (Tcl 8.6.4, loaded TH_OK: 8.6.4)
> JSON (API 20120713)
> UNICODE_COMMAND_LINE
> DYNAMIC_BUILD
>
>
> Seems to work fine for me!


Well, I guess that's good, thank you for trying it...

but I'm still stuck:

test e$ fossil clone https://chiselapp.com/user/e/repository/ldecNumber
ldecNumber.fossil
SSL: cannot connect to host chiselapp.com:443 ()
Clone done, sent: 0  received: 0  ip:
server returned an error - clone aborted

test e$ fossil version -v
This is fossil version 1.33 [7febc31883] 2015-08-29 15:24:16 UTC
Compiled on Aug 31 2015 15:55:30 using gcc-4.2.1 Compatible Apple LLVM
6.1.0 (clang-602.0.53) (64-bit)
SQLite 3.8.11.1 2015-07-29 20:00:57 cf538e2783
Schema version 2015-01-24
zlib 1.2.5, loaded 1.2.5
SSL (OpenSSL 0.9.8zg 14 July 2015)
UNICODE_COMMAND_LINE
DYNAMIC_BUILD


e
___
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] cannot connect to host

2015-08-31 Thread Doug Currie
On Mon, Aug 31, 2015 at 5:07 PM, Warren Young  wrote:

> My guess: The SSL implementation running on ChiselApp has been tightened
> down, to make it refuse old broken SSL features that used to work in the
> past, as a result of all the security problems found in OpenSSL over the
> past year or so:
> 
>

That's probably it...

test e$ fossil_libressl clone
https://chiselapp.com/user/e/repository/ldecNumber ldecNumber.fossil
Round-trips: 2   Artifacts sent: 0  received: 339
Clone done, sent: 523  received: 1281643  ip: 216.250.117.7
Rebuilding repository meta-data...
  100.0% complete...
Extra delta compression...
Vacuuming the database...
project-id: 2f6fa92a60ff07446846433609b70d028bf121e7
server-id:  d5a48b19b1fc82e70df48bf3044c354b915f1f23
admin-user: e (password is "77d3fb")

test e$ fossil_libressl version -v
This is fossil version 1.33 [7febc31883] 2015-08-29 15:24:16 UTC
Compiled on Aug 31 2015 17:18:38 using gcc-4.2.1 Compatible Apple LLVM
6.1.0 (clang-602.0.53) (64-bit)
SQLite 3.8.11.1 2015-07-29 20:00:57 cf538e2783
Schema version 2015-01-24
zlib 1.2.5, loaded 1.2.5
SSL (LibreSSL 2.2.2)
UNICODE_COMMAND_LINE
DYNAMIC_BUILD

I'm up and running again. Thank you Warren and jungle Boogie.

Since OpenSSL 0.9.8 is the default on OS X 10.10, this issue will surely
affect others.

e
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


[fossil-users] cannot connect to host

2015-08-28 Thread Doug Currie
This cannot connect to host question has come up before, but earlier
threads on this subject seem to lead to server credentials/certificate
re-configuration or mis-configuration, and in this case I'm using
chiselapp...

Sync to chiselapp was working for me three days ago. The last sync that
worked was a configuration push to update the wiki:

e$ fossil configuration push all
Round-trips: 1   Artifacts sent: 0  received: 0
Push done, sent: 874  received: 260  ip: 216.250.117.7

(Maybe I broke something by pushing 'all' from local to chiselapp?)

Today I get:

e$ fossil sync
Sync with https://e...@chiselapp.com/user/e/repository/myrepo
SSL: cannot connect to host chiselapp.com:443 ()
Sync done, sent: 0  received: 0  ip:

I can log onto chiselapp on https://chiselapp.com and access the repo, so
the route is fine.

I updated and rebuilt fossil and tried again to no avail.

e$ fossil version
This is fossil version 1.33 [d43847c968] 2015-08-27 14:24:09 UTC

This is on Mac OS X 10.10.5

Any ideas?

Thanks.

e
___
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] Examples of public Fossil repositories

2015-01-02 Thread Doug Currie
Hi Richard,

There is http://lua.sqlite.org/ -- it is somewhat dormant, but is the
primary face of LuaSQLite3 and referenced from LuaRocks.

e


On Fri, Jan 2, 2015 at 9:34 AM, Richard Hipp d...@sqlite.org wrote:

 I'm trying to compile a list of interesting public Fossil repositories.
 My list currently includes:

 http://www.fossli-scm.org/fossil/
 http://www.sqlite.org/src/
 http://www.eagle.to/cgi-bin/eagle/timeline
 http://core.tcl.tk/tcl/timeline
 http://www.androwish.org/
 http://netbsd.sonnenberger.org/

 And, of course, all of the repos on http://chiselapp.com/

 Are there any others that I should add to the list?

 --
 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 mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


Re: [fossil-users] libfossil www interface: looking for ideas

2014-02-20 Thread Doug Currie
On Thu, Feb 20, 2014 at 6:37 PM, Nico Williams n...@cryptonector.comwrote:

 On Mon, Feb 17, 2014 at 4:26 PM, Stephan Beal sgb...@googlemail.com
 wrote:
  Can you recommend one in C? i'm self-imposed bound to C here. i might
 be
  convinced to write it in C++.

 If you look aroung in http://github.com/stedolan you'll find a minimal
 http server, with much of the code you need for building something
 like this.


Or Mongoose: https://code.google.com/p/mongoose/

e
___
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] chosen project name might interfere with tar/zip download

2013-10-08 Thread Doug Currie

On Oct 8, 2013, at 8:31 AM, j. van den hoff veedeeh...@googlemail.com wrote:

 coming back to this problem of problematic character such as `/' causing 
 tar/zip download to fail since the
 URL generated by fossil is invalid: would it not be sensible to simply use as 
 name the sha1 hash itself plus the suitable extension,

My repos integrate with packaging/build systems (some not under my control) 
that would break if the archive name was changed by fossil. Accessing URLs like

  http://lua.sqlite.org/index.cgi/zip/lsqlite3_fsl09b.zip?uuid=fsl_9b

shouldn't add a SHA to the archive name.

e

___
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] Chiselapp.com shutting down

2013-03-29 Thread Doug Currie
Thank you, James, for Chiselapp. I'm sorry to see it go.

On Mar 29, 2013, at 7:55 AM, Richard Hipp d...@sqlite.org wrote:

   (5)  Require unpaid accounts to be open-source?

One of the most important things that drew me to Chiselapp, and to using Fossil 
for personal projects, was free private accounts. It is important to have a low 
barrier to entry. I imagine there would need to be bandwidth and storage 
limitations for free accounts, but these limits should be set up so a new user 
would be assured that the limits would not be exceeded accidentally. They could 
be big enough to make this obvious, or actual usage could be reported 
prominently to the repo owner.

   (4)  Require advertising (example http://system.data.sqlite.org/) for 
 unpaid accounts?

I find the word advertising to be confusing here in the context of  the 
linked page.

Do you mean banner ads on pages in unpaid accounts? That would be OK to me.

   (6)  Some mechanism to accept payment for private or add-free accounts? 

Yes. 

My Chiselapp usage includes a mix of open-source and private repos in the same 
account, so perhaps the designation of {open/free, open/paid, private/free, 
private/paid} should be on a repo-basis and not on an account basis.

e

___
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] althttpd cgi chroot stunnel

2013-03-17 Thread Doug Currie
On Jan 10, 2012, at 3:27 PM, Thomas Stover c...@thomasstover.com wrote:

 “-user www-data” is of course the user to run programs as and access files as 
 (so again everything in /repos needs read/write/execute permission with user 
 www-data). 

Thank you Thomas for summarizing your althttpd usage with stunnel, and Richard 
for providing althttpd and fossil.

Having recently installed these programs on Debian Wheezy (Raspberry Pi), 
things went quite smoothly overall. However, I tried to finesse the permissions 
in my chroot jail, and was surprised to learn that although althttpd sets the 
user and primary group, it does not set any supplementary groups. 

What I had tried to do was make www-data a member of a new web-var group. That 
web-var group was the one given write permission on repositories. That way, 
www-data never has any special ownership or write permissions itself, other 
than on log files or temp files althttpd creates. I also use the setgid bit in 
the website directory permissions so web-var group propagates to 
subdirectories. Non-group (other) users get no permissions on the directories 
or files, and the file owners are regular uses who are also members of the 
www-var group.

But since althttpd [1] doesn't set any supplementary groups, my scheme failed. 
I am considering modifying althttpd to use initgroups [2] to set supplementary 
groups, but I wonder if any althttpd users (or authors) have advice to offer, 
either on the wisdom of making this change, or more generally on my permissions 
design.

Thanks!

e

[1] http://www.sqlite.org/docsrc/artifact/c028190e17ce?ln=1693-1698
[2] http://www.gnu.org/software/libc/manual/html_node/Setting-Groups.html
___
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.?

2012-12-31 Thread Doug Currie

On Dec 31, 2012, at 1:29 PM, Nico Williams n...@cryptonector.com wrote:

 I haven't yet re-unsubscribed.  Joerg's note added hope 

Thank you for explaining rebase. It's not something I've ever needed to do, so 
I was skeptical of its value, and even more skeptical that it would ever be 
adopted by Fossil. While you have not converted me to an advocate, I've learned 
why you find it useful, and how it may be achieved without destroying history. 
I thank you for that, and for trying to be constructive and civil on this 
mailing list. 

e

___
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] Install from binary on Macbook Pro OSX

2012-09-04 Thread Doug Currie

On Sep 4, 2012, at 2:09 PM, Kevin Martin ke...@khn.org.uk wrote:

 Fossil on my machine finds the readline library from MacPorts 
 (http://www.macports.org). You may want to install MacPorts, as it looks like 
 fossil is also using other libraries from there too.

I also have MacPorts installed, but my fossil built form source on OS X 10.8…

e$ otool -L /usr/local/bin/fossil
/usr/local/bin/fossil:
/usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 
1.2.5)
/usr/lib/libssl.0.9.8.dylib (compatibility version 0.9.8, current 
version 47.0.0)
/usr/lib/libcrypto.0.9.8.dylib (compatibility version 0.9.8, current 
version 47.0.0)
/usr/lib/libedit.3.dylib (compatibility version 2.0.0, current version 
3.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current 
version 169.3.0)

e

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


[fossil-users] clone using downloaded binary on Linux

2012-08-10 Thread Doug Currie
Using fossil built from source on OSX, this works fine, but using the binary 
from 

http://www.fossil-scm.org/download/fossil-linux-x86-20120808112557.zip

on a (fairly) freshly installed Debian Wheezy, I get:

e@eSammy:~/dev$ fossil clone http://www.fossil-scm.org/fossil fossil.fossil
Bytes  Cards  Artifacts Deltas
Sent:  53  1  0  0
fossil: can't resolve host name: www.fossil-scm.org
Total network traffic: 0 bytes sent, 0 bytes received
fossil: server returned an error - clone aborted
e@eSammy:~/dev$ 


The can't resolve host name is odd; Chrome can browse to that address just 
fine -- it's where I downloaded the binary.

Am I overlooking something?

e

___
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] clone using downloaded binary on Linux

2012-08-10 Thread Doug Currie

On Aug 10, 2012, at 10:35 PM, Richard Hipp d...@sqlite.org wrote:

 Maybe this is a problem with the new IPv6 logic and an older Linux that 
 doesn't do IPv6 very well?

This is on a very new Linux: Debian Wheezy, Linux kernel 3.2 -- 2012-08-04: 
Wheezy releases beta 1.

e

___
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] clone using downloaded binary on Linux

2012-08-10 Thread Doug Currie

On Aug 10, 2012, at 11:00 PM, Richard Hipp d...@sqlite.org wrote:
 
 Perhaps a libc incompatibility.  Does it work on Wheezy if you build from 
 sources?

Yes, I just built from sources, and clone works. 

I believe it is a libc incompatibility; in a slightly different Wheezy 
configuration I got something like:

error: /lib/libnss_mdns4_minimal.so.2: symbol strlen, version GLIBC_2.0 not 
defined in file libc.so.6 with link time reference'

e

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


[fossil-users] Apple clang version 4.0 warnings

2012-07-26 Thread Doug Currie
Here are some interesting warnings from clang compiling trunk today:

fossil e$ cc --version
Apple clang version 4.0 (tags/Apple/clang-421.0.57) (based on LLVM 3.1svn)
Target: x86_64-apple-darwin12.0.0
Thread model: posix


cc -I/usr/include -Wdeprecated-declarations  -g -O2 -DHAVE_AUTOCONFIG_H  -I. 
-I./src -Ibld -o bld/blob.o -c bld/blob_.c
./src/blob.c:444:17: warning: comparison of unsigned expression  0 is always 
false [-Wtautological-compare]
  if( p-iCursor0 ){


cc -I/usr/include -Wdeprecated-declarations  -g -O2 -DHAVE_AUTOCONFIG_H  -I. 
-I./src -Ibld -o bld/md5.o -c bld/md5_.c
./src/md5.c:269:31: warning: argument to 'sizeof' in '__builtin___memset_chk' 
call is the same expression as the destination; did you mean to dereference it? 
[-Wsizeof-pointer-memaccess]
memset(ctx, 0, sizeof(ctx));/* In case it's sensitive */
~~^
/usr/include/secure/_string.h:77:41: note: expanded from macro 'memset'
   ? __builtin___memset_chk (dest, val, len, __darwin_obsz0 (dest)) \
^


cc -I/usr/include -Wdeprecated-declarations  -g -O2 -DHAVE_AUTOCONFIG_H  -I. 
-I./src -Ibld -o bld/path.o -c bld/path_.c
./src/path.c:94:27: warning: argument to 'sizeof' in '__builtin___memset_chk' 
call is the same expression as the destination; did you mean to remove the 
addressof? [-Wsizeof-pointer-memaccess]
  memset(path, 0, sizeof(path));
  ^~~
/usr/include/secure/_string.h:77:41: note: expanded from macro 'memset'
   ? __builtin___memset_chk (dest, val, len, __darwin_obsz0 (dest)) \
^
e

___
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] SQLite 4

2012-06-27 Thread Doug Currie
On Jun 27, 2012, at 10:41 AM, Richard Hipp wrote:

 This is a work in progress.  

The SQLite4 numeric format sounds like a great improvement; on the doc page you 
say:

 The SQLite4 numeric format is for internal use. Numbers can be translated 
 between integers or doubles for input and output. 

Presumably SQLite4 numbers may also be translated from/to text without going 
through integers or doubles? This would avoid all the issues with why does 1 / 
10 != 0.1? we see on the mailing list.

e

___
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] Looking for a name for Android Fossil client...

2012-06-22 Thread Doug Currie

On Jun 22, 2012, at 3:37 PM, Stephan Beal wrote:

 But it needs a name, and that's where i need your help :). Fossilroid is my 
 current favourite but i'm not emotionally attached to it.
 
 Ideas?

Palentolodroid

e

___
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] Avoiding problems with fossil default Makefile

2011-07-21 Thread Doug Currie
On OSX 10.6.8...

I've installed a few macports programs; this creates /opt, and puts 
/opt/local/bin:/opt/local/sbin on the front of my PATH environment variable.

I'd like to build fossil with the system's /usr includes and libraries, and 
this is how the Makefile works. Is there a way to force this choice with 
autosetup's ./configure?

Using the Makefile, files are compiled (with no warnings or errors) with, e.g.,

gcc -g -Os -Wall -DFOSSIL_ENABLE_SSL   -I. -I./src -o ./bld/add.o -c 
./bld/add_.c

whereas using the configure generated GNUMakefile

cc -I/opt/local/include-g -O2 -DHAVE_AUTOCONFIG_H  -I. -I./src -o 
./bld/add.o -c ./bld/add_.c

Note the extraneous -I/opt/local/include

Similarly with the configure generated GNUMakefile I also get a LIB option 

-L/opt/local/lib


I found that if I removed /opt/local/bin:/opt/local/sbin from my PATH then 
fossil was built as I expected. This seems like an awkward workaround.


e

___
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] Removing the need for anonymous login...

2011-02-17 Thread Doug Currie

On Feb 17, 2011, at 10:21 AM, Justin Mazzi wrote:

 Disabling Zips  Diff generation seems like the most sensible option. 

Anonymous zips are important to allow for access by users of packaging systems 
(luarocks, ruby gems) that grab the zip based on a URI in the package 
specification. So, I have z access enabled for Anonymous, but h disabled. I 
believe this is safe because the URI is not visible as a hyperlink for 
Anonymous access even though the zip is accessible.

e

___
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] Removing the need for anonymous login...

2011-02-17 Thread Doug Currie
On Feb 17, 2011, at 10:31 AM, Justin Mazzi wrote:

 He's talking about 'nobody', not 'anonymous'.

Thanks; I also meant Nobody, and said Anonymous erroneously.

e

 On Thu, Feb 17, 2011 at 10:30 AM, Doug Currie doug.cur...@gmail.com wrote:
 
 On Feb 17, 2011, at 10:21 AM, Justin Mazzi wrote:
 
  Disabling Zips  Diff generation seems like the most sensible option.
 
 Anonymous zips are important to allow for access by users of packaging 
 systems (luarocks, ruby gems) that grab the zip based on a URI in the package 
 specification. So, I have z access enabled for Anonymous, but h disabled. I 
 believe this is safe because the URI is not visible as a hyperlink for 
 Anonymous access even though the zip is accessible.
 
 e
 
 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
 
 
 
 -- 
 Justin Mazzi

___
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 import from svn-dump-fast-export

2011-01-11 Thread Doug Currie

On Jan 11, 2011, at 6:51 PM, Richard Hipp wrote:

 On Tue, Jan 11, 2011 at 4:14 PM, Doug Currie doug.cur...@gmail.com wrote:
 
 I dumped my small svn repo using svn-dump-fast-export from 
 http://barrbrain.github.com/
 and imported it using fossil import --git
 
 The repo was created but all of my svn checkins look like separate leaves, 
 all on branch: master. There is no ancestor.
 
 The latest check-in of fossil should fix this problem.  Thx for bringing it 
 to my attention.

Thanks. The repo now has links between commits, but files that are not modified 
in each commit are considered deleted in that leaf.

e

___
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] three-way merge

2010-04-12 Thread Doug Currie

On Apr 12, 2010, at 12:52 PM, D. Richard Hipp wrote:

 Can anyone suggest a good 3-way graphical merger that I can use for  
 testing (Mac or Linux).

I have used DeltaWalker on Mac. Once installed it can be invoked with a command 
line (or shell script line) such as 

/Applications/DeltaWalker.app/Contents/MacOS/DeltaWalker -nosplash  $1 $2 
$3 -merge=$4


e

___
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] Numbering in the ticket view

2010-01-22 Thread Doug Currie

On Jan 22, 2010, at 6:32 AM, Jacek Cała wrote:

 Do you have any idea how to add numbering to the list of tickets. It would be 
 nice to have a quantitative view on the solved/unsolved issues. I was 
 skimming through the sqllite manual but couldn't find anything usable.

SELECT
  CASE WHEN status IN ('Open','Verified') THEN '#f2dcdc'
   WHEN status='Review' THEN '#e8e8e8'
   WHEN status='Fixed' THEN '#cfe8bd'
   WHEN status='Tested' THEN '#bde5d6'
   WHEN status='Deferred' THEN '#cacae5'
   ELSE '#c8c8c8' END AS 'bgcolor',
  status,
  count (*) AS 'count'
FROM ticket GROUP BY status


e

___
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] 3 Feature requests - globbing using the repository.

2009-12-10 Thread Doug Currie

On Dec 9, 2009, at 4:45 PM, Joshua Paine wrote:

 On Wed, 2009-12-09 at 22:22 +0100, Stephan Beal wrote:
 
 That said, presumably when you rm a file, it already exists in the
 repo, and the chance of a significant loss due to an unwanted unlink()
 on the file seems to be small.
 
 [...]

Re: --keep 

 If that's not acceptable, let them keep their current default function,
 but add a --do or --force flag to make them work on the filesystem, too.

This is not consistent with svn --force (and so I think it will confuse 
people); svn does:

Files (and directories that have not been committed) are immediately removed 
from the working copy. The command will not remove any unversioned or modified 
items; use the --force switch to override this behavior.

In other words, svn always deletes locally unless there are uncommitted 
modifications.

 I agree with Jeremy's proposal to prompt before destroying work that
 hasn't been committed (and the consequent necessity of the --force
 option).

Right, this is what --force should do. It should not be required for locally 
deleting versioned and unmodified files.

e

___
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] cannot pull

2009-11-05 Thread Doug Currie
Thanks, Richard, that fixed it.

I need to make a sticky note about fossil all rebuild; it seems I  
forget it a few weeks before each time I need to use it. Perhaps  
fossil could detect the schema error and ask if I meant to fossil all  
rebuild?

e

On Nov 5, 2009, at 9:15 PM, D. Richard Hipp wrote:


 On Nov 5, 2009, at 9:11 PM, Doug Currie wrote:

 fossil: table event has no column named tagid
 REPLACE INTO event(type,tagid,mtime,objid,user,comment,brief)VALUES
 ('t',263,2455096.863576389,5207,'anonymous','New ticket [3f0c73f2d2]
 idiff-command with parameter doesn''t work/i.','New ticket
 [3f0c73f2d2].')


 You must have upgraded to a new version of fossil recently (or at
 least since the last time you did a pull on that repository).
 Sometimes the internal schema changes.  So whenever you upgrade, it is
 a good idea to run:

 fossil all rebuild

 That command will reconstruct all your repositories based on the
 original artifacts and should fix the problem.


 D. Richard Hipp
 d...@hwaci.com



 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users