Thanks. The rebuild helped.
My 2 observations :
- Need to clean up the files manually as well
- Purging happens only in local clone copy and never syncs back.
Need to copy back the clone to central repo
Thanks.
-----Original Message-----
From: fossil-users [mailto:[email protected]] On Behalf
Of [email protected]
Sent: Tuesday, February 27, 2018 9:45 AM
To: [email protected]
Subject: fossil-users Digest, Vol 121, Issue 26
Send fossil-users mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific than "Re:
Contents of fossil-users digest..."
Today's Topics:
1. Re: Setting up an internet Fossil server (Warren Young)
2. Re: Setting up an internet Fossil server (Roy Keene)
3. Re: Setting up an internet Fossil server (Warren Young)
4. Fossil purge Command (Agrawal, Ritika)
5. Re: Setting up an internet Fossil server (Roy Keene)
6. Re: Fossil purge Command (Richard Hipp)
----------------------------------------------------------------------
Message: 1
Date: Tue, 27 Feb 2018 08:32:42 -0700
From: Warren Young <[email protected]>
To: Fossil SCM user's discussion <[email protected]>
Subject: Re: [fossil-users] Setting up an internet Fossil server
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
On Feb 26, 2018, at 3:33 PM, Thomas Levine <[email protected]> wrote:
>
> Since it seems that the only dynamic stuff is in PHP and fossil, I
> suggest using Apache mod_php and mod_cgi (contrary to Warren's
> suggestion), as I think the configuration will be easier.
Of course, but then you lose HTTPS, which is the only reason my configuration
is difficult at all. If all you wanted is reverse proxying, you’d do away with
steps 1-6, simplifying the HOWTO considerably.
I don’t view TLS as optional for password-protected public web resources in
these post-Firesheep days.
Even if you don’t care about your own Fossil repo’s security, Google has been
punishing sites that are not available via HTTPS for a couple of years now,
both through reduced rankings in the search engine and through increasingly
strident warnings in Chrome.
That’s not speculation, Google’s been announcing these things publicly:
https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html
https://developers.google.com/web/updates/2016/10/avoid-not-secure-warn
There may come a day when going to an HTTP-only web site will require multiple
affirmations asymptotically approaching “Yes, I’m really quite certain I want
my face eaten by a rabid grue. Just let me look at this one web site first,
please.”
------------------------------
Message: 2
Date: Tue, 27 Feb 2018 09:37:10 -0600 (CST)
From: Roy Keene <[email protected]>
To: "Fossil SCM user's discussion" <[email protected]>
Subject: Re: [fossil-users] Setting up an internet Fossil server
Message-ID: <[email protected]>
Content-Type: text/plain; charset=US-ASCII; format=flowed
You don't lose support for TLS, since Apache supports TLS. It's just running
Fossil as a CGI -- this is exactly how ChiselApp works.
On Tue, 27 Feb 2018, Warren Young wrote:
> On Feb 26, 2018, at 3:33 PM, Thomas Levine <[email protected]> wrote:
>>
>> Since it seems that the only dynamic stuff is in PHP and fossil, I
>> suggest using Apache mod_php and mod_cgi (contrary to Warren's
>> suggestion), as I think the configuration will be easier.
>
> Of course, but then you lose HTTPS, which is the only reason my configuration
> is difficult at all. If all you wanted is reverse proxying, you?d do away
> with steps 1-6, simplifying the HOWTO considerably.
>
> I don?t view TLS as optional for password-protected public web resources in
> these post-Firesheep days.
>
> Even if you don?t care about your own Fossil repo?s security, Google has been
> punishing sites that are not available via HTTPS for a couple of years now,
> both through reduced rankings in the search engine and through increasingly
> strident warnings in Chrome.
>
> That?s not speculation, Google?s been announcing these things publicly:
>
> https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html
>
> https://developers.google.com/web/updates/2016/10/avoid-not-secure-war
> n
>
> There may come a day when going to an HTTP-only web site will require
> multiple affirmations asymptotically approaching ?Yes, I?m really quite
> certain I want my face eaten by a rabid grue. Just let me look at this one
> web site first, please.?
> _______________________________________________
> fossil-users mailing list
> [email protected]
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
------------------------------
Message: 3
Date: Tue, 27 Feb 2018 08:44:47 -0700
From: Warren Young <[email protected]>
To: Fossil SCM user's discussion <[email protected]>
Subject: Re: [fossil-users] Setting up an internet Fossil server
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
On Feb 27, 2018, at 8:37 AM, Roy Keene <[email protected]> wrote:
>
> You don't lose support for TLS, since Apache supports TLS. It's just running
> Fossil as a CGI -- this is exactly how ChiselApp works.
Compare Thomas’ post to the HOWTO I linked in my first post in this thread.
The largest part of the difference between them is that my HOWTO gives you a
Let’s Encrypt setup as well as a Fossil server. Since Thomas doesn’t describe
how to configure TLS on Apache, I’d say that it’s fair to say that’s one big
reason why Thomas’ configuration is simpler than mine.
A much smaller part of the delta is plain old CGI vs “fossil server --scgi”,
which I think is well worth the minor complexity to avoid the CPU and disk hits
of repeated Fossil launches.
------------------------------
Message: 4
Date: Tue, 27 Feb 2018 15:56:16 +0000
From: "Agrawal, Ritika" <[email protected]>
To: "[email protected]"
<[email protected]>
Subject: [fossil-users] Fossil purge Command
Message-ID:
<d1b5b600ee5bf04ea33dd0a5e61a204c38f7b...@fmsmsx103.amr.corp.intel.com>
Content-Type: text/plain; charset="utf-8"
Hi,
I am trying to use the purge command available with fossil 2.5 release.
Steps performed :
1. fossil purge files <dir to be purged> 2. fossil purge list 3. fossil purge
obliterate <artifact id>
After obliteration, the size of the repo remains the same. After trying to
commit the changes to the repo, I see the error :
working checkout does not match manifest after commit:
e60149b4a3df3f1328936051f4cc5f80 versus 0734caf2221c1050ab1cf07cf8616043
Both these ids are neither current checkout id nor parent id. Any ideas?
Thanks,
Ritika
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.fossil-scm.org:8080/pipermail/fossil-users/attachments/20180227/b46a39f5/attachment-0001.html>
------------------------------
Message: 5
Date: Tue, 27 Feb 2018 09:59:28 -0600 (CST)
From: Roy Keene <[email protected]>
To: "Fossil SCM user's discussion" <[email protected]>
Subject: Re: [fossil-users] Setting up an internet Fossil server
Message-ID: <[email protected]>
Content-Type: text/plain; charset=US-ASCII; format=flowed
ChiselApp also uses Let's Encrypt
On Tue, 27 Feb 2018, Warren Young wrote:
> On Feb 27, 2018, at 8:37 AM, Roy Keene <[email protected]> wrote:
>>
>> You don't lose support for TLS, since Apache supports TLS. It's just
>> running Fossil as a CGI -- this is exactly how ChiselApp works.
>
> Compare Thomas? post to the HOWTO I linked in my first post in this thread.
> The largest part of the difference between them is that my HOWTO gives you a
> Let?s Encrypt setup as well as a Fossil server. Since Thomas doesn?t
> describe how to configure TLS on Apache, I?d say that it?s fair to say that?s
> one big reason why Thomas? configuration is simpler than mine.
>
> A much smaller part of the delta is plain old CGI vs ?fossil server --scgi?,
> which I think is well worth the minor complexity to avoid the CPU and disk
> hits of repeated Fossil launches.
> _______________________________________________
> fossil-users mailing list
> [email protected]
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
------------------------------
Message: 6
Date: Tue, 27 Feb 2018 11:44:42 -0500
From: Richard Hipp <[email protected]>
To: "Fossil SCM user's discussion" <[email protected]>
Subject: Re: [fossil-users] Fossil purge Command
Message-ID:
<CALwJ=mzuk2nfmwheys4e0j3g-ejhxfyxvdtfpb30xi94xey...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
On 2/27/18, Agrawal, Ritika <[email protected]> wrote:
> Hi,
>
> I am trying to use the purge command available with fossil 2.5 release.
>
> Steps performed :
> 1. fossil purge files <dir to be purged> 2. fossil purge list 3.
> fossil purge obliterate <artifact id>
>
> After obliteration, the size of the repo remains the same.
You probably need to run VACUUM on the database.
fossil sql VACUUM
Or you can vacuum as part of a rebuild:
fossil rebuild --vacuum
> After trying to
> commit the changes to the repo, I see the error :
>
> working checkout does not match manifest after commit:
> e60149b4a3df3f1328936051f4cc5f80 versus
> 0734caf2221c1050ab1cf07cf8616043
>
Background information:
https://www.fossil-scm.org/fossil/doc/trunk/www/selfcheck.wiki
Those are MD5 checksums over the entire content of the check-in as it exists on
disk versus what Fossil is trying to push into the repository. Something has
gone wrong so that the two do not agree, hence Fossil rolls back the check-in
to avoid problems.
--
D. Richard Hipp
[email protected]
------------------------------
Subject: Digest Footer
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
------------------------------
End of fossil-users Digest, Vol 121, Issue 26
*********************************************
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
