Re: [fossil-users] using fossil server --repolist behind nginx proxy

[Dewey Hylton]

 From: David Macek david.mace...@gmail.com
 Sent: Sunday, March 29, 2015 10:56:07 AM
 
 On 29. 3. 2015 16:55, Andy Bradford wrote:
  Given  that you're  using nginx  as  a proxy,  perhaps you  need to  add
  --baseurl to the fossil server options?
 
 OP mentioned that he tried it.

yeah ... that feature seems to be relevant only when one is *not* serving a 
directory. at least that's what my testing has shown. 

and for what it's worth, i'm working with:
$ fossil version
This is fossil version 1.32 [6c40678e91] 2015-03-14 13:20:34 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] using fossil server --repolist behind nginx proxy

[Dewey Hylton]

 From: Dewey Hylton dewey.hyl...@gmail.com
 To: Fossil SCM user's discussion fossil-users@lists.fossil-scm.org
 Sent: Sunday, March 29, 2015 11:07:31 AM
 Subject: Re: [fossil-users] using fossil server --repolist behind nginx 
 proxy
 
  From: David Macek david.mace...@gmail.com
  Sent: Sunday, March 29, 2015 10:56:07 AM
  
  On 29. 3. 2015 16:55, Andy Bradford wrote:
   Given  that you're  using nginx  as  a proxy,  perhaps you  need to  add
   --baseurl to the fossil server options?
  
  OP mentioned that he tried it.
 
 yeah ... that feature seems to be relevant only when one is *not* serving a
 directory. at least that's what my testing has shown.
 
 and for what it's worth, i'm working with:
 $ fossil version
 This is fossil version 1.32 [6c40678e91] 2015-03-14 13:20:34 UTC

... any other suggestions? i really prefer to stay away from cgi and making my 
own index page ...
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] using fossil server --repolist behind nginx proxy

[Dewey Hylton]

i have the following running to serve a directory full of fossil archives:
/usr/bin/fossil server --repolist --port 8181 /data/fossil

this appears to work perfectly when directly hitting the site:
http://fossil.server.local:8181/
http://fossil.server.local:8181/somefossil
http://fossil.server.local:8181/somefossil/wiki

i need this behind nginx so that is accessible via proxy. so i've added the 
following config to my nginx.conf:
server {
  listen 80 ;
  server_name fossil.server.local ;
  location / {
proxy_pass http://localhost:8181/ ;
proxy_set_header Host $host ;
  }
}

this also appears to work properly. BUT the fossil repo needs to live under 
/fossil on the main site. so i've changed the nginx.conf to look like this:
server {
  listen 80 ;
  server_name www.server.local ;
  location /fossil/ {
proxy_pass http://localhost:8181/ ;
proxy_set_header Host $host ;
  }
}

with this, the repolist works properly the links are relative so the browser 
gets directed to the fossil archive under /fossil/ ... 

however, each reference inside the rendered pages do not include /fossil/ so 
all links are broken and of course the theme does not show. for example, 
visiting this page:
http://www.server.local/fossil/somefossil/home
produces the following link (among others):
http://www.server.local/somefossil/wiki

so i change the fossil command line to this:
/usr/bin/fossil server --repolist --port 8181 
--baseurl=http://www.server.local/fossil /data/fossil

this causes similar breakage, only the generated reference is now missing the 
project name and looks like this:
http://www.server.local/fossil/wiki

so ... is there a way to accomplish this without using cgi? am i on the right 
track? what am i missing?
___
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] using fossil server --repolist behind nginx proxy

[Dewey Hylton]

 From: Andy Bradford 
 amb-sendok-1430461727.niogihkppihojgmic...@bradfords.org
 To: Dewey Hylton dewey.hyl...@gmail.com
 Cc: Fossil SCM user's discussion fossil-users@lists.fossil-scm.org
 Sent: Wednesday, April 1, 2015 2:28:46 AM
 Subject: Re: [fossil-users] using fossil server --repolist behind nginx 
 proxy
 
 I believe --baseurl  is what you actually want to  use, however, I'm not
 sure --baseurl even works. Everytime I've seen someone try to use it, it
 never seems  to work right.  Is there  anyone successfully using  it? So
 it's possible that --baseurl  has a bug in that when it  is set, it does
 not append  the name  of the  actual repository  once the  repository is
 known.
 
 Please try the following:
 
 http://www.fossil-scm.org/index.html/info/7c8eb85c24ab99ed
 
 Thanks,
 
 Andy
 --
 TAI64 timestamp: 4000551b9041

thanks, andy! this appears to work as it should. in case someone else ever 
searches
the list for this (i find it hard to believe i'm the only one wanting to use 
this
functionality), i'll include both fossil and nginx configurations below.

meanwhile, should we expect this change to be committed to trunk and available 
in
the next version?


fossil command:
/usr/local/bin/fossil server \
--repolist \
--port 8181 \
--baseurl=http://www.server.local/fossil \
/data/fossil


nginx cfg block:
server {
  listen 80 ;
  server_name www.server.local ;
  location ^~ /fossil/ {
proxy_pass http://localhost:8181/ ;
proxy_set_header Host $host ;
}
}

in fact, it appears as if the Host header doesn't actually need to be set for 
this to work properly.

thanks again, andy, for stepping up to the plate and doing this!
___
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] is fossil repo web configuration possible from command-line?

[Dewey Hylton]

i suppose banging out some sql wouldn't be out of the question, though i
had not thought of this. it makes perfect sense, though. if i get stuck
i'll ask to see what you came up with. thanks for the suggestion!

On Wed, Jan 20, 2016 at 11:50 PM, Scott Robison 
wrote:

> On Wed, Jan 20, 2016 at 8:33 PM, dewey.hyl...@gmail.com <
> dewey.hyl...@gmail.com> wrote:
>
>> i'm a command-line junkie, and tend to script/automate everything ... and
>> i tend to create a lot of fossil repos for small projects. so i'm trying to
>> figure out how to programmatically configure individual repos so that i
>> don't have to deal with the web browser for configuration.
>>
>> i'm currently able to create users and set permissions and such, but so
>> far i haven't been able to figure out how to set:
>>
>> project name
>> project description
>> index page
>>
>> how can this be done via command-line? and where is this documented? i'm
>> sure i'll end up wanting more configuration items, but figure if someone
>> can explain this part to me i'll be able to figure out the others.
>>
>
> I created my own PHP based front end to a multi-repo fossil setup that
> allows me to create a repo using any of the others as a "template" and
> specify the project name & description. It uses SQL to tweak the settings
> rather than anything specific to fossil. I'm happy to share what I have
> (ugly though it is) if you think it might be helpful.
>
> --
> Scott Robison
>
>
> ___
> 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] is fossil repo web configuration possible from command-line?

[Dewey Hylton]

the "most official" way is exactly what i was looking for, and i did miss
the export/import features. the template feature doesn't appear to do all
i'd like (such as modifying the project description). export/import for my
purposes would be fiddly because of the byte counts and such. perhaps the
sql method is safer in the end due to the byte count issue, and more
complete because i'd be able to handle all of these through the one method.

i'll definitely play with these different options and see what works best
for me.

thanks for the suggestions!

On Wed, Jan 20, 2016 at 11:13 PM, Ross Berteig  wrote:

>
> On 1/20/2016 7:33 PM, dewey.hyl...@gmail.com wrote:
>
>> 
>> i'm currently able to create users and set permissions and such, but
>> so far i haven't been able to figure out how to set:
>>
>> project name
>>
> > project description
> > index page
>
>>
>> how can this be done via command-line? and where is this documented?
>>
>
> The most "official" way is probably through the --template option to the
> "fossil new" command. According to "fossil help new", it specifies a
> repository to use as a template for the new one, carrying over most
> settings from the template to the new repository, except for the list of
> normal users.
>
>
> After you have a repository, you can copy the configuration from an
> existing one with "fossil configuration pull AREA".
>
>
> A trickier by very scripty approach would also be through the "fossil
> configuration" command. It's export, import, and merge subcommands allow
> the configuration to be saved and loaded from a file.
>
> On my clone of the fossil repository, the command:
>
> C:\...> fossil configuration export project project.txt
>
> created project.txt containing these lines:
>
> # The "project" configuration exported from
> # repository "C:/Users/Ross/Documents/tmp/fossil4/..\fossil.fossil"
> # on 2016-01-21 03:54:09
> config /config 40
> 1318883638 'project-name' value 'Fossil'
> config /config 51
> 1318883638 'project-description' value 'Fossil SCM'
> config /config 55
> 1318883638 'index-page' value '/doc/tip/www/index.wiki'
> config /config 32
> 1318883638 'manifest' value 'on'
>
> which by some coincidence covers all three of the items you asked about. I
> believe that you can generally edit this file, although you probably have
> to adjust the byte count at the end of each "config /config n" line to be
> correct for the import or merge subcommands to read the file.
>
> See the output of fossil help configuration for documentation.
>
> The configuration is broken into areas which can be handled individually.
> The areas are: all email project shun skin ticket user
>
> Most items have a fairly obvious format in the file, a little
> experimentation will lead you where you want to go.
>
>
> i'm sure i'll end up wanting more configuration items, but figure if
>> someone can explain this part to me i'll be able to figure out the
>> others.
>>
>
> If you have a lot of repositories that should share the same list of users
> and related login details, you might be better served by using the login
> group mechanism, although it can be quirky to get set up. Once it is happy,
> logging in to any repository through the web interface logs you into all of
> them.
>
> --
> Ross Berteig   r...@cheshireeng.com
> Cheshire Engineering Corp.   http://www.CheshireEng.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

Re: [fossil-users] is fossil repo web configuration possible from command-line?

[Dewey Hylton]

In the end I think the sql method is the safest and best bet for my use
case. This was really quick to cobble together, and of course doesn't have
any protection (eg. from sql-injection or whatever), but as I'm just
focusing on rolling out new repositories via script I think I'm off to a
decent start.

%-=
#!/bin/sh

usage() { echo usage: $0 'archive.fossil "project name" "project
description"' ; exit 1 ; }

dbname="$1"
pname="$2"
pdesc="$3"

test -z "$4" || usage
test -f "${dbname}" || usage
test -n "${pname}"  || usage
test -n "${pdesc}"  || usage

fossil sqlite -R "${dbname}" "insert or replace into config values
(\"project-name\", \"${pname}\", now());"
fossil sqlite -R "${dbname}" "insert or replace into config values
(\"project-description\", \"${pdesc}\", now());"
%-=

next steps for me are to pre-populate a README.md, commit, and have /home
referencing that.

thanks again for your help!

On Thu, Jan 21, 2016 at 11:26 AM, Dewey Hylton <dewey.hyl...@gmail.com>
wrote:

> the "most official" way is exactly what i was looking for, and i did miss
> the export/import features. the template feature doesn't appear to do all
> i'd like (such as modifying the project description). export/import for my
> purposes would be fiddly because of the byte counts and such. perhaps the
> sql method is safer in the end due to the byte count issue, and more
> complete because i'd be able to handle all of these through the one method.
>
> i'll definitely play with these different options and see what works best
> for me.
>
> thanks for the suggestions!
>
> On Wed, Jan 20, 2016 at 11:13 PM, Ross Berteig <r...@cheshireeng.com>
> wrote:
>
>>
>> On 1/20/2016 7:33 PM, dewey.hyl...@gmail.com wrote:
>>
>>> 
>>> i'm currently able to create users and set permissions and such, but
>>> so far i haven't been able to figure out how to set:
>>>
>>> project name
>>>
>> > project description
>> > index page
>>
>>>
>>> how can this be done via command-line? and where is this documented?
>>>
>>
>> The most "official" way is probably through the --template option to the
>> "fossil new" command. According to "fossil help new", it specifies a
>> repository to use as a template for the new one, carrying over most
>> settings from the template to the new repository, except for the list of
>> normal users.
>>
>>
>> After you have a repository, you can copy the configuration from an
>> existing one with "fossil configuration pull AREA".
>>
>>
>> A trickier by very scripty approach would also be through the "fossil
>> configuration" command. It's export, import, and merge subcommands allow
>> the configuration to be saved and loaded from a file.
>>
>> On my clone of the fossil repository, the command:
>>
>> C:\...> fossil configuration export project project.txt
>>
>> created project.txt containing these lines:
>>
>> # The "project" configuration exported from
>> # repository "C:/Users/Ross/Documents/tmp/fossil4/..\fossil.fossil"
>> # on 2016-01-21 03:54:09
>> config /config 40
>> 1318883638 'project-name' value 'Fossil'
>> config /config 51
>> 1318883638 'project-description' value 'Fossil SCM'
>> config /config 55
>> 1318883638 'index-page' value '/doc/tip/www/index.wiki'
>> config /config 32
>> 1318883638 'manifest' value 'on'
>>
>> which by some coincidence covers all three of the items you asked about.
>> I believe that you can generally edit this file, although you probably have
>> to adjust the byte count at the end of each "config /config n" line to be
>> correct for the import or merge subcommands to read the file.
>>
>> See the output of fossil help configuration for documentation.
>>
>> The configuration is broken into areas which can be handled individually.
>> The areas are: all email project shun skin ticket user
>>
>> Most items have a fairly obvious format in the file, a little
>> experimentation will lead you where you want to go.
>>
>>
>> i'm sure i'll end up wanting more configuration items, but figure if
>>> someone can explain this part to me i'll be able to figure out the
>>> others.
>>>
>>
>> If you have a lot of repositories that should share the same list of
>> users and related login details, you might be better served by using the
>> login group mechanism, although it can be quirky to get set up. Once it is
>> happy, logging in to any repository through the web interface logs you into
>> all of them.
>>
>> --
>> Ross Berteig   r...@cheshireeng.com
>> Cheshire Engineering Corp.   http://www.CheshireEng.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

Re: [fossil-users] toc.tcl

[Dewey Hylton]

I predict this to be the best email I receive today.

My first thought was "This is like paid support!"
My second thought was "Wait ... paid support has *never* been this good ..."

Thanks for your work!

On Thu, Aug 17, 2017 at 10:10 PM Andy Goth  wrote:

> On 08/16/17 10:54, dewey.hyl...@gmail.com wrote:
> > I've been wishing for something similar to the TOC macro available in
> > moinmoin, and this is fairly close. The only thing missing from my
> > perspective is a link at each heading which points back to the top.
> >
> > I don't know jack about TCL, but perhaps it's time for me to look into
> it!
>
> Worth it.
>
> > I appreciate your work on this!
>
> Try this new version:
>
> https://chiselapp.com/user/andy/repository/brush/file/doc/toc.tcl
>
> --
> Andy Goth | 
> ___
> 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] Strange IP address on repository sync report.

[Dewey Hylton]

just for completeness ... i verified that i am seeing the same address
during a commit:

Autosync:  https://redacted
Round-trips: 1   Artifacts sent: 0  received: 0
Pull done, sent: 390  received: 994  ip: 2.0.1.187
New_Version: 906246b7cd7e5fec91c69502981582bdbfc0a89e
Autosync:  https://redacted
Round-trips: 1   Artifacts sent: 2  received: 0
Sync done, sent: 1344  received: 1045  ip: 2.0.1.187


i suppose the environment variables don't matter at this point, but this is
what i see:

uid=10080, gid=10080
g.zBaseURL = https://redacted
g.zHttpsURL =
g.zTop = /fossil/ansible-ceph
g.zPath = test_env
g.userUid = 6
g.zLogin = redacted
g.isHuman = 1
capabilities = abcefghijklmnopqrstwz
g.zRepositoryName = /data/fossil/ansible-ceph.fossil
load_average() = 0.01
--
GATEWAY_INTERFACE = CGI/1.0
HTTP_ACCEPT_ENCODING = gzip, deflate, br
HTTP_HOST = redacted
HTTP_USER_AGENT = Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:55.0)
Gecko/20100101 Firefox/55.0
PATH_INFO = test_env
QUERY_STRING =
REMOTE_ADDR = 127.0.0.1
REQUEST_METHOD = GET
REQUEST_URI = /ansible-ceph/test_env
SCRIPT_NAME = /ansible-ceph

On Fri, Sep 15, 2017 at 3:32 PM Richard Hipp  wrote:

> On 9/15/17, Richard Hipp  wrote:
> >
> > Perhaps Apache is setting the REMOTE_ADDR environment variable.  What
> > does https://asm32.info/fossil/repo/asmbb/test_env show for the
> > administrator?  (You have that page turned off for anonymous, so I
> > cannot see it.)
>
> Nevermind - the problem is on the client side, not on the server.  So
> it is not an Apache problem  Not sure what might be causing
> that
>
> --
> 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] Strange IP address on repository sync report.

[Dewey Hylton]

Sadly, I do not know how to do such a thing as I am not a developer. The 
concept is not foreign to me as I have a bit of experience with python, so I'll 
give it a shot starting with Google. Pointers to get me on the right track 
would be welcomed. 

> On Sep 15, 2017, at 3:58 PM, Richard Hipp <d...@sqlite.org> wrote:
> 
>> On 9/15/17, Dewey Hylton <dewey.hyl...@gmail.com> wrote:
>> just for completeness ... i verified that i am seeing the same address
>> during a commit:
>> 
>> Autosync:  https://redacted
>> Round-trips: 1   Artifacts sent: 0  received: 0
>> Pull done, sent: 390  received: 994  ip: 2.0.1.187
>> New_Version: 906246b7cd7e5fec91c69502981582bdbfc0a89e
>> Autosync:  https://redacted
>> Round-trips: 1   Artifacts sent: 2  received: 0
>> Sync done, sent: 1344  received: 1045  ip: 2.0.1.187
> 
> Please rerun in a debugger with a breakpoint on this line:
> 
>https://www.fossil-scm.org/fossil/artifact/91aa0e52?ln=394
> 
> And let me know if that is where g.zIpAddr is getting set and why it
> is being set to the wrong IP address.
> 
>> 
>> 
>> i suppose the environment variables don't matter at this point, but this is
>> what i see:
>> 
>> uid=10080, gid=10080
>> g.zBaseURL = https://redacted
>> g.zHttpsURL =
>> g.zTop = /fossil/ansible-ceph
>> g.zPath = test_env
>> g.userUid = 6
>> g.zLogin = redacted
>> g.isHuman = 1
>> capabilities = abcefghijklmnopqrstwz
>> g.zRepositoryName = /data/fossil/ansible-ceph.fossil
>> load_average() = 0.01
>> --
>> GATEWAY_INTERFACE = CGI/1.0
>> HTTP_ACCEPT_ENCODING = gzip, deflate, br
>> HTTP_HOST = redacted
>> HTTP_USER_AGENT = Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:55.0)
>> Gecko/20100101 Firefox/55.0
>> PATH_INFO = test_env
>> QUERY_STRING =
>> REMOTE_ADDR = 127.0.0.1
>> REQUEST_METHOD = GET
>> REQUEST_URI = /ansible-ceph/test_env
>> SCRIPT_NAME = /ansible-ceph
>> 
>>> On Fri, Sep 15, 2017 at 3:32 PM Richard Hipp <d...@sqlite.org> wrote:
>>> 
>>>> On 9/15/17, Richard Hipp <d...@sqlite.org> wrote:
>>>> 
>>>> Perhaps Apache is setting the REMOTE_ADDR environment variable.  What
>>>> does https://asm32.info/fossil/repo/asmbb/test_env show for the
>>>> administrator?  (You have that page turned off for anonymous, so I
>>>> cannot see it.)
>>> 
>>> Nevermind - the problem is on the client side, not on the server.  So
>>> it is not an Apache problem  Not sure what might be causing
>>> that
>>> 
>>> --
>>> 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
>>> 
>> 
> 
> 
> -- 
> 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] How to rename a directory

[Dewey Hylton]

Like Andy, I'm sure I've read that file names are what gets
tracked - and wasn't even aware anyone had worked on a
directory rename function ... At times when a project
grows, I do tend to create new subproject directories and
move existing files to those directories - and a directory
rename function in fossil which was basically a wrapper
around file renames would certainly make those operations
easier.

I've always just used this method:

for F in file1 file2 file3 ; do
  move="mv dir1/${F} dir2/${F}"
  $move && fossil $move
done

Looping around output from 'find' can be used for larger
numbers of files or those in several subdirectories.

When I'm working on one of my own boxes that get my own
environment setup, I use a shell function called "fmv"
which does this for me.

The end result appears to be what OP is looking for,
though of course the hard work is performed in the shell.

On Sun, May 6, 2018 at 12:40 AM Andy Bradford 
wrote:

> Thus said Dingyuan Wang on Sun, 06 May 2018 00:37:23 +0800:
>
> > The fossil mv command seems can't rename a directory.
>
> I  thought Fossil  only  tracked  files (which  is  their complete  path
> relative  to  the  repository  checkout) and  does  not  actually  track
> directories by themselves.
>
> For example, this works fine:
>
> $ mkdir first
> $ touch first/file
> $ ./fossil add first/file
> ADDED  first/file
> $ ./fossil ci -m go
> New_Version:
> 600ce3e31ee64a3ff98a9af360b50d5ca24323acac04ee25d26eee82de78fa58
> $ ./fossil mv --hard first/file second/file
> RENAME first/file second/file
> MOVED_FILE /tmp/first/file
> $ ./fossil ci -m again
> New_Version:
> 5107ce9a7299518f44799149094ace083f7cec994578d429ca94897e3b09e395
> $ ls first
> $ ls second
> file
>
> Andy
> --
> TAI64 timestamp: 40005aee8760
>
>
> ___
> 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] branch assistance needed

[Dewey Hylton]

I've used fossil for years now with lots of commits to trunk and very few
very simple branches which tend to get merged right into trunk after only a
few commits. I have managed to get myself in a confusing place with one of
my projects.

Essentially what I did was to commit a change to a new branch, forget I was
in that branch and committed another unrelated change which should have
gone back to trunk but went into the branch. I then attempted to change
that latest commit by adding a 'trunk' tag and cancelling the new branch
tag. I'm pretty sure that was wrong, but I'm unsure now where to go with
this. I've tried a few other things to no avail, but now even after
executing 'fossil update trunk' the 'fossil branch' command shows I'm still
in the new branch.

So I have two problems to solve:
1) how do I properly move commits between branches (and to trunk, in my
case)?
2) how do I unfudge my current condition and get back to trunk?
___
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 showing no repositories

[Dewey Hylton]

All users have read/write permissions on those files, so this doesn’t make 
sense (to me) from a Unix permissions standpoint. 

I am indeed a BSD guy, but ... in reality fossil is running in a docker 
container on a Linux server and accessing the files via sshfs mount. I can futz 
about and make the UIDs match, but unless fossil itself is making decisions 
based on UID I don’t understand the point. 

I haven’t looked at the code and understand fossil may be dropping permissions 
at some point, but the fossil binary is running as the root user in this case. 

> On Dec 20, 2017, at 5:54 PM, Warren Young  wrote:
> 
>> On Dec 20, 2017, at 3:40 PM, dewey.hyl...@gmail.com wrote:
>> 
>> # ls -lh /fossils|grep fossil
>> -rw-rw-rw-1 1000 root  272.0K Dec 19 14:37 archsetup.fossil
>> -rw-rw-rw-1 1000 root  224.0K Dec 19 14:36 
>> guac-install-script.fossil
>> -rw-rw-rw-1 1000 root  224.0K Dec 19 14:37 miscreports.fossil
>> -rw-rw-rw-1 1000 root  304.0K Dec 19 14:37 pkgReport.fossil
> 
> # chown -R arealuser /fossils
> 
> User 1000 doesn’t exist on your system, so those files are unreadable by 
> Fossil, which isn’t running as root.
> 
> Bonus guess: you scp’d or rsync’d this over to a BSD box from a Linux box 
> with permission preservation, where the Linux box starts normal users at UID 
> 1000 and the BSD box starts at 500.
> ___
> 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] fossil --repolist showing no repositories

[Dewey Hylton]

Oh, and THANK YOU for responding. 

> On Dec 20, 2017, at 5:54 PM, Warren Young  wrote:
> 
>> On Dec 20, 2017, at 3:40 PM, dewey.hyl...@gmail.com wrote:
>> 
>> # ls -lh /fossils|grep fossil
>> -rw-rw-rw-1 1000 root  272.0K Dec 19 14:37 archsetup.fossil
>> -rw-rw-rw-1 1000 root  224.0K Dec 19 14:36 
>> guac-install-script.fossil
>> -rw-rw-rw-1 1000 root  224.0K Dec 19 14:37 miscreports.fossil
>> -rw-rw-rw-1 1000 root  304.0K Dec 19 14:37 pkgReport.fossil
> 
> # chown -R arealuser /fossils
> 
> User 1000 doesn’t exist on your system, so those files are unreadable by 
> Fossil, which isn’t running as root.
> 
> Bonus guess: you scp’d or rsync’d this over to a BSD box from a Linux box 
> with permission preservation, where the Linux box starts normal users at UID 
> 1000 and the BSD box starts at 500.
> ___
> 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