Re: [PR] Remove Urchin Tracker - a use of google analytics [openoffice-org]

2024-05-15 Thread via GitHub
DiGro commented on PR #92: URL: https://github.com/apache/openoffice-org/pull/92#issuecomment-2112377203 @dave2wave feel free to dump it. It is a relic from the past -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub

Re: [PR] misc: fix spelling [openoffice]

2024-05-14 Thread via GitHub
Pilot-Pirx merged PR #213: URL: https://github.com/apache/openoffice/pull/213 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

Re: [PR] Remove Urchin Tracker - a use of google analytics [openoffice-org]

2024-05-14 Thread via GitHub
dave2wave commented on PR #92: URL: https://github.com/apache/openoffice-org/pull/92#issuecomment-2111040621 @DiGro Does this very old page have any use? http://www.openoffice.org/nl/thankyoupage/. It has a tracker on it and seems to exist from Sun -> Oracle times. I would like to rip it

[PR] Remove Urchin Tracker - a use of google analytics [openoffice-org]

2024-05-14 Thread via GitHub
dave2wave opened a new pull request, #92: URL: https://github.com/apache/openoffice-org/pull/92 Accumulating changes here first. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific

[PR] misc: fix spelling [openoffice]

2024-05-14 Thread via GitHub
jbampton opened a new pull request, #213: URL: https://github.com/apache/openoffice/pull/213 (no comment) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe,

Re: [PR] Fix spelling in code comments [openoffice]

2024-05-14 Thread via GitHub
Pilot-Pirx merged PR #212: URL: https://github.com/apache/openoffice/pull/212 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

[PR] Fix spelling in code comments [openoffice]

2024-05-14 Thread via GitHub
jbampton opened a new pull request, #212: URL: https://github.com/apache/openoffice/pull/212 (no comment) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe,

Re: [PR] Fix spelling in code comments [openoffice]

2024-05-14 Thread via GitHub
Pilot-Pirx merged PR #211: URL: https://github.com/apache/openoffice/pull/211 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

[PR] Fix spelling in code comments [openoffice]

2024-05-14 Thread via GitHub
jbampton opened a new pull request, #211: URL: https://github.com/apache/openoffice/pull/211 (no comment) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe,

Re: [PR] Blog post about development on trunk branch [openoffice-project]

2024-04-03 Thread via GitHub
ardovm merged PR #11: URL: https://github.com/apache/openoffice-project/pull/11 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

Re: [PR] Possible fix for issue 60859 [openoffice]

2024-04-02 Thread via GitHub
ardovm merged PR #200: URL: https://github.com/apache/openoffice/pull/200 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

Re: [PR] Fix spelling in code comments [openoffice]

2024-04-01 Thread via GitHub
Pilot-Pirx merged PR #210: URL: https://github.com/apache/openoffice/pull/210 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

Re: [PR] Link pthread library when using OpenSSL on Linux [openoffice]

2024-04-01 Thread via GitHub
ardovm merged PR #206: URL: https://github.com/apache/openoffice/pull/206 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

Re: [PR] Possible fix for issue 60859 [openoffice]

2024-04-01 Thread via GitHub
pedlino commented on PR #200: URL: https://github.com/apache/openoffice/pull/200#issuecomment-2030108118 Windows build tested. Bug is fixed in trunk -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go

[PR] Fix spelling in code comments [openoffice]

2024-04-01 Thread via GitHub
jbampton opened a new pull request, #210: URL: https://github.com/apache/openoffice/pull/210 (no comment) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe,

Re: [PR] Fix spelling in comments [openoffice]

2024-04-01 Thread via GitHub
Pilot-Pirx merged PR #209: URL: https://github.com/apache/openoffice/pull/209 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

[PR] Fix spelling in comments [openoffice]

2024-04-01 Thread via GitHub
jbampton opened a new pull request, #209: URL: https://github.com/apache/openoffice/pull/209 (no comment) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe,

Re: [PR] Fix spelling in code comments [openoffice]

2024-04-01 Thread via GitHub
Pilot-Pirx commented on PR #208: URL: https://github.com/apache/openoffice/pull/208#issuecomment-2029737332 Thanks again! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment.

Re: [PR] Fix spelling in code comments [openoffice]

2024-04-01 Thread via GitHub
Pilot-Pirx merged PR #208: URL: https://github.com/apache/openoffice/pull/208 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

[PR] Fix spelling in code comments [openoffice]

2024-04-01 Thread via GitHub
jbampton opened a new pull request, #208: URL: https://github.com/apache/openoffice/pull/208 (no comment) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe,

Re: [PR] Fix spelling in code comments and descriptions only [openoffice]

2024-04-01 Thread via GitHub
Pilot-Pirx merged PR #207: URL: https://github.com/apache/openoffice/pull/207 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

[PR] Fix spelling in code comments and descriptions only [openoffice]

2024-04-01 Thread via GitHub
jbampton opened a new pull request, #207: URL: https://github.com/apache/openoffice/pull/207 (no comment) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe,

[PR] Blog post about development on trunk branch [openoffice-project]

2024-04-01 Thread via GitHub
ardovm opened a new pull request, #11: URL: https://github.com/apache/openoffice-project/pull/11 Proposal for blog post about our latest development on the trunk branch. **Note**: The post is dated 2 April. -- This is an automated message from the Apache Git Service. To respond to

Re: [PR] Possible fix for issue 60859 [openoffice]

2024-03-31 Thread via GitHub
Pilot-Pirx commented on PR #200: URL: https://github.com/apache/openoffice/pull/200#issuecomment-2028644068 It did build fine and I have no crashes anymore. The behavior now is logical for me. Maybe this is something we would want to backport for AOO41X? -- This is an automated

Re: [PR] Link pthread library when using OpenSSL on Linux [openoffice]

2024-03-29 Thread via GitHub
DamjanJovanovic commented on PR #206: URL: https://github.com/apache/openoffice/pull/206#issuecomment-2027757168 Oh right, on Linux pthreads is in a separate library, and internal OpenSSL is linked statically, so the binary linking to OpenSSL has to link to pthreads as well. Forgot about

Re: [PR] Possible fix for issue 60859 [openoffice]

2024-03-29 Thread via GitHub
ardovm commented on PR #200: URL: https://github.com/apache/openoffice/pull/200#issuecomment-2027708940 The logic had to be a little more complex than that. If there is a visible slides after the selection, then it has to be selected. Otherwise, we have to search for a visible slide

Re: [PR] Allow compilation of AOO41X under Ubuntu Jammy (GCC 11) [openoffice]

2024-03-11 Thread via GitHub
ardovm commented on PR #198: URL: https://github.com/apache/openoffice/pull/198#issuecomment-1987694519 It was better to start from trunk. Trunk now builds on Jammy and we will be able to cherry-pick the relevant commits into AOO41X. -- This is an automated message from the Apache Git

Re: [PR] Allow compilation of AOO41X under Ubuntu Jammy (GCC 11) [openoffice]

2024-03-11 Thread via GitHub
ardovm closed pull request #198: Allow compilation of AOO41X under Ubuntu Jammy (GCC 11) URL: https://github.com/apache/openoffice/pull/198 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the

Re: [PR] Build nss with OS_TARGET=WINNT [openoffice]

2024-03-07 Thread via GitHub
Pilot-Pirx merged PR #199: URL: https://github.com/apache/openoffice/pull/199 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

Re: [PR] docs: fix spelling in code comments [openoffice]

2024-02-22 Thread via GitHub
Pilot-Pirx merged PR #205: URL: https://github.com/apache/openoffice/pull/205 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

Re: [PR] Update boost - Part 1 [openoffice]

2024-02-22 Thread via GitHub
Pilot-Pirx commented on PR #202: URL: https://github.com/apache/openoffice/pull/202#issuecomment-1959880734 **Let boost promote to double the sinc_pi() operation.** Modern processors should handle this without any trouble. -- This is an automated message from the Apache Git

Re: [PR] Update boost - Part 1 [openoffice]

2024-02-22 Thread via GitHub
Pilot-Pirx commented on PR #202: URL: https://github.com/apache/openoffice/pull/202#issuecomment-1959879198 Original comments from Pedro: Minor cleanup to internal boost header packaging We normally don't install all the headers available in boost. There is an interesting

[PR] docs: fix spelling in code comments [openoffice]

2024-02-21 Thread via GitHub
jbampton opened a new pull request, #205: URL: https://github.com/apache/openoffice/pull/205 (no comment) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe,

Re: [PR] docs: fix spelling in code comments [openoffice]

2024-02-21 Thread via GitHub
Pilot-Pirx merged PR #204: URL: https://github.com/apache/openoffice/pull/204 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

[PR] docs: fix spelling in code comments [openoffice]

2024-02-21 Thread via GitHub
jbampton opened a new pull request, #204: URL: https://github.com/apache/openoffice/pull/204 (no comment) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe,

Re: [PR] docs: fix spelling in code comments [openoffice]

2024-02-21 Thread via GitHub
Pilot-Pirx merged PR #203: URL: https://github.com/apache/openoffice/pull/203 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

Re: [PR] docs: fix spelling in code comments [openoffice]

2024-02-21 Thread via GitHub
Pilot-Pirx commented on PR #203: URL: https://github.com/apache/openoffice/pull/203#issuecomment-1957180180 Looks good to me! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific

[PR] docs: fix spelling in code comments [openoffice]

2024-02-21 Thread via GitHub
jbampton opened a new pull request, #203: URL: https://github.com/apache/openoffice/pull/203 (no comment) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe,

Re: [PR] Update base.html [openoffice-project]

2024-02-18 Thread via GitHub
dave2wave merged PR #10: URL: https://github.com/apache/openoffice-project/pull/10 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

[PR] Update boost - Part 1 [openoffice]

2024-02-15 Thread via GitHub
Pilot-Pirx opened a new pull request, #202: URL: https://github.com/apache/openoffice/pull/202 This is a remake of the first part of Pedro Giffuni's original PR: https://github.com/apache/openoffice/pull/194 -- This is an automated message from the Apache Git Service. To respond to the

Re: [PR] Remove code for unused bmpmaker [openoffice]

2024-02-11 Thread via GitHub
Pilot-Pirx merged PR #201: URL: https://github.com/apache/openoffice/pull/201 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

Re: [PR] Remove code for unused bmpmaker [openoffice]

2024-02-10 Thread via GitHub
Pilot-Pirx commented on PR #201: URL: https://github.com/apache/openoffice/pull/201#issuecomment-1937060815 My Windows build was successful. I would like to merge this PR to trunk now and let the Linux buildbot do its job. ;-) -- This is an automated message from the Apache Git

Re: [PR] Remove code for unused bmpmaker [openoffice]

2024-02-10 Thread via GitHub
Pilot-Pirx commented on PR #201: URL: https://github.com/apache/openoffice/pull/201#issuecomment-1936993392 And I like the idea of preserving useful code... Could we keep it in some sort of "internal attic" maybe in https://svn.apache.org/repos/asf/openoffice/devtools/ ? -- This is

[PR] Remove code for unused bmpmaker [openoffice]

2024-02-09 Thread via GitHub
Pilot-Pirx opened a new pull request, #201: URL: https://github.com/apache/openoffice/pull/201 See: https://bz.apache.org/ooo/show_bug.cgi?id=83198 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to

Re: [PR] Possible fix for issue 60859 [openoffice]

2024-02-07 Thread via GitHub
Pilot-Pirx commented on PR #200: URL: https://github.com/apache/openoffice/pull/200#issuecomment-1932700934 I updated my build now with the above changes, but unfortunately it still crashes... -- This is an automated message from the Apache Git Service. To respond to the message, please

Re: [PR] Build nss with OS_TARGET=WINNT [openoffice]

2024-02-06 Thread via GitHub
ardovm commented on PR #199: URL: https://github.com/apache/openoffice/pull/199#issuecomment-1930679444 This PR looks good to me. Thank you! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the

Re: [PR] Build nss with OS_TARGET=WINNT [openoffice]

2024-02-06 Thread via GitHub
Pilot-Pirx commented on PR #199: URL: https://github.com/apache/openoffice/pull/199#issuecomment-1930610843 > Did you try signing and verifying signatures with this build? That should be a good check that everything works. I could successfully sign a document with my recent build.

Re: [PR] Possible fix for issue 60859 [openoffice]

2024-02-06 Thread via GitHub
ardovm commented on PR #200: URL: https://github.com/apache/openoffice/pull/200#issuecomment-1930585461 > After some testing I have found a problem: I get a crash when I hide the last slide, select it and start a presentation (by pressing F5). This does not happen when there is only one

Re: [PR] first implementation of datedif [openoffice]

2024-02-06 Thread via GitHub
DamjanJovanovic commented on PR #178: URL: https://github.com/apache/openoffice/pull/178#issuecomment-1930389666 Great work, thank you! Can you also please add a description of this function to our help system, probably under main/helpcontent2/source/text/scalc/01/? -- This is an

Re: [PR] first implementation of datedif [openoffice]

2024-02-06 Thread via GitHub
oooforum commented on PR #178: URL: https://github.com/apache/openoffice/pull/178#issuecomment-1929618537 Thanks for this patch. Can it be pushed for the next build? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use

Re: [PR] Update boost to version 1.64 + minor enhancements [openoffice]

2024-02-05 Thread via GitHub
Pilot-Pirx commented on PR #194: URL: https://github.com/apache/openoffice/pull/194#issuecomment-1928222573 Unfortunately GitHub does not seem to allow to re-open a PR once it was merged... If you don't mind (and my time permits) I would like to do "remakes" of your original PR.

Re: [PR] Build nss with OS_TARGET=WINNT [openoffice]

2024-02-05 Thread via GitHub
Pilot-Pirx commented on PR #199: URL: https://github.com/apache/openoffice/pull/199#issuecomment-1927863520 Please find a Windows build here: https://www.dropbox.com/scl/fi/8kx1kwcet1ldnb5ckpiax/Apache_OpenOffice_4.5.0_Win_x86_install_en-US_nss.exe?rlkey=o4qh04sd805weh62h8iycdcsd=0 --

Re: [PR] Possible fix for issue 60859 [openoffice]

2024-02-05 Thread via GitHub
Pilot-Pirx commented on PR #200: URL: https://github.com/apache/openoffice/pull/200#issuecomment-1927852752 After some testing I have found a problem: I get a crash when I hide the last slide, select it and start a presentation (by pressing F5). This does not happen when there is only

Re: [PR] Possible fix for issue 60859 [openoffice]

2024-02-04 Thread via GitHub
Pilot-Pirx commented on PR #200: URL: https://github.com/apache/openoffice/pull/200#issuecomment-1925915743 Please find a Windows build here: https://www.dropbox.com/scl/fi/ph0fogxba7wkbvxlfsr96/Apache_OpenOffice_4.5.0_Win_x86_install_en-US_Slide.exe?rlkey=vaxkxtaq9ix6vqms9q5d1uf15=0

Re: [PR] Build nss with OS_TARGET=WINNT [openoffice]

2024-02-04 Thread via GitHub
Pilot-Pirx commented on code in PR #199: URL: https://github.com/apache/openoffice/pull/199#discussion_r1477352624 ## main/libxmlsec/xmlsec1-configure.patch: ## @@ -759,7 +759,7 @@ XMLSEC_OPENSSL_ALIBS= libeay32.lib wsock32.lib kernel32.lib user32.lib gdi32.lib

Re: [PR] Build nss with OS_TARGET=WINNT [openoffice]

2024-02-04 Thread via GitHub
Pilot-Pirx commented on code in PR #199: URL: https://github.com/apache/openoffice/pull/199#discussion_r1477351327 ## main/libxmlsec/xmlsec1-configure.patch: ## @@ -759,7 +759,7 @@ XMLSEC_OPENSSL_ALIBS= libeay32.lib wsock32.lib kernel32.lib user32.lib gdi32.lib

Re: [PR] Build nss with OS_TARGET=WINNT [openoffice]

2024-02-04 Thread via GitHub
ardovm commented on code in PR #199: URL: https://github.com/apache/openoffice/pull/199#discussion_r1477351087 ## main/libxmlsec/xmlsec1-configure.patch: ## @@ -759,7 +759,7 @@ XMLSEC_OPENSSL_ALIBS= libeay32.lib wsock32.lib kernel32.lib user32.lib gdi32.lib

Re: [PR] Fix for issue 60859 [openoffice]

2024-01-26 Thread via GitHub
Pilot-Pirx commented on code in PR #200: URL: https://github.com/apache/openoffice/pull/200#discussion_r1468106347 ## main/sd/source/ui/slideshow/slideshowimpl.cxx: ## @@ -236,6 +236,17 @@ AnimationSlideController::AnimationSlideController( Reference< XIndexAccess > xS

Re: [PR] Fix for issue 60859 [openoffice]

2024-01-25 Thread via GitHub
Pilot-Pirx commented on code in PR #200: URL: https://github.com/apache/openoffice/pull/200#discussion_r1466304570 ## main/sd/source/ui/slideshow/slideshowimpl.cxx: ## @@ -236,6 +236,17 @@ AnimationSlideController::AnimationSlideController( Reference< XIndexAccess > xS

Re: [PR] Fix for issue 60859 [openoffice]

2024-01-24 Thread via GitHub
oooforum commented on code in PR #200: URL: https://github.com/apache/openoffice/pull/200#discussion_r1464537713 ## main/sd/source/ui/slideshow/slideshowimpl.cxx: ## @@ -236,6 +236,17 @@ AnimationSlideController::AnimationSlideController( Reference< XIndexAccess > xS

Re: [PR] Fix for issue 60859 [openoffice]

2024-01-23 Thread via GitHub
ardovm commented on code in PR #200: URL: https://github.com/apache/openoffice/pull/200#discussion_r1463061431 ## main/sd/source/ui/slideshow/slideshowimpl.cxx: ## @@ -236,6 +236,17 @@ AnimationSlideController::AnimationSlideController( Reference< XIndexAccess > xS

[PR] Fix for issue 60859 [openoffice]

2024-01-23 Thread via GitHub
oooforum opened a new pull request, #200: URL: https://github.com/apache/openoffice/pull/200 If 1st slide is hidden and selected, show presentation does start after this. Thanks to iammisc for this patch https://bz.apache.org/ooo/show_bug.cgi?id=60859 -- This is an automated

Re: [PR] Update boost to version 1.64 + minor enhancements [openoffice]

2024-01-22 Thread via GitHub
pgiffuni commented on PR #194: URL: https://github.com/apache/openoffice/pull/194#issuecomment-1905206856 I wish the 1.55 changes had been merged separately. The sinc_pi change was useful despite the version. In any case it appears that the boost build per-se didn't fail but that the

[PR] Build nss with OS_TARGET=WINNT [openoffice]

2024-01-21 Thread via GitHub
Pilot-Pirx opened a new pull request, #199: URL: https://github.com/apache/openoffice/pull/199 (no comment) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe,

[PR] Allow compilation of AOO41X under Ubuntu Jammy (GCC 11) [openoffice]

2024-01-16 Thread via GitHub
ardovm opened a new pull request, #198: URL: https://github.com/apache/openoffice/pull/198 The AOO41X branch does not seem to build on Ubuntu 22.04 "Jammy". The purpose of this pull request is to gather and review the modifications that make AOO41X build again. The edits

Re: [PR] Revert "Enhance a bit our current boost usage" [openoffice]

2024-01-14 Thread via GitHub
Pilot-Pirx commented on PR #197: URL: https://github.com/apache/openoffice/pull/197#issuecomment-1891101395 This is already reverted. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific

Re: [PR] Revert "Enhance a bit our current boost usage" [openoffice]

2024-01-14 Thread via GitHub
Pilot-Pirx closed pull request #197: Revert "Enhance a bit our current boost usage" URL: https://github.com/apache/openoffice/pull/197 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific

Re: [PR] Enhance a bit our current boost usage [openoffice]

2024-01-14 Thread via GitHub
Pilot-Pirx commented on PR #194: URL: https://github.com/apache/openoffice/pull/194#issuecomment-1891100904 Not being a developer I will now step back and let others take over... -- This is an automated message from the Apache Git Service. To respond to the message, please log on to

Re: [PR] Enhance a bit our current boost usage [openoffice]

2024-01-14 Thread via GitHub
Pilot-Pirx commented on PR #194: URL: https://github.com/apache/openoffice/pull/194#issuecomment-1891100756 Buildbot does not build: 1 module(s): sal need(s) to be rebuilt Reason(s): ERROR: error 65280 occurred while making

[PR] Revert "Enhance a bit our current boost usage" [openoffice]

2024-01-14 Thread via GitHub
Pilot-Pirx opened a new pull request, #197: URL: https://github.com/apache/openoffice/pull/197 Reverts apache/openoffice#194 Buildbot does not build: 1 module(s): sal need(s) to be rebuilt Reason(s): ERROR: error 65280 occurred while making

Re: [PR] Enhance a bit our current boost usage [openoffice]

2024-01-14 Thread via GitHub
Pilot-Pirx merged PR #194: URL: https://github.com/apache/openoffice/pull/194 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

Re: [PR] Enhance a bit our current boost usage [openoffice]

2024-01-14 Thread via GitHub
Pilot-Pirx commented on PR #194: URL: https://github.com/apache/openoffice/pull/194#issuecomment-1891036420 Yes, I can "Squash and merge" it to trunk. In fact I will do it now. If something goes wrong it is just one commit to revert... If the Linux buildbot is successful, I will

Re: [PR] Enhance a bit our current boost usage [openoffice]

2024-01-14 Thread via GitHub
pgiffuni commented on PR #194: URL: https://github.com/apache/openoffice/pull/194#issuecomment-1891020126 Can you cheerypick the 1.55 updates and squash the 1.64 update in one commit? I did try to make it easier for you guys to revert in case something went really wrong although it seems

Re: [PR] Enhance a bit our current boost usage [openoffice]

2024-01-14 Thread via GitHub
Pilot-Pirx commented on PR #194: URL: https://github.com/apache/openoffice/pull/194#issuecomment-1890902258 Thanks for the info! I can merge it, although it still is a "shot in the dark" for me. For Linux I can see the results from our buildbot (trunk):

Re: [PR] Enhance a bit our current boost usage [openoffice]

2024-01-13 Thread via GitHub
pgiffuni commented on PR #194: URL: https://github.com/apache/openoffice/pull/194#issuecomment-1890822397 > > Since it builds on BSD how high is the probability that it also builds on macOS? Very high .. FreeBSD and macOS share most of libc and FreeBSD adopted natively LLVM

Re: [PR] Enhance a bit our current boost usage [openoffice]

2024-01-13 Thread via GitHub
Pilot-Pirx commented on PR #194: URL: https://github.com/apache/openoffice/pull/194#issuecomment-1890775948 Hi Pedro, I am highly motivated to merge this PR but I didn't want to do it without being sure that it builds on macOS and Linux. We definitely want to have this in AOO

Re: [PR] Enhance a bit our current boost usage [openoffice]

2024-01-13 Thread via GitHub
pgiffuni commented on PR #194: URL: https://github.com/apache/openoffice/pull/194#issuecomment-1890767770 @Pilot-Pirx Thanks so much for finishing the bits for Windows. Since it's getting so long to merge(!), let me provide some motivation: We currently make [limited

Re: [PR] Enhance a bit our current boost usage [openoffice]

2024-01-06 Thread via GitHub
Pilot-Pirx commented on PR #194: URL: https://github.com/apache/openoffice/pull/194#issuecomment-1879941167 @jimjag Can you please try to build on macOS/Linux? I think this would be nice for AOO 4.2.0-Dev5. -- This is an automated message from the Apache Git Service. To respond to the

Re: [PR] Enhance a bit our current boost usage [openoffice]

2024-01-06 Thread via GitHub
Pilot-Pirx commented on PR #194: URL: https://github.com/apache/openoffice/pull/194#issuecomment-1879940017 Builds on Windows now: https://www.dropbox.com/scl/fi/5ooqaxvdec34l30v99xmo/Apache_OpenOffice_4.5.0_Win_x86_install_en-US_boost.exe?rlkey=k5r4bwmxrvzlzraypu42jod2c=0 -- This is

[PR] CVE in MarkDown format [openoffice-org]

2024-01-02 Thread via GitHub
ardovm opened a new pull request, #91: URL: https://github.com/apache/openoffice-org/pull/91 This is a proposal for a template that allows to prepare CVE pages in MarkDown format. The purpose is making our life easier when publishing new security bulletins. As an example, the

Re: [PR] Removed whitespace between tags and other superfluous whitespace (branch Latest) [openoffice]

2024-01-02 Thread via GitHub
Pilot-Pirx commented on PR #74: URL: https://github.com/apache/openoffice/pull/74#issuecomment-1874009640 I think I have done the major part in cleaning up the Help files. There are certainly a lot of small errors left but that can be fixed with normal maintenance. The resulting

Re: [PR] Removed whitespace between tags and other superfluous whitespace (branch Latest) [openoffice]

2024-01-02 Thread via GitHub
Pilot-Pirx closed pull request #74: Removed whitespace between tags and other superfluous whitespace (branch Latest) URL: https://github.com/apache/openoffice/pull/74 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the

Re: [PR] Fixed - single file patches combined into one PR and commit 97a1911 [openoffice]

2024-01-01 Thread via GitHub
Pilot-Pirx commented on PR #80: URL: https://github.com/apache/openoffice/pull/80#issuecomment-1873368293 Happy New Year to you, too! I think I will finish this week, after that we can go back to normal maintenance of the Help files. I will let you know. -- This is an automated

Re: [PR] Fixed - single file patches combined into one PR and commit 97a1911 [openoffice]

2024-01-01 Thread via GitHub
DiGro commented on PR #80: URL: https://github.com/apache/openoffice/pull/80#issuecomment-1873350577 @Pilot-Pirx Matthias, thanks for your tremendous efforts. I'm not sure how to help you with the Help files, but if there is something I can do, please let me know. Frohes neues

Re: [PR] Fixed - single file patches combined into one PR and commit 97a1911 [openoffice]

2024-01-01 Thread via GitHub
Pilot-Pirx commented on PR #80: URL: https://github.com/apache/openoffice/pull/80#issuecomment-1873337097 Hi Dick, thank you for all this work. I think I have updated all files from this PR with my big "Cleanup". So I will close it now. However, there are still a lot of small

Re: [PR] Fixed - single file patches combined into one PR and commit 97a1911 [openoffice]

2024-01-01 Thread via GitHub
Pilot-Pirx closed pull request #80: Fixed - single file patches combined into one PR and commit 97a1911 URL: https://github.com/apache/openoffice/pull/80 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to

Re: [PR] Enhance a bit our current boost usage [openoffice]

2023-12-31 Thread via GitHub
pgiffuni commented on PR #194: URL: https://github.com/apache/openoffice/pull/194#issuecomment-1872969954 Happy new year!! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment.

Re: [PR] Enhance a bit our current boost usage [openoffice]

2023-12-31 Thread via GitHub
Pilot-Pirx commented on PR #194: URL: https://github.com/apache/openoffice/pull/194#issuecomment-1872960941 I will try that! Next year... ;-) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to

Re: [PR] Enhance a bit our current boost usage [openoffice]

2023-12-31 Thread via GitHub
pgiffuni commented on PR #194: URL: https://github.com/apache/openoffice/pull/194#issuecomment-1872958147 Looking at your d.lst changes, there is a dll/detail directory which may be needed for windows. his didn't exist in 1.55 -- This is an automated message from the Apache Git

Re: [PR] Enhance a bit our current boost usage [openoffice]

2023-12-31 Thread via GitHub
Pilot-Pirx commented on PR #194: URL: https://github.com/apache/openoffice/pull/194#issuecomment-1872951893 I will try to do that. For the moment I will change this to a Draft. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to

Re: [PR] Update boost to version 1.64 [openoffice]

2023-12-31 Thread via GitHub
pgiffuni commented on PR #194: URL: https://github.com/apache/openoffice/pull/194#issuecomment-1872947861 Bummer! Please merge the 1.55 header updates. I won't have time to work on further updates to boost but I'll keep the patch for playing with 1.64 in the future. -- This is an

Re: [PR] Update boost to version 1.64 [openoffice]

2023-12-31 Thread via GitHub
Pilot-Pirx commented on PR #194: URL: https://github.com/apache/openoffice/pull/194#issuecomment-1872921751 I am now able to build further on Windows, but I get a lot of these warnings and the build stops at some point: ![VirtualBox_Windows 10

Re: [PR] Removed whitespace from tags 20200229 1835 [openoffice]

2023-12-28 Thread via GitHub
Pilot-Pirx closed pull request #76: Removed whitespace from tags 20200229 1835 URL: https://github.com/apache/openoffice/pull/76 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific

Re: [PR] Removed whitespace from tags 20200229 1835 [openoffice]

2023-12-28 Thread via GitHub
Pilot-Pirx commented on PR #76: URL: https://github.com/apache/openoffice/pull/76#issuecomment-1871049289 Closing this PR as all files are updated now. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to

Re: [PR] Removed whitespace from tags 20200229 1835 [openoffice]

2023-12-27 Thread via GitHub
Pilot-Pirx commented on PR #76: URL: https://github.com/apache/openoffice/pull/76#issuecomment-1870613756 I am in the massive process of cleaning up our Help files... The whitespace (not only) before should be gone now. Even if we don't use Pootle in the future a clean structure is

Re: [PR] Enhance a bit our current boost usage [openoffice]

2023-12-26 Thread via GitHub
pgiffuni commented on PR #194: URL: https://github.com/apache/openoffice/pull/194#issuecomment-1869749245 The latest version should work. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the

Re: [PR] Enhance a bit our current boost usage [openoffice]

2023-12-26 Thread via GitHub
Pilot-Pirx commented on PR #194: URL: https://github.com/apache/openoffice/pull/194#issuecomment-1869685450 Builds on Windows with 1.55. Breaks with 1.64 in module sal: Building module sal = Entering /cygdrive/c/Source/openoffice/main/sal/inc

Re: [PR] Update main0108.xhp [openoffice]

2023-12-24 Thread via GitHub
Pilot-Pirx commented on PR #195: URL: https://github.com/apache/openoffice/pull/195#issuecomment-1868628286 The code for the "Purchase-Wizard" seems to be long gone... So the Help file does not make sense anymore. -- This is an automated message from the Apache Git Service. To respond

Re: [PR] Update main0108.xhp [openoffice]

2023-12-24 Thread via GitHub
Pilot-Pirx merged PR #195: URL: https://github.com/apache/openoffice/pull/195 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

Re: [PR] Aoo41 x [openoffice]

2023-12-24 Thread via GitHub
Pilot-Pirx closed pull request #196: Aoo41 x URL: https://github.com/apache/openoffice/pull/196 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

  1   2   3   4   >