On Thu, Sep 9, 2010 at 12:54 PM, Michael Schlenker
wrote:
>
> Am 09.09.2010 um 16:03 schrieb Richard Hipp:
>
>>
>>
>> On Thu, Sep 9, 2010 at 9:48 AM, James Peverill
>> wrote:
>> On 09/09/2010 09:26 AM, fossil-users-requ...@lists.fossil-scm.org wrote:
>> > Fossil never generates a 401 error. The
On 09/09/2010 03:54 PM, fossil-users-requ...@lists.fossil-scm.org wrote:
> 1. Trust a front end webserver like apache and what it sets in the
> REMOTE_USER cgi variable (you could use Kerberos/SPNEGO Auth that way too,
> same principle if you used mod_kerb).
>
This is what we have been doing
On 09/09/2010 03:54 PM, fossil-users-requ...@lists.fossil-scm.org wrote:
> 1. Trust a front end webserver like apache and what it sets in the
> REMOTE_USER cgi variable (you could use Kerberos/SPNEGO Auth that way too,
> same principle if you used mod_kerb).
>
This is what we have been doing
Am 09.09.2010 um 16:03 schrieb Richard Hipp:
>
>
> On Thu, Sep 9, 2010 at 9:48 AM, James Peverill
> wrote:
> On 09/09/2010 09:26 AM, fossil-users-requ...@lists.fossil-scm.org wrote:
> > Fossil never generates a 401 error. The "401 Authorization Required"
> > message is coming from someplace
Hi,
I'm trying to tidy up a build directory after I mistakenly added a
bunch of temp build files. So I did:
699 terms-win> fossil rm build
DELETED build/Debug/terms-win
DELETED build/terms-win.build/Debug/terms-win.build/build-state.dat
DELETED build/terms-win.build/Debug/terms-win.
> I see. Right - "fossil sync" does not have any idea how to do LDAP
> authentication.
>
> I guess LDAP credentials are stored in the browser somehow. But "fossil
> sync" bypasses the browser completely. So I guess it will somehow need
to
> understand some kind of LDAP authentication protocol
On 09/09/2010 10:03 AM, Richard Hipp wrote:
> I see. Right - "fossil sync" does not have any idea how to do LDAP
> authentication.
AFAICT, mod_ldap lets Apache use an LDAP directory for authentication
information instead of a .htpasswd file. So if I'm reading right, fossil
sync wouldn't need to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wow, thanks for the quick feature! At first glance it seems to work.
I'll make some commits later today or this week and report back if
anything should break.
On 09/09/2010 08:59 AM, Richard Hipp wrote:
> On Thu, Sep 9, 2010 at 9:25 AM, Nolan Darilek
On Thu, Sep 9, 2010 at 9:48 AM, James Peverill
wrote:
> On 09/09/2010 09:26 AM, fossil-users-requ...@lists.fossil-scm.org wrote:
> > Fossil never generates a 401 error. The "401 Authorization Required"
> > message is coming from someplace else. Are you sure your webserver is
> > configured corre
On Thu, Sep 9, 2010 at 9:25 AM, Nolan Darilek wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 09/09/2010 07:43 AM, Richard Hipp wrote:
> > It seems that the "is_a_version()" function used to determine if the
> thing
> > you are trying to checkout really is a checkin, works by looki
On 09/09/2010 09:26 AM, fossil-users-requ...@lists.fossil-scm.org wrote:
> Fossil never generates a 401 error. The "401 Authorization Required"
> message is coming from someplace else. Are you sure your webserver is
> configured correctly?
>
Well... it is configured correctly for the browser
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/09/2010 07:43 AM, Richard Hipp wrote:
> It seems that the "is_a_version()" function used to determine if the thing
> you are trying to checkout really is a checkin, works by looking to see if
> the object has ancestors or children. (It used to o
On Thu, Sep 9, 2010 at 8:50 AM, James Peverill
wrote:
>
> I use mod-ldap authentication on our website, coupled with https, for
> all our pages. I am adding a fossil site to our system for a new
> project. Accessing the site with a web browser works great now, but my
> fossil binary doesn't seem
I use mod-ldap authentication on our website, coupled with https, for
all our pages. I am adding a fossil site to our system for a new
project. Accessing the site with a web browser works great now, but my
fossil binary doesn't seem to be able to login. When I try to clone it
connects fine
On Thu, Sep 9, 2010 at 8:33 AM, Nolan Darilek wrote:
>
> Any thoughts on why I can't check out the first, empty commit? I just
> tried on another test repository and it works fine, but in
> http://dev.thewordnerd.info/hermes I'm told that it isn't a commit.
>
It seems that the "is_a_version()" fu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Cool, thanks for the note about rebuild. I had already run that a few
times after shunning and it worked fine, so I'm glad to know that this
is a reliable indicator that integrity is OK.
Any thoughts on why I can't check out the first, empty commit? I
On Thu, Sep 9, 2010 at 6:52 AM, Nolan Darilek wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hello.
>
> Last night I decided to convert one of my larger, unreleased projects to
> Fossil, and to try a soft launch to see how I like it. Only, my
> conversion process was somewhat convolu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello.
Last night I decided to convert one of my larger, unreleased projects to
Fossil, and to try a soft launch to see how I like it. Only, my
conversion process was somewhat convoluted, and I have this fear that
while it looks OK in the web interfac
18 matches
Mail list logo
