927197 – dev-qt/*-6.6.2: stabilize on arm64

Bug 927197 - dev-qt/*-6.6.2: stabilize on arm64

Summary: dev-qt/*-6.6.2: stabilize on arm64

Status:	RESOLVED FIXED

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Stabilization (show other bugs)
Hardware:	ARM64 Linux

Importance:	Normal normal (vote)
Assignee:	Qt Bug Alias

URL:
Whiteboard:
Keywords:	CC-ARCHES

Depends on:
Blocks:

Reported:	2024-03-17 12:57 UTC by Piotr Kubaj
Modified:	2024-03-22 06:31 UTC (History)
CC List:	4 users (show)

See Also:
Package list:	dev-qt/qt-docs-6.6.2_p202402121133 arm64 dev-qt/qt5compat-6.6.2 arm64 dev-qt/qtbase-6.6.2 arm64 dev-qt/qtcharts-6.6.2 arm64 dev-qt/qtconnectivity-6.6.2 arm64 dev-qt/qtdeclarative-6.6.2-r1 arm64 dev-qt/qtimageformats-6.6.2 arm64 dev-qt/qtmultimedia-6.6.2 arm64 dev-qt/qtpositioning-6.6.2 arm64 dev-qt/qtquick3d-6.6.2 arm64 dev-qt/qtquicktimeline-6.6.2 arm64 dev-qt/qtsensors-6.6.2 arm64 dev-qt/qtserialport-6.6.2 arm64 dev-qt/qtshadertools-6.6.2 arm64 dev-qt/qtspeech-6.6.2 arm64 dev-qt/qtsvg-6.6.2 arm64 dev-qt/qttools-6.6.2 arm64 dev-qt/qttranslations-6.6.2 arm64 dev-qt/qtwayland-6.6.2-r1 arm64 dev-qt/qtwebchannel-6.6.2 arm64 dev-qt/qtwebengine-6.6.2 arm64 dev-qt/qtwebsockets-6.6.2 arm64
Runtime testing required:	---

Flags:	nattka: sanity-check+

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Piotr Kubaj 2024-03-17 12:57:16 UTC

ctest -j 6 --test-load 6 -E (tst_seatv4|tst_surface|tst_xdgdecorationv1)
Test project /var/tmp/portage/dev-qt/qtwayland-6.6.2-r1/work/qtwayland-everywhere-src-6.6.2_build
      Start  1: tst_client
 1/19 Test  #1: tst_client .......................   Passed    3.12 sec
      Start  2: tst_clientextension
 2/19 Test  #2: tst_clientextension ..............   Passed    0.78 sec
      Start  3: tst_wayland_cursor
 3/19 Test  #3: tst_wayland_cursor ...............   Passed    0.73 sec
      Start  4: tst_datadevicev1
 4/19 Test  #4: tst_datadevicev1 .................   Passed    2.18 sec
      Start  5: tst_client_fullscreenshellv1
 5/19 Test  #5: tst_client_fullscreenshellv1 .....   Passed    0.56 sec
      Start  6: tst_client_iviapplication
 6/19 Test  #6: tst_client_iviapplication ........   Passed    0.77 sec
      Start  7: tst_nooutput
      Start  8: tst_output
 7/19 Test  #7: tst_nooutput .....................   Passed    0.49 sec
      Start  9: tst_primaryselectionv1
      Start 10: tst_wl_reconnect
 8/19 Test  #8: tst_output .......................   Passed    1.87 sec
      Start 11: tst_seatv7
      Start 12: tst_seat
 9/19 Test  #9: tst_primaryselectionv1 ...........   Passed    1.52 sec
      Start 13: tst_tabletv2
      Start 14: tst_wlconnect
10/19 Test #10: tst_wl_reconnect .................   Passed    1.54 sec
      Start 15: tst_xdgoutput
      Start 16: tst_xdgshell
11/19 Test #14: tst_wlconnect ....................   Passed    0.17 sec
      Start 17: tst_scaling
12/19 Test #11: tst_seatv7 .......................   Passed    0.85 sec
      Start 18: tst_multithreaded
13/19 Test #15: tst_xdgoutput ....................   Passed    1.11 sec
      Start 19: tst_inputcontext
14/19 Test #17: tst_scaling ......................   Passed    0.99 sec
15/19 Test #18: tst_multithreaded ................   Passed    0.50 sec
16/19 Test #13: tst_tabletv2 .....................   Passed    3.68 sec
17/19 Test #16: tst_xdgshell .....................   Passed    3.92 sec
18/19 Test #12: tst_seat .........................   Passed    4.85 sec
19/19 Test #19: tst_inputcontext .................   Passed    6.10 sec

100% tests passed, 0 tests failed out of 19

Label Time Summary:
tests/auto/client/client/tst_client                                 =   3.12 sec*proc (1 test)
tests/auto/client/clientextension/tst_clientextension               =   0.78 sec*proc (1 test)
tests/auto/client/cursor/tst_wayland_cursor                         =   0.73 sec*proc (1 test)
tests/auto/client/datadevicev1/tst_datadevicev1                     =   2.18 sec*proc (1 test)
tests/auto/client/fullscreenshellv1/tst_client_fullscreenshellv1    =   0.56 sec*proc (1 test)
tests/auto/client/inputcontext/tst_inputcontext                     =   6.10 sec*proc (1 test)
tests/auto/client/iviapplication/tst_client_iviapplication          =   0.77 sec*proc (1 test)
tests/auto/client/multithreaded/tst_multithreaded                   =   0.50 sec*proc (1 test)
tests/auto/client/nooutput/tst_nooutput                             =   0.49 sec*proc (1 test)
tests/auto/client/output/tst_output                                 =   1.87 sec*proc (1 test)
tests/auto/client/primaryselectionv1/tst_primaryselectionv1         =   1.52 sec*proc (1 test)
tests/auto/client/reconnect/tst_wl_reconnect                        =   1.54 sec*proc (1 test)
tests/auto/client/scaling/tst_scaling                               =   0.99 sec*proc (1 test)
tests/auto/client/seat/tst_seat                                     =   4.85 sec*proc (1 test)
tests/auto/client/seatv7/tst_seatv7                                 =   0.85 sec*proc (1 test)
tests/auto/client/tabletv2/tst_tabletv2                             =   3.68 sec*proc (1 test)
tests/auto/client/wl_connect/tst_wlconnect                          =   0.17 sec*proc (1 test)
tests/auto/client/xdgoutput/tst_xdgoutput                           =   1.11 sec*proc (1 test)
tests/auto/client/xdgshell/tst_xdgshell                             =   3.92 sec*proc (1 test)

Total Test time (real) =  17.57 sec
 * Tests succeeded.

Reproducible: Always

Comment 1 NATTkA bot gentoo-dev

2024-03-17 13:00:11 UTC Comment hidden (obsolete)

Sanity check failed:

> dev-qt/qtwayland-6.6.2-r1
>   depend arm64 stable profile default/linux/arm64/17.0 (8 total)
>     ~dev-qt/qtbase-6.6.2:6[accessibility,gui,opengl,vulkan]
>     ~dev-qt/qtdeclarative-6.6.2:6
>   depend arm64 dev profile default/linux/arm64/17.0/hardened/selinux (2 total)
>     ~dev-qt/qtbase-6.6.2:6[accessibility,gui,opengl,vulkan]
>     ~dev-qt/qtdeclarative-6.6.2:6
>   rdepend arm64 stable profile default/linux/arm64/17.0 (8 total)
>     ~dev-qt/qtbase-6.6.2:6[accessibility,gui,opengl,vulkan]
>     ~dev-qt/qtdeclarative-6.6.2:6
>   rdepend arm64 dev profile default/linux/arm64/17.0/hardened/selinux (2 total)
>     ~dev-qt/qtbase-6.6.2:6[accessibility,gui,opengl,vulkan]
>     ~dev-qt/qtdeclarative-6.6.2:6

Comment 2 NATTkA bot gentoo-dev

2024-03-17 13:04:09 UTC Comment hidden (obsolete)

Unable to check for sanity:

> no match for package: dev-qt/qtbase-6.6.2-r1

Comment 3 NATTkA bot gentoo-dev

2024-03-17 15:12:12 UTC Comment hidden (obsolete)

Sanity check failed:

> dev-qt/qtdeclarative-6.6.2-r1
>   bdepend arm64 stable profile default/linux/arm64/17.0 (8 total)
>     ~dev-qt/qtshadertools-6.6.2:6
>   bdepend arm64 dev profile default/linux/arm64/17.0/hardened/selinux (2 total)
>     ~dev-qt/qtshadertools-6.6.2:6
> dev-qt/qtbase-6.6.2
>   pdepend arm64 stable profile default/linux/arm64/17.0 (8 total)
>     ~dev-qt/qttranslations-6.6.2:6
>   pdepend arm64 dev profile default/linux/arm64/17.0/hardened/selinux (2 total)
>     ~dev-qt/qttranslations-6.6.2:6

Comment 4 NATTkA bot gentoo-dev

2024-03-17 15:24:13 UTC Comment hidden (obsolete)

Sanity check failed:

> dev-qt/qttranslations-6.6.2
>   bdepend arm64 stable profile default/linux/arm64/17.0 (8 total)
>     ~dev-qt/qttools-6.6.2:6[linguist]
>   bdepend arm64 dev profile default/linux/arm64/17.0/hardened/selinux (2 total)
>     ~dev-qt/qttools-6.6.2:6[linguist]

Comment 5 NATTkA bot gentoo-dev

2024-03-17 15:40:15 UTC Comment hidden (obsolete)

All sanity-check issues have been resolved

Comment 6 Andreas Sturmlechner gentoo-dev

2024-03-17 21:04:58 UTC

Why do you want to stabilise libraries without any need of a reverse dependency (yet)?

Comment 7 Piotr Kubaj 2024-03-17 21:08:29 UTC

I actually do use fcitx-qt, but since it's not even marked stable on amd64, I still leave it manually keyworded.

Comment 8 Andreas Sturmlechner gentoo-dev

2024-03-17 21:09:25 UTC

app-i18n/fcitx-qt itself is not stable on *any* arch.

Comment 9 Andreas Sturmlechner gentoo-dev

2024-03-17 21:11:43 UTC

I mean, ultimately will be up to qt proj but I think this would be better done in a coordinated way with potentially other arches' (in need of) stabilisation to not endup with a hotchpotch of different stable keywords within dev-qt/*.

Comment 10 Piotr Kubaj 2024-03-17 21:22:18 UTC

(In reply to Andreas Sturmlechner from comment #8)
> app-i18n/fcitx-qt itself is not stable on *any* arch.

Yes, I know, this is why I mentioned that I enable it locally myself.

Comment 11 Ionen Wolkens gentoo-dev

2024-03-18 04:07:29 UTC

(In reply to Andreas Sturmlechner from comment #6)
> Why do you want to stabilise libraries without any need of a reverse
> dependency (yet)?
There actually are Qt6 revdeps, but USE=qt6 is use.stable.masked "until" this is stabled. So stabling for arm64 been something I meant to do sooner or later so I can start dropping these (want to clear these for every arches where Qt5 was stable).

If I try to remove it, pkgcheck tells me that at least the following stable packages are optionally using qt6:

    app-crypt/gpgme
    app-crypt/qca
    app-text/poppler
    dev-build/cmake
    dev-libs/qtkeychain
    media-libs/opencv
    net-analyzer/wireshark
    net-libs/libquotient
    www-client/chromium

There may be further packages that are pending stable but been holding back due to (non-optional) Qt6 too, haven't checked.

Now the question is whether I want to treat this like amd64 and stable every module that is keyworded right away (that means qtwebengine too which been keyworded on arm64 already) to help users avoid conflicts when accepting ~arm64 things, or stable only the strict minimum we need. fwiw given this is arm64 and plasma 5 was stable for arm64, we'll "eventually" need most of it either way.

Guess this is more of a question for AT given it means having to do qtwebengine with every Qt bumps. Regular stabilization process does help ensure that things don't become broken though.

qutebrowser and/or calibre could be stabled for arm64 if we wanted something using qtwebengine though :)

Comment 12 Ionen Wolkens gentoo-dev

2024-03-18 04:19:23 UTC

(In reply to Ionen Wolkens from comment #11)
> Guess this is more of a question for AT given it means having to do
> qtwebengine with every Qt bumps. Regular stabilization process does help
> ensure that things don't become broken though.
Then again, given we have jiji I guess there's no need to be too worried there.

Comment 13 Ionen Wolkens gentoo-dev

2024-03-18 04:24:29 UTC

CC'ing sam in case has as a preference

Comment 14 Ionen Wolkens gentoo-dev

2024-03-19 03:33:14 UTC

Well, let's try going with all. Hopefully tests for other packages still pass (the big worry on non-amd64 tend to always be qtbase, if that passes then the rest tend to be fine bare occasional non-issue system-specific quirks).

Should be able to drop the use.stable.mask after assuming no non-dev-qt/ deps that need stabling.

Comment 15 Arthur Zamarin archtester

2024-03-22 06:15:16 UTC

arm64 done

all arches done

Comment 16 Larry the Git Cow gentoo-dev

2024-03-22 06:31:21 UTC

The bug has been referenced in the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7124e55fe272ba57d5794e13a195d49cf1bd2016

commit 7124e55fe272ba57d5794e13a195d49cf1bd2016
Author:     Ionen Wolkens <ionen@gentoo.org>
AuthorDate: 2024-03-22 06:19:57 +0000
Commit:     Ionen Wolkens <ionen@gentoo.org>
CommitDate: 2024-03-22 06:31:07 +0000

    profiles/arch/arm64/use.stable.mask: drop obsolete qt6 mask
    
    Unkown if all the revdeps build/test fine, but with the mask gone
    they'll finally start getting tested properly.
    
    Bug: https://bugs.gentoo.org/927197
    Signed-off-by: Ionen Wolkens <ionen@gentoo.org>

 profiles/arch/arm64/use.stable.mask | 4 ----
 1 file changed, 4 deletions(-)