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
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 problem
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
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 commi
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 s
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
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:
> >
> >
>
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
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?
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
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
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 "sync
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
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
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
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
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
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
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 wa
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
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
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
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
478
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
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
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
26 matches
Mail list logo
