Re: Please update boost (1.79.0 would be just great)
For Clang, c++14 is the default, see https://clang.llvm.org/cxx_status.html where it says "By default, Clang builds C++ code according to the C++14 standard". On Sat, Jan 21, 2023 at 8:45 AM Yury Tarasievich wrote: > Apologies if I'm being dense here, but is this > indeed compiling to c++14? Won't you need > explicit -std=c++14 option for that? > > To compile 'just' to c++11 (on linux) a patch of > about 19 parts is needed, although admittedly it > consists mostly of these guys: > > +#define BOOST_NO_CXX11_RVALUE_REFERENCES 1 > +#define BOOST_NO_CXX11_DELETED_FUNCTIONS 1 > +#include > > On 20/01/2023 21:52, Damjan Jovanovic wrote: > > So I eventually succeeded in getting OpenOffice > > to compile against the "c++14" standard now, and > > to use a newer Boost. > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > >
Re: Icons proposal
Do you see my message ? If you want the icons to be changed, could you tell me how to change them on the software permanently? Cordially Manjiro (C.Verbreghe) Le ven. 20 janv. 2023 à 19:27, Xavier Verbrèghe < corentin.verbreg...@gmail.com> a écrit : > I was already subscribed to dev OpenOffice so I deleted my subscription > then I updated it. > > Le ven. 20 janv. 2023 à 18:04, Pedro Lino a > écrit : > >> Dear Xavier >> >> Thank you for the much better link! >> >> The previous message did arrive to the mailing list and Delio already >> commented that >> "The icons result modern and attractive." >> >> but you did not receive this comment because you are not subscribed to >> dev@openoffice.apache.org >> >> I agree that they have a nice modern design without being too different >> from the old ones which is excellent. >> >> I believe they could be tested on the 4.2.x branch if the group agrees? >> >> All the best, >> Pedro >> >> >> > On 01/20/2023 4:01 PM WET Xavier Verbrèghe < >> corentin.verbreg...@gmail.com> wrote: >> > >> > >> > I have the impression that the mail did not find recipient so here is >> the >> > link of my proposal for new icons of AOO software: >> > >> https://drive.google.com/drive/folders/1zaocgHeB30J5J-IGLnXAEPdeGKc075Iz >> > Hoping that you will like them and that they will become the new icons. >> > >> > Regards. >> > Manjiro >> >
Re: Nightly Builds
Hi Gavin, Am 21.01.23 um 13:33 schrieb Gavin McDonald: > Hi All, > > The nightly builds at https://ci2.apache.org/#/builders/58 are using up > much unnecessary > disk space on the nightlies.apache.org server. > > Currently Openoffice alone is using more than 1TB - all due to these > nightly builds. > Over 600GB are the linux64 snapshots and the rest are the linsnap* ones. > > Many many of these snapshots are identical to previous ones, but because > the date of the build is included then they are just repeated each day. > Even if no commits for weeks there is multi GB tars and debs being uploaded > each day. > > This seems a waste. > > Not only this, but no snapshots are being cleaned up, we have snapshots > dating back nearly a year just sitting there. > > Lets clean this up and be smarter going forwards. > > I would like to see these nightlies changed :- > > 1. Change to run weekly instead of daily. > 2. Instead of, or in addition to 1, build and upload by commit trigger. Just to clarify: I think the logic should be: Look every day (night) if there was a code change. If yes, do a build, otherwise skip. I don't want to trigger a build with every single commit... ;-) Regards, Matthias > 3. Clean up snapshots older than 1 month. > > Thoughts please > smime.p7s Description: S/MIME Cryptographic Signature
Re: [ANNOUNCE] Maintenance Window on Forums and Wiki
Hi! On Fri, Jan 20, 2023 at 5:37 PM wrote: > It seems that nobody cares about the Italian forum... > Please refresh the browser (and maybe also cookies) , I believe I have fixed this for you. PS. Love Italy - especially my friends in Gragnano Gav... > > - Messaggio originale - > Da: casa...@email.it > A: "dev" > Cc: "users" > Inviato: Mercoledì, 11 gennaio 2023 16:42:52 > Oggetto: Re: [ANNOUNCE] Maintenance Window on Forums and Wiki > > I was hoping that the opportunity was good to fix the registration form of > the Italian forum, but it was not so. > From the Italian forum it seems you don't care about anyone... > > - Messaggio originale - > Da: "Dave Fisher" > A: "dev" , us...@openoffice.apache.org > Inviato: Martedì, 10 gennaio 2023 18:57:25 > Oggetto: [ANNOUNCE] Maintenance Window on Forums and Wiki > > ASF Infrastructure Scheduled routine maintenance, OpenOffice forums and > wiki starting at Jan 11, 2023 - 11:00AM UTC and ending at Jan 11, 2023 - > 11:15AM UTC. > > The server hosting the OpenOffice forums and Wiki will be undergoing > routine maintenance on Wednesday the 11th of January at 11AM UTC. We expect > this operation to last 10-15 minutes at most, during which the OpenOffice > forums and wiki will be unavailable. > > Please send an email to d...@openoffice.org if there is trouble with > either website after the end of this window. > - > 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 > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > > -- *Gavin McDonald* Systems Administrator ASF Infrastructure Team
Re: Nightly Builds
Hi Rory, Am 21.01.23 um 14:18 schrieb Rory O'Farrell: > On Sat, 21 Jan 2023 14:13:54 +0100 > Matthias Seidel wrote: > >> Hi Rory, >> >> Am 21.01.23 um 13:52 schrieb Rory O'Farrell: >>> On Sat, 21 Jan 2023 13:33:38 +0100 >>> Gavin McDonald wrote: >>> Hi All, The nightly builds at https://ci2.apache.org/#/builders/58 are using up much unnecessary disk space on the nightlies.apache.org server. Currently Openoffice alone is using more than 1TB - all due to these nightly builds. Over 600GB are the linux64 snapshots and the rest are the linsnap* ones. Many many of these snapshots are identical to previous ones, but because the date of the build is included then they are just repeated each day. Even if no commits for weeks there is multi GB tars and debs being uploaded each day. This seems a waste. Not only this, but no snapshots are being cleaned up, we have snapshots dating back nearly a year just sitting there. Lets clean this up and be smarter going forwards. I would like to see these nightlies changed :- 1. Change to run weekly instead of daily. 2. Instead of, or in addition to 1, build and upload by commit trigger. 3. Clean up snapshots older than 1 month. Thoughts please >>> Agreed - the nightlies run well, as far as my use of them uses their >>> features. A weekly build would be good, and no need to have extended >>> availability of older builds further back than (say) four weeks - four/five >>> weeks might be simpler to program than a month. >> A nightly build of trunk should run every day *if* there was a code >> change. This is important for developers to see if something they >> committed does break the build process. > I had (silently) assumed this would happen. I thought it a detail in the > overall picture of removing and re-ordering the nightlies. No, Gavin wrote, that it doesn't happen... And a nightly is a nightly. Otherwise it would be a weekly? ;-) Regards, Matthias > > Rory > > >> The other branches (AOO42X, AOO41X) only build a snapshot once a week. >> >> Four weeks are a good period to have archived if a regression occurs. >> >> @Gavin: We discussed at some point, if we can trigger nightlies only if >> there was a commit (change in git hash) but we didn't know how to do it. >> So I would prefer 2. instead of 1. and concur with 3. >> >> Regards, >> >> Matthias >> > smime.p7s Description: S/MIME Cryptographic Signature
Re: Nightly Builds
On Sat, 21 Jan 2023 14:13:54 +0100 Matthias Seidel wrote: > Hi Rory, > > Am 21.01.23 um 13:52 schrieb Rory O'Farrell: > > On Sat, 21 Jan 2023 13:33:38 +0100 > > Gavin McDonald wrote: > > > >> Hi All, > >> > >> The nightly builds at https://ci2.apache.org/#/builders/58 are using up > >> much unnecessary > >> disk space on the nightlies.apache.org server. > >> > >> Currently Openoffice alone is using more than 1TB - all due to these > >> nightly builds. > >> Over 600GB are the linux64 snapshots and the rest are the linsnap* ones. > >> > >> Many many of these snapshots are identical to previous ones, but because > >> the date of the build is included then they are just repeated each day. > >> Even if no commits for weeks there is multi GB tars and debs being uploaded > >> each day. > >> > >> This seems a waste. > >> > >> Not only this, but no snapshots are being cleaned up, we have snapshots > >> dating back nearly a year just sitting there. > >> > >> Lets clean this up and be smarter going forwards. > >> > >> I would like to see these nightlies changed :- > >> > >> 1. Change to run weekly instead of daily. > >> 2. Instead of, or in addition to 1, build and upload by commit trigger. > >> 3. Clean up snapshots older than 1 month. > >> > >> Thoughts please > >> > > Agreed - the nightlies run well, as far as my use of them uses their > > features. A weekly build would be good, and no need to have extended > > availability of older builds further back than (say) four weeks - four/five > > weeks might be simpler to program than a month. > > A nightly build of trunk should run every day *if* there was a code > change. This is important for developers to see if something they > committed does break the build process. I had (silently) assumed this would happen. I thought it a detail in the overall picture of removing and re-ordering the nightlies. Rory > The other branches (AOO42X, AOO41X) only build a snapshot once a week. > > Four weeks are a good period to have archived if a regression occurs. > > @Gavin: We discussed at some point, if we can trigger nightlies only if > there was a commit (change in git hash) but we didn't know how to do it. > So I would prefer 2. instead of 1. and concur with 3. > > Regards, > > Matthias > > > > -- Rory O'Farrell - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Nightly Builds
Hi Rory, Am 21.01.23 um 13:52 schrieb Rory O'Farrell: > On Sat, 21 Jan 2023 13:33:38 +0100 > Gavin McDonald wrote: > >> Hi All, >> >> The nightly builds at https://ci2.apache.org/#/builders/58 are using up >> much unnecessary >> disk space on the nightlies.apache.org server. >> >> Currently Openoffice alone is using more than 1TB - all due to these >> nightly builds. >> Over 600GB are the linux64 snapshots and the rest are the linsnap* ones. >> >> Many many of these snapshots are identical to previous ones, but because >> the date of the build is included then they are just repeated each day. >> Even if no commits for weeks there is multi GB tars and debs being uploaded >> each day. >> >> This seems a waste. >> >> Not only this, but no snapshots are being cleaned up, we have snapshots >> dating back nearly a year just sitting there. >> >> Lets clean this up and be smarter going forwards. >> >> I would like to see these nightlies changed :- >> >> 1. Change to run weekly instead of daily. >> 2. Instead of, or in addition to 1, build and upload by commit trigger. >> 3. Clean up snapshots older than 1 month. >> >> Thoughts please >> > Agreed - the nightlies run well, as far as my use of them uses their > features. A weekly build would be good, and no need to have extended > availability of older builds further back than (say) four weeks - four/five > weeks might be simpler to program than a month. A nightly build of trunk should run every day *if* there was a code change. This is important for developers to see if something they committed does break the build process. The other branches (AOO42X, AOO41X) only build a snapshot once a week. Four weeks are a good period to have archived if a regression occurs. @Gavin: We discussed at some point, if we can trigger nightlies only if there was a commit (change in git hash) but we didn't know how to do it. So I would prefer 2. instead of 1. and concur with 3. Regards, Matthias > smime.p7s Description: S/MIME Cryptographic Signature
Re: Nightly Builds
On Sat, 21 Jan 2023 13:33:38 +0100 Gavin McDonald wrote: > Hi All, > > The nightly builds at https://ci2.apache.org/#/builders/58 are using up > much unnecessary > disk space on the nightlies.apache.org server. > > Currently Openoffice alone is using more than 1TB - all due to these > nightly builds. > Over 600GB are the linux64 snapshots and the rest are the linsnap* ones. > > Many many of these snapshots are identical to previous ones, but because > the date of the build is included then they are just repeated each day. > Even if no commits for weeks there is multi GB tars and debs being uploaded > each day. > > This seems a waste. > > Not only this, but no snapshots are being cleaned up, we have snapshots > dating back nearly a year just sitting there. > > Lets clean this up and be smarter going forwards. > > I would like to see these nightlies changed :- > > 1. Change to run weekly instead of daily. > 2. Instead of, or in addition to 1, build and upload by commit trigger. > 3. Clean up snapshots older than 1 month. > > Thoughts please > Agreed - the nightlies run well, as far as my use of them uses their features. A weekly build would be good, and no need to have extended availability of older builds further back than (say) four weeks - four/five weeks might be simpler to program than a month. -- Rory O'Farrell - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Nightly Builds
Hi All, The nightly builds at https://ci2.apache.org/#/builders/58 are using up much unnecessary disk space on the nightlies.apache.org server. Currently Openoffice alone is using more than 1TB - all due to these nightly builds. Over 600GB are the linux64 snapshots and the rest are the linsnap* ones. Many many of these snapshots are identical to previous ones, but because the date of the build is included then they are just repeated each day. Even if no commits for weeks there is multi GB tars and debs being uploaded each day. This seems a waste. Not only this, but no snapshots are being cleaned up, we have snapshots dating back nearly a year just sitting there. Lets clean this up and be smarter going forwards. I would like to see these nightlies changed :- 1. Change to run weekly instead of daily. 2. Instead of, or in addition to 1, build and upload by commit trigger. 3. Clean up snapshots older than 1 month. Thoughts please -- *Gavin McDonald* Systems Administrator ASF Infrastructure Team
Re: [ANNOUNCE] Maintenance Window on Forums and Wiki
Hi Charlie, Do you refer to the problem with the missing SIGNATURE_REQUIRED string missing in this thread [1]. If a user enters the proper information in this field does the registration work? [1] https://lists.apache.org/thread/zj3m2q4bk0z5htt97npbk28dcw04po4n Thanks, Carl On 1/20/23 11:36 AM, casa...@email.it wrote: It seems that nobody cares about the Italian forum... - Messaggio originale - Da: casa...@email.it A: "dev" Cc: "users" Inviato: Mercoledì, 11 gennaio 2023 16:42:52 Oggetto: Re: [ANNOUNCE] Maintenance Window on Forums and Wiki I was hoping that the opportunity was good to fix the registration form of the Italian forum, but it was not so. From the Italian forum it seems you don't care about anyone... - Messaggio originale - Da: "Dave Fisher" A: "dev" , us...@openoffice.apache.org Inviato: Martedì, 10 gennaio 2023 18:57:25 Oggetto: [ANNOUNCE] Maintenance Window on Forums and Wiki ASF Infrastructure Scheduled routine maintenance, OpenOffice forums and wiki starting at Jan 11, 2023 - 11:00AM UTC and ending at Jan 11, 2023 - 11:15AM UTC. The server hosting the OpenOffice forums and Wiki will be undergoing routine maintenance on Wednesday the 11th of January at 11AM UTC. We expect this operation to last 10-15 minutes at most, during which the OpenOffice forums and wiki will be unavailable. Please send an email to d...@openoffice.org if there is trouble with either website after the end of this window. - 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 - 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
