On Sat, Jul 11, 2020 at 8:26 PM sebb <seb...@gmail.com> wrote: > > On Sat, 11 Jul 2020 at 20:57, Craig Russell <apache....@gmail.com> wrote: > > > > Testing the (move to emeritus) and (move to active) with the one emeritus > > request we have: > > > > Move to emeritus: No errors reported. The file was not moved from > > emeritus-requests-received to emeritus. The entry in members.txt was moved > > to the wrong place. The active member count was not adjusted. > > > > Move to active: No errors reported. The entry in members.txt was moved to > > the wrong place. The active member count was not adjusted. > > I think the latest code is better. > AFAICT it is now working. > > However there is an issue in testing, in that SVN is only updated > every 10 minutes, so the workspace won't show the updated files > immediately.
Almost, but not quite, a year ago, you asked this question: https://lists.apache.org/thread.html/64cfda89066f658480f0997517555609ca06649d6971808bfba01c61%40%3Cusers.infra.apache.org%3E A little over two months ago I mentioned that there was progress: "The infrastructure team has already enabled pubsub for LDAP data, and is working on pubsub for private svn repositories. " https://lists.apache.org/thread.html/r5a9b6b61a9b4300d9e40003c58f9e87ac34cbe8dada7eaf2f3b02fbd%40%3Cdev.whimsical.apache.org%3E Search #whimsy in slack for "pubsub" in April of this year for more status. We have an existing cron job using pubsub to watch for changes in the whimsy source code and, when a change occurs, initiates a puppet run. These updates complement but don't replace the running of puppet by the infrastructure team. In the (possibly near) future, we could have different cron job using pubsub to watch for changes in svn repositories, match changes against repository.yml, and if found do a full or partial "rake svn:update". These updates could complement but not replace the running of svn update every 10 minutes. If this were done, a number of mail subscriptions could be retired. I suggest two separate cron jobs as these two tasks would need to run under separate user ids. - Sam Ruby > Sebb > > Back to drawing cartoons. > > > > Craig > > > > > On Jul 11, 2020, at 12:11 PM, Craig Russell <apache....@gmail.com> wrote: > > > > > > Hi Sebb, > > > > > > Does this mean that multiUpdate will now work with multiple directory > > > roots, or is there still an update needed for svnmucc in svn.rb? > > > > > > Thanks, > > > Craig > > > > > >> On Jul 11, 2020, at 6:59 AM, sebb <seb...@gmail.com> wrote: > > >> > > >> On Sat, 11 Jul 2020 at 08:56, Greg Stein <gst...@gmail.com> wrote: > > >>> > > >>> On 2020/07/10 15:05:05, sebb <seb...@gmail.com> wrote: > > >>>> ... > > >>>> Of course this will only be needed if the permission issue is not > > >>>> sorted. > > >>> > > >>> With the help of Humbedooh, I believe we have sorted out the > > >>> permissions. I > > >>> was able to do this via svnmucc, but that was because of elevated > > >>> permissions. A Member with access to the pair of directories could not > > >>> (due > > >>> to limited access to the root dir). Changing the permissions was easier > > >>> than changing the httpd configuration to force authn (lack of, appeared > > >>> to > > >>> be a root cause). > > >>> > > >>> I've added a new block to the authz template, and perms for the > > >>> secretary > > >>> group. It is loaded on the svn server now. Please give it a shot. > > >> > > >> A dual svnmucc put worked for me. > > >> > > >>> Cheers, > > >>> Greg > > >>> InfraAdmin, ASF > > > > > > Craig L Russell > > > c...@apache.org > > > > > > > Craig L Russell > > c...@apache.org > >
