Re: SVN problem

On Wed, Aug 14, 2019 at 8:37 AM Andrea Pescetti wrote: > On 13/08/2019 Kay Schenk wrote: > > The page name from the current project website repository is -- > > source_new.mdtext as you probably saw. > > There is no need to be shy here... we have version control and we can > just update source.md

Re: SVN problem

On 13/08/2019 Kay Schenk wrote: The page name from the current project website repository is -- source_new.mdtext as you probably saw. There is no need to be shy here... we have version control and we can just update source.mdtext. I've moved your source_new.mdtext to be the new version of so

Re: SVN problem

Hi Kay, Am 13.08.19 um 22:56 schrieb Kay Schenk: > Hi Matthias -- > The page name from the current project website repository is -- > source_new.mdtext > as you probably saw. > I really know VERY little about git but I will try to do some editing and > hope others will do a lot more. ☺ Yes, let's

Re: SVN problem

Hi Matthias -- The page name from the current project website repository is -- source_new.mdtext as you probably saw. I really know VERY little about git but I will try to do some editing and hope others will do a lot more. ☺ -- Kay On Tue, Aug 13, 2019 at 1:25 PM Matthias Seidel wrote: > Thank

Re: SVN problem

Thanks Kay, I already got notified via commits@ ;-) Do you plan to publish that page later? It is indeed one, that needs to be updated due to the Git switch. Regards,    Matthias Am 13.08.19 um 21:43 schrieb Kay Schenk: > As an FYI, I was able to add and commit a new page to the project web si

Re: SVN problem

As an FYI, I was able to add and commit a new page to the project web site -- https://openoffice.apache.org/ to verify that svn is still OK there also. On Tue, Aug 13, 2019 at 2:48 AM Matthias Seidel wrote: > Hi all, > > Totally forgot to say that I was able to commit to that directory early

Re: SVN problem

Hi all, Totally forgot to say that I was able to commit to that directory early this morning. I have not checked other directories yet. Thank you Peter for the talk on Slack #asfinfra. (We really should use this more for quick communication) Regards,    Matthias Am 13.08.19 um 00:37 schrieb M

Re: SVN problem

Am 13.08.19 um 00:28 schrieb Peter Kovacs: Infra Chat Log from on slack ( for documentation reasons): petko 23:44 Uhr Hello, is SVN path https://svn.apache.org/repos/asf/openoffice/updates-site/trunk/ readonly? (edited) warwalrux 23:54 Uhr I believe it's readonly to all but members of the openo

Re: SVN problem

Infra Chat Log from on slack ( for documentation reasons): petko 23:44 Uhr Hello, is SVN path  https://svn.apache.org/repos/asf/openoffice/updates-site/trunk/ readonly? (edited) warwalrux 23:54 Uhr I believe it's readonly to all but members of the openoffice group. (edited) Gavin McDonald 23:58 U

Re: SVN problem

Hi Andrea, Am 13.08.19 um 00:05 schrieb Andrea Pescetti: > Matthias Seidel wrote: >> https://svn.apache.org/repos/asf/openoffice/updates-site/ seems to be >> read-only now? >> Can anyone confirm? > > Confirmed. I tried adding an empty "aoo417" directory and commit was > rejected. Transcript below.

Re: SVN problem

Matthias Seidel wrote: https://svn.apache.org/repos/asf/openoffice/updates-site/ seems to be read-only now? Can anyone confirm? Confirmed. I tried adding an empty "aoo417" directory and commit was rejected. Transcript below. $ svn mkdir aoo417 A aoo417 $ svn ci -m "Empty dir for 4.1.

Re: SVN problem

Infra confirms. I ask now what they need to fix it. On 13.08.19 00:00, Marcus wrote: > Am 12.08.19 um 23:39 schrieb Matthias Seidel: >> https://svn.apache.org/repos/asf/openoffice/updates-site/ seems to be >> read-only now? >> >> Can anyone confirm? > > yes, I cannot send a commit as access is den

Re: SVN problem

Am 12.08.19 um 23:39 schrieb Matthias Seidel: https://svn.apache.org/repos/asf/openoffice/updates-site/ seems to be read-only now? Can anyone confirm? yes, I cannot send a commit as access is denied. Marcus - To unsubscribe