Re: [fossil-users] Cloning failure via SSH on MSYS2

[Andy Bradford]

Thus said =?windows-1252?Q?Marko_K=E4ning?= on Sat, 14 May 2016 12:34:48 +0200:

> SSH is  correctly configured, as I  can log onto the  host no problem,
> but above clone hangs once I press the "y" and then RETURN.

The next  progression from  the SSH  connection that  is to  be expected
after one has accepted the remote SSH host key is that of a username and
password prompt.

Where is the SSH password prompt for your user?

> It could be, that I have a  firewall issue on that machine, so I don't
> want to point a finger on Fossil.

I doubt it's a firewall. You hit the SSH server as evidenced by the fact
that  you got  an SSH  host  key. Did  you verify  that the  fingerprint
actually matches the server's host key?

> How can  I see more (debug)  information in order to  understand which
> process is the blocking one?

Fossil does have one option for SSH tracing, but your better bet will be
to turn  on SSH debugging. This  is typically done with  multiplying the
number of -v options  to the ssh command, but I  don't know what options
you will have if you're using putty. For example, you could do:

fossil clone --verbose -c 'ssh -vvv -e none -T' --sshtrace 
ssh://marko@IP:PORT//home/REPOS/FOSSIL/test.fossil test.fossil

This  will give  you as  much information  as can  be possibly  expected
(except, and unless you want also an HTTP trace).

Andy
-- 
TAI64 timestamp: 400057380bf1


___
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] ilegible stash listing

[fran]

my point basically is the output of the command looks like

[STASHID]:[CHANGESET] on DATE

but that statement should be

[STASHID] on DATE based on [CHANGESET]

or anything... but the important is to make the expressed relations
more accurate. See, [CHANGESET]'s date is not DATE, well then why
[CHANGETSET] on DATE expresses just that?



2016-05-14 16:05 GMT-03:00 Andy Bradford
:
> Thus said fran on Fri, 13 May 2016 03:58:44 -0300:
>
>> You mention the context. What context?
>
> The context  is the context  of ``fossil  stash'' and nothing  else. The
> stash listing does  not list committed code, it lists  code changes that
> you  have  made  that  have  not yet  been  committed  to  the  official
> repository. Anything that  one views as a result of  ``fossil stash ls''
> is clearly not committed  code by virtue of the fact  that one has saved
> the changes into the stash and not committed it.
>
> If one  has used ``fossil stash''  to save uncommitted changes  into the
> stash, then one learns that ``fossil  stash ls'' lists those things that
> have not yet been committed.
>
> In  my opinion,  there  is a  clear difference  between  the context  of
> ``fossil timeline'' and ``fossil stash''  but maybe I misunderstand your
> argument?
>
> Andy
> --
> TAI64 timestamp: 40005737770d
>
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Repairing trunk/timeline after a shun

[John P. Rouillard]

Hi Everybody:

I had to recently shun some artifacts from a fossil repo (due to
embedded security credentials). Now when I look at the fossil timeline
that spans that shunning I no longer have a single connected trunk.

To reproduce use:

fossil init shun.fossil
mkdir shun
cd shun
fossil open ../shun.fossil
echo 2 > 2
fossil addremove
fossil ci -m "initial commit"
echo 2a > 2
fossil ci -m "second commit"
echo 2b > 2
fossil ci -m "third commit"
echo 2shun > 2
fossil ci -m "fourth shunable commit"
echo 2c > 2
fossil ci -m "fifth commit"
echo 2d > 2
fossil ci -m "sixth commit"

then shun the forth commit. You can rebuild the repo if you like it
makes no difference.

fossil ui's timeline shows the initial checkin on the leftmost rail
with nodes for the initial, first, second, third commits. The third
commit is marked as a leaf. Then next to the left rail is a second
rail with no nodes until the fifth and sixth commits. The sixth commit
was marked as leaf before the shunning but not after the shunning.

So the fourth commit (shunned) is missing, but the timeline is
disjoint at the point of the shunning. Also the end of the trunk
branch is located at the fourth commit (which is marked as a leaf).

If I try to: fossil up trunk
in the shun subdirectory (with the 6th commit) I get:

  fossil: ../fossil/src/bag.c:146: bag_find: Assertion `e>0' failed.
  Aborted

which seems wrong.

I tried to reconnect the timelines by adding a new propagating branch
tag called trunk to commit 5. This did make commit 6 into a leaf, but
the timeline is still split. However I do get the following when
running 'fossil update trunk'

checkout: 7d1873d50037c56a9d610ef557590f33cc1ccbe1 2016-05-14 21:43:24 UTC
tags: trunk
comment:  sixth commit (user: rouilj)
changes:  None. Already up-to-date
WARNING: multiple open leaf check-ins on trunk:
  (1) 2016-05-14 21:43:24 [7d1873d500] (current)
  (2) 2016-05-14 21:43:19 [43059e2375]

So is there some way to reintegrate the trunk across the shun? Is this
split timeline just a side-effect of shunning? Would doing a
fossil git-export | fossil git-import
"fix" things?

(As a side note, is there a shun cli command? fossil help/help -all
doesn't seem to show one.)

Thanks for any insight.

--
-- rouilj
John Rouillard
===
My employers don't acknowledge my existence much less my opinions.
___
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] ilegible stash listing

[Andy Bradford]

Thus said fran on Fri, 13 May 2016 03:58:44 -0300:

> You mention the context. What context?

The context  is the context  of ``fossil  stash'' and nothing  else. The
stash listing does  not list committed code, it lists  code changes that
you  have  made  that  have  not yet  been  committed  to  the  official
repository. Anything that  one views as a result of  ``fossil stash ls''
is clearly not committed  code by virtue of the fact  that one has saved
the changes into the stash and not committed it.

If one  has used ``fossil stash''  to save uncommitted changes  into the
stash, then one learns that ``fossil  stash ls'' lists those things that
have not yet been committed.

In  my opinion,  there  is a  clear difference  between  the context  of
``fossil timeline'' and ``fossil stash''  but maybe I misunderstand your
argument?

Andy
-- 
TAI64 timestamp: 40005737770d


___
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 render a vertical line in a Markdown code snippet?

[Natacha Porté]

Hello,

on Saturday 14 May 2016 at 16:50, Svyatoslav Mishyn wrote:
> (Sat, 14 May 16:14) Svyatoslav Mishyn:
> > (Sat, 14 May 13:03) Marko Käning:
> > > How to render a vertical line in a Markdown code snippet?
> > > 
> > > I tried `|`, `\|` and `||` but all to no avail. The bare vertical in text 
> > > flow even caused fossil’s UI to try to render a table at one point.
> > > 
> > > If I do the same in a multiline code block it works:
> > > `
> > > |
> > > `
> > > but how to get this done w/o trouble in a code snippet??
> > 
> > I think, it is a bug in libsoldout.

I would argue that it's not a clear-cut bug, but rather an unfortunate
side-effect of the table structure being so light while having a higher
precedence than spans.

But yes, you encounter the same thing in libsoldout, and you have to
work around it the same way.

> It also works if a code snippet starts on a new line, i.e.
> bla bla
> `ps aux | grep firefox` zzz..

It's easier than that: you can't have a vertical bar (`|`) in the first
line of a makrdown paragraph, unless it's preceeded by a backslash ("\|")
(but then the backslash is not removed in a code span).

Fortunately, whitespaces are collapsed in HTML, so all the alternatives
below should render the vertical bar without table:

bla bla
`ps aux | grep firefox` zzz..

bla bla
bla bla `ps aux | grep firefox` zzz..

bla
bla `ps aux | grep firefox` zzz..

\
`ps aux | grep firefox` if you really need a code span at the beginning
of the paragraph


In other words, anything that pushes the vertical bar beyond the first
line perevents the paragraph from being interepreted as a table.


Hoping this help,
Natacha Porté


signature.asc
Description: PGP signature
___
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 render a vertical line in a Markdown code snippet?

[Svyatoslav Mishyn]

(Sat, 14 May 13:03) Marko Käning:
> How to render a vertical line in a Markdown code snippet?
> 
> I tried `|`, `\|` and `||` but all to no avail. The bare vertical in text 
> flow even caused fossil’s UI to try to render a table at one point.
> 
> If I do the same in a multiline code block it works:
> `
> |
> `
> but how to get this done w/o trouble in a code snippet??

I think, it is a bug in libsoldout.

/home/juef/dl/discount-2.2.0: cat test
Name | Description
 | ---
a| b
c| d


bla bla `ps aux | grep firefox` zzz..


# discount
/home/juef/dl/discount-2.2.0: ./markdown test



Name 
 Description




a
 b


c
 d





bla bla ps aux | grep firefox zzz..


# libsoldout + discount extensions; however without them it works,
# but of course without a table..
/home/juef/dl/discount-2.2.0: mkd2html -d test


  
Name
Description
  


  
a
b
  
  
c
d
  




  
bla bla `ps aux
grep firefox` zzz..
  



# and finally fossil..
/home/juef/dl/discount-2.2.0: f test-th-eval "markdown {`cat test`}"
{} {



  
Name
Description
  


  
a
b
  
  
c
d
  




  
bla bla `ps aux
grep firefox` zzz..
  



}


-- 
https://www.juef.tk/
___
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] Unrecognized command-line option, or missing argument: --https

[Piotr Orzechowski]

Hi Warren,
thanks for your help! In fact, I have already set an "A+" graded site. The 
problem is I'm hosting multiple repositories, as you can see here: 
https://orzechowski.tech. You solution seems to work with single repo only. I 
was just trying to migrate from xinetd to systemd with my fossil configuration, 
but to no avail.
Regards,
Orzech___
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] Pushing and pulling of ticket reports

[Marko Käning]

Would be nice if this
---
$ fsl config pull help
Available configuration areas:
  email  Concealed email addresses in tickets
  projectProject name and description
  skin   Web interface appearance settings
  cssStyle sheet
  shun   List of shunned artifacts
  ticket Ticket setup
  user   Users and privilege settings
  xfer   Transfer setup
  allAll of the above
no such configuration area: “help"
---
would explicitly mark all the areas which are auto-synched, no!?
:)


The configuration command help page should also mention the defaults.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] How to render a vertical line in a Markdown code snippet?

[Marko Käning]

How to render a vertical line in a Markdown code snippet?

I tried `|`, `\|` and `||` but all to no avail. The bare vertical in text flow 
even caused fossil’s UI to try to render a table at one point.

If I do the same in a multiline code block it works:
`
|
`
but how to get this done w/o trouble in a code snippet??
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Pushing and pulling of ticket reports

[Marko Käning]

It seems like the ticket area - which contains the ticket reports - is not 
pushed/pulled automatically to the parent repository (just like skin area)...

What is the reason for that and where are these exceptions actually documented? 
Can’t find it anywhere at the moment, but remember to have seen it somewhere 
(for
the skin area). Perhaps I’ve spotted this only on the mailing list even.
___
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] No progress on "fossil cp"

[Marko Käning]

Hi Stephan,

On 14 May 2016, at 12:35 , Stephan Beal  wrote:
> But in svn, now that i think about it, cp is, in practice, only used for 
> branching. i've never seen it used to copy something within the same tree.

maybe. So, I might have abused it all along. :)


> That would require a backwards-incompatible change to the manifest format, 
> which would bring with it a lot of pain for a feature which seems to be only 
> rarely useful (and never critical).

Yeah, forget it. I’ll keep info in the commit message if I need it, which 
happens rarely enough.

Thanks for caring!
Greets,
Marko___
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] No progress on "fossil cp"

[Stephan Beal]

On Sat, May 14, 2016 at 12:25 PM, Marko Käning 
wrote:

> On 14 May 2016, at 12:11 , Stephan Beal  wrote:
> > in 20+ years of using source control, i've never seen an 'cp' command
> (maybe i've just overlooked it in CVS/SVN). Fossil does have an 'mv'
> command which does retain history. Copying the same file to multiple
> places, while keeping the history for each and every copy, seems highly
> questionable to me.
>
> SVN and Mercurial have a copy command which keeps history.
>

But in svn, now that i think about it, cp is, in practice, only used for
branching. i've never seen it used to copy something within the same tree.


> > consider:
> >
> > scm cp a b
> >
> > now my history looks like 'b' has existed as long as 'a' has, which
> would be a bald-faced lie.
>
> Admittedly. :)
>
>
> > Checking out an older version, from before the copy, would presumably
> _not_ want to check out 'b', but retaining its history would imply that 'b'
> should indeed be retroactively applied to checkouts of any version which
> contains 'a’.
>
> Well, I guess in Fossil one will simply have to leave a not in the commit
> message from where a specific copied file originates then. :)
>

That would require a backwards-incompatible change to the manifest format,
which would bring with it a lot of pain for a feature which seems to be
only rarely useful (and never critical).


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

[fossil-users] Cloning failure via SSH on MSYS2

[Marko Käning]

Hi,

on an MSYS2 install I was trying to clone a repo which I can reach via SSH like 
this
---
$ fossil clone ssh://marko@IP:PORT//home/REPOS/FOSSIL/test.fossil test.fossil
The server's host key is not cached in the registry. You
have no guarantee that the server is the computer you
think it is.
The server's rsa2 key fingerprint is:
ssh-rsa 2048 78:83:99:b2:AA:87:5B:a9:05:81:12:f7:97:9f:77:c0
If you trust this host, enter "y" to add the key to
PuTTY's cache and carry on connecting.
If you want to carry on connecting just once, without
adding the key to the cache, enter "n".
If you do not trust this host, press Return to abandon the
connection.
Store key in cache? (y/n) y
---

SSH is correctly configured, as I can log onto the host no problem, but above 
clone 
hangs once I press the "y" and then RETURN.

What's going on here?

It could be, that I have a firewall issue on that machine, so I don’t want to
point a finger on Fossil. Fossil but might be able to give me some info about 
the
hang. How can I see more (debug) information in order to understand which 
process
is the blocking one?


Greets,
Marko
___
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] No progress on "fossil cp"

[Marko Käning]

On 14 May 2016, at 12:11 , Stephan Beal  wrote:
> in 20+ years of using source control, i've never seen an 'cp' command (maybe 
> i've just overlooked it in CVS/SVN). Fossil does have an 'mv' command which 
> does retain history. Copying the same file to multiple places, while keeping 
> the history for each and every copy, seems highly questionable to me.

SVN and Mercurial have a copy command which keeps history.


> consider:
> 
> scm cp a b
> 
> now my history looks like 'b' has existed as long as 'a' has, which would be 
> a bald-faced lie.

Admittedly. :)


> Checking out an older version, from before the copy, would presumably _not_ 
> want to check out 'b', but retaining its history would imply that 'b' should 
> indeed be retroactively applied to checkouts of any version which contains 
> 'a’.

Well, I guess in Fossil one will simply have to leave a not in the commit 
message from where a specific
copied file originates then. :)

Greets,
Marko
___
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] Feature request: auto-closing of tickets a la Trac

[Marko Käning]

On 13 May 2016, at 18:58 , Warren Young  wrote:
> We aren’t talking about fossil ui.  We’re talking about
> 
>  $ f ci -m “closes [12345abc]”

+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] How to create a ticket link in the wiki?

[Marko Käning]

On 12 May 2016, at 23:22 , Warren Young  wrote:
> The only reason to argue for [12345abc] form is that’s the form artifact IDs 
> take everywhere else in Fossil, most especially including the magic links in 
> checkin comments, which Makrdown wiki links most closely resemble.  Markdown 
> also uses square brackets for links, so it fits.

+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] Suggestions for list of branches in web-UI

[Marko Käning]

Hi list,

thanks for being so welcomingly responsive to all my posts! :)
I am delighted!!!

What about the issues found in this thread though?

Greets,
Marko
___
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] No progress on "fossil cp"

[Stephan Beal]

On Sat, May 14, 2016 at 11:43 AM, Marko Käning 
wrote:

> Hi devs,
>
> as it seems there is no demand of a “cp” command for fossil, really, as
> nothing
> seems to have been done about it in the last 3 years [1].
>
> I guess, it’s the same issue: someone would have to implement it...
> No, it’s not me either. ;)
>
> Anyway, still, I consider Fossil a great tool despite it lacking keeping
> history
> when copying files around.
>

in 20+ years of using source control, i've never seen an 'cp' command
(maybe i've just overlooked it in CVS/SVN). Fossil does have an 'mv'
command which does retain history. Copying the same file to multiple
places, while keeping the history for each and every copy, seems highly
questionable to me.


consider:

scm cp a b

now my history looks like 'b' has existed as long as 'a' has, which would
be a bald-faced lie. Checking out an older version, from before the copy,
would presumably _not_ want to check out 'b', but retaining its history
would imply that 'b' should indeed be retroactively applied to checkouts of
any version which contains 'a'.


-- 
- 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] Workaround for the missing 'squash' command?

[Marko Käning]

Hi Ron,

from what I read about merges in Fossil I had assumed, that they always merge 
in all changes 
changeset after changeset...

On 12 May 2016, at 03:15 , Ron W  wrote:
> I think you are misunderstanding how a merge works in Fossil. The commands:
> fossil update trunk
> fossil merge private
> fossil commit
> will merge the final result of the private branch in to trunk as a single 
> commit. The same result as your diff/patch commands.

But I see now, that I was mistaken in case of a private branch. I think 
fossil’s help page for merge 
should make that difference clear. Could find that on the wiki’s page for 
merging either [1].

Greets,
Marko



[1] http://www.fossil-scm.org/index.html/doc/trunk/www/branching.wiki___
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] Timestamps in ticket overview pages not shown in local time

[Marko Käning]

Hi Warren,

On 12 May 2016, at 02:05 , Warren Young  wrote:
> … Repeat until expert. :)

nicely said. :)

Will see how much pressure the issues I find/found will be for me and whether 
that
is enough motivation to invest time in this tool.

Well, the least I can do is to post my findings. This might highlight them and
perhaps even trigger someone else to do the work, as there is suddenly a worthy
little project popping up. :)

Thanks for all your replies and caring!

Greets,
Marko
___
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 timeline on console quirk with ticket titles

[Marko Käning]

Hi Warren,

thanks for the digging! :)

On 12 May 2016, at 01:27 , Warren Young  wrote:
> The problem is on line 1693 of src/manifest.c, if you want to try and fix it. 
>  I believe the proper fix would involve moving these tags into 
> www_print_timeline() in src/timeline.c.

If it bugs me enough I will have a look at it.

Greets,
Marko

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

[fossil-users] No progress on "fossil cp"

[Marko Käning]

Hi devs,

as it seems there is no demand of a “cp” command for fossil, really, as nothing
seems to have been done about it in the last 3 years [1].

I guess, it’s the same issue: someone would have to implement it...
No, it’s not me either. ;)

Anyway, still, I consider Fossil a great tool despite it lacking keeping history
when copying files around.

Greets,
Marko



[1] 
http://www.mail-archive.com/fossil-users%40lists.fossil-scm.org/msg09155.html
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users