Re: [PATCH 24/24] gnu: qt: Update qt to 5.7.0.

[Leo Famulari]

On Sat, Aug 20, 2016 at 09:50:51PM +0200, David Craven wrote:
> I fixed all regression except vlc and avidemux (locally). I'll have to
> do some more debugging tomorrow. Forcing --std=gnu++11 worked in all
> other cases. With the release of vlc 3 eminent, would it be acceptable
> to use qt-4 with vlc 2.2.4 (if I don't manage to fix it)? That's what
> arch linux is doing currently - and forcing --std=gnu++98, since
> they're on gcc6.

My interpretation of the Qt security policy is that qt-4 is unsupported.

"What Version of Qt are Supported?

Fixes are only guaranteed to be provided for:

The latest released version.

The preceding minor version.

Fixes for earlier versions (such as 4.8, 5.0, etc.) may be provided,
but the qt-project makes no commitment to do so. Other groups such
as Digia may choose to make such fixes available, but that is
outside the scope of the qt-project."

source: https://wiki.qt.io/Qt_project_security_policy

Re: [PATCH 24/24] gnu: qt: Update qt to 5.7.0.

[Efraim Flashner]

On Sat, Aug 20, 2016 at 09:50:51PM +0200, David Craven wrote:
> I fixed all regression except vlc and avidemux (locally). I'll have to
> do some more debugging tomorrow. Forcing --std=gnu++11 worked in all
> other cases. With the release of vlc 3 eminent, would it be acceptable
> to use qt-4 with vlc 2.2.4 (if I don't manage to fix it)? That's what
> arch linux is doing currently - and forcing --std=gnu++98, since
> they're on gcc6.
> 

you could also try using regular qt, that's still on 5.6.1-1

-- 
Efraim Flashner      אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Re: [PATCH 24/24] gnu: qt: Update qt to 5.7.0.

[David Craven]

I fixed all regression except vlc and avidemux (locally). I'll have to
do some more debugging tomorrow. Forcing --std=gnu++11 worked in all
other cases. With the release of vlc 3 eminent, would it be acceptable
to use qt-4 with vlc 2.2.4 (if I don't manage to fix it)? That's what
arch linux is doing currently - and forcing --std=gnu++98, since
they're on gcc6.

Re: [PATCH 24/24] gnu: qt: Update qt to 5.7.0.

[David Craven]

Are we still using gcc 4.9 as our default compiler? I think that some
of the build failures could be caused by that. qt 5.7 requires a c11
compiler and gcc 4.9 still defaults to the c99 standard. Any
dependency on qt 5.7 also needs to be compiled with a c11 compiler.

Are there plans to upgrade the default gcc? I look into fixing the
packages temporarily.

Re: [PATCH 24/24] gnu: qt: Update qt to 5.7.0.

[David Craven]

Yes, would have probably been better. I got sidetracked today, but I intend
to get it fixed over the weekend.

On Aug 19, 2016 8:42 PM, "Mark H Weaver"  wrote:

> David Craven  writes:
>
> >> Thank you for all of this!  Hydra indicates that there are some
> >> regressions.  Can you take a look?
> >>
> >>   https://hydra.gnu.org/eval/109084#tabs-now-fail
> >>   https://hydra.gnu.org/eval/109084#tabs-new
> >
> > Ah, now I understand where the fun in distributing starts =P It may
> > take me a while... Aren't minor releases supposed to be backwards
> > compatible?
>
> I don't know, ask the Qt developers.  Anyway, it's probably better to do
> these kinds of upgrades on a separate branch to allow regressions to be
> fixed without leaving 'master' broken in the meantime.  We can ask hydra
> to build another branch and check for regressions there before merging
> to master.
>
>   Mark
>

Re: [PATCH 24/24] gnu: qt: Update qt to 5.7.0.

[Mark H Weaver]

David Craven  writes:

>> Thank you for all of this!  Hydra indicates that there are some
>> regressions.  Can you take a look?
>>
>>   https://hydra.gnu.org/eval/109084#tabs-now-fail
>>   https://hydra.gnu.org/eval/109084#tabs-new
>
> Ah, now I understand where the fun in distributing starts =P It may
> take me a while... Aren't minor releases supposed to be backwards
> compatible?

I don't know, ask the Qt developers.  Anyway, it's probably better to do
these kinds of upgrades on a separate branch to allow regressions to be
fixed without leaving 'master' broken in the meantime.  We can ask hydra
to build another branch and check for regressions there before merging
to master.

  Mark

Re: [PATCH 24/24] gnu: qt: Update qt to 5.7.0.

[David Craven]

> Thank you for all of this!  Hydra indicates that there are some
> regressions.  Can you take a look?
>
>   https://hydra.gnu.org/eval/109084#tabs-now-fail
>   https://hydra.gnu.org/eval/109084#tabs-new

Ah, now I understand where the fun in distributing starts =P It may
take me a while... Aren't minor releases supposed to be backwards
compatible?

Re: [PATCH 24/24] gnu: qt: Update qt to 5.7.0.

[Mark H Weaver]

Hi David,

David Craven  writes:

> * gnu/packages/qt.scm
>   (qtbase): Update it.
>   (qtsvg): Update it.
>   (qtimageformats): Update it.
>   (qtx11extras): Update it.
>   (qtxmlpatterns): Update it.
>   (qtdeclarative): Update it.
>   (qtconnectivity): Update it.
>   (qtwebsockets): Update it.
>   (qtsensors): Update it.
>   (qtmultimedia): Update it.
>   (qtwayland): Update it.
>   (qtserialport): Update it.
>   (qtwebchannel): Update it.
>   (qtlocation): Update it.
>   (qttools): Update it.
>   (qtscript): Update it.
>   (qtquickcontrols): Update it.
>   (qtquickcontrols2): Update it.
>   (qtgraphicaleffects): Update it.

Thank you for all of this!  Hydra indicates that there are some
regressions.  Can you take a look?

  https://hydra.gnu.org/eval/109084#tabs-now-fail
  https://hydra.gnu.org/eval/109084#tabs-new

  Mark

Re: [PATCH 24/24] gnu: qt: Update qt to 5.7.0.

[Danny Milosavljevic]

LGTM!