On Wed, Feb 13, 2013 at 08:32:35PM +, Philip Martin wrote:
> Stefan Sperling writes:
>
> > It is possible that authz rules prohibit access to the path affected
> > by the revision. In which case svnsync would silently omit that path.
>
> $ svn log -vqr129027 svn://svn.zope.org/repos/main/
>
Stefan Sperling writes:
> It is possible that authz rules prohibit access to the path affected
> by the revision. In which case svnsync would silently omit that path.
$ svn log -vqr129027 svn://svn.zope.org/repos/main/
r129
On Wed, Feb 13, 2013 at 09:19:13PM +0200, Marius Gedminas wrote:
> But then I ran svnsync again and it gave me broken revisions again:
>
> $ svnsync sync file:///$PWD/zope-mirror
> $ svnlook author -r 129030 zope-mirror/ | wc -c
> 1
>
> And then I noticed that r129027 also became broken in
On Tue, Feb 12, 2013 at 06:54:14PM +0100, Stefan Sperling wrote:
> On Tue, Feb 12, 2013 at 05:18:01PM +0200, Marius Gedminas wrote:
> > Anyway, this takes care of prevention. What about recovery? Can I fix
> > the three missing revisions manually somehow?
>
> If you can obtain the original revis
On 02/13/2013 03:04 AM, Thomas Hemmer wrote:
> Have a look at
> http://svnbook.red-bean.com/en/1.7/svn.serverconfig.pathbasedauthz.html.
>
> If you are in need of a conditional commit access control mechanism, you
> should consider using a start-commit hook - see
> http://svnbook.red-bean.com/en/1
> -Ursprüngliche Nachricht-
> Von: Mark Phippard [mailto:markp...@gmail.com]
> Gesendet: Freitag, 8. Februar 2013 18:34
> An: Michael Zender
> Cc: users@subversion.apache.org
> Betreff: Re: Could not read chunk size: connection was closed by
> server on Windows 7
>
> On Fri, Feb 8, 2013 at
On 13.02.2013 10:30, Schmidt, Michael wrote:
>
> Hello,
>
>
>
> In my research institute we are using SVN with path based access
> control via mod_svn_authz. Now I am facing the problem that we had
> some code within our trunk folder which is only accessible to a
> subgroup of developers. In orde
Am Mittwoch, 13. Februar 2013, 12:34:37 schrieb Stefan Sperling:
> On Wed, Feb 13, 2013 at 11:45:34AM +0100, Hans Meine wrote:
> > I am seeing some strange behavior I cannot explain at all, but I am not
> > sure whether it is a bug or some strange state of my working copy which I
> > do not know ho
On Wed, Feb 13, 2013 at 11:45:34AM +0100, Hans Meine wrote:
> Hi,
>
> I am seeing some strange behavior I cannot explain at all, but I am not sure
> whether it is a bug or some strange state of my working copy which I do not
> know how to inspect yet.
>
> After some "svn switch"ing, there is a
Am Mittwoch, 13. Februar 2013, 11:45:34 schrieb Hans Meine:
> After some "svn switch"ing, there is a directory missing from my working
> copy now, but svn status says I am clean, and svn revert does not bring it
> back. "svn st" displays nothing, "svn revert --depth=infinity ." does
> nothing, but
Hi,
I am seeing some strange behavior I cannot explain at all, but I am not sure
whether it is a bug or some strange state of my working copy which I do not
know how to inspect yet.
After some "svn switch"ing, there is a directory missing from my working copy
now, but svn status says I am clea
Hello,
In my research institute we are using SVN with path based access control via
mod_svn_authz. Now I am facing the problem that we had some code within our
trunk folder which is only accessible to a subgroup of developers. In order to
protect it from unauthorized access we added an access r
Have a look at
http://svnbook.red-bean.com/en/1.7/svn.serverconfig.pathbasedauthz.html.
If you are in need of a conditional commit access control mechanism, you
should consider using a start-commit hook - see
http://svnbook.red-bean.com/en/1.7/svn.ref.reposhooks.start-commit.html for
details.
Be
13 matches
Mail list logo
