svn and svnadmin builds directories with the sticky bit set. This makes
the repository and working copies partialy unusable.
The real problem is a bug in the apr version from apache 2.0.50
according to Ben Colins-Sussman.
On Sun, Aug 15, 2004 at 06:48:37PM +0200, Bastian Blank wrote:
svn and svnadmin builds directories with the sticky bit set. This makesWould you please provide a reference?
the repository and working copies partialy unusable.
Also, shouldn't this be
assigned to libapr0?
On Sun, Aug 15, 2004 at 10:43:55AM -0700, Matt Kraai wrote:
On Sun, Aug 15, 2004 at 06:48:37PM +0200, Bastian Blank wrote:
svn and svnadmin builds directories with the sticky bit set. This makes the repository and working copies partialy unusable.Would you please provide a reference?
http://www.contactor.se/~dast/svn/archive-2004-08/0340.shtml
Also, shouldn't this be
assigned to libapr0?
Feel free, but please make it RC, it breaks the working copies.
I don't think it's an RC bug in libapr0;
it may be one in
Subversion. Do you know if it breaks all (or most) working
copies?
It looks like upstream plans to use a workaround forThanks for the backport in advance; even if I think a bug should be
1.1.0, so I'll try to backport their fix (as well as assigning a
clone of this bug to libapr0).
I don't think it's an RC bug in libapr0; it may be one inI think it is a libapr0 bug. Anyway, please note that apache2 2.0.50-9
Subversion.
* Matt Kraai <[email protected]> [2004-08-15 14:53:09 -0700]:
It looks like upstream plans to use a workaround forThanks for the backport in advance; even if I think a bug should be
1.1.0, so I'll try to backport their fix (as well as assigning a
clone of this bug to libapr0).
fixed where it occurs, and not workaround in other apps. When you go to release a new package version, please update the apache2 dependency to 2.0.50-9, see below for reason.
I don't think it's an RC bug in libapr0; it may be one inI think it is a libapr0 bug.
Subversion.
On Sun, Aug 15, 2004 at 02:53:09PM -0700, Matt Kraai wrote:
I don't think it's an RC bug in libapr0;
I think it is one, as the apache people pulled in a broken version of
apr. I don't know if there are further things which uses apr and break
on the same thing.
it may be one in
Subversion. Do you know if it breaks all (or most) working
copies?
It is not possible to use them in a multiuser environment.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 715 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 44:17:40 |
| Calls: | 12,111 |
| Calls today: | 2 |
| Files: | 15,010 |
| Messages: | 6,518,458 |