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.mdtext. I've moved your source_new.mdtext to be the > new version of source.mdtext and we'll continue from there. > Sounds good... This page also references a "Subversion Basics" page -- https://openoffice.apache.org/svn-basics.html which has a LOT of information that either needs attention or a good comparable git resource, especially the merge/cherrypicking aspects > > I really know VERY little about git but I will try to do some editing and > > hope others will do a lot more. ☺ > > I am quite knowledgeable about git itself (I've used it daily for > several years) so I can definitely provide some text and I will do some > edits. What I am quite unfamiliar with is how we are supposed to use git > at the ASF, why we have two master repositories and so on; all I can > find is https://gitbox.apache.org/ so I guess all other policies are up > to us for defining. > I started looking for something like this also. Hopefully INFRA can enlighten. > > Regards, >Andrea. > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > > -- "And in the end, only kindness matters." -- Jewel, "Hands" MzK
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 source.mdtext and we'll continue from there. I really know VERY little about git but I will try to do some editing and hope others will do a lot more. ☺ I am quite knowledgeable about git itself (I've used it daily for several years) so I can definitely provide some text and I will do some edits. What I am quite unfamiliar with is how we are supposed to use git at the ASF, why we have two master repositories and so on; all I can find is https://gitbox.apache.org/ so I guess all other policies are up to us for defining. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
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 work together on that page. Do your editing, publish it and we can add further changes. As already mentioned, staging does not work on o.a.o due to HTTPS redirection. Otherwise we could work together on the staged page. BTW: This page is important since the README from GitHub [1] points to the source code page at o.a.o [2]. Matthias [1] https://github.com/apache/openoffice [2] https://openoffice.apache.org/source.html > > -- Kay > > On Tue, Aug 13, 2019 at 1:25 PM Matthias Seidel > wrote: > >> 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 >> 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 < >> matthias.sei...@hamburg.de> >>> wrote: >>> 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 Marcus: > 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 openoffice group. >> (edited) >> Gavin McDonald 23:58 Uhr >> I imagine the move to Git made more of svn read only than was wanted >> petko 00:02 Uhr >> can you make it writeable again? >> We (OpenOffice Members) can not write to it. Do you need an infra >> ticket? >> Gavin McDonald 00:07 Uhr >> are there any other paths need r/w or just ‘site’ and ‘updates-site’ ? >> (and ooo-site) >> petko 00:10 Uhr >> IMO only trunk, branches and tags should be read only. (edited) >> Gavin McDonald 00:25 Uhr >> >> ok > or to make it clearer for all: > > Root: https://svn.apache.org/repos/asf/openoffice/ > > r/wDISCLAIMER > r/wREADME > rbranches/ > r/wbranding/ > r/wdevtools/ > r/wooo-site/ > r/wsite/ > rsymphony/ > rtags/ > r/wtest/ > rtrunk/ > r/wupdates-site/ > > Marcus > > > >> On 13.08.19 00:08, Matthias Seidel wrote: >>> 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. $ svn mkdir aoo417 A aoo417 $ svn ci -m "Empty dir for 4.1.7 update feeds." Adding aoo417 svn: E195023: Commit failed: svn: E195023: Changing directory '/.../updates-site/trunk/aoo417' is forbidden by the server svn: E175013: Access to '/repos/asf/!svn/txr/1864989-14y1k/openoffice/updates-site/trunk/aoo417' forbidden >>> Yes, that is exactly what I wanted to do... ;-) > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > > >> smime.p7s Description: S/MIME Cryptographic Signature
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: > 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 > 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 < > matthias.sei...@hamburg.de> > > wrote: > > > >> 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 Marcus: > >>> 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 openoffice group. > (edited) > Gavin McDonald 23:58 Uhr > I imagine the move to Git made more of svn read only than was wanted > petko 00:02 Uhr > can you make it writeable again? > We (OpenOffice Members) can not write to it. Do you need an infra > ticket? > Gavin McDonald 00:07 Uhr > are there any other paths need r/w or just ‘site’ and ‘updates-site’ ? > (and ooo-site) > petko 00:10 Uhr > IMO only trunk, branches and tags should be read only. (edited) > Gavin McDonald 00:25 Uhr > > ok > >>> or to make it clearer for all: > >>> > >>> Root: https://svn.apache.org/repos/asf/openoffice/ > >>> > >>> r/wDISCLAIMER > >>> r/wREADME > >>> rbranches/ > >>> r/wbranding/ > >>> r/wdevtools/ > >>> r/wooo-site/ > >>> r/wsite/ > >>> rsymphony/ > >>> rtags/ > >>> r/wtest/ > >>> rtrunk/ > >>> r/wupdates-site/ > >>> > >>> Marcus > >>> > >>> > >>> > On 13.08.19 00:08, Matthias Seidel wrote: > > 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. > >> > >> $ svn mkdir aoo417 > >> A aoo417 > >> $ svn ci -m "Empty dir for 4.1.7 update feeds." > >> Adding aoo417 > >> svn: E195023: Commit failed: > >> svn: E195023: Changing directory '/.../updates-site/trunk/aoo417' is > >> forbidden by the server > >> svn: E175013: Access to > >> > >> '/repos/asf/!svn/txr/1864989-14y1k/openoffice/updates-site/trunk/aoo417' > >> forbidden > > Yes, that is exactly what I wanted to do... ;-) > >>> > >>> - > >>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > >>> For additional commands, e-mail: dev-h...@openoffice.apache.org > >>> > >>> > >> > > -- "And in the end, only kindness matters." -- Jewel, "Hands" MzK
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 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 >> 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 Marcus: >>> 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 openoffice group. (edited) Gavin McDonald 23:58 Uhr I imagine the move to Git made more of svn read only than was wanted petko 00:02 Uhr can you make it writeable again? We (OpenOffice Members) can not write to it. Do you need an infra ticket? Gavin McDonald 00:07 Uhr are there any other paths need r/w or just ‘site’ and ‘updates-site’ ? (and ooo-site) petko 00:10 Uhr IMO only trunk, branches and tags should be read only. (edited) Gavin McDonald 00:25 Uhr ok >>> or to make it clearer for all: >>> >>> Root: https://svn.apache.org/repos/asf/openoffice/ >>> >>> r/wDISCLAIMER >>> r/wREADME >>> rbranches/ >>> r/wbranding/ >>> r/wdevtools/ >>> r/wooo-site/ >>> r/wsite/ >>> rsymphony/ >>> rtags/ >>> r/wtest/ >>> rtrunk/ >>> r/wupdates-site/ >>> >>> Marcus >>> >>> >>> On 13.08.19 00:08, Matthias Seidel wrote: > 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. >> >> $ svn mkdir aoo417 >> A aoo417 >> $ svn ci -m "Empty dir for 4.1.7 update feeds." >> Adding aoo417 >> svn: E195023: Commit failed: >> svn: E195023: Changing directory '/.../updates-site/trunk/aoo417' is >> forbidden by the server >> svn: E175013: Access to >> >> '/repos/asf/!svn/txr/1864989-14y1k/openoffice/updates-site/trunk/aoo417' >> forbidden > Yes, that is exactly what I wanted to do... ;-) >>> >>> - >>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >>> For additional commands, e-mail: dev-h...@openoffice.apache.org >>> >>> >> smime.p7s Description: S/MIME Cryptographic Signature
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 > 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 Marcus: > > 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 openoffice group. > >> (edited) > >> Gavin McDonald 23:58 Uhr > >> I imagine the move to Git made more of svn read only than was wanted > >> petko 00:02 Uhr > >> can you make it writeable again? > >> We (OpenOffice Members) can not write to it. Do you need an infra > >> ticket? > >> Gavin McDonald 00:07 Uhr > >> are there any other paths need r/w or just ‘site’ and ‘updates-site’ ? > >> (and ooo-site) > >> petko 00:10 Uhr > >> IMO only trunk, branches and tags should be read only. (edited) > >> Gavin McDonald 00:25 Uhr > >> > >> ok > > > > or to make it clearer for all: > > > > Root: https://svn.apache.org/repos/asf/openoffice/ > > > > r/wDISCLAIMER > > r/wREADME > > rbranches/ > > r/wbranding/ > > r/wdevtools/ > > r/wooo-site/ > > r/wsite/ > > rsymphony/ > > rtags/ > > r/wtest/ > > rtrunk/ > > r/wupdates-site/ > > > > Marcus > > > > > > > >> On 13.08.19 00:08, Matthias Seidel wrote: > >>> 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. > > $ svn mkdir aoo417 > A aoo417 > $ svn ci -m "Empty dir for 4.1.7 update feeds." > Adding aoo417 > svn: E195023: Commit failed: > svn: E195023: Changing directory '/.../updates-site/trunk/aoo417' is > forbidden by the server > svn: E175013: Access to > > '/repos/asf/!svn/txr/1864989-14y1k/openoffice/updates-site/trunk/aoo417' > > forbidden > >>> Yes, that is exactly what I wanted to do... ;-) > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > > For additional commands, e-mail: dev-h...@openoffice.apache.org > > > > > > -- "And in the end, only kindness matters." -- Jewel, "Hands" MzK
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 Marcus: > 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 openoffice group. >> (edited) >> Gavin McDonald 23:58 Uhr >> I imagine the move to Git made more of svn read only than was wanted >> petko 00:02 Uhr >> can you make it writeable again? >> We (OpenOffice Members) can not write to it. Do you need an infra >> ticket? >> Gavin McDonald 00:07 Uhr >> are there any other paths need r/w or just ‘site’ and ‘updates-site’ ? >> (and ooo-site) >> petko 00:10 Uhr >> IMO only trunk, branches and tags should be read only. (edited) >> Gavin McDonald 00:25 Uhr >> >> ok > > or to make it clearer for all: > > Root: https://svn.apache.org/repos/asf/openoffice/ > > r/w DISCLAIMER > r/w README > r branches/ > r/w branding/ > r/w devtools/ > r/w ooo-site/ > r/w site/ > r symphony/ > r tags/ > r/w test/ > r trunk/ > r/w updates-site/ > > Marcus > > > >> On 13.08.19 00:08, Matthias Seidel wrote: >>> 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. $ svn mkdir aoo417 A aoo417 $ svn ci -m "Empty dir for 4.1.7 update feeds." Adding aoo417 svn: E195023: Commit failed: svn: E195023: Changing directory '/.../updates-site/trunk/aoo417' is forbidden by the server svn: E175013: Access to '/repos/asf/!svn/txr/1864989-14y1k/openoffice/updates-site/trunk/aoo417' forbidden >>> Yes, that is exactly what I wanted to do... ;-) > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > > smime.p7s Description: S/MIME Cryptographic Signature
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 openoffice group. (edited) Gavin McDonald 23:58 Uhr I imagine the move to Git made more of svn read only than was wanted petko 00:02 Uhr can you make it writeable again? We (OpenOffice Members) can not write to it. Do you need an infra ticket? Gavin McDonald 00:07 Uhr are there any other paths need r/w or just ‘site’ and ‘updates-site’ ? (and ooo-site) petko 00:10 Uhr IMO only trunk, branches and tags should be read only. (edited) Gavin McDonald 00:25 Uhr ok or to make it clearer for all: Root: https://svn.apache.org/repos/asf/openoffice/ r/w DISCLAIMER r/w README r branches/ r/w branding/ r/w devtools/ r/w ooo-site/ r/w site/ r symphony/ r tags/ r/w test/ r trunk/ r/w updates-site/ Marcus On 13.08.19 00:08, Matthias Seidel wrote: 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. $ svn mkdir aoo417 A aoo417 $ svn ci -m "Empty dir for 4.1.7 update feeds." Adding aoo417 svn: E195023: Commit failed: svn: E195023: Changing directory '/.../updates-site/trunk/aoo417' is forbidden by the server svn: E175013: Access to '/repos/asf/!svn/txr/1864989-14y1k/openoffice/updates-site/trunk/aoo417' forbidden Yes, that is exactly what I wanted to do... ;-) - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
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 Uhr I imagine the move to Git made more of svn read only than was wanted petko 00:02 Uhr can you make it writeable again? We (OpenOffice Members) can not write to it. Do you need an infra ticket? Gavin McDonald 00:07 Uhr are there any other paths need r/w or just ‘site’ and ‘updates-site’ ? (and ooo-site) petko 00:10 Uhr IMO only trunk, branches and tags should be read only. (edited) Gavin McDonald 00:25 Uhr ok On 13.08.19 00:08, Matthias Seidel wrote: > 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. >> >> $ svn mkdir aoo417 >> A aoo417 >> $ svn ci -m "Empty dir for 4.1.7 update feeds." >> Adding aoo417 >> svn: E195023: Commit failed: >> svn: E195023: Changing directory '/.../updates-site/trunk/aoo417' is >> forbidden by the server >> svn: E175013: Access to >> '/repos/asf/!svn/txr/1864989-14y1k/openoffice/updates-site/trunk/aoo417' >> forbidden > Yes, that is exactly what I wanted to do... ;-) > > Regards, > > Matthias > >> Regards, >> Andrea. >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >> For additional commands, e-mail: dev-h...@openoffice.apache.org >> - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
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. > > $ svn mkdir aoo417 > A aoo417 > $ svn ci -m "Empty dir for 4.1.7 update feeds." > Adding aoo417 > svn: E195023: Commit failed: > svn: E195023: Changing directory '/.../updates-site/trunk/aoo417' is > forbidden by the server > svn: E175013: Access to > '/repos/asf/!svn/txr/1864989-14y1k/openoffice/updates-site/trunk/aoo417' > forbidden Yes, that is exactly what I wanted to do... ;-) Regards, Matthias > > Regards, > Andrea. > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > smime.p7s Description: S/MIME Cryptographic Signature
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.7 update feeds." Adding aoo417 svn: E195023: Commit failed: svn: E195023: Changing directory '/.../updates-site/trunk/aoo417' is forbidden by the server svn: E175013: Access to '/repos/asf/!svn/txr/1864989-14y1k/openoffice/updates-site/trunk/aoo417' forbidden Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
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 denied. > > Marcus > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
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, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
SVN problem
Hi all, https://svn.apache.org/repos/asf/openoffice/updates-site/ seems to be read-only now? Can anyone confirm? Regards, Matthias smime.p7s Description: S/MIME Cryptographic Signature
