Re: INSTALL.MacOSX - last bit of qt4 piece

Am 11.04.2024 um 18:36 schrieb Pavel Sanda : > > Hi Stephan, > > our last piece item in TODO.killqt4 is to update INSTALL.MacOSX. > Would you have time to have a look on that these days? I’ll have a look. Stephan -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/li

INSTALL.MacOSX - last bit of qt4 piece

Hi Stephan, our last piece item in TODO.killqt4 is to update INSTALL.MacOSX. Would you have time to have a look on that these days? Pavel -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: [LyX/2.3.x] Qt4 compilable again

On Thu, Nov 24, 2022 at 04:21:04PM +, José Matos wrote: > On Wed, 2022-11-23 at 22:47 +0100, Pavel Sanda wrote: > > +#else > > +#define qDegreesToRadians(degree) (degree * (M_PI / 180)) > > +#endif > > Probably here it does not mater but in general the safer version would > be to move the pare

Re: [LyX/2.3.x] Qt4 compilable again

On Fri, Nov 25, 2022 at 12:17:03AM +0100, Jean-Marc Lasgouttes wrote: > Le 24/11/2022 à 17:21, José Matos a écrit : > > Probably here it does not mater but in general the safer version would > > be to move the parenthesis from right to let, i.e. > > > > (degree) * M_PI/180 > > > > I am thinking

Re: [LyX/2.3.x] Qt4 compilable again

Le 24/11/2022 à 17:21, José Matos a écrit : Probably here it does not mater but in general the safer version would be to move the parenthesis from right to let, i.e. (degree) * M_PI/180 I am thinking about examples like qDegreesToRadians(a+b) I did that on master. Note that I have doubts th

Re: [LyX/2.3.x] Qt4 compilable again

On Wed, 2022-11-23 at 22:47 +0100, Pavel Sanda wrote: > +#else > +#define qDegreesToRadians(degree) (degree * (M_PI / 180)) > +#endif Probably here it does not mater but in general the safer version would be to move the parenthesis from right to let, i.e. (degree) * M_PI/180 I am thinking about

Re: [LyX features/remotes/origin/killqt4] Amend ac248e39, get rid of Qt4 code also in cmake build

Am Sat, 19 Nov 2022 21:34:41 +0100 schrieb Kornel Benko : > > If that doesn't work, do you want me to try to push the commit you made? > > > > Scott > > Yes please. > Thanks. Kornel pgpTupO85XP9P.pgp Description: Digitale Signatur von OpenPGP -- lyx-devel mailing list lyx-devel@li

Re: [LyX features/remotes/origin/killqt4] Amend ac248e39, get rid of Qt4 code also in cmake build

On Sat, Nov 19, 2022 at 09:34:41PM +0100, Kornel Benko wrote: > Am Sat, 19 Nov 2022 15:13:41 -0500 > schrieb Scott Kostyshak : > > > On Sat, Nov 19, 2022 at 07:09:51PM +0100, Kornel Benko wrote: > > > Am Sat, 19 Nov 2022 11:50:44 -0500 > > > schrieb Scott Kostyshak : > > > > > > > git branch ki

Re: [LyX features/remotes/origin/killqt4] Amend ac248e39, get rid of Qt4 code also in cmake build

Am Sat, 19 Nov 2022 15:13:41 -0500 schrieb Scott Kostyshak : > On Sat, Nov 19, 2022 at 07:09:51PM +0100, Kornel Benko wrote: > > Am Sat, 19 Nov 2022 11:50:44 -0500 > > schrieb Scott Kostyshak : > > > > > git branch killqt4 --set-upstream-to features/killqt4 > > > > I get > > fatal: branch 'k

Re: [LyX features/remotes/origin/killqt4] Amend ac248e39, get rid of Qt4 code also in cmake build

On Sat, Nov 19, 2022 at 07:09:51PM +0100, Kornel Benko wrote: > Am Sat, 19 Nov 2022 11:50:44 -0500 > schrieb Scott Kostyshak : > > > git branch killqt4 --set-upstream-to features/killqt4 > > I get > fatal: branch 'killqt4' does not exist > Exit 128 > > > Sorry, I am lost. I cannot even remove t

Re: [LyX features/remotes/origin/killqt4] Amend ac248e39, get rid of Qt4 code also in cmake build

Am Sat, 19 Nov 2022 11:50:44 -0500 schrieb Scott Kostyshak : > git branch killqt4 --set-upstream-to features/killqt4 I get fatal: branch 'killqt4' does not exist Exit 128 Sorry, I am lost. I cannot even remove the wrong branch. $ git branch -r | grep kill origin/kill-print origin/kill-tex

Re: [LyX features/remotes/origin/killqt4] Amend ac248e39, get rid of Qt4 code also in cmake build

t; > at 1a46a146e45984091ef1b3168a7ba7b940a14b09 (commit) > > > > > > > > > > - Log > > > > > - > > > > > > > > > > commit 1a46a146e45984091ef1b3168a7ba7b940a14b09 > > > > > Author: Kornel Benko &g

Re: [LyX features/remotes/origin/killqt4] Amend ac248e39, get rid of Qt4 code also in cmake build

; > > > > > > > commit 1a46a146e45984091ef1b3168a7ba7b940a14b09 > > > > Author: Kornel Benko > > > > Date: Sat Nov 19 14:45:03 2022 +0100 > > > > > > > > Amend ac248e39, get rid of Qt4 code also in cmake build

Re: New features/killqt4 branch (was: Re: [Qt4???] Re: [PATCH] Show branches from master document in branch inset dialog)

Le 19/11/2022 à 11:38, Jürgen Spitzmüller a écrit : Am Freitag, dem 18.11.2022 um 17:33 +0100 schrieb Jean-Marc Lasgouttes: What can you do to help? * have look at the diff in src to spot what I broke Looks good from what I can tell. Thanks for checking. * and look at KILLQT4 annotations t

Re: [LyX features/remotes/origin/killqt4] Amend ac248e39, get rid of Qt4 code also in cmake build

> > Date: Sat Nov 19 14:45:03 2022 +0100 > > > > > > Amend ac248e39, get rid of Qt4 code also in cmake build > > > > I seem to be unable to commit to origin/killqt4. > > I think it is on the "features" repository: features/killqt4. >

Re: [LyX features/remotes/origin/killqt4] Amend ac248e39, get rid of Qt4 code also in cmake build

ommit) > > > > - Log - > > > > commit 1a46a146e45984091ef1b3168a7ba7b940a14b09 > > Author: Kornel Benko > > Date: Sat Nov 19 14:45:03 2022 +0100 > > > > Amend ac248e39, get rid of Qt4 code also in cmake bu

Re: [LyX features/remotes/origin/killqt4] Amend ac248e39, get rid of Qt4 code also in cmake build

> > commit 1a46a146e45984091ef1b3168a7ba7b940a14b09 > Author: Kornel Benko > Date: Sat Nov 19 14:45:03 2022 +0100 > > Amend ac248e39, get rid of Qt4 code also in cmake build I seem to be unable to commit to origin/killqt4. Kornel pgpyY9FJgHrk9.pgp Description: Digitale Signatur von

Re: New features/killqt4 branch (was: Re: [Qt4???] Re: [PATCH] Show branches from master document in branch inset dialog)

Am Freitag, dem 18.11.2022 um 17:33 +0100 schrieb Jean-Marc Lasgouttes: > What can you do to help? > * have look at the diff in src to spot what I broke Looks good from what I can tell. > * and look at KILLQT4 annotations to see whethe rsome of them are in > your ballpark > * look for things to

Re: New features/killqt4 branch (was: Re: [Qt4???] Re: [PATCH] Show branches from master document in branch inset dialog)

Le 18/11/2022 à 18:03, Scott Kostyshak a écrit : What can you do to help? * have look at the diff in src to spot what I broke * and look at KILLQT4 annotations to see whethe rsome of them are in your ballpark * look for things to do in TODO.killqt4 I think this was meant for Jürgen, but to be c

Re: New features/killqt4 branch (was: Re: [Qt4???] Re: [PATCH] Show branches from master document in branch inset dialog)

nd forward)? > > > > No. I think now is the time to do it. > > I created a new branch killqt4 Judging by the name, I see that Qt4 has caused you some pain :) > that removes #ifdefs in src and adds a TODO > list in TODO.killqt4. Great, Thank you for doing this on a branch!

New features/killqt4 branch (was: Re: [Qt4???] Re: [PATCH] Show branches from master document in branch inset dialog)

Le 17/11/2022 à 07:34, Jürgen Spitzmüller a écrit : Am Mittwoch, dem 16.11.2022 um 11:11 -0500 schrieb Scott Kostyshak: Does anyone object then to supporting only Qt5 for 2.4.0 (and forward)? No. I think now is the time to do it. I created a new branch killqt4 that removes #ifdefs in src and

Re: [Qt4???] Re: [PATCH] Show branches from master document in branch inset dialog

Am Mittwoch, dem 16.11.2022 um 11:11 -0500 schrieb Scott Kostyshak: > Does anyone object then to supporting only Qt5 for > 2.4.0 (and forward)? No. I think now is the time to do it. -- Jürgen signature.asc Description: This is a digitally signed message part -- lyx-devel mailing list lyx-deve

Re: [Qt4???] Re: [PATCH] Show branches from master document in branch inset dialog

On Wed, Nov 16, 2022 at 06:03:04PM +0100, Jean-Marc Lasgouttes wrote: > Le 16/11/2022 à 17:57, Scott Kostyshak a écrit : > > I don't know. What do others think? Do we go all-in and drop Qt4 and do > > all the clean up now to simplify the code? That would indeed feel nice. >

Re: [Qt4???] Re: [PATCH] Show branches from master document in branch inset dialog

Le 16/11/2022 à 17:57, Scott Kostyshak a écrit : I don't know. What do others think? Do we go all-in and drop Qt4 and do all the clean up now to simplify the code? That would indeed feel nice. Or do we leave it as is, and just officially not support Qt4, so that if some (from what I under

Re: [Qt4???] Re: [PATCH] Show branches from master document in branch inset dialog

gt; > > <https://www.phoronix.com/news/Intel-i486-Linux-Possible-Drop>, though). > > > > Thanks, Thibaut. Does anyone object then to supporting only Qt5 for > > 2.4.0 (and forward)? > > I won't object. Does this mean that we shall remove now all the #ifde

Re: [Qt4???] Re: [PATCH] Show branches from master document in branch inset dialog

I won't object. Does this mean that we shall remove now all the #ifdef pertaining to Qt4? JMarc -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: [Qt4???] Re: [PATCH] Show branches from master document in branch inset dialog

On Wed, Nov 16, 2022 at 02:37:18PM +0100, Thibaut Cuvelier wrote: > Well, if barely anyone tests with Qt 4 (I'm only using Qt 5.15), it's > already unsupported in practice and making the necessary changes would be > (1) cumbersome and (2) a waste of resources (little gain in supporting > versions

Re: [Qt4???] Re: [PATCH] Show branches from master document in branch inset dialog

> Still, I am wondering why we insist on supporting Qt4 for 2.4.0 > (especially > > > > considering that we will have to continue this game for 2+ years > after > > > > that). > > > > > > That was decided when we planned to release 2.4 at the end of 2

Re: [Qt4???] Re: [PATCH] Show branches from master document in branch inset dialog

On Tue, Oct 18, 2022 at 10:51:34AM -0400, Scott Kostyshak wrote: > On Tue, Oct 18, 2022 at 03:12:40PM +0200, Pavel Sanda wrote: > > On Fri, Oct 07, 2022 at 05:05:43PM +0200, Jean-Marc Lasgouttes wrote: > > > Still, I am wondering why we insist on supporting Qt4 for 2.4.0

Re: [Qt4???] Re: [PATCH] Show branches from master document in branch inset dialog

On Tue, Oct 18, 2022 at 06:27:00PM +0200, Jean-Marc Lasgouttes wrote: > >That was decided when we planned to release 2.4 at the end of 2019. > >It's clear we won't be able to push 2.4 even for next debian stable > >and I think we can relax Qt4 support and move on. >

Re: [Qt4???] Re: [PATCH] Show branches from master document in branch inset dialog

Le 18/10/2022 à 15:12, Pavel Sanda a écrit : On Fri, Oct 07, 2022 at 05:05:43PM +0200, Jean-Marc Lasgouttes wrote: Still, I am wondering why we insist on supporting Qt4 for 2.4.0 (especially considering that we will have to continue this game for 2+ years after that). That was decided when we

Re: [Qt4???] Re: [PATCH] Show branches from master document in branch inset dialog

On Tue, Oct 18, 2022 at 03:12:40PM +0200, Pavel Sanda wrote: > On Fri, Oct 07, 2022 at 05:05:43PM +0200, Jean-Marc Lasgouttes wrote: > > Still, I am wondering why we insist on supporting Qt4 for 2.4.0 (especially > > considering that we will have to continue this game for 2+ years

Re: [Qt4???] Re: [PATCH] Show branches from master document in branch inset dialog

On Fri, Oct 07, 2022 at 05:05:43PM +0200, Jean-Marc Lasgouttes wrote: > Still, I am wondering why we insist on supporting Qt4 for 2.4.0 (especially > considering that we will have to continue this game for 2+ years after > that). That was decided when we planned to release 2.4 at the en

[Qt4???] Re: [PATCH] Show branches from master document in branch inset dialog

Still, I am wondering why we insist on supporting Qt4 for 2.4.0 (especially considering that we will have to continue this game for 2+ years after that). I join to your wondering. And here is the patch to at least clean conditional code portions for Qt < 4.8. Yuriy F

[Qt4???] Re: [PATCH] Show branches from master document in branch inset dialog

Le 07/10/2022 à 17:02, Yuriy Skalko a écrit : Now with "(master)" suffix in combobox labels we cannot use them directly as branch names. Is is OK to disable this for Qt4 alltogether, as README says that LyX is only compilable on Qt4? This seems like an acceptable solution, if t

Re: Do we need Qt4 for LyX 2.4.0?

On Fri, 2022-07-15 at 00:34 +0200, Jean-Marc Lasgouttes wrote: > So is there one person on this list who needs Qt4 support? I can also > ask on lyx-users if needed. Although not answering your question I think that we should add a section to the release notes saying that this will be th

Re: Do we need Qt4 for LyX 2.4.0?

On Fri, Jul 15, 2022 at 12:34:37AM +0200, Jean-Marc Lasgouttes wrote: > [this is a reboot of a discussion oat developp...@lyx.org. Sorry for the > repetition] > > Hi there, > > I am currently fighting with Qt4 for getting correct line-breaking [*]. > > I had to creat

Do we need Qt4 for LyX 2.4.0?

[this is a reboot of a discussion oat developp...@lyx.org. Sorry for the repetition] Hi there, I am currently fighting with Qt4 for getting correct line-breaking [*]. I had to create a Ubuntu 18.04 virtual machine to have a working Qt4, and I do not know how this will work in 2026 when we

Jenkins build is back to normal : Build branch "master" » ubuntu-xenial-qt4-autotools #2203

https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools/2203/ -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel

Build failed in Jenkins: Build branch "master" » ubuntu-xenial-qt4-autotools #2202

https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools/2202/Changes: [kornel] FindAdv: Omit possible empty patterns -- [...truncated 735 lines...] GEN moc_GuiHyperlink.cpp GEN moc_GuiInclude.cpp GEN

Jenkins build is back to normal : Build branch "master" » ubuntu-xenial-qt4-autotools #2147

https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools/2147/ -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel

Build failed in Jenkins: Build branch "master" » ubuntu-xenial-qt4-autotools #2146

https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools/2146/-- [...truncated 704 lines...] GEN moc_DialogView.cpp GEN moc_DockView.cpp GEN moc_EmptyTable.cpp GEN moc_FancyLineEdit.cpp GEN

Jenkins build is back to normal : Build branch "master" » ubuntu-xenial-qt4-autotools #2112

https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools/2112/ -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel

Build failed in Jenkins: Build branch "master" » ubuntu-xenial-qt4-autotools #2111

https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools/2111/-- [...truncated 612 lines...] GEN ui_BranchUi.h GEN ui_BulletsUi.h GEN ui_ChangesUi.h GEN ui_ChangeTrackingUi.h GEN ui_CharacterUi.h GEN

Jenkins build is back to normal : Build branch "master" » ubuntu-xenial-qt4-autotools-extended #2274

https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools-extended/2274/ -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: Drop QT4 from master

Le 04/01/2021 à 17:25, Thibaut Cuvelier a écrit : On Mon, 4 Jan 2021 at 14:56, Jean-Marc Lasgouttes > wrote: Le 29/12/2020 à 09:42, Yuriy Skalko a écrit : > Seems like boost::regex has the same issues as std::regex: > https://www.boost.org/doc/libs/1

Re: Drop QT4 from master

On Mon, 4 Jan 2021 at 14:56, Jean-Marc Lasgouttes wrote: > Le 29/12/2020 à 09:42, Yuriy Skalko a écrit : > > Seems like boost::regex has the same issues as std::regex: > > > https://www.boost.org/doc/libs/1_75_0/libs/regex/doc/html/boost_regex/unicode.html > > > > As I understand the ICU library

Re: Drop QT4 from master

Le 29/12/2020 à 09:42, Yuriy Skalko a écrit : Seems like boost::regex has the same issues as std::regex: https://www.boost.org/doc/libs/1_75_0/libs/regex/doc/html/boost_regex/unicode.html As I understand the ICU library is the only ultimate solution for Unicode support. Qt relies on ICU, it

Re: Drop QT4 from master

Am Mon, 28 Dec 2020 19:00:26 +0100 schrieb Pavel Sanda : > On Mon, Dec 28, 2020 at 06:51:42PM +0100, Thibaut Cuvelier wrote: > > > So the question is: Can we drop support for QT4 in master? > > > Or has someone a better sollution? > > > > > > > Giv

Re: Drop QT4 from master

On Tue, Dec 29, 2020 at 12:52:20AM +0100, Jean-Marc Lasgouttes wrote: > > Sorry for letting everyone down. Wrong timing. Frankly I wouldn't do any better in these times. On Tue, Dec 29, 2020 at 11:01:51AM -0500, Richard Kimberly Heck wrote: > What is it that needs doing here? I can probably find

Re: Drop QT4 from master

Am Dienstag, dem 29.12.2020 um 12:00 -0500 schrieb Richard Kimberly Heck: > That may be ambitious, but we can try. I can certainly get another > alpha out ASAP and will do so. Thanks, much appreciated! Jürgen signature.asc Description: This is a digitally signed message part -- lyx-devel mail

Re: Drop QT4 from master

On 12/29/20 11:57 AM, Jürgen Spitzmüller wrote: Am Dienstag, dem 29.12.2020 um 11:01 -0500 schrieb Richard Kimberly Heck: What is it that needs doing here? I can probably find the time. I think what it needs most urgently is someone telling us: Stop tinkering with new pet projects (including re

Re: Drop QT4 from master

Am Dienstag, dem 29.12.2020 um 11:01 -0500 schrieb Richard Kimberly Heck: > What is it that needs doing here? I can probably find the time. I think what it needs most urgently is someone telling us: Stop tinkering with new pet projects (including refactoring), there will be no more new feature, we

Re: Drop QT4 from master

On 12/28/20 6:52 PM, Jean-Marc Lasgouttes wrote: > Le 28 décembre 2020 21:29:02 GMT+01:00, Pavel Sanda a écrit : >> It's hard to believe, but looking back at the archives we had the 2.4 >> release-manager decision in May 2019 and first alpha1 thread in June 2019 :) >> >> JMarc, what is your situat

Re: Drop QT4 from master

Could it be that this is why boost::regex was useful after all? Did we rush too fast in our joy of getting rid of it? I do not think that solving issues with crappy compilers involves going all the way in Qt's arms. Qt does have its flaws and bugs, and besides banging our head against the wall

Re: Drop QT4 from master

Am Tue, 29 Dec 2020 00:44:25 +0100 schrieb Jean-Marc Lasgouttes : > Le 28 décembre 2020 19:04:35 GMT+01:00, "Jürgen Spitzmüller" > a écrit : > >Am Montag, dem 28.12.2020 um 19:00 +0100 schrieb Pavel Sanda: > >> But this position gets weaker as we do not seem to get closer to the > >> actual rele

Re: Drop QT4 from master

Le 28 décembre 2020 21:29:02 GMT+01:00, Pavel Sanda a écrit : >It's hard to believe, but looking back at the archives we had the 2.4 >release-manager decision in May 2019 and first alpha1 thread in June 2019 :) > >JMarc, what is your situation nowadays? Is it still feasible for you >to do the rele

Re: Drop QT4 from master

Le 28 décembre 2020 19:04:35 GMT+01:00, "Jürgen Spitzmüller" a écrit : >Am Montag, dem 28.12.2020 um 19:00 +0100 schrieb Pavel Sanda: >> But this position gets weaker as we do not seem to get closer to the >> actual release, I know. > >This is what we should really aim at, actually (independent o

Re: Drop QT4 from master

actually (independent of the qt > question). Well, it's connected. If there is push towards 2.4 I'll try to defend qt4, but if we have no manpower to do it in foreseeable future, lets have refactoring hell break loose ;) It's hard to believe, but looking back at the archives we

Re: Drop QT4 from master

On Mon, 28 Dec 2020 at 19:04, Jürgen Spitzmüller wrote: > Am Montag, dem 28.12.2020 um 19:00 +0100 schrieb Pavel Sanda: > > But this position gets weaker as we do not seem to get closer to the > > actual release, I know. > > This is what we should really aim at, actually (independent of the qt >

Re: Drop QT4 from master

Am Montag, dem 28.12.2020 um 19:00 +0100 schrieb Pavel Sanda: > But this position gets weaker as we do not seem to get closer to the > actual release, I know. This is what we should really aim at, actually (independent of the qt question). Also, I seemed to remember that there was reluctance pull

Re: Drop QT4 from master

On Mon, Dec 28, 2020 at 06:51:42PM +0100, Thibaut Cuvelier wrote: > > So the question is: Can we drop support for QT4 in master? > > Or has someone a better sollution? > > > > Given that Qt 6 is now out, and that Qt 4 has been unmaintained for roughly > five years ( &g

Re: Drop QT4 from master

docstring does not help much. > > The next try is using QString. This works pretty good, but uses classes > introduced in QT5. > > The differences in lyxfind.cpp are big, so that using '#ifdef's does not > seem appropriate. > (See attached) > > So the ques

Drop QT4 from master

roduced in QT5. The differences in lyxfind.cpp are big, so that using '#ifdef's does not seem appropriate. (See attached) So the question is: Can we drop support for QT4 in master? Or has someone a better sollution? Kornel diff --git a/src/lyxfind.cpp b/src/lyxfind.cpp index 4b

Build failed in Jenkins: Build branch "master" » ubuntu-xenial-qt4-autotools-extended #2273

https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools-extended/2273/-- Started by an SCM change Building remotely on lyx-linux1 (linux) in workspace <https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autoto

Jenkins build is back to normal : Build branch "master" » ubuntu-xenial-qt4-autotools #2073

https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools/2073/ -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel

Jenkins build is back to normal : Build branch "master" » ubuntu-xenial-qt4-autotools-extended #2272

https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools-extended/2272/ -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel

Build failed in Jenkins: Build branch "master" » ubuntu-xenial-qt4-autotools #2072

https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools/2072/-- [...truncated 937 lines...] CXX FuncRequest.o CXX FuncStatus.o CXX Graph.o CXX IndicesList.o CXX InsetIterator.o CXX InsetList.o

Build failed in Jenkins: Build branch "master" » ubuntu-xenial-qt4-autotools-extended #2271

https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools-extended/2271/-- Started by an SCM change Building remotely on lyx-linux1 (linux) in workspace <https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autoto

Build failed in Jenkins: Build branch "master" » ubuntu-xenial-qt4-autotools #2071

https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools/2071/-- Started by an SCM change Building remotely on lyx-linux1 (linux) in workspace <https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools/ws/&g

Build failed in Jenkins: Build branch "master" » ubuntu-xenial-qt4-autotools-extended #2270

https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools-extended/2270/-- Started by an SCM change Building remotely on lyx-linux1 (linux) in workspace <https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autoto

Build failed in Jenkins: Build branch "master" » ubuntu-xenial-qt4-autotools #2070

https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools/2070/-- Started by an SCM change Building remotely on lyx-linux1 (linux) in workspace <https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools/ws/&g

Build failed in Jenkins: Build branch "master" » ubuntu-xenial-qt4-autotools-extended #2269

https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools-extended/2269/-- Started by an SCM change Building remotely on lyx-linux1 (linux) in workspace <https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autoto

Build failed in Jenkins: Build branch "master" » ubuntu-xenial-qt4-autotools #2069

https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools/2069/-- Started by an SCM change Building remotely on lyx-linux1 (linux) in workspace <https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools/ws/&g

Build failed in Jenkins: Build branch "master" » ubuntu-xenial-qt4-autotools #2068

https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools/2068/Changes: [sanda] Improve VCS error message when RCS is not installed. -- Started by an SCM change Building remotely on lyx-linux1 (linux) in workspace <https://ci.inria

Build failed in Jenkins: Build branch "master" » ubuntu-xenial-qt4-autotools-extended #2268

https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools-extended/2268/Changes: [sanda] Improve VCS error message when RCS is not installed. -- Started by an SCM change Building remotely on lyx-linux1 (linux) in workspace <ht

Build failed in Jenkins: Build branch "master" » ubuntu-xenial-qt4-autotools #2067

https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools/2067/Changes: [lasgouttes] Disable some Adv F&R widgets for read-only documents -- Started by an SCM change Building remotely on lyx-linux1 (linux) in workspace &l

Build failed in Jenkins: Build branch "master" » ubuntu-xenial-qt4-autotools-extended #2267

https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools-extended/2267/-- Started by an SCM change Building remotely on lyx-linux1 (linux) in workspace <https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autoto

Build failed in Jenkins: Build branch "master" » ubuntu-xenial-qt4-autotools #2066

https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools/2066/-- Started by an SCM change Building remotely on lyx-linux1 (linux) in workspace <https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools/ws/&g

Build failed in Jenkins: Build branch "master" » ubuntu-xenial-qt4-autotools-extended #2266

https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools-extended/2266/-- Started by an SCM change Building remotely on lyx-linux1 (linux) in workspace <https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autoto

Build failed in Jenkins: Build branch "master" » ubuntu-xenial-qt4-autotools #2065

https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools/2065/-- Started by an SCM change Building remotely on lyx-linux1 (linux) in workspace <https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools/ws/&g

Build failed in Jenkins: Build branch "master" » ubuntu-xenial-qt4-autotools-extended #2265

https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools-extended/2265/-- Started by an SCM change Building remotely on lyx-linux1 (linux) in workspace <https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autoto

Build failed in Jenkins: Build branch "master" » ubuntu-xenial-qt4-autotools #2064

https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools/2064/-- Started by an SCM change Building remotely on lyx-linux1 (linux) in workspace <https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools/ws/&g

Build failed in Jenkins: Build branch "master" » ubuntu-xenial-qt4-autotools-extended #2264

https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools-extended/2264/-- Started by an SCM change Building remotely on lyx-linux1 (linux) in workspace <https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autoto

Build failed in Jenkins: Build branch "master" » ubuntu-xenial-qt4-autotools #2063

https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools/2063/-- Started by an SCM change Building remotely on lyx-linux1 (linux) in workspace <https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools/ws/&g

Build failed in Jenkins: Build branch "master" » ubuntu-xenial-qt4-autotools-extended #2263

https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools-extended/2263/-- Started by an SCM change Building remotely on lyx-linux1 (linux) in workspace <https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autoto

Build failed in Jenkins: Build branch "master" » ubuntu-xenial-qt4-autotools #2062

https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools/2062/-- Started by an SCM change Building remotely on lyx-linux1 (linux) in workspace <https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools/ws/&g

Build failed in Jenkins: Build branch "master" » ubuntu-xenial-qt4-autotools-extended #2262

https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools-extended/2262/-- [...truncated 771 lines...] GEN moc_InsetParamsDialog.cpp GEN moc_InsetParamsWidget.cpp GEN moc_LayoutBox.cpp GEN moc_LengthCombo.cpp

Re: Build failed in Jenkins: Build branch "master" » ubuntu-xenial-qt4-autotools #2057

Am Mon, 30 Nov 2020 02:32:19 +0100 schrieb Kornel Benko : > Am Sun, 29 Nov 2020 22:49:48 +0100 > schrieb Jean-Marc Lasgouttes : > > > Le 29/11/2020 à 20:21, Kornel Benko a écrit : > > >> I have reverted your previous > > >> patches locally. We are not getting rid of boost here, only of regex. >

Re: Build failed in Jenkins: Build branch "master" » ubuntu-xenial-qt4-autotools #2057

Am Sun, 29 Nov 2020 22:49:48 +0100 schrieb Jean-Marc Lasgouttes : > Le 29/11/2020 à 20:21, Kornel Benko a écrit : > >> I have reverted your previous > >> patches locally. We are not getting rid of boost here, only of regex. > >> And I did not plan to make it impossible to select local boost, just

Jenkins build is back to normal : Build branch "master" » ubuntu-xenial-qt4-autotools #2058

https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools/2058/ -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: Build failed in Jenkins: Build branch "master" » ubuntu-xenial-qt4-autotools #2057

Le 29/11/2020 à 20:21, Kornel Benko a écrit : I have reverted your previous patches locally. We are not getting rid of boost here, only of regex. And I did not plan to make it impossible to select local boost, just not make it the default. I had the impression that regex was the only thing we n

Jenkins build is back to normal : Build branch "master" » ubuntu-xenial-qt4-autotools-extended #2259

https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools-extended/2259/ -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: Build failed in Jenkins: Build branch "master" » ubuntu-xenial-qt4-autotools #2057

Am Sun, 29 Nov 2020 19:28:30 +0100 schrieb Jean-Marc Lasgouttes : > Le 29/11/2020 à 18:29, Kornel Benko a écrit : > > Am Sun, 29 Nov 2020 17:50:36 +0100 (CET) > > schrieb ci-...@inria.fr: > > > >> https://ci.inria.fr/lyx/job/build-master-head/job/ub

Re: Build failed in Jenkins: Build branch "master" » ubuntu-xenial-qt4-autotools #2057

Le 29/11/2020 à 18:29, Kornel Benko a écrit : Am Sun, 29 Nov 2020 17:50:36 +0100 (CET) schrieb ci-...@inria.fr: https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools/2057/-- ... Should be fixed. Please do not fix autoconf

Re: Build failed in Jenkins: Build branch "master" » ubuntu-xenial-qt4-autotools #2057

Am Sun, 29 Nov 2020 17:50:36 +0100 (CET) schrieb ci-...@inria.fr: > https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools/2057/-- ... Should be fixed. Kornel pgpzRyRbJldtr.pgp Description: Digitale Signatur von Open

Build failed in Jenkins: Build branch "master" » ubuntu-xenial-qt4-autotools #2057

https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools/2057/-- [...truncated 8 lines...] Cloning repository git://git.lyx.org/lyx.git > git init > <https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-aut

Re: Build failed in Jenkins: Build branch "master" » ubuntu-xenial-qt4-autotools-extended #2258

Am Sun, 29 Nov 2020 11:26:40 +0100 (CET) schrieb ci-...@inria.fr: > checking for main in -lole32... no > checking whether to use included boost library... yes > checking for grep that handles long lines and -e... /bin/grep Apparently wrong, we still allow '--with-included-boost' Kornel

Build failed in Jenkins: Build branch "master" » ubuntu-xenial-qt4-autotools-extended #2258

https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools-extended/2258/-- [...truncated 14 lines...] > git config remote.origin.url git://git.lyx.org/lyx.git # timeout=10 Fetching upstream changes from git://git.lyx.org/lyx.git &g

Jenkins build is back to normal : Build branch "master" » ubuntu-xenial-qt4-autotools-extended #2257

https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools-extended/2257/ -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel

  1   2   3   4   5   6   7   8   9   10   >