Re: [fossil-users] crlf-glob

[Warren Young]

On May 15, 2017, at 4:16 PM, Thomas  wrote:
> 
> On 2017-05-15 23:09, Warren Young wrote:
>> On May 15, 2017, at 3:27 PM, Thomas  wrote:
>>> 
>>> Does it really matter in the 21st century if a line is terminated by CR, 
>>> LF, or CR/LF anymore?
>> 
>> Notepad.exe
> 
> So, after editing a file that belongs to your project with Notepad on 
> Windows, would you expect an SCM complaining about it when you commit?

If I knew I was building a project where the *.txt files needed to be readable 
on all common platforms, including Windows, I’d save them with CRLF line 
endings and add a *.txt line in .fossil-settings/crlf-glob.  That way, the text 
editors on Linux, macOS, and such won’t molest the CRLF endings, and if the 
Windows-based end users of the project haven’t associated something decent with 
*.txt, they’ll see the file as-intended and their text editor will save the 
file back out with CRLF, which is fine.

This policy means you can save most every other text file in the project with 
LF line endings since those are probably only associated with decent text 
editors on Windows (e.g. *.c, *.md, *.xml…) so those line endings won’t be 
molested, either.

The core of this philosophy is to cause the files in the repository to obey the 
principle of least surprise, with the burden of understanding what’s going on 
being placed on the person(s) maintaining the repository.

The alternative, where Fossil just tries to do magic but dumps a burden on the 
end users of the repository when the heuristics fail is fundamentally 
backwards.  It burdens the masses for the sake of the few.

Maybe you’d like to explain how the line endings got screwed up in your 
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] crlf-glob

[Thomas]

On 2017-05-15 23:09, Warren Young wrote:

On May 15, 2017, at 3:27 PM, Thomas  wrote:


Does it really matter in the 21st century if a line is terminated by CR, LF, or 
CR/LF anymore?


Notepad.exe in Windows 10 Creator’s Edition still only works properly with 
CR+LF.  Since that’s the default handler for *.txt on Windows, yes, line ending 
type still matters for any cross-platform project.


So, after editing a file that belongs to your project with Notepad on 
Windows, would you expect an SCM complaining about it when you commit?


I wouldn't.


___
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] crlf-glob

[Warren Young]

On May 15, 2017, at 3:27 PM, Thomas  wrote:
> 
> Does it really matter in the 21st century if a line is terminated by CR, LF, 
> or CR/LF anymore?

Notepad.exe in Windows 10 Creator’s Edition still only works properly with 
CR+LF.  Since that’s the default handler for *.txt on Windows, yes, line ending 
type still matters for any cross-platform project.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] crlf-glob

[Thomas]

Hello,

Since this was causing us quite a lot of hassle I was wondering what's 
the reason to have a crlf-glob in the first place?


Does it really matter in the 21st century if a line is terminated by CR, 
LF, or CR/LF anymore?



Cheers
Thomas
___
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] /dev/null and /dev/urandom not available ?

[Ross Berteig]

On 5/13/2017 5:50 AM, Richard Hipp wrote:

On 5/13/17, Olivier R.  wrote:


To launch the server, I simply type:

fossil open repo.fossil
nohup fossil server &

Are you running the commands above as root?  If so, Fossil will
automatically put itself in a chroot jail on the directory containing
the repository and drop root privileges before doing anything else.
This is a security feature.

If you are going into a chroot jail, probably /dev/null and
/dev/urandom are no longer in that chroot jail.  You can fix that by
running:

mkdir dev
mknod dev/null c 1 3
mknod dev/urandom c 1 9


You will also probably want to put the local timezone file inside the 
jail, so that the server can display the timeline in server local time 
instead of UTC if you choose. Without that, the option "Use UTC" in 
/setup_timeline will have no effect. That puzzled me for a while when I 
first stood up a fossil on Ubuntu because there are no error messages 
anywhere when there is no timezone. Processes just see local time and 
UTC time as equivalent, silently.


In that installation I'm using inetd to do the listening on a port other 
than 80 and launching fossil as needed. But it is launched as root, so 
it lands in a chroot jail. The jail is rooted at the folder containing 
the .fossil file (or folder of .fossil files) being served, so along 
with *.fossil I have dev/urandom, dev/null, and etc/localtime (which is 
a copy and not a symbolic link because the chroot jail won't allow the 
link to be followed).


--

Ross Berteig   r...@cheshireeng.com
Cheshire Engineering Corp.   http://www.CheshireEng.com/
+1 626 303 1602

___
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] How to transfer/move/upload local repository to chiselapp.com

[Javier Guerra Giraldez]

On 15 May 2017 at 21:02, The Tick  wrote:
> That was exactly what I was doing -- after clicking 'Create Repository' my
> focus was on the form and I was totally oblivious to the additional options
> that had appeared.


just for the record, in the "create repository" form, there's an
"Override project code" option, with a short explanation "(Optional,
but may be needed if pushing an already created repo to Chisel.)"
that allows that option to work.  just copy there the existing
project's code and it will accept your push.


-- 
Javier
___
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] How to transfer/move/upload local repository to chiselapp.com

[The Tick]

On 5/15/2017 9:21 AM, Roy Keene wrote:

There is a way to upload the repository -- what you are probably doing
now is creating a new repo with the same project code then pushing to
that, which won't work out great.

When you go to "Create Repository" there are 3 options: 1. Create a new
repository; 2. Pull a repository from somewhere; 3. Upload a repository
file -- pick the last one.



That was exactly what I was doing -- after clicking 'Create Repository' 
my focus was on the form and I was totally oblivious to the additional 
options that had appeared.


It is now uploaded and is working fine. Thank you.
___
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] Where can I find a pre-compiled 32-bit Linux version?

[Warren Young]

On May 15, 2017, at 12:54 PM, Tony Papadimitriou  wrote:
> 
> I need a pre-compiled 32-bit Linux version of the release fossil
> (The same Windows version says: This is fossil version 2.2 [81d7d3f43e] 
> 2017-04-11 20:54:55 UTC)

Here: goo.gl/Tp7Foq

It’s built on a 32-bit CentOS 5 system, statically, with internal OpenSSL.  
Default options otherwise.

> (I’m locked out from being able to update either fossil or sqlite3 directly 
> from Linux.)

Do you not have a local C compiler, related development tools and libraries?

About that only time that happens to be these days is in embedded systems, but 
from your question, I assume that is not the 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] /dev/null and /dev/urandom not available ?

[Warren Young]

On May 13, 2017, at 6:50 AM, Richard Hipp  wrote:
> 
> Are you running the commands above as root?

…and if so, I would guess the only reason you’re running it as root is so that 
it can listen on port 80, in which case I *strongly* encourage you to bind 
Fossil to localhost on a high-numbered random port and put a proxy in front of 
it, ideally configured for TLS.

That way, not only do you fix the /dev access problems, you bypass or wall off 
a whole pile of security problems.

I wrote up a guide to do that [1] about a year ago, at which time Let’s Encrypt 
on nginx required manual certificate updating.  I should probably rewrite that 
guide now that the automatic update stuff is sorted out in certbot.

The bulk of that guide won’t be substantially different, though, so if you can 
work out the differences on your own, it’ll probably still be helpful to you 
as-is.


[1]: 
https://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg22907.html

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

[fossil-users] Where can I find a pre-compiled 32-bit Linux version?

[Tony Papadimitriou]

I need a pre-compiled 32-bit Linux version of the release fossil
(The same Windows version says: This is fossil version 2.2 [81d7d3f43e] 
2017-04-11 20:54:55 UTC)

The download page only offers a 64-bit Linux version.

(I’m locked out from being able to update either fossil or sqlite3 directly 
from Linux.)

Thanks.___
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] How to transfer/move/upload local repository to chiselapp.com

[Warren Young]

On May 15, 2017, at 8:21 AM, Roy Keene  wrote:
> 
> what you are probably doing now is creating a new repo with the same project 
> code then pushing to that, which won't work out great.

To clarify, one of the things Fossil does when it creates a new repository is 
to generate a universally unique project code, which was done on both sides — 
once for your local repo and once for the remote chiselapp.com repo — so the 
two repos are essentially incompatible.  No matter which direction you push, 
the receiving repo will decide those artifacts aren’t for it, so it will ignore 
them.

It would defeat some Fossil’s core security architecture to allow a “foreign” 
repo to push the way you tried from start.
___
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] Minor bug with SEARCH command

[Tony Papadimitriou]

An alternate fix for [2d69772e] so that SEARCH without target behaves the same 
both from within an open repo, and with the –R option.

if( g.argc<2 ) return;
blob_init(, g.argc<3?"":g.argv[2], -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] /dev/null and /dev/urandom not available ?

[Richard Hipp]

On 5/15/17, Roy Keene  wrote:
> Maybe it should open /dev/null and /dev/urandom before chroot()'ing ?

That would be difficult to implement.

-- 
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

Re: [fossil-users] /dev/null and /dev/urandom not available ?

[Joerg Sonnenberger]

On Mon, May 15, 2017 at 09:15:02AM -0500, Roy Keene wrote:
> Maybe it should open /dev/null and /dev/urandom before chroot()'ing ?

At /dev/urandom doesn't need to be used on newer Linux systems,
getentropy/getrandom provide the same service as system call.

Joerg
___
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] How to transfer/move/upload local repository to chiselapp.com

[Roy Keene]

There is a way to upload the repository -- what you are probably doing now 
is creating a new repo with the same project code then pushing to that, 
which won't work out great.


When you go to "Create Repository" there are 3 options: 1. Create a 
new repository; 2. Pull a repository from somewhere; 3. Upload a 
repository file -- pick the last one.


Thanks,
Roy Keene

On Sun, 14 May 2017, The Tick wrote:

Hmmm. I now see on the timeline that there are two users and the last leaf is 
unconnected to the timeline entries from my local repository. There are two 
users: my windows user name (which I guess I now want to get rid of) and the 
username that I use on chiselapp.com


The chiselapp.com username is the one with the "empty" checkin
My windows username is now there on chiselapp.com after my 'push'

47 timeline items

2017-05-14
21:03 
[7a7ff8235f] Leaf: initial empty check-in (user: iamdave, tags: trunk)

20:59   ? Deleted wiki page CWind 1.4 (user: imdave) [details]
20:57   ? Changes to wiki page CWind (user: imdave) [details]
20:56   ? Changes to wiki page CWind (user: imdave) [details]
20:35   ? Changes to wiki page CWind 1.4 (user: imdave) [details]
20:31   ? Changes to wiki page manpage (user: imdave) [details]
20:20   ? Changes to wiki page manpage (user: imdave) [details]
20:04   ? Changes to wiki page CWind 1.4 (user: imdave) [details]
19:56 
[0d276cd236] Leaf: Rename all files from .cpp to .c -- there is no reason to 
use C++ (user: imdave, tags: trunk)

19:28   ? Changes to wiki page CWind 1.4 (user: imdave) [details]
05:39   ? Changes to wiki page CWind 1.4 (user: imdave) [details]

The 21:03 and the 19:56 leaf's are not connected with the little arrow lines.

I'm probably really messing this up.

Is there a way to upload my local repository (created on windows and which is 
using my windows user name) to chiselapp.com and somehow create an 
equivalence to the username on chiselapp and my windows username?



___
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] How to transfer/move/upload local repository to chiselapp.com

[Roy Keene]

I run ChiselApp.com now and have no plans to stop doing so -- it's viable 
I'd say !


On Sun, 14 May 2017, The Tick wrote:


Sorry for all these questions.

I ran across an exchange from 2013 (I think) that talked about chiselapp.com 
shutting down. Obviously it has not done so.


What is the status of chiselapp.com and is it a viable place to put an open 
source repository as of 2017?

___
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] /dev/null and /dev/urandom not available ?

[Roy Keene]

Maybe it should open /dev/null and /dev/urandom before chroot()'ing ?

On Sat, 13 May 2017, Richard Hipp wrote:


On 5/13/17, Olivier R.  wrote:

Hello,

I?m running Fossil on Debian Jessie 8.2
(x86_64-debian-jessie-2016-04-06_15:26) at Scaleway.com (VC1S).

In the admin panel, Fossil says:

   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.

fossil is in usr/bin.
repo.fossil is in /root/repo.

To launch the server, I simply type:

   fossil open repo.fossil
   nohup fossil server &


Are you running the commands above as root?  If so, Fossil will
automatically put itself in a chroot jail on the directory containing
the repository and drop root privileges before doing anything else.
This is a security feature.

If you are going into a chroot jail, probably /dev/null and
/dev/urandom are no longer in that chroot jail.  You can fix that by
running:

  mkdir dev
  mknod dev/null c 1 3
  mknod dev/urandom c 1 9

See also the "managing server load" heading of
http://fossil-scm.org/fossil/doc/trunk/www/server.wiki where it talks
about the importance of making /proc available inside the chroot jail
so that Fossil can determine the load average.

Or, you can use the --nojail option on the "fossil server" command, in
which case Fossil will still drop its root privilege but will not
attempt to form a chroot jail.  This is less secure, but probably
still plenty safe.





In /dev, there is:

   crw-rw-rw- 1 root root 1, 3 Apr 8 2016 null
   crw-rw-rw- 1 root root 1, 9 Apr 8 2016 urandom


If I clone the repository, modify something, commit the modification,
fossil says when trying to sync:

   Autosync:  http://xxx.xxx.xxx.xxx:8080
   Round-trips: 1  Artifacts sent: 0  received: 0
   Pull done, sent: 312  received: 328  ip: xxx.xxx.xxx.xxx
   New_Version: _hash_code_x
   Autosync:  http://xxx.xxx.xxx.xxx:8080
   Round-trips: 1  Artifacts sent: 2  received: 0
   Error: not authorized to write
   Round-trips: 1  Artifacts sent: 2  received: 0
   Sync done, sent: 759  received: 355  ip: xxx.xxx.xxx.xxx
   Autosync failed.

The repository has not been updated.

How to solve these problems?

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




--
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