Re: [fossil-users] How can I determine if a repository has actually changed?
Any changes in configuration will not show-up in timeline. > - Original Message - > From: Leo Razoumov > Sent: 03/22/12 02:54 AM > To: Fossil SCM user's discussion > Subject: Re: [fossil-users] How can I determine if a repository has actually > changed? > > On Wed, Mar 21, 2012 at 17:17, Stephan Beal wrote: > > On Wed, Mar 21, 2012 at 8:40 PM, Ron Aaron wrote: > >> > >> So what I am looking for is a way to take a 'snapshot' of a repo, and > >> determine if the new version of that repo is actually different, even > >> though I may have done multiple "pulls" in between checks. > > > > > > Doesn't the timeline reveal if anything meaningful was changed? Could you > > not query the timeline (e.g. via scripting fossil json timeline...)? > > > > I think this is the winner. I cannot thing of any (non pathologically > esoteric) cases when a repo changes but the > last 20 commits stay the same. > > --Leo-- > ___ > 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] moving repository
I formatted my system and the drive my original repository refers to doesn't exist any more. I can still use subst but following SQL fixed my problem: C:\test> sqlite3 _FOSSIL_ sqlite> UPDATE vvar SET value='new.fsl' WHERE name='repository'; Unfortunately, fossil sqlite3 command also requires the main repository. I guess it is a bug that these commands (sqlite3, test-move-repository) require access to repository. They could (and should) operate independent of it. - Altu - Original Message - > windows, too). Following this line of thinking I could as well just run sqlite3 command-line binary on the checkout fossil database and manually hack the necessary entry in an appropriate table. ___ 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 can I determine if a repository has actually changed?
On Wed, Mar 21, 2012 at 17:17, Stephan Beal wrote: > On Wed, Mar 21, 2012 at 8:40 PM, Ron Aaron wrote: >> >> So what I am looking for is a way to take a 'snapshot' of a repo, and >> determine if the new version of that repo is actually different, even >> though I may have done multiple "pulls" in between checks. > > > Doesn't the timeline reveal if anything meaningful was changed? Could you > not query the timeline (e.g. via scripting fossil json timeline...)? > I think this is the winner. I cannot thing of any (non pathologically esoteric) cases when a repo changes but the last 20 commits stay the same. --Leo-- ___ 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 can I determine if a repository has actually changed?
On Wed, Mar 21, 2012 at 10:17 PM, Stephan Beal wrote: > Doesn't the timeline reveal if anything meaningful was changed? Could you > not query the timeline (e.g. via scripting fossil json timeline...)? > > Or, more simply: ~> echo $(fossil fossil timeline -n 1) | cut -d'[' -f 2 | cut -d']' -f1 47817fefdf (the echo/subshell there is to strip the newlines from the output) That can probably be done more elegantly. -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ 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 can I determine if a repository has actually changed?
On Wed, Mar 21, 2012 at 8:40 PM, Ron Aaron wrote: > So what I am looking for is a way to take a 'snapshot' of a repo, and > determine if the new version of that repo is actually different, even > though I may have done multiple "pulls" in between checks. > Doesn't the timeline reveal if anything meaningful was changed? Could you not query the timeline (e.g. via scripting fossil json timeline...)? -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ 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 can I determine if a repository has actually changed?
On 03/21/2012 09:18 PM, Leo Razoumov wrote: > Poor man's way of figuring it out is to capture the output from fossil > pull (or fossil push) command, parse it and if all numbers of > transfered artifacts and deltas are zero than nothing changed. That will not work in this case, because I do not do the external save all the time. That is to say, that the encrypted off-site files are only updated periodically, while the fossil repos they are made from are updated possibly often. So what I am looking for is a way to take a 'snapshot' of a repo, and determine if the new version of that repo is actually different, even though I may have done multiple "pulls" in between checks. I hope I'm explaning what I want to do sufficiently well... The main reason for these contortions is that I don't want to send a 500M file over my limited bandwidth if I don't need to. ___ 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 can I determine if a repository has actually changed?
On Wed, Mar 21, 2012 at 14:53, Ron Aaron wrote: > On 03/21/2012 08:06 PM, Leo Razoumov wrote: >> True, but does not help if your file is encrypted. You change a single >> byte of your plain-text-file and your encrypted version changes >> entirely. > > Precisely so. And I don't want to encrypt and synch the file, unless it > has changed in a meaningful way (e.g. not just some synch timestamp inside) Poor man's way of figuring it out is to capture the output from fossil pull (or fossil push) command, parse it and if all numbers of transfered artifacts and deltas are zero than nothing changed. --Leo-- ___ 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 can I determine if a repository has actually changed?
On 03/21/2012 08:06 PM, Leo Razoumov wrote: > True, but does not help if your file is encrypted. You change a single > byte of your plain-text-file and your encrypted version changes > entirely. Precisely so. And I don't want to encrypt and synch the file, unless it has changed in a meaningful way (e.g. not just some synch timestamp inside) ___ 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 can I determine if a repository has actually changed?
On Wed, Mar 21, 2012 at 13:25, Stephan Beal wrote: > > i don't know about Ubuntu1, but dropbox synchronizes only the bytes which > changed, so the sync is really fast. There is, however, still a couple > caveats with this approach (sorry for my brevity earlier - i was on my > phone): > True, but does not help if your file is encrypted. You change a single byte of your plain-text-file and your encrypted version changes entirely. --Leo-- ___ 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] merge strategy "ours"
On Wed, Mar 21, 2012 at 12:23, Themba Fletcher
wrote:
> On Tue, 2012-03-20 at 15:04 -0400, Leo Razoumov wrote:
>> On Tue, Mar 20, 2012 at 09:57, Richard Hipp wrote:
>> >
>> > Why not just "fossil revert my/file.txt"?
>> >
>> For each one of dozens of files in the manifest??
>
> Does this do what you want?
>
> fossil merge foo
> fossil changes | head -n -1 | awk '{print $2}' | xargs fossil revert
>
Themba,
thanks for a script. I hope that the files deleted by the merge would
not cause any problems.
--Leo--
>> I tried
>>
>> $ fossil revert
>>
>> and it reverts the contents of all files but at the same time it also removes
>> merge record (clears vmerge table).
>> All I want is to record a new merge parent without merging in file contents.
>>
>> --Leo--
>>
>> >>
>> >> On Tue, Mar 20, 2012 at 14:14, Leo Razoumov wrote:
>> >> > Hi there,
>> >> > GIT has a useful merge strategy "git merge -s ours" that always
>> >> > chooses our current version over the version being merged in. The
>> >> > resulting merge has exactly the same files contents as its base
>> >> > parent. The only difference being that the commit merged in is now
>> >> > added to the list of merge parents.
>> >> >
>> >> > How to achieve the same effect in fossil??
>> >> >
>> >> > For those who wonder why do I need such a thing here is a use case. I
>> >> > tend to commit very often. In order to prevent polluting public
>> >> > branches I work mostly on private branches periodically merging the
>> >> > changes (when they are in good shape) into public branches. When
>> >> > merging private branch into a public one fossil does not record
>> >> > private branch as a merge parent (and for a good reason!). Often I do
>> >> > have a suitable merge parent candidate. How do I trick fossil into
>> >> > just adding a commit into manifest's "P" card to make it a merge
>> >> > parent??
>> >> >
>> >> > --Leo--
>> ___
___
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 can I determine if a repository has actually changed?
On Wed, Mar 21, 2012 at 6:06 PM, Ron Aaron wrote: > Certainly I could, but that means that my fsl files are put there as-is, > and I want them encrypted before putting up there. It also means that > the fsl files will always be synched, even if nothing actually changes, > which is what I want to avoid. > i don't know about Ubuntu1, but dropbox synchronizes only the bytes which changed, so the sync is really fast. There is, however, still a couple caveats with this approach (sorry for my brevity earlier - i was on my phone): - The temp journal files from sqlite3 can sometimes get synced. i "pause" dropbox when i'm actively using a dropboxed repo. i don't remember if U1 has a pause option. - If you use the repo from multiple machines and one or both are intermittently offline, it can lead to file change conflcts. Dropbox keeps both copies, one renamed to something like "filename (hostname2's conflicted copy).fsl". So... it's not an ideal solution, but it works fine for single-developer/single-machine repos. -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ 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 can I determine if a repository has actually changed?
Certainly I could, but that means that my fsl files are put there as-is, and I want them encrypted before putting up there. It also means that the fsl files will always be synched, even if nothing actually changes, which is what I want to avoid. On 03/21/2012 06:32 PM, Stephan Beal wrote: > > You can place the fsl files directly in your ubuntu1 folder (or > dropbox, or whatever) and serve them from there. > ___ 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 can I determine if a repository has actually changed?
You can place the fsl files directly in your ubuntu1 folder (or dropbox, or whatever) and serve them from there. - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal On Mar 21, 2012 5:02 PM, "Ron Aaron" wrote: > I've got a bunch of Fossil repositories which I back up by doing: > > fossil pull > fossil config pull all > > > I am now also encrypting the repos after backing up, and putting the > encrypted files on "Ubuntu One" for off-site failsafe backup. > > The problem I am trying to solve is that I do NOT want to "synchronize" > a repo which has not changed; that is, I do not want to update the > encrypted file in the Ubuntu One sync folder -- since that is wasteful > of my bandwidth for no purpose. > > What I had *hoped* would work, was to do "fossil sha" on the > repositories, and "fossil sha" again after the sync, and only copy files > whose SHA1 sums are different, thus minimizing both my processing time > and the network bandwidth. > > Unfortunately, my current testing shows that doing the "fossil pull; > fossil config pull all" modifies the repository even when I know for > sure that there are no actual changes since the last sync. > > What would you recommend as a method for accomplishing what I am trying > to do? > > Thanks > Ron > ___ > 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] merge strategy "ours"
On Tue, 2012-03-20 at 15:04 -0400, Leo Razoumov wrote:
> On Tue, Mar 20, 2012 at 09:57, Richard Hipp wrote:
> >
> > Why not just "fossil revert my/file.txt"?
> >
>
> For each one of dozens of files in the manifest??
Does this do what you want?
fossil merge foo
fossil changes | head -n -1 | awk '{print $2}' | xargs fossil revert
>
> I tried
>
> $ fossil revert
>
> and it reverts the contents of all files but at the same time it also removes
> merge record (clears vmerge table).
> All I want is to record a new merge parent without merging in file contents.
>
> --Leo--
>
> >>
> >> On Tue, Mar 20, 2012 at 14:14, Leo Razoumov wrote:
> >> > Hi there,
> >> > GIT has a useful merge strategy "git merge -s ours" that always
> >> > chooses our current version over the version being merged in. The
> >> > resulting merge has exactly the same files contents as its base
> >> > parent. The only difference being that the commit merged in is now
> >> > added to the list of merge parents.
> >> >
> >> > How to achieve the same effect in fossil??
> >> >
> >> > For those who wonder why do I need such a thing here is a use case. I
> >> > tend to commit very often. In order to prevent polluting public
> >> > branches I work mostly on private branches periodically merging the
> >> > changes (when they are in good shape) into public branches. When
> >> > merging private branch into a public one fossil does not record
> >> > private branch as a merge parent (and for a good reason!). Often I do
> >> > have a suitable merge parent candidate. How do I trick fossil into
> >> > just adding a commit into manifest's "P" card to make it a merge
> >> > parent??
> >> >
> >> > --Leo--
> ___
> 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] How can I determine if a repository has actually changed?
I've got a bunch of Fossil repositories which I back up by doing: fossil pull fossil config pull all I am now also encrypting the repos after backing up, and putting the encrypted files on "Ubuntu One" for off-site failsafe backup. The problem I am trying to solve is that I do NOT want to "synchronize" a repo which has not changed; that is, I do not want to update the encrypted file in the Ubuntu One sync folder -- since that is wasteful of my bandwidth for no purpose. What I had *hoped* would work, was to do "fossil sha" on the repositories, and "fossil sha" again after the sync, and only copy files whose SHA1 sums are different, thus minimizing both my processing time and the network bandwidth. Unfortunately, my current testing shows that doing the "fossil pull; fossil config pull all" modifies the repository even when I know for sure that there are no actual changes since the last sync. What would you recommend as a method for accomplishing what I am trying to do? Thanks Ron ___ 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] moving repository
On Wed, 21 Mar 2012 10:08:58 -0500 Bill Burdick wrote: [...] > >> > C:\test>fossil test-move-repository c:\test\new.fsl > >> > C:\test\fossil.exe: repository does not exist or is in an > >> > unreadable directory: C:/test/test.fsl > >> > > >> > C:\test>fossil version > >> > This is fossil version 1.22 [5dd5d39e7c] 2012-03-19 12:45:47 UTC > >> Same problem here with 1.21 also on Windows. > >> Not renaming the original repository before running the command > >> complains that the target repository does not exist. > >> So in the end there seems to be no way to actually run this command > >> successfully. > > What about copying the repository, doing a test-move-repository, > > and then removing the original? > Or, you could hard link it, instead of copying it, if the new > location is on the same volume as the old (hard linking works on > windows, too). Following this line of thinking I could as well just run sqlite3 command-line binary on the checkout fossil database and manually hack the necessary entry in an appropriate table. What the OP implied is that that command's implementation probabaly contains a bug and I demonstrated that it indeed seems so. Also see this discussion: http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg06792.html P.S. Please don't top-post. ___ 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] copy configuration from repo to repo?
Maybe this shoud be reported as bug? ST On Wed, 2012-03-21 at 11:05 -0400, Tomek Kott wrote: > I've noticed that myself, so I never to 'fossil config export all'. I > only export 'tickets' or 'skins' usually, so not a big deal. I avoid > every pulling / pushing the users table. > > Tomek > > On Wed, Mar 21, 2012 at 7:20 AM, ST wrote: > On Tue, 2012-03-20 at 08:27 -0400, Richard Hipp wrote: > > > > > > On Tue, Mar 20, 2012 at 6:19 AM, ST > wrote: > > Hi, > > 1) I've just configured my first fossil repo and now > would > > like to copy > > this configuration to other projects. Is it > possible? > > Most problematic part is enabling "assigned_to" and > > "opened_by" in > > tickets as per this: > > > http://fossil-scm.org/index.html/doc/trunk/www/custom_ticket.wiki . > Why > > isn't it actually there out of the box? Or it is > there and I > > just missed > > it? It is a bit painful to go through this process > for all the > > project > > that I have... > > > > On the repo you've already set up: > > > > fossil configuration export all config.txt -R > alreadysetup.fossil > > > > Then on your new repo: > > > > fossil configuration import config.txt -R newrepo.fossil > > > > All the configuration information is transferred through the > filed > > "config.txt" in the example above. That file is pure SQL so > it is > > ASCII text and readable. You can move the file across > systems in > > between the two operations, if you need to. > > > > If you only want to transfer some subset of the > configuration, you can > > replace "all" by "email", "project", "shun", "skin", > "ticket", or > > "user". > > > I tried that but after this I can no longer login neither with > my > password from alreadysetup.fossil nor with the default > password > generated by fossil which was created during repo > initialization. > > Thank you, > ST > > > ___ > 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 mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] moving repository
Or, you could hard link it, instead of copying it, if the new location is on the same volume as the old (hard linking works on windows, too). On Wed, Mar 21, 2012 at 10:07 AM, Bill Burdick wrote: > What about copying the repository, doing a test-move-repository, and then > removing the original? > > > Bill > > > > On Wed, Mar 21, 2012 at 10:03 AM, Konstantin Khomoutov < > flatw...@users.sourceforge.net> wrote: > >> On Wed, 21 Mar 2012 09:30:55 -0400 >> "Altu Faltu" wrote: >> >> > Is following sequence supposed to work for moving repository? >> > >> > C:\test>fossil new test.fsl >> > C:\test>fossil open test.fsl >> > C:\test>ren test.fsl new.fsl >> > C:\test>fossil test-move-repository new.fsl >> > C:\test\fossil.exe: repository does not exist or is in an unreadable >> > directory: C:/test/test.fsl >> > >> > C:\test>fossil test-move-repository c:\test\new.fsl >> > C:\test\fossil.exe: repository does not exist or is in an unreadable >> > directory: C:/test/test.fsl >> > >> > C:\test>fossil version >> > This is fossil version 1.22 [5dd5d39e7c] 2012-03-19 12:45:47 UTC >> Same problem here with 1.21 also on Windows. >> Not renaming the original repository before running the command >> complains that the target repository does not exist. >> So in the end there seems to be no way to actually run this command >> successfully. >> ___ >> 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] moving repository
What about copying the repository, doing a test-move-repository, and then removing the original? Bill On Wed, Mar 21, 2012 at 10:03 AM, Konstantin Khomoutov < flatw...@users.sourceforge.net> wrote: > On Wed, 21 Mar 2012 09:30:55 -0400 > "Altu Faltu" wrote: > > > Is following sequence supposed to work for moving repository? > > > > C:\test>fossil new test.fsl > > C:\test>fossil open test.fsl > > C:\test>ren test.fsl new.fsl > > C:\test>fossil test-move-repository new.fsl > > C:\test\fossil.exe: repository does not exist or is in an unreadable > > directory: C:/test/test.fsl > > > > C:\test>fossil test-move-repository c:\test\new.fsl > > C:\test\fossil.exe: repository does not exist or is in an unreadable > > directory: C:/test/test.fsl > > > > C:\test>fossil version > > This is fossil version 1.22 [5dd5d39e7c] 2012-03-19 12:45:47 UTC > Same problem here with 1.21 also on Windows. > Not renaming the original repository before running the command > complains that the target repository does not exist. > So in the end there seems to be no way to actually run this command > successfully. > ___ > 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] copy configuration from repo to repo?
I've noticed that myself, so I never to 'fossil config export all'. I only export 'tickets' or 'skins' usually, so not a big deal. I avoid every pulling / pushing the users table. Tomek On Wed, Mar 21, 2012 at 7:20 AM, ST wrote: > On Tue, 2012-03-20 at 08:27 -0400, Richard Hipp wrote: > > > > > > On Tue, Mar 20, 2012 at 6:19 AM, ST wrote: > > Hi, > > 1) I've just configured my first fossil repo and now would > > like to copy > > this configuration to other projects. Is it possible? > > Most problematic part is enabling "assigned_to" and > > "opened_by" in > > tickets as per this: > > > http://fossil-scm.org/index.html/doc/trunk/www/custom_ticket.wiki . Why > > isn't it actually there out of the box? Or it is there and I > > just missed > > it? It is a bit painful to go through this process for all the > > project > > that I have... > > > > On the repo you've already set up: > > > > fossil configuration export all config.txt -R alreadysetup.fossil > > > > Then on your new repo: > > > > fossil configuration import config.txt -R newrepo.fossil > > > > All the configuration information is transferred through the filed > > "config.txt" in the example above. That file is pure SQL so it is > > ASCII text and readable. You can move the file across systems in > > between the two operations, if you need to. > > > > If you only want to transfer some subset of the configuration, you can > > replace "all" by "email", "project", "shun", "skin", "ticket", or > > "user". > > I tried that but after this I can no longer login neither with my > password from alreadysetup.fossil nor with the default password > generated by fossil which was created during repo initialization. > > Thank you, > ST > > > ___ > 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] moving repository
On Wed, 21 Mar 2012 09:30:55 -0400 "Altu Faltu" wrote: > Is following sequence supposed to work for moving repository? > > C:\test>fossil new test.fsl > C:\test>fossil open test.fsl > C:\test>ren test.fsl new.fsl > C:\test>fossil test-move-repository new.fsl > C:\test\fossil.exe: repository does not exist or is in an unreadable > directory: C:/test/test.fsl > > C:\test>fossil test-move-repository c:\test\new.fsl > C:\test\fossil.exe: repository does not exist or is in an unreadable > directory: C:/test/test.fsl > > C:\test>fossil version > This is fossil version 1.22 [5dd5d39e7c] 2012-03-19 12:45:47 UTC Same problem here with 1.21 also on Windows. Not renaming the original repository before running the command complains that the target repository does not exist. So in the end there seems to be no way to actually run this command successfully. ___ 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] can a repo be local and global?
On Wed, 21 Mar 2012 16:49:12 +0200 ST wrote: > can a repo be local and global at the same time, i.e. if I want to > provide access to my repo through apache - do I need to have one repo > for apache and one local or can it be one and the same repo? It can: you do this every time you run `fossil server` in an open checkout. `fossil ui` basically does kind of the same: it runs fossil in server mode and spawns a local browser which is then told to connect to the port opened by the serving fossil instance. > If it can be one and the same repo does this mean that I don't need to > make push/pull only commit/update? That is correct. Just be aware of the fact that your local checkout is not automatically updated by "foreign" pushes to the same branch. I mean, if you have, say, a branch "trunk" currently checked out, and it's updated externally you'll have to update your checkout or your next commit will create a fork. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] can a repo be local and global?
Hi, can a repo be local and global at the same time, i.e. if I want to provide access to my repo through apache - do I need to have one repo for apache and one local or can it be one and the same repo? If it can be one and the same repo does this mean that I don't need to make push/pull only commit/update? Thank you, ST ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] moving repository
Is following sequence supposed to work for moving repository? C:\test>fossil new test.fsl C:\test>fossil open test.fsl C:\test>ren test.fsl new.fsl C:\test>fossil test-move-repository new.fsl C:\test\fossil.exe: repository does not exist or is in an unreadable directory: C:/test/test.fsl C:\test>fossil test-move-repository c:\test\new.fsl C:\test\fossil.exe: repository does not exist or is in an unreadable directory: C:/test/test.fsl C:\test>fossil version This is fossil version 1.22 [5dd5d39e7c] 2012-03-19 12:45:47 UTC - Altu ___ 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] copy configuration from repo to repo?
On Tue, 2012-03-20 at 08:27 -0400, Richard Hipp wrote: > > > On Tue, Mar 20, 2012 at 6:19 AM, ST wrote: > Hi, > 1) I've just configured my first fossil repo and now would > like to copy > this configuration to other projects. Is it possible? > Most problematic part is enabling "assigned_to" and > "opened_by" in > tickets as per this: > http://fossil-scm.org/index.html/doc/trunk/www/custom_ticket.wiki . > Why > isn't it actually there out of the box? Or it is there and I > just missed > it? It is a bit painful to go through this process for all the > project > that I have... > > On the repo you've already set up: > > fossil configuration export all config.txt -R alreadysetup.fossil > > Then on your new repo: > > fossil configuration import config.txt -R newrepo.fossil > > All the configuration information is transferred through the filed > "config.txt" in the example above. That file is pure SQL so it is > ASCII text and readable. You can move the file across systems in > between the two operations, if you need to. > > If you only want to transfer some subset of the configuration, you can > replace "all" by "email", "project", "shun", "skin", "ticket", or > "user". I tried that but after this I can no longer login neither with my password from alreadysetup.fossil nor with the default password generated by fossil which was created during repo initialization. Thank you, ST ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Database error: database is locked
Hi, I started to play with fossil and here is my first problem: 1) I created a repo, made it available as cgi script through apache, a friend of mine made a commit to it and now I try to "fossil pull" but here is what I get (regardless whether apache runs or not; btw. I can see his commit through the web interface): Server:file:///home/user/Repositories/test.fossil Bytes Cards Artifacts Deltas Sent: 146 2 0 0 Error: Database error: database is locked COMMIT Received: 53 1 0 0 Total network traffic: 283 bytes sent, 255 bytes received What's wrong? Maybe I'm missing some permissions (but web interface does work)? Is it related to: http://fossil-scm.org/index.html/tktview?name=8f8083f230 ? Anyway I tried "fossil sql" and here is what I get: SQLite header and source version mismatch 2012-01-16 13:28:40 ebd01a8deffb5024a5d7494eef800d2366d97204 2011-11-14 02:53:54 54cc11981127b52145e39f551d958580b1d45169 I use version 1.21 from Debian Wheezy. 2) Three ideas for future features (please tell me whether you will consider implementing them): a) alias for urls: possibility to provide an alias for url of each page so that it looks cleaner. For example for the page ( http://fossil-scm.org/index.html/doc/trunk/www/custom_ticket.wiki ) alias could be "custom_ticket", so that the url will look like: http://fossil-scm.org/custom_ticket b) a page with a simple contact form (optionaly with captcha and attachments) that will send the message to a predifined email according to topic selected by sender. c) SSL support for "fossil server". Thank you, ST ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
