Odd...

I just upgraded pound-1.8.2 to pound-1.9.4-1 on a Debian 3.1 serving up 
subversion repository.

I verified that pound.cfg (unmodified)  still contains these 2 entries:

ExtendedHTTP    1
WebDAV          1

After restarting pound, I get PROFIND 501 Not Implemented errors when I 
try to access the repository.

I installed pound-1.9.4-1 using apt-get (did not compile from source).

FX wrote:

> Odd...
>
> I just upgraded pound-1.8.2 to pound-1.9.4-1 on a Debian 3.1 serving 
> up subversion repository.
>
> I verified that pound.cfg (unmodified)  still contains these 2 entries:
>
> ExtendedHTTP    1
> WebDAV          1
>
> After restarting pound, I get PROFIND 501 Not Implemented errors when 
> I try to access the repository.
>
> I installed pound-1.9.4-1 using apt-get (did not compile from source).
>
>
Well, turns out the prior version was compiled from source with 
--enable-msdav added.

To fix, just use dpkg-source and then dpkg-buildpackage after modifying 
./debian/rules in the unpacked directory.

And you used the -MSDAV configure option, right? Because you need that for
WebDAV with Subersion...

-marc

-----Original Message-----
From: FX [mailto:gentoo(at)sbcglobal.net] 
Sent: Tuesday, November 01, 2005 8:28 PM
To: pound(at)apsis.ch
Subject: [Pound Mailing List] PROPFIND 501 Not Implemented - after upgrading
from 1.8.2 to 1.9.4

Odd...

I just upgraded pound-1.8.2 to pound-1.9.4-1 on a Debian 3.1 serving up 
subversion repository.

I verified that pound.cfg (unmodified)  still contains these 2 entries:

ExtendedHTTP    1
WebDAV          1

After restarting pound, I get PROFIND 501 Not Implemented errors when I 
try to access the repository.

I installed pound-1.9.4-1 using apt-get (did not compile from source).


-- 
To unsubscribe send an email with subject 'unsubscribe' to pound(at)apsis.ch.
Please contact roseg(at)apsis.ch for questions.
http://192.168.1.2:8080/Apsis/pound/pound_list/manage_mailboxer

This email may contain privileged information, and is intended only for the
named
recipient and may be privileged. Distribution, disclosure or copying of this
email
by anyone other than the named recipient is prohibited. If you are not the
named
recipient, please notify us immediately, by return email, and permanently
destroy
this email and all copies of it. Internet email is not private, secure, or
reliable.
Neither Rockwater Capital Corporation, its affiliates nor employees or
contractors
are liable for any errors or omissions in the content or transmission of this
email.
Any opinions contained in this email are solely those of the author and, unless
clearly indicated otherwise in writing are not endorsed by Rockwater Capital
Corporation or its affiliates.

> > I just upgraded pound-1.8.2 to pound-1.9.4-1 on a Debian 3.1 serving
> > up subversion repository.
> >
> > I verified that pound.cfg (unmodified)  still contains these 2 entries:
> >
> > ExtendedHTTP    1
> > WebDAV          1
> >
> > After restarting pound, I get PROFIND 501 Not Implemented errors when
> > I try to access the repository.
> >
> > I installed pound-1.9.4-1 using apt-get (did not compile from source).
> >
> Well, turns out the prior version was compiled from source with
> --enable-msdav added.

I don't recall this ever having been the case for the Debian package
(see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=242066), but it
would be easy enough to verify - it's public information :)

Here were my comments on the issue back in August:

#242066: please enable DAV support
Apparently one also needs a config setting, but to be sure I trawled
through the code and found that the list of characters matched in
regular expressions is more lenient with this option enabled, even
when the config file setting is disabled. The functionality seems
useful enough to be included in pound proper (eg for subversion
support), even if without the extra characters. Ideally they would be
separate runtime options. This would no doubt require an amount of
work upstream though.

> To fix, just use dpkg-source and then dpkg-buildpackage after modifying
> ./debian/rules in the unpacked directory.

I would like to support subversion by default. My understanding of the
situation is this:

 - we enforce RFC compliance. this is good and i agree with it.
 - subversion should be RFC compliant - is it?
 - MSDAV is not RFC compliant and needs workarounds which have to be
enabled at compile time
 - currently subversion and msdav are bundled together under the same
compile time and config directives and as such I can't make a
subversion friendly package without also introducing potential
security issues associated with allowing MSDAV.

Please let me know if these assumptions are accurate,

Sam

There is a typo in my last post which points at the wrong bug. Please
reply to this post (cc 242066), NOT the last (cc 242866).

thanks

 - samj

On 11/2/05, Sam Johnston <samjie(at)gmail.com> wrote:
> > > I just upgraded pound-1.8.2 to pound-1.9.4-1 on a Debian 3.1 serving
> > > up subversion repository.
> > >
> > > I verified that pound.cfg (unmodified)  still contains these 2 entries:
> > >
> > > ExtendedHTTP    1
> > > WebDAV          1
> > >
> > > After restarting pound, I get PROFIND 501 Not Implemented errors when
> > > I try to access the repository.
> > >
> > > I installed pound-1.9.4-1 using apt-get (did not compile from source).
> > >
> > Well, turns out the prior version was compiled from source with
> > --enable-msdav added.
>
> I don't recall this ever having been the case for the Debian package
> (see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=242066), but it
> would be easy enough to verify - it's public information :)
>
> Here were my comments on the issue back in August:
>
> #242066: please enable DAV support
> Apparently one also needs a config setting, but to be sure I trawled
> through the code and found that the list of characters matched in
> regular expressions is more lenient with this option enabled, even
> when the config file setting is disabled. The functionality seems
> useful enough to be included in pound proper (eg for subversion
> support), even if without the extra characters. Ideally they would be
> separate runtime options. This would no doubt require an amount of
> work upstream though.
>
> > To fix, just use dpkg-source and then dpkg-buildpackage after modifying
> > ./debian/rules in the unpacked directory.
>
> I would like to support subversion by default. My understanding of the
> situation is this:
>
>  - we enforce RFC compliance. this is good and i agree with it.
>  - subversion should be RFC compliant - is it?
>  - MSDAV is not RFC compliant and needs workarounds which have to be
> enabled at compile time
>  - currently subversion and msdav are bundled together under the same
> compile time and config directives and as such I can't make a
> subversion friendly package without also introducing potential
> security issues associated with allowing MSDAV.
>
> Please let me know if these assumptions are accurate,
>
> Sam
>

Sam Johnston wrote:

>I don't recall this ever having been the case for the Debian package
>(see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=242066), but it
>would be easy enough to verify - it's public information :)
>
>Here were my comments on the issue back in August:
>
>#242066: please enable DAV support
>Apparently one also needs a config setting, but to be sure I trawled
>through the code and found that the list of characters matched in
>regular expressions is more lenient with this option enabled, even
>when the config file setting is disabled. The functionality seems
>useful enough to be included in pound proper (eg for subversion
>support), even if without the extra characters. Ideally they would be
>separate runtime options. This would no doubt require an amount of
>work upstream though.
>
>  
>
>>To fix, just use dpkg-source and then dpkg-buildpackage after modifying
>>./debian/rules in the unpacked directory.
>>    
>>
>
>I would like to support subversion by default. My understanding of the
>situation is this:
>
> - we enforce RFC compliance. this is good and i agree with it.
> - subversion should be RFC compliant - is it?
> - MSDAV is not RFC compliant and needs workarounds which have to be
>enabled at compile time
> - currently subversion and msdav are bundled together under the same
>compile time and config directives and as such I can't make a
>subversion friendly package without also introducing potential
>security issues associated with allowing MSDAV.
>
>Please let me know if these assumptions are accurate,
>
>Sam
>
>  
>

Sam,

I agree with you for the reasons you list.  And the effort involved for 
users to modify debian/rules and dpkg-buildpackage is minimal.

Speaking of Debian packages, will pound 2.0 go into pound or pound2 when 
released?

> I agree with you for the reasons you list.  And the effort involved for
> users to modify debian/rules and dpkg-buildpackage is minimal.

Ok, so we'll leave it as it - svn users are likely to be the clueful minority.

> Speaking of Debian packages, will pound 2.0 go into pound or pound2 when
> released?

According to popcon there aren't a whole swarm of pound users. 1.8.2
will be supported in stable for some time so the question is do I just
migrate to 2.0b1 now? I'm happy enough to do that - it should be
stable by release and it means more eyeballs...

 - samj