Re: svn commit: r1865164 - /openoffice/branches/AOO417/main/sal/osl/unx/nlsupport.c

2019-08-15 Thread Matthias Seidel
Hi Andrea, Am 15.08.19 um 08:30 schrieb Andrea Pescetti: > Matthias Seidel wrote: >> Shouldn't SVN be read-only now?! >> This will introduce some inconsistencies to Git now... > > If it is writable, please do not fix it! > > We definitely need some README there (in trunk) that points to the new >

Re: get Revision from Git (short Hash)

2019-08-15 Thread Jim Jagielski
That's exactly what I did ;) > On Aug 15, 2019, at 8:52 AM, Mechtilde wrote: > > Hello, > > we should commit to trunk and if that code should also be in 42x or 417 > we can cherry- pick the commit. > > regards > > Mechtilde > > Am 15.08.19 um 14:02 schrieb Jim Jagielski: >> Anyone have

Re: Python 2.7.16 update

2019-08-15 Thread Mechtilde
Hello Pedro, I try to build AOO under Debian 9 (Stretch - oldstable). There is no version 2.7.16 for python available. I already tried to build under Debian 10 (Buster - stable). But this is coming with Java 11. This introduce new problems. So I need special assistance to fix it. Regards

Re: Python 2.7.16 update

2019-08-15 Thread Matthias Seidel
Hi Pedro, Am 15.08.19 um 07:32 schrieb Pedro Giffuni: > Hello guys; > > I never had the time to test?? a minor update to Python. > > From the update notes it doesn't seem urgent, but feel free to give it > a spin and commit if ready: > >

Re: get Revision from Git (short Hash)

2019-08-15 Thread Mechtilde
Hello, we should commit to trunk and if that code should also be in 42x or 417 we can cherry- pick the commit. regards Mechtilde Am 15.08.19 um 14:02 schrieb Jim Jagielski: > Anyone have issues if we also commit to the 42X and 417 branches? > >> On Aug 15, 2019, at 1:03 AM, Peter Kovacs

Re: get Revision from Git (short Hash)

2019-08-15 Thread Jim Jagielski
Anyone have issues if we also commit to the 42X and 417 branches? > On Aug 15, 2019, at 1:03 AM, Peter Kovacs wrote: > > I pushed the change to gitbox trunk. > > On 15.08.19 00:15, Kay Schenk wrote: >> On Wed, Aug 14, 2019 at 3:07 PM Matthias Seidel >> wrote: >> >>> Hi Kay, >>> >>> Am

Re: Broken tools from GIT migration

2019-08-15 Thread Jim Jagielski
> On Aug 15, 2019, at 2:34 AM, Andrea Pescetti wrote: > > 3) Open Hub tracker https://www.openhub.net/p/openoffice > > "Our SVN tree is read by the Open Hub tracker to generate some various > statistics. Note that the migration from the legacy Mercurial repository to > SVN at Apache has

Re: Broken tools from GIT migration

2019-08-15 Thread Carl Marcum
Hi Andrea, On 8/15/19 2:34 AM, Andrea Pescetti wrote: > ... > > 5) Devtools > > Our devtools are code and should have been included in the migration > to Git. I didn't notice they were left out. > > Proposal: talk to Infra to see if we can easily add them retaining > history, or just copy them

Other Administrators for the Facebook Fan Page

2019-08-15 Thread Raphael Bircher
Hi all I've still the administrator access to the Apache OpenOffice Fan Page. I'm inactive in the project for over a year, and I have no plane to change this in the next time. So I would like to step back from my admin Roul at the AOO Fanpage in Facebook. Can someone take over this. Thanks a

Re: Broken tools from GIT migration

2019-08-15 Thread Matthias Seidel
Hi Andrea, Am 15.08.19 um 08:34 schrieb Andrea Pescetti: > Unless the discussion about this happened off-list, the SVN to Git > migration resulted in breaking some tools without any plans to fix > them. I'm listing the ones I found so far, and the course of action I > propose for each. As usual,

Re: Broken tools from GIT migration

2019-08-15 Thread Peter Kovacs
1) fisheye The instance has been broken for quite some time. I had a talk with infra, and my impression was they are not very engaged to fix it. Proposal: ask infra to fix it with migration to git or to remove us from fisheye. 2) openGrok Software is installed. Git migration is on todo list.

Broken tools from GIT migration

2019-08-15 Thread Andrea Pescetti
Unless the discussion about this happened off-list, the SVN to Git migration resulted in breaking some tools without any plans to fix them. I'm listing the ones I found so far, and the course of action I propose for each. As usual, 72 hours for lazy consensus before acting (but I can take care

Re: svn commit: r1865164 - /openoffice/branches/AOO417/main/sal/osl/unx/nlsupport.c

2019-08-15 Thread Andrea Pescetti
Matthias Seidel wrote: Shouldn't SVN be read-only now?! This will introduce some inconsistencies to Git now... If it is writable, please do not fix it! We definitely need some README there (in trunk) that points to the new repository URL, and a last commit message for it saying "Point to the