Re: [fossil-users] An old fossil issue with not saving passwords... is there a resolution?

2018-06-19 Thread Ron Aaron
One workaround is to open a regular CMD shell on the machine itself (not over ssh).  Do 'fossil remo' or whatever there, then the password etc gets saved and it will subsequently work over ssh. Not the best solution, but it does work. On 19/06/2018

Re: [fossil-users] A fossil library

2018-06-19 Thread Richard Hipp
On 6/19/18, Stephan Beal wrote: > i have _no_ idea what the differences are between sha1 and > sha1-hard, SHA1-hard is a modified SHA1 algorithm that is resistant to the SHAttered attack (https://shattered.io/) against SHA1 that came out about a year ago. SHA1-hard generates the same hashes as

Re: [fossil-users] A fossil library

2018-06-19 Thread Stephan Beal
On Tue, Jun 19, 2018 at 8:13 PM Sam Putman wrote: > >> >>> I got the sense from the docs that the hash is using the SQLite style >>> versioned API, so it follows that >>> the old hash code is sitting where it needs to. >>> >>> Does this amount to following the style of that file for another

[fossil-users] An old fossil issue with not saving passwords... is there a resolution?

2018-06-19 Thread Ron Aaron
Just today I decided I need to set up a windows build machine, and I put "msys2" on it, with ssh and build tools .  It's great, in general. However, after having to specify "user:pwd" in the clone URL to get a clone working, I now always have to do that as

Re: [fossil-users] A fossil library

2018-06-19 Thread Sam Putman
On Tue, Jun 19, 2018 at 11:28 AM, Stephan Beal wrote: > On Tue, Jun 19, 2018 at 8:13 PM Sam Putman wrote: > >> >>> I got the sense from the docs that the hash is using the SQLite style versioned API, so it follows that the old hash code is sitting where it needs to.

Re: [fossil-users] Using fossil with Golang (go get)

2018-06-19 Thread Carlo Miron
On Tue, Jun 19, 2018 at 8:54 AM, Mark Janssen (fossil) wrote: > Has someone managed to make `go get` work with `hydra.ecd.space`? `chiselapp.com` works out of the box, even without the `` trickery: $ GOPATH=/tmp/go go get chiselapp.com/user/C8E/repository/go $ /tmp/go/bin/go

Re: [fossil-users] Using fossil with Golang (go get)

2018-06-19 Thread Zack Scholl
Hi Carlo, Actually chiselapp.com is a special case. They included it specifically as a pre-defined VCS path [1]. So to get it work with your own fossil, you should add the meta tag. [1]: https://github.com/golang/go/blob/master/src/cmd/go/internal/get/vcs.go#L1009-L1015 On Tue, Jun 19, 2018

[fossil-users] Are commits with "a lot" of small files still an issue?

2018-06-19 Thread Martin Vahi
I have not experienced any problems like that myself, but when searching for online documentation for recursive unversioned insertion of files, id est I wanted to use the fossil unversioned add recursively without it telling me that paths with "./" like fossil unversioned add

Re: [fossil-users] A fossil library

2018-06-19 Thread Stephan Beal
On Mon, Jun 18, 2018 at 7:18 PM Sam Putman wrote: > A Capitalized pure-C struct being referred to as an object is not unheard > of! But it did lead me down > the wrong path. > Here's my little contribution to spreading the word about OO in C:

Re: [fossil-users] A fossil library

2018-06-19 Thread Sam Putman
On Tue, Jun 19, 2018 at 10:20 AM, Stephan Beal wrote: > On Mon, Jun 18, 2018 at 7:18 PM Sam Putman wrote: > >> A Capitalized pure-C struct being referred to as an object is not unheard >> of! But it did lead me down >> the wrong path. >> > > Here's my little contribution to spreading the word

Re: [fossil-users] Are commits with "a lot" of small files still an issue?

2018-06-19 Thread Stephan Beal
On Tue, Jun 19, 2018 at 7:56 PM Martin Vahi wrote: > The reason, why I write the current letter > is that IF the insertion of large amounts of > very small files is still an issue, then > there would be an opportunity to fix it > before anybody reports the issue. > i think we're all curious

Re: [fossil-users] Using fossil with Golang (go get)

2018-06-19 Thread Mark Janssen (fossil)
On 2018-06-18 23:42, Zack Scholl wrote: Hi Mark, The meta tag will not work for importing Go code. The first term needs to match the import path, e.g. "X" in the `go get X` command. And "http(s)://" is not allowed in the import path for `go get`. Is there a fossil variable similar to