Re: [fossil-users] Fossil mentioned on HN

[Gaurav M. Bhandarkar]

>It's a matter of taste

I agree.


>To me that seems simpler than [ab]using the SCM for that type of thing

I think the power of versioning given by the SCM may not be limited to just
the publishable code that I write. IMO using it to version other things
isn't abusing but realizing its true potential :)




On Wed, Dec 16, 2015 at 4:36 PM, Stephan Beal <sgb...@googlemail.com> wrote:

> On Wed, Dec 16, 2015 at 11:59 AM, Gaurav M. Bhandarkar <
> gaurav.a...@gmail.com> wrote:
>
>> "git rebase -i" seems to enable me to work on multiple projects at the
>> same time. Because of it I can maintain versioned "development sessions" of
>> not only my code but other things that were required/relevant to make that
>> code. Without it I find it impossible to handle the "context switch" that
>> comes when you work on multiple projects.
>>
>
> fossil supports multiple open checkouts of any given repo db copy, which
> is arguably a cleaner approach than temporarily sticking stuff into SCM
> (when you've no intention of keeping it there). It's a matter of taste, of
> course, but fossil does offer an option other than keeping separate trains
> of thought in the same physical copy of the tree. To me that seems simpler
> than [ab]using the SCM for that type of thing, in particular because a
> context switch is a simple 'cd' instead of SCM commands.
>
> --
> - 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 mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Fossil mentioned on HN

[Gaurav M. Bhandarkar]

Yes, rebase is just a faster way to cherry-pick and other things:
http://think-like-a-git.net/sections/rebase-from-the-ground-up/using-git-cherry-pick-to-simulate-git-rebase.html



On Thu, Dec 17, 2015 at 11:43 AM, Scott Robison <sc...@casaderobison.com>
wrote:

> On Wed, Dec 16, 2015 at 10:34 PM, Gaurav M. Bhandarkar <
> gaurav.a...@gmail.com> wrote:
>
>> > Don't need rebase to use fast-forward merge.
>>
>> Normal merge or rebase both "enables" fast-forward merges. But the
>> advantage "rebase-before-ff-merge" has is that it avoids other(s) extra
>> "merge commits" that you would have done to get your branch updated with
>> changes from remote.
>>
>> See the section "Don't merge upstream code at random points":
>> https://www.mail-archive.com/dri-devel@lists.sourceforge.net/msg39091.html
>>
>>
>> > You can use private branches to the same effect
>> I'm not sure. The thing that immediately comes to mind is that fossil's
>> private branches will show up as a single commit in the public branch.
>>
>
> It depends on how you go about it:
>
> Create a private branch off trunk. Edit, commit, do whatever you want with
> it.
>
> When you're finished and ready to rebase, create a public branch off trunk
> and cherry pick merge the private commits you want in the public history.
> You have as much opportunity as you want to clean and massage them.
>
> Now you can merge that branch to trunk.
>
> I'm not trying to suggest it is in any way nearly as "elegant" as "rebase
> -i" (those who prefer that would find this clunky at best). Still, it seems
> possible.
>
> --
> 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] Fossil mentioned on HN

[Gaurav M. Bhandarkar]

> Don't need rebase to use fast-forward merge.

Normal merge or rebase both "enables" fast-forward merges. But the
advantage "rebase-before-ff-merge" has is that it avoids other(s) extra
"merge commits" that you would have done to get your branch updated with
changes from remote.

See the section "Don't merge upstream code at random points":
https://www.mail-archive.com/dri-devel@lists.sourceforge.net/msg39091.html


> You can use private branches to the same effect
I'm not sure. The thing that immediately comes to mind is that fossil's
private branches will show up as a single commit in the public branch.

> I strongly prefer to not use it(rebase) as it results in commits with
questionable content
I agree and thus I use rebase to remove only those commits that had binary
files, sample test codes and misc. stuff.


On Thu, Dec 17, 2015 at 7:12 AM, Ron W <ronw.m...@gmail.com> wrote:

> On Wed, Dec 16, 2015 at 4:27 AM, Gaurav M. Bhandarkar <
> gaurav.a...@gmail.com> wrote:
>>
>> fast forward merges is just one of the advantages of rebase. It is done
>> to avoid the extra “merge-commit” and thus reduces the noise in repo
>> history.
>>
>
> Don't need rebase to use fast-forward merge. As I said, I usually only
> submit the final revision - after merging in the lastest tip from the trunk
> of the (open source) projects I'm contributing to. (For work, we keep all
> revisions in our department repos.)
>
>
>> Then I run “git rebase -i master” which gives me an option to “squash”
>> commits that happened after “where-master-is-currently-at”. I can now
>> remove those commits that had binary files, code samples etc. from my local
>> branch’s history while keeping the actual code-changes and their commit
>> messages. In the end I get a clean revision history ready to be merged in
>> the master.
>>
>>
>> I really miss this feature when I use fossil.
>>
>
> You can use private branches to the same effect, optionally scrubbing the
> private branches when done. But even if you don't scrub the private
> branches, they won't get sync'd to the upstream repo (unless you use the
>  --private option on the pull command (possibly also push and sync as
> well)).
>
> While I have used rebase a few times when I was asked to preserve the
> change history, I strongly prefer to not use it as it results in commits
> with questionable content. Granted those intermediate commits are rarely
> used to build run-able or releasable code, but I dislike "publishing" them.
>
>
> ___
> 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 mentioned on HN

[Gaurav M. Bhandarkar]

>The forced "merge commit" is (IMO) a design flaw in git
Ya. But people can enforce a merge process where the contributor has to
rebase(not rebase -i) and test before the ff-merge to avoid the flaw. Ron W
has explained that in detail.

> If "cleanliness is godliness" then git might have fossil beat in that
regard.
My e.g. doesn't stress cleanliness. I don't seem to mind a noisy commit
history.

"git rebase -i" seems to enable me to work on multiple projects at the same
time. Because of it I can maintain versioned "development sessions" of not
only my code but other things that were required/relevant to make that
code. Without it I find it impossible to handle the "context switch" that
comes when you work on multiple projects.

-Gaurav

On Wed, Dec 16, 2015 at 3:06 PM, Stephan Beal <sgb...@googlemail.com> wrote:

>
>
> On Wed, Dec 16, 2015 at 10:27 AM, Gaurav M. Bhandarkar <
> gaurav.a...@gmail.com> wrote:
>
>> > The end result is theoretically the equivalent of having started your
>> branch at the latest trunk tip instead of where ever you really started it
>>
>>
>> fast forward merges is just one of the advantages of rebase. It is done
>> to avoid the extra “merge-commit” and thus reduces the noise in repo
>> history.
>>
>
> The forced "merge commit" is (IMO) a design flaw in git, as such a forced
> commit _could not possibly_ have been tested by a person before the
> committing.
>
> Then I run “git rebase -i master” which gives me an option to “squash”
>> commits that happened after “where-master-is-currently-at”. I can now
>> remove those commits that had binary files, code samples etc. from my local
>> branch’s history while keeping the actual code-changes and their commit
>> messages. In the end I get a clean revision history ready to be merged in
>> the master.
>>
>>
>> I really miss this feature when I use fossil.
>>
>
> If "cleanliness is godliness" then git might have fossil beat in that
> regard. One of the reasons i always liked StarWars better than Star Trek is
> because in Star Trek everything is so antiseptically _clean_, whereas in
> Star Wars ships have dirt ("carbon scoring") and scratches on them, and the
> lights don't all work (some flicker).
>
> While we're cleaning up, we can go ahead and do:
>
> git branch -D master
> git push origin:master
>
> :-D
>
> --
> - 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 mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Fossil mentioned on HN

[Gaurav M. Bhandarkar]

> The end result is theoretically the equivalent of having started your
branch at the latest trunk tip instead of where ever you really started it


fast forward merges is just one of the advantages of rebase. It is done to
avoid the extra “merge-commit” and thus reduces the noise in repo history.



> If you have changes on a branch you actually care about the change history


But sometimes you don’t really care about some of the change history on
your branch. Let me explain.


What I think is the real power of rebase is the “git rebase -i". This
command helps me use git as a “development session manager”.


E.g. Suppose I’m tasked with writing a small webserver. I update my local
master branch with changes from remote master branch and I create a new
local branch “initial-webserver”.


Now I google samples for webserver like those using the "select" api, those
using epoll etc. etc. I also find some command line tools (binary files)
that can stress the webserver. I just commit them to my local branch
“initial-webserver”.


I then start writing my code, and keep on committing frequently in my local
branch. If my task takes 1 week, my “development session” is saved in the
branch.


When I say “development session” I mean relevant code samples, relevant
articles found on web, temp makefile changes to automatically copy files to
test machine after build, misc. binary files and even huge entire virtual
machine’s snapshot images.


After my job is complete I just delete those binary files, sample codes
etc. and make another commit to local branch “initial-webserver”. Those
files are now deleted from the tip of my local branch but not from the
earlier revisions.


Then I run “git rebase -i master” which gives me an option to “squash”
commits that happened after “where-master-is-currently-at”. I can now
remove those commits that had binary files, code samples etc. from my local
branch’s history while keeping the actual code-changes and their commit
messages. In the end I get a clean revision history ready to be merged in
the master.


I really miss this feature when I use fossil.



On Tue, Dec 15, 2015 at 10:33 PM, Ron W  wrote:

> On Tue, Dec 15, 2015 at 11:04 AM, Warren Young  wrote:
>
>> Could someone who understands “git rebase” weigh in on that thread?
>> People are claiming that “fossil shun” means there is no difference between
>> Git and Fossil.
>>
>> Either my understanding of fossil shun is just as weak as my
>> understanding of git rebase, or this is a false equivalency,
>>
>
> Fossil shun only excludes selected artifacts while git rebase actualy
> rewrites history. Shun requires you find the IDs of the artifacts you
> want/need to exclude. Rebase does the dirty work for you.
>
> In the simple cases I've had to deal with git, the core maintainers of the
> projects involved required that submissions be "fast-forward merge" ready.
> That is, the affected files are up to date with respect to the trunk (aka
> "master") tip.
>
> Since the project maintainers were completely uninterested in my local
> revision history, for me, this amounted to updating my local git, merging
> trunk tip to my branch, build/test/fix/, then finally, merging my
> branch tip to trunk, pushing to my github fork and sending a pull request
> to the maintainers. If their "fast-forward merge" failed, I would have to
> repeat the above process and resubmit my pull request.
>
> If you have changes on a branch you actually care about the change
> history, git rebase can be used to, effectively, transplant your branch
> from whichever truck commit it started from to the trunk tip. This is sort
> of like merging the trunk tip into your branch;s first commit, then into
> each subsequent branch commit. The end result is theoretically the
> equivalent of having started your branch at the latest trunk tip instead of
> where ever you really started it.
>
>
> ___
> 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] Query executes from admin_sql page but not report page

[Gaurav M. Bhandarkar]

Well I ended up using following query. For some reason New report format
page does not work with a sub query.

SELECT
  ticket.tkt_id,
  substr(ticket.tkt_uuid,1,10) AS '#',
  ticket.title,
  ticket.comment As 'description',
  date(ticketchng.tkt_mtime) AS 'last update',
  ticketchng.icomment AS 'progress status',
  ticket.assigned_to,
  ticket.opened_by,
  ticket.status,
  ticket.severity,
  ticket.priority,
  ticket.type
 FROM ticket, ticketchng
 WHERE ticket.tkt_id=ticketchng.tkt_id
 AND ticketchng.icomment IS NOT NULL
 AND ticket.status IS NOT 'Closed'
 GROUP BY ticketchng.tkt_id
 ORDER BY ticketchng.tkt_mtime DESC

-Gaurav

On Mon, Oct 5, 2015 at 10:49 AM, Gaurav M. Bhandarkar <gaurav.a...@gmail.com
> wrote:

> Hi,
> I am trying to have a report that shows me the last comment. Following
> works from http://localhost:8080/admin_sql page
>
> \\\
> >>> SQL start
> ///
> SELECT
>   tkt_id,
>   substr(tkt_uuid,1,10) AS '#',
>   datetime(tkt_mtime) AS 'mtime',
>   type,
>   status,
>   assigned_to,
>   title,
>   severity,
>   priority,
>   resolution,
>   opened_by,
>   (select icomment from (select tkt_id As 'xtkt_id',icomment from
> ticketchng WHERE icomment IS NOT NULL GROUP BY tkt_id) where
> xtkt_id=tkt_id) AS 'lastcomment'
> FROM ticket
> \\\
> >>> SQL end
> ///
>
> But when I put this in a report I get only 1 row of result and the
> following error:
> "SQLITE_ABORT: statement aborts at 24"
>
> Can anybody tell me what I'm doing wrong?
> FYI, platform is windows.
>
> -Gaurav
>
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Query executes from admin_sql page but not report page

[Gaurav M. Bhandarkar]

Hi,
I am trying to have a report that shows me the last comment. Following
works from http://localhost:8080/admin_sql page

\\\
>>> SQL start
///
SELECT
  tkt_id,
  substr(tkt_uuid,1,10) AS '#',
  datetime(tkt_mtime) AS 'mtime',
  type,
  status,
  assigned_to,
  title,
  severity,
  priority,
  resolution,
  opened_by,
  (select icomment from (select tkt_id As 'xtkt_id',icomment from
ticketchng WHERE icomment IS NOT NULL GROUP BY tkt_id) where
xtkt_id=tkt_id) AS 'lastcomment'
FROM ticket
\\\
>>> SQL end
///

But when I put this in a report I get only 1 row of result and the
following error:
"SQLITE_ABORT: statement aborts at 24"

Can anybody tell me what I'm doing wrong?
FYI, platform is windows.

-Gaurav
___
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] Tags and unhide

[Gaurav M. Bhandarkar]

OK. The idea that comment on a version is also a tag is new to me. IMO,
this fossil specific tag definition caused this query. When we say Tags
in context of a SCM, people usually think of a label which wraps around a
specific version of file(s).

I think you guys could just display something like
https://www.fossil-scm.org/fossil/tagtimeline instead of what we are
displaying now for tags.

Thanks for explaining.

-Gaurav

On Thu, Feb 26, 2015 at 12:48 AM, Ron W ronw.m...@gmail.com wrote:

 On Wed, Feb 25, 2015 at 3:37 AM, Gaurav M. Bhandarkar 
 gaurav.a...@gmail.com wrote:

 How is the output lines, eg 16:06 Edit [72114148]: Edit check-in comment.
 (user: drh) [details], related to most recent tags.


 For a check-in (or a ticket), comment is a tag. The comment tag also
 has a value, which is the test of the comment.

 (Beside being symbolic names, tags may also have values.)


 ___
 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] Tags and unhide

[Gaurav M. Bhandarkar]

 Tags are symbolic names that may or may not be propagate
Yes. But what does the page :
https://www.fossil-scm.org/index.html/timeline?n=50y=gv=0
mean by 50 most recent tags ?

How is the output lines, eg 16:06 Edit [72114148]: Edit check-in comment.
(user: drh) [details], related to most recent tags.

Note that I went to the page by selecting tags from timeline, I didn't
manually generate that URL.

Also, what does selecting tags from the drop-down menu means when you are
viewing a branch:
Eg. when you're viewing the timeline of json branch,
https://www.fossil-scm.org/index.html/timeline?n=100r=json
selecting tags from drop-down menu shows: 0 tags related to json

 if a branch is marked as closed, it is (by default) hidden
Oh, I think I understood the significance of unhide. Thanks for explaining.

-Gaurav

On Wed, Feb 25, 2015 at 1:07 AM, bch brad.har...@gmail.com wrote:

 Tags are symbolic names that may or may not be propagate -- a branch
 name is an example of a propagating tag, and a non-propagating tag may
 be (for example) a tag that marks a specific commit as a release
 (see: http://fossil-scm.org/index.html/timeline?r=version-1.30) -- if
 a branch is marked as closed, it is (by default) hidden. The idea is
 that it's closed because we don't generally care about it, and
 therefore to display it is just to clutter the timeline. Of course, as
 is fossils model, no content is actually deleted or modified.

 On 2/24/15, Gaurav M. Bhandarkar gaurav.a...@gmail.com wrote:
  Hi,
  What does selecting Tags in Timeline actually do? I was expecting to
 see
  the list of non-propagating tags but I don't understand how I could use
 the
  output I see.
 
  Also, what does unhide actually do? Why do I need to explicitly click
  unhide to see any output on this page:
  https://www.fossil-scm.org/fossil/timeline?n=100r=mistake
 
  Thanks.
 
  -Gaurav
 
 ___
 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] Tags and unhide

[Gaurav M. Bhandarkar]

Hi,
What does selecting Tags in Timeline actually do? I was expecting to see
the list of non-propagating tags but I don't understand how I could use the
output I see.

Also, what does unhide actually do? Why do I need to explicitly click
unhide to see any output on this page:
https://www.fossil-scm.org/fossil/timeline?n=100r=mistake

Thanks.

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

[fossil-users] move many files

[Gaurav M. Bhandarkar]

Hi,
What is the easiest way to move many files in fossil on windows?

1)
dir

Directory of F:\dev2\fossil-experiment\tinymce

06-Oct-14  15:41DIR  .
06-Oct-14  15:41DIR  ..
06-Oct-14  14:54DIR  javascript
06-Oct-14  14:34DIR  tinymce
06-Oct-14  14:34  2 testfile.txt

2)
fossil changes -v
  (none)

3)
\tinymce has :
 282 File(s)
 341 Dir(s)

4)
I want to move \tinymce to javascript\tinymce. So do I need to write
some kind of script that :
fires fossil ls
filters that output to consider only files inside \tinymce (ie ignore
testfile.txt)
and then fires fossil rename on that output

?

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] Is it possible to add empty folders to the repo?

[Gaurav M. Bhandarkar]

maybe you could use :
fossil settings empty-dirs

A comma or newline-separated list of pathnames. On
update and checkout commands, if no file or directory
exists with that name, an empty directory will be
created.


On Mon, Oct 6, 2014 at 8:07 PM, Baruch Burstein bmburst...@gmail.com
wrote:

 I tried doing:
 mkdir a
 fossil add a

 but that didn't work.

 --
 ˙uʍop-ǝpısdn sı ɹoʇıuoɯ ɹnoʎ 'sıɥʇ pɐǝɹ uɐɔ noʎ ɟı

 ___
 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] new ticket script changes

[Gaurav M. Bhandarkar]

OK. Thanks for pointing those out.

Another question, is TH1 used only for ticketing? or does it generates most
of the web ui too?

On Tue, Sep 30, 2014 at 11:53 PM, Stephan Beal sgb...@googlemail.com
wrote:

 On Tue, Sep 30, 2014 at 8:14 PM, Gaurav M. Bhandarkar 
 gaurav.a...@gmail.com wrote:

 I get following error while creating new ticket :
 ERROR: SQL error: access to table user is restricted
 error code 23: access to user.info is prohibited

 How can I resolve this?


 i can't answer that one, but i suspect that Joe M. will be able to.

 Also where can I find documentation for TH1


 AFAIK the closest thing we have to th1 docs is:

 http://www.sqliteconcepts.org/THManual.pdf

 there's a spin-off of that book here in GDocs:


 https://docs.google.com/document/d/1qBDuO6T4A-KOwZr2WyWTLX9XzWjKZvbiRJYaPaTBE7Y/view

 it's a tiny bit newer but not notably better - i'd start with the PDF
 first.


 Like what is $seenRow? I can only guess it means a row count or something.


 i don't think we have any docs for th1 at this level :/. Not that i'm
 aware of, anyway.

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

Re: [fossil-users] new ticket script changes

[Gaurav M. Bhandarkar]

Well, I attempted it because
http://www.fossil-scm.org/index.html/doc/tip/www/custom_ticket.wiki
suggested it was possible.

it might be good to automatically scoop up the user's email and put it
here


On Wed, Oct 1, 2014 at 12:02 AM, Andreas Kupries andre...@activestate.com
wrote:

 On Tue, Sep 30, 2014 at 11:23 AM, Stephan Beal sgb...@googlemail.com
 wrote:
  On Tue, Sep 30, 2014 at 8:14 PM, Gaurav M. Bhandarkar
  gaurav.a...@gmail.com wrote:
 
  I get following error while creating new ticket :
  ERROR: SQL error: access to table user is restricted
  error code 23: access to user.info is prohibited
 
  How can I resolve this?
 
 
  i can't answer that one, but i suspect that Joe M. will be able to.

 The restriction is coded in fossil as a special sqlite authorizer callback.
 It also ensures that reports can only do SELECTS and not INSERT, UPDATE,
 etc.

 I believe/speculate that access to the user table is restricted to
 prevent accidental (or malicious) exposure of the password hashes for
 the users.

 AFAIK the only way around that is to use direct sqlite3 access to the
 repository to create a table fx_users [1] or some such which is
 partial copy of the users table and will be accessible in reports,
 and other TH1 code.

 Of course, creating such a shadow then creates the need to somehow
 track changes to the users table and copy them over into the shadow.

 [1] While the name in general can be as you like the fx prefix
 ensures that the fossil app will consider it an extension table it has
 to ignore at all times. Not using the fx prefix means that a
 'rebuild' will wipe the shadow table, for example.

 If JoeM has better ideas I will be interested in them as well.


 --
 Andreas Kupries
 Senior Tcl Developer
 Code to Cloud: Smarter, Safer, Faster™
 F: 778.786.1133
 andre...@activestate.com, http://www.activestate.com
 Learn about Stackato for Private PaaS: http://www.activestate.com/stackato

 21'st Tcl/Tk Conference: Nov 10-14, Portland, OR, USA --
 http://www.tcl.tk/community/tcl2014/
 Send mail to tclconfere...@googlegroups.com, by Sep 8
 Registration is open.
 ___
 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] new ticket script changes

[Gaurav M. Bhandarkar]

views did not work when I executed sql from http://localhost:8080/admin_sql

FYI, same error for the http://localhost:8080/tktsetup_com (Edit Ticket
Common Script)
My script was:
...
set assigned_choices {
  unassigned
  Mendelssohn
  another-user
}

query {SELECT login as xlogin from user} {
set assigned_choices $xlogin
}




On Wed, Oct 1, 2014 at 1:02 AM, Andreas Kupries andre...@activestate.com
wrote:

 Now I wonder if wrapping the user table into a VIEW is good enough to
 allow access.
 Likely not, because that would then be a much too easy way of
 circumventing the authorizer.

 On Tue, Sep 30, 2014 at 12:25 PM, Gaurav M. Bhandarkar
 gaurav.a...@gmail.com wrote:
  Well, I attempted it because
  http://www.fossil-scm.org/index.html/doc/tip/www/custom_ticket.wiki
  suggested it was possible.
 
  it might be good to automatically scoop up the user's email and put it
  here
 
 
  On Wed, Oct 1, 2014 at 12:02 AM, Andreas Kupries 
 andre...@activestate.com
  wrote:
 
  On Tue, Sep 30, 2014 at 11:23 AM, Stephan Beal sgb...@googlemail.com
  wrote:
   On Tue, Sep 30, 2014 at 8:14 PM, Gaurav M. Bhandarkar
   gaurav.a...@gmail.com wrote:
  
   I get following error while creating new ticket :
   ERROR: SQL error: access to table user is restricted
   error code 23: access to user.info is prohibited
  
   How can I resolve this?
  
  
   i can't answer that one, but i suspect that Joe M. will be able to.
 
  The restriction is coded in fossil as a special sqlite authorizer
  callback.
  It also ensures that reports can only do SELECTS and not INSERT, UPDATE,
  etc.
 
  I believe/speculate that access to the user table is restricted to
  prevent accidental (or malicious) exposure of the password hashes for
  the users.
 
  AFAIK the only way around that is to use direct sqlite3 access to the
  repository to create a table fx_users [1] or some such which is
  partial copy of the users table and will be accessible in reports,
  and other TH1 code.
 
  Of course, creating such a shadow then creates the need to somehow
  track changes to the users table and copy them over into the shadow.
 
  [1] While the name in general can be as you like the fx prefix
  ensures that the fossil app will consider it an extension table it has
  to ignore at all times. Not using the fx prefix means that a
  'rebuild' will wipe the shadow table, for example.
 
  If JoeM has better ideas I will be interested in them as well.
 
 
  --
  Andreas Kupries
  Senior Tcl Developer
  Code to Cloud: Smarter, Safer, Faster™
  F: 778.786.1133
  andre...@activestate.com, http://www.activestate.com
  Learn about Stackato for Private PaaS:
 http://www.activestate.com/stackato
 
  21'st Tcl/Tk Conference: Nov 10-14, Portland, OR, USA --
  http://www.tcl.tk/community/tcl2014/
  Send mail to tclconfere...@googlegroups.com, by Sep 8
  Registration is open.
  ___
  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
 



 --
 Andreas Kupries
 Senior Tcl Developer
 Code to Cloud: Smarter, Safer, Faster™
 F: 778.786.1133
 andre...@activestate.com, http://www.activestate.com
 Learn about Stackato for Private PaaS: http://www.activestate.com/stackato

 21'st Tcl/Tk Conference: Nov 10-14, Portland, OR, USA --
 http://www.tcl.tk/community/tcl2014/
 Send mail to tclconfere...@googlegroups.com, by Sep 8
 Registration is open.
 ___
 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] case sensitivity fossil all list

[Gaurav M. Bhandarkar]

Platform windows.

Run:
1) fossil open ../fOSSIL/FossilBook.fossil
2) fossil close
3) fossil open ../FOSSIL/FossilBook.fossil
4) fossil close

(note the changed case of 'F' )

5) fossil all list
output of 5th command :

C:/temp/session5/fe/FOSSIL/FossilBook.fossil
C:/temp/session5/fe/fOSSIL/FossilBook.fossil

Even though I have a single repo, fossil reports I have 2.

I think this could cause issues later.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users