Script: modify common.sh #5848
KangLinbuild.yml
on: push
Matrix: android / build_android
Matrix: docker / build_docker
Matrix: flatpak / build_flatpak
Matrix: linux / build_linux
Matrix: macos / build_macos
Matrix: msvc / build_msvc
doxygen
/
build_doxygen
5m 45s
snap
/
build_snap
Matrix: aarch64 / build_arch
Waiting for pending jobs
Matrix: appimage / build_appimage
Waiting for pending jobs
Matrix: macos_script / build_macos
Matrix: mingw / build_mingw
Matrix: ubuntu / build_ubuntu
Waiting for pending jobs
deploy
42s
Annotations
202 warnings
|
docker / build_docker (deb, debian, 12, ubuntu-24.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
docker / build_docker (deb, debian, 13, ubuntu-24.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
docker / build_docker (rpm, fedora, 43, ubuntu-24.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
docker / build_docker (rpm, fedora, 42, ubuntu-24.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
docker / build_docker (rpm, fedora, 41, ubuntu-24.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
docker / build_docker (deb, ubuntu, 25.04, ubuntu-24.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
docker / build_docker (deb, ubuntu, 26.04, ubuntu-24.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
macos_script / build_macos (arm64-osx, macos-14)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v3, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
linux / build_linux (Release, 6.10.3, ubuntu-24.04-arm, deb)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v3, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
docker / build_docker (deb, ubuntu, 26.04, ubuntu-24.04-arm)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
docker / build_docker (appimage, ubuntu, 25.04, ubuntu-24.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
macos / build_macos (arm64-osx, macos-15, 6.9.3, clang_64, false)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v3, actions/upload-artifact@v4, lukka/run-vcpkg@v11. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
macos / build_macos (arm64-osx, macos-15, 6.9.3, clang_64, false)
By not providing "FindQt6Keychain.cmake" in CMAKE_MODULE_PATH this project
|
|
macos / build_macos (arm64-osx, macos-15, 6.9.3, clang_64, false)
By not providing "FindRabbitVNC.cmake" in CMAKE_MODULE_PATH this project
|
|
macos / build_macos (arm64-osx, macos-15, 6.9.3, clang_64, false)
By not providing "FindQtService.cmake" in CMAKE_MODULE_PATH this project
|
|
macos / build_macos (arm64-osx, macos-15, 6.9.3, clang_64, false)
Please create file:
|
|
macos / build_macos (arm64-osx, macos-15, 6.9.3, clang_64, false)
By not providing "FindQt6Keychain.cmake" in CMAKE_MODULE_PATH this project
|
|
macos / build_macos (arm64-osx, macos-15, 6.9.3, clang_64, false)
By not providing "FindLibDataChannel.cmake" in CMAKE_MODULE_PATH this
|
|
macos / build_macos (arm64-osx, macos-15, 6.9.3, clang_64, false)
By not providing "Findcmark-gfm-extensions.cmake" in CMAKE_MODULE_PATH this
|
|
macos / build_macos (arm64-osx, macos-15, 6.9.3, clang_64, false)
By not providing "Findcmark-gfm.cmake" in CMAKE_MODULE_PATH this project
|
|
macos / build_macos (arm64-osx, macos-15, 6.9.3, clang_64, false):
build/vcpkg_installed/arm64-osx/share/vcpkg-cmake/vcpkg_cmake_configure.cmake#L344
The following variables are not used in CMakeLists.txt:
|
|
macos / build_macos (arm64-osx, macos-15, 6.9.3, clang_64, false):
build/vcpkg_installed/arm64-osx/share/vcpkg-cmake/vcpkg_cmake_configure.cmake#L344
The following variables are not used in CMakeLists.txt:
|
|
macos / build_macos (arm64-osx, macos-15, 6.9.3, clang_64, false)
zstd 1.5.7_1 is already installed and up-to-date.
To reinstall 1.5.7_1, run:
brew reinstall zstd
|
|
macos / build_macos (arm64-osx, macos-15, 6.9.3, clang_64, false)
pkgconf 2.5.1 is already installed and up-to-date.
To reinstall 2.5.1, run:
brew reinstall pkgconf
|
|
macos / build_macos (arm64-osx, macos-15, 6.9.3, clang_64, false)
ninja 1.13.2 is already installed and up-to-date.
To reinstall 1.13.2, run:
brew reinstall ninja
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.11.0, Release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4, lukka/run-vcpkg@v11. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.11.0, Release)
By not providing "Findqtermwidget6.cmake" in CMAKE_MODULE_PATH this project
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.11.0, Release)
By not providing "FindQt6WebEngineWidgets.cmake" in CMAKE_MODULE_PATH this
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.11.0, Release)
By not providing "FindPcapPlusPlus.cmake" in CMAKE_MODULE_PATH this project
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.11.0, Release)
By not providing "FindRabbitVNC.cmake" in CMAKE_MODULE_PATH this project
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.11.0, Release)
By not providing "FindQtService.cmake" in CMAKE_MODULE_PATH this project
|
|
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.11.0, Release)
By not providing "Findqtermwidget6.cmake" in CMAKE_MODULE_PATH this project
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.11.0, Release)
By not providing "FindLibDataChannel.cmake" in CMAKE_MODULE_PATH this
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.11.0, Release):
.cache/tools/qt/Qt/6.11.0/android_arm64_v8a/lib/cmake/Qt6/QtPublicDependencyHelpers.cmake#L339
This project is using headers of the CorePrivate module and will therefore
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.11.0, Release):
build/android-arm64-v8a/vcpkg_installed/x64-linux/share/vcpkg-cmake/vcpkg_cmake_configure.cmake#L344
The following variables are not used in CMakeLists.txt:
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.11.0, Release)
By not providing "FindQtService.cmake" in CMAKE_MODULE_PATH this project
|
|
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.11.0, Release)
By not providing "Findqtermwidget6.cmake" in CMAKE_MODULE_PATH this project
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.11.0, Release)
By not providing "FindLibDataChannel.cmake" in CMAKE_MODULE_PATH this
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.11.0, Release):
.cache/tools/qt/Qt/6.11.0/android_arm64_v8a/lib/cmake/Qt6/QtPublicDependencyHelpers.cmake#L339
This project is using headers of the CorePrivate module and will therefore
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.11.0, Release)
By not providing "FindQt6WebView.cmake" in CMAKE_MODULE_PATH this project
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.11.0, Release)
By not providing "FindQt6WebEngineWidgets.cmake" in CMAKE_MODULE_PATH this
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.11.0, Release)
By not providing "Findcmark-gfm-extensions.cmake" in CMAKE_MODULE_PATH this
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.11.0, Release)
By not providing "Findcmark-gfm.cmake" in CMAKE_MODULE_PATH this project
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.11.0, Release):
build/vcpkg_installed/x64-linux/share/vcpkg-cmake/vcpkg_cmake_configure.cmake#L344
The following variables are not used in CMakeLists.txt:
|
|
macos / build_macos (arm64-osx, macos-14, 6.9.3, clang_64, true)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v3, actions/upload-artifact@v4, lukka/run-vcpkg@v11. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
macos / build_macos (arm64-osx, macos-14, 6.9.3, clang_64, true)
No files were found with the provided path: /Users/runner/work/RabbitRemoteControl/RabbitRemoteControl/build/RabbitRemoteControl_v0.1.0-dev_macos-14.zip
#/Users/runner/work/RabbitRemoteControl/RabbitRemoteControl/build/RabbitRemoteControl_v0.1.0-dev_macos-14_bundle.zip
/Users/runner/work/RabbitRemoteControl/RabbitRemoteControl/build/update_macos_6.9.3.json
/Users/runner/work/RabbitRemoteControl/RabbitRemoteControl/build/RabbitRemoteControl_v0.1.0-dev_macos-14.dmg. No artifacts will be uploaded.
|
|
macos / build_macos (arm64-osx, macos-14, 6.9.3, clang_64, true)
By not providing "FindQt6Keychain.cmake" in CMAKE_MODULE_PATH this project
|
|
macos / build_macos (arm64-osx, macos-14, 6.9.3, clang_64, true)
By not providing "FindRabbitVNC.cmake" in CMAKE_MODULE_PATH this project
|
|
macos / build_macos (arm64-osx, macos-14, 6.9.3, clang_64, true)
By not providing "FindQtService.cmake" in CMAKE_MODULE_PATH this project
|
|
macos / build_macos (arm64-osx, macos-14, 6.9.3, clang_64, true)
Please create file:
|
|
macos / build_macos (arm64-osx, macos-14, 6.9.3, clang_64, true)
By not providing "FindQt6Keychain.cmake" in CMAKE_MODULE_PATH this project
|
|
macos / build_macos (arm64-osx, macos-14, 6.9.3, clang_64, true)
By not providing "FindLibDataChannel.cmake" in CMAKE_MODULE_PATH this
|
|
macos / build_macos (arm64-osx, macos-14, 6.9.3, clang_64, true)
By not providing "Findcmark-gfm-extensions.cmake" in CMAKE_MODULE_PATH this
|
|
macos / build_macos (arm64-osx, macos-14, 6.9.3, clang_64, true)
By not providing "Findcmark-gfm.cmake" in CMAKE_MODULE_PATH this project
|
|
macos / build_macos (arm64-osx, macos-14, 6.9.3, clang_64, true):
build/vcpkg_installed/arm64-osx/share/vcpkg-cmake/vcpkg_cmake_configure.cmake#L344
The following variables are not used in CMakeLists.txt:
|
|
macos / build_macos (arm64-osx, macos-14, 6.9.3, clang_64, true):
build/vcpkg_installed/arm64-osx/share/vcpkg-cmake/vcpkg_cmake_configure.cmake#L344
The following variables are not used in CMakeLists.txt:
|
|
macos / build_macos (arm64-osx, macos-14, 6.9.3, clang_64, true)
zstd 1.5.7_1 is already installed and up-to-date.
To reinstall 1.5.7_1, run:
brew reinstall zstd
|
|
macos / build_macos (arm64-osx, macos-14, 6.9.3, clang_64, true)
pkgconf 2.5.1 is already installed and up-to-date.
To reinstall 2.5.1, run:
brew reinstall pkgconf
|
|
macos / build_macos (arm64-osx, macos-14, 6.9.3, clang_64, true)
ninja 1.13.2 is already installed and up-to-date.
To reinstall 1.13.2, run:
brew reinstall ninja
|
|
msvc / build_msvc (Win32, x86-windows, v143, vcpkg/ports, Release, 5.15.2, win32_msvc2019, qtwebengine, ...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4, lukka/run-vcpkg@v11. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
msvc / build_msvc (Win32, x86-windows, v143, vcpkg/ports, Release, 5.15.2, win32_msvc2019, qtwebengine, ...
SAVE_TARGET: Target 'netapi32' does not exist
|
|
msvc / build_msvc (Win32, x86-windows, v143, vcpkg/ports, Release, 5.15.2, win32_msvc2019, qtwebengine, ...
SAVE_TARGET: Target 'Shell32' does not exist
|
|
msvc / build_msvc (Win32, x86-windows, v143, vcpkg/ports, Release, 5.15.2, win32_msvc2019, qtwebengine, ...
SAVE_TARGET: Target 'Ole32' does not exist
|
|
msvc / build_msvc (Win32, x86-windows, v143, vcpkg/ports, Release, 5.15.2, win32_msvc2019, qtwebengine, ...
SAVE_TARGET: Target 'Advapi32' does not exist
|
|
msvc / build_msvc (Win32, x86-windows, v143, vcpkg/ports, Release, 5.15.2, win32_msvc2019, qtwebengine, ...
SAVE_TARGET: Target 'Dbghelp' does not exist
|
|
msvc / build_msvc (Win32, x86-windows, v143, vcpkg/ports, Release, 5.15.2, win32_msvc2019, qtwebengine, ...
By not providing "Findcmark-gfm-extensions.cmake" in CMAKE_MODULE_PATH this
|
|
msvc / build_msvc (Win32, x86-windows, v143, vcpkg/ports, Release, 5.15.2, win32_msvc2019, qtwebengine, ...
By not providing "Findcmark-gfm.cmake" in CMAKE_MODULE_PATH this project
|
|
msvc / build_msvc (Win32, x86-windows, v143, vcpkg/ports, Release, 5.15.2, win32_msvc2019, qtwebengine, ...:
build/vcpkg_installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_configure.cmake#L344
The following variables are not used in CMakeLists.txt:
|
|
msvc / build_msvc (Win32, x86-windows, v143, vcpkg/ports, Release, 5.15.2, win32_msvc2019, qtwebengine, ...
vcpkg_replace_string made no changes.
|
|
msvc / build_msvc (Win32, x86-windows, v143, vcpkg/ports, Release, 5.15.2, win32_msvc2019, qtwebengine, ...
vcpkg_replace_string made no changes.
|
|
android / build_android (android_x86_64, x64-android, x86_64, 6.10.3, Release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4, lukka/run-vcpkg@v11. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
android / build_android (android_x86_64, x64-android, x86_64, 6.10.3, Release)
By not providing "Findqtermwidget6.cmake" in CMAKE_MODULE_PATH this project
|
|
android / build_android (android_x86_64, x64-android, x86_64, 6.10.3, Release)
By not providing "FindQt6WebEngineWidgets.cmake" in CMAKE_MODULE_PATH this
|
|
android / build_android (android_x86_64, x64-android, x86_64, 6.10.3, Release)
By not providing "FindPcapPlusPlus.cmake" in CMAKE_MODULE_PATH this project
|
|
android / build_android (android_x86_64, x64-android, x86_64, 6.10.3, Release)
By not providing "FindRabbitVNC.cmake" in CMAKE_MODULE_PATH this project
|
|
android / build_android (android_x86_64, x64-android, x86_64, 6.10.3, Release)
By not providing "FindQtService.cmake" in CMAKE_MODULE_PATH this project
|
|
android / build_android (android_x86_64, x64-android, x86_64, 6.10.3, Release)
Please create file:
|
|
android / build_android (android_x86_64, x64-android, x86_64, 6.10.3, Release)
By not providing "Findqtermwidget6.cmake" in CMAKE_MODULE_PATH this project
|
|
android / build_android (android_x86_64, x64-android, x86_64, 6.10.3, Release)
By not providing "FindLibDataChannel.cmake" in CMAKE_MODULE_PATH this
|
|
android / build_android (android_x86_64, x64-android, x86_64, 6.10.3, Release):
.cache/tools/qt/Qt/6.10.3/android_x86_64/lib/cmake/Qt6/QtPublicDependencyHelpers.cmake#L335
This project is using headers of the CorePrivate module and will therefore
|
|
android / build_android (android_x86_64, x64-android, x86_64, 6.10.3, Release):
build/android-x86_64/vcpkg_installed/x64-linux/share/vcpkg-cmake/vcpkg_cmake_configure.cmake#L344
The following variables are not used in CMakeLists.txt:
|
|
android / build_android (android_x86_64, x64-android, x86_64, 6.10.3, Release)
By not providing "FindQtService.cmake" in CMAKE_MODULE_PATH this project
|
|
android / build_android (android_x86_64, x64-android, x86_64, 6.10.3, Release)
Please create file:
|
|
android / build_android (android_x86_64, x64-android, x86_64, 6.10.3, Release)
By not providing "Findqtermwidget6.cmake" in CMAKE_MODULE_PATH this project
|
|
android / build_android (android_x86_64, x64-android, x86_64, 6.10.3, Release)
By not providing "FindLibDataChannel.cmake" in CMAKE_MODULE_PATH this
|
|
android / build_android (android_x86_64, x64-android, x86_64, 6.10.3, Release):
.cache/tools/qt/Qt/6.10.3/android_x86_64/lib/cmake/Qt6/QtPublicDependencyHelpers.cmake#L335
This project is using headers of the CorePrivate module and will therefore
|
|
android / build_android (android_x86_64, x64-android, x86_64, 6.10.3, Release)
By not providing "FindQt6WebView.cmake" in CMAKE_MODULE_PATH this project
|
|
android / build_android (android_x86_64, x64-android, x86_64, 6.10.3, Release)
By not providing "FindQt6WebEngineWidgets.cmake" in CMAKE_MODULE_PATH this
|
|
android / build_android (android_x86_64, x64-android, x86_64, 6.10.3, Release)
By not providing "Findcmark-gfm-extensions.cmake" in CMAKE_MODULE_PATH this
|
|
android / build_android (android_x86_64, x64-android, x86_64, 6.10.3, Release)
By not providing "Findcmark-gfm.cmake" in CMAKE_MODULE_PATH this project
|
|
android / build_android (android_x86_64, x64-android, x86_64, 6.10.3, Release):
build/vcpkg_installed/x64-linux/share/vcpkg-cmake/vcpkg_cmake_configure.cmake#L344
The following variables are not used in CMakeLists.txt:
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.10.3, Release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4, lukka/run-vcpkg@v11. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.10.3, Release)
By not providing "Findqtermwidget6.cmake" in CMAKE_MODULE_PATH this project
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.10.3, Release)
By not providing "FindQt6WebEngineWidgets.cmake" in CMAKE_MODULE_PATH this
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.10.3, Release)
By not providing "FindPcapPlusPlus.cmake" in CMAKE_MODULE_PATH this project
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.10.3, Release)
By not providing "FindRabbitVNC.cmake" in CMAKE_MODULE_PATH this project
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.10.3, Release)
By not providing "FindQtService.cmake" in CMAKE_MODULE_PATH this project
|
|
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.10.3, Release)
By not providing "Findqtermwidget6.cmake" in CMAKE_MODULE_PATH this project
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.10.3, Release)
By not providing "FindLibDataChannel.cmake" in CMAKE_MODULE_PATH this
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.10.3, Release):
.cache/tools/qt/Qt/6.10.3/android_arm64_v8a/lib/cmake/Qt6/QtPublicDependencyHelpers.cmake#L335
This project is using headers of the CorePrivate module and will therefore
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.10.3, Release):
build/android-arm64-v8a/vcpkg_installed/x64-linux/share/vcpkg-cmake/vcpkg_cmake_configure.cmake#L344
The following variables are not used in CMakeLists.txt:
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.10.3, Release)
By not providing "FindQtService.cmake" in CMAKE_MODULE_PATH this project
|
|
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.10.3, Release)
By not providing "Findqtermwidget6.cmake" in CMAKE_MODULE_PATH this project
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.10.3, Release)
By not providing "FindLibDataChannel.cmake" in CMAKE_MODULE_PATH this
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.10.3, Release):
.cache/tools/qt/Qt/6.10.3/android_arm64_v8a/lib/cmake/Qt6/QtPublicDependencyHelpers.cmake#L335
This project is using headers of the CorePrivate module and will therefore
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.10.3, Release)
By not providing "FindQt6WebView.cmake" in CMAKE_MODULE_PATH this project
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.10.3, Release)
By not providing "FindQt6WebEngineWidgets.cmake" in CMAKE_MODULE_PATH this
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.10.3, Release)
By not providing "Findcmark-gfm-extensions.cmake" in CMAKE_MODULE_PATH this
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.10.3, Release)
By not providing "Findcmark-gfm.cmake" in CMAKE_MODULE_PATH this project
|
|
android / build_android (android_arm64_v8a, arm64-android, arm64-v8a, 6.10.3, Release):
build/vcpkg_installed/x64-linux/share/vcpkg-cmake/vcpkg_cmake_configure.cmake#L344
The following variables are not used in CMakeLists.txt:
|
|
macos / build_macos (arm64-osx, macos-14, 6.9.3, clang_64, false)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v3, actions/upload-artifact@v4, lukka/run-vcpkg@v11. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
macos / build_macos (arm64-osx, macos-14, 6.9.3, clang_64, false)
By not providing "FindQt6Keychain.cmake" in CMAKE_MODULE_PATH this project
|
|
macos / build_macos (arm64-osx, macos-14, 6.9.3, clang_64, false)
By not providing "FindRabbitVNC.cmake" in CMAKE_MODULE_PATH this project
|
|
macos / build_macos (arm64-osx, macos-14, 6.9.3, clang_64, false)
By not providing "FindQtService.cmake" in CMAKE_MODULE_PATH this project
|
|
macos / build_macos (arm64-osx, macos-14, 6.9.3, clang_64, false)
Please create file:
|
|
macos / build_macos (arm64-osx, macos-14, 6.9.3, clang_64, false)
By not providing "FindQt6Keychain.cmake" in CMAKE_MODULE_PATH this project
|
|
macos / build_macos (arm64-osx, macos-14, 6.9.3, clang_64, false)
By not providing "FindLibDataChannel.cmake" in CMAKE_MODULE_PATH this
|
|
macos / build_macos (arm64-osx, macos-14, 6.9.3, clang_64, false)
By not providing "Findcmark-gfm-extensions.cmake" in CMAKE_MODULE_PATH this
|
|
macos / build_macos (arm64-osx, macos-14, 6.9.3, clang_64, false)
By not providing "Findcmark-gfm.cmake" in CMAKE_MODULE_PATH this project
|
|
macos / build_macos (arm64-osx, macos-14, 6.9.3, clang_64, false):
build/vcpkg_installed/arm64-osx/share/vcpkg-cmake/vcpkg_cmake_configure.cmake#L344
The following variables are not used in CMakeLists.txt:
|
|
macos / build_macos (arm64-osx, macos-14, 6.9.3, clang_64, false):
build/vcpkg_installed/arm64-osx/share/vcpkg-cmake/vcpkg_cmake_configure.cmake#L344
The following variables are not used in CMakeLists.txt:
|
|
macos / build_macos (arm64-osx, macos-14, 6.9.3, clang_64, false)
zstd 1.5.7_1 is already installed and up-to-date.
To reinstall 1.5.7_1, run:
brew reinstall zstd
|
|
macos / build_macos (arm64-osx, macos-14, 6.9.3, clang_64, false)
pkgconf 2.5.1 is already installed and up-to-date.
To reinstall 2.5.1, run:
brew reinstall pkgconf
|
|
macos / build_macos (arm64-osx, macos-14, 6.9.3, clang_64, false)
ninja 1.13.2 is already installed and up-to-date.
To reinstall 1.13.2, run:
brew reinstall ninja
|
|
doxygen / build_doxygen
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
linux / build_linux (Release, 6.10.3, ubuntu-24.04, deb)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v3, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
docker / build_docker (deb, ubuntu, 25.04, ubuntu-24.04-arm)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
docker / build_docker (rpm, fedora, 42, ubuntu-24.04-arm)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
docker / build_docker (rpm, fedora, 41, ubuntu-24.04-arm)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
flatpak / build_flatpak (aarch64, ubuntu-24.04-arm)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, flathub-infra/flatpak-github-actions/flatpak-builder@master. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
android / build_android (android_x86_64, x64-android, x86_64, 6.11.0, Release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4, lukka/run-vcpkg@v11. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
android / build_android (android_x86_64, x64-android, x86_64, 6.11.0, Release)
By not providing "Findqtermwidget6.cmake" in CMAKE_MODULE_PATH this project
|
|
android / build_android (android_x86_64, x64-android, x86_64, 6.11.0, Release)
By not providing "FindQt6WebEngineWidgets.cmake" in CMAKE_MODULE_PATH this
|
|
android / build_android (android_x86_64, x64-android, x86_64, 6.11.0, Release)
By not providing "FindPcapPlusPlus.cmake" in CMAKE_MODULE_PATH this project
|
|
android / build_android (android_x86_64, x64-android, x86_64, 6.11.0, Release)
By not providing "FindRabbitVNC.cmake" in CMAKE_MODULE_PATH this project
|
|
android / build_android (android_x86_64, x64-android, x86_64, 6.11.0, Release)
By not providing "FindQtService.cmake" in CMAKE_MODULE_PATH this project
|
|
android / build_android (android_x86_64, x64-android, x86_64, 6.11.0, Release)
Please create file:
|
|
android / build_android (android_x86_64, x64-android, x86_64, 6.11.0, Release)
By not providing "Findqtermwidget6.cmake" in CMAKE_MODULE_PATH this project
|
|
android / build_android (android_x86_64, x64-android, x86_64, 6.11.0, Release)
By not providing "FindLibDataChannel.cmake" in CMAKE_MODULE_PATH this
|
|
android / build_android (android_x86_64, x64-android, x86_64, 6.11.0, Release):
.cache/tools/qt/Qt/6.11.0/android_x86_64/lib/cmake/Qt6/QtPublicDependencyHelpers.cmake#L339
This project is using headers of the CorePrivate module and will therefore
|
|
android / build_android (android_x86_64, x64-android, x86_64, 6.11.0, Release):
build/android-x86_64/vcpkg_installed/x64-linux/share/vcpkg-cmake/vcpkg_cmake_configure.cmake#L344
The following variables are not used in CMakeLists.txt:
|
|
android / build_android (android_x86_64, x64-android, x86_64, 6.11.0, Release)
By not providing "FindQtService.cmake" in CMAKE_MODULE_PATH this project
|
|
android / build_android (android_x86_64, x64-android, x86_64, 6.11.0, Release)
Please create file:
|
|
android / build_android (android_x86_64, x64-android, x86_64, 6.11.0, Release)
By not providing "Findqtermwidget6.cmake" in CMAKE_MODULE_PATH this project
|
|
android / build_android (android_x86_64, x64-android, x86_64, 6.11.0, Release)
By not providing "FindLibDataChannel.cmake" in CMAKE_MODULE_PATH this
|
|
android / build_android (android_x86_64, x64-android, x86_64, 6.11.0, Release):
.cache/tools/qt/Qt/6.11.0/android_x86_64/lib/cmake/Qt6/QtPublicDependencyHelpers.cmake#L339
This project is using headers of the CorePrivate module and will therefore
|
|
android / build_android (android_x86_64, x64-android, x86_64, 6.11.0, Release)
By not providing "FindQt6WebView.cmake" in CMAKE_MODULE_PATH this project
|
|
android / build_android (android_x86_64, x64-android, x86_64, 6.11.0, Release)
By not providing "FindQt6WebEngineWidgets.cmake" in CMAKE_MODULE_PATH this
|
|
android / build_android (android_x86_64, x64-android, x86_64, 6.11.0, Release)
By not providing "Findcmark-gfm-extensions.cmake" in CMAKE_MODULE_PATH this
|
|
android / build_android (android_x86_64, x64-android, x86_64, 6.11.0, Release)
By not providing "Findcmark-gfm.cmake" in CMAKE_MODULE_PATH this project
|
|
android / build_android (android_x86_64, x64-android, x86_64, 6.11.0, Release):
build/vcpkg_installed/x64-linux/share/vcpkg-cmake/vcpkg_cmake_configure.cmake#L344
The following variables are not used in CMakeLists.txt:
|
|
docker / build_docker (rpm, fedora, 43, ubuntu-24.04-arm)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
flatpak / build_flatpak (x86_64, ubuntu-24.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, flathub-infra/flatpak-github-actions/flatpak-builder@master. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
docker / build_docker (deb, debian, 13, ubuntu-24.04-arm)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
macos_script / build_macos (arm64-osx, macos-15)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v3, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
docker / build_docker (deb, debian, 12, ubuntu-24.04-arm)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
docker / build_docker (appimage, ubuntu, 25.04, ubuntu-24.04-arm)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
mingw / build_mingw (Release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
msvc / build_msvc (arm64, arm64-windows, v143, Release, 6.10.3, win64_msvc2022_arm64, qt5compat qtimagef...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4, lukka/run-vcpkg@v11. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
msvc / build_msvc (arm64, arm64-windows, v143, Release, 6.10.3, win64_msvc2022_arm64, qt5compat qtimagef...
SAVE_TARGET: Target 'Shell32' does not exist
|
|
msvc / build_msvc (arm64, arm64-windows, v143, Release, 6.10.3, win64_msvc2022_arm64, qt5compat qtimagef...
SAVE_TARGET: Target 'Ole32' does not exist
|
|
msvc / build_msvc (arm64, arm64-windows, v143, Release, 6.10.3, win64_msvc2022_arm64, qt5compat qtimagef...
SAVE_TARGET: Target 'Advapi32' does not exist
|
|
msvc / build_msvc (arm64, arm64-windows, v143, Release, 6.10.3, win64_msvc2022_arm64, qt5compat qtimagef...
SAVE_TARGET: Target 'Dbghelp' does not exist
|
|
msvc / build_msvc (arm64, arm64-windows, v143, Release, 6.10.3, win64_msvc2022_arm64, qt5compat qtimagef...
By not providing "FindQt6WebView.cmake" in CMAKE_MODULE_PATH this project
|
|
msvc / build_msvc (arm64, arm64-windows, v143, Release, 6.10.3, win64_msvc2022_arm64, qt5compat qtimagef...
By not providing "FindQt6WebEngineWidgets.cmake" in CMAKE_MODULE_PATH this
|
|
msvc / build_msvc (arm64, arm64-windows, v143, Release, 6.10.3, win64_msvc2022_arm64, qt5compat qtimagef...
By not providing "Findcmark-gfm-extensions.cmake" in CMAKE_MODULE_PATH this
|
|
msvc / build_msvc (arm64, arm64-windows, v143, Release, 6.10.3, win64_msvc2022_arm64, qt5compat qtimagef...
By not providing "Findcmark-gfm.cmake" in CMAKE_MODULE_PATH this project
|
|
msvc / build_msvc (arm64, arm64-windows, v143, Release, 6.10.3, win64_msvc2022_arm64, qt5compat qtimagef...:
build/vcpkg_installed/arm64-windows/share/vcpkg-cmake/vcpkg_cmake_configure.cmake#L344
The following variables are not used in CMakeLists.txt:
|
|
msvc / build_msvc (arm64, arm64-windows, v143, Release, 6.10.3, win64_msvc2022_arm64, qt5compat qtimagef...:
build/vcpkg_installed/arm64-windows/share/vcpkg-cmake/vcpkg_cmake_configure.cmake#L344
The following variables are not used in CMakeLists.txt:
|
|
macos / build_macos (x64-osx, macos-15-intel, 6.9.3, clang_64, false)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v3, actions/upload-artifact@v4, lukka/run-vcpkg@v11. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
macos / build_macos (x64-osx, macos-15-intel, 6.9.3, clang_64, false)
By not providing "FindQt6Keychain.cmake" in CMAKE_MODULE_PATH this project
|
|
macos / build_macos (x64-osx, macos-15-intel, 6.9.3, clang_64, false)
By not providing "FindRabbitVNC.cmake" in CMAKE_MODULE_PATH this project
|
|
macos / build_macos (x64-osx, macos-15-intel, 6.9.3, clang_64, false)
By not providing "FindQtService.cmake" in CMAKE_MODULE_PATH this project
|
|
macos / build_macos (x64-osx, macos-15-intel, 6.9.3, clang_64, false)
Please create file:
|
|
macos / build_macos (x64-osx, macos-15-intel, 6.9.3, clang_64, false)
By not providing "FindQt6Keychain.cmake" in CMAKE_MODULE_PATH this project
|
|
macos / build_macos (x64-osx, macos-15-intel, 6.9.3, clang_64, false)
By not providing "FindLibDataChannel.cmake" in CMAKE_MODULE_PATH this
|
|
macos / build_macos (x64-osx, macos-15-intel, 6.9.3, clang_64, false)
By not providing "Findcmark-gfm-extensions.cmake" in CMAKE_MODULE_PATH this
|
|
macos / build_macos (x64-osx, macos-15-intel, 6.9.3, clang_64, false)
By not providing "Findcmark-gfm.cmake" in CMAKE_MODULE_PATH this project
|
|
macos / build_macos (x64-osx, macos-15-intel, 6.9.3, clang_64, false):
build/vcpkg_installed/x64-osx/share/vcpkg-cmake/vcpkg_cmake_configure.cmake#L344
The following variables are not used in CMakeLists.txt:
|
|
macos / build_macos (x64-osx, macos-15-intel, 6.9.3, clang_64, false):
build/vcpkg_installed/x64-osx/share/vcpkg-cmake/vcpkg_cmake_configure.cmake#L344
The following variables are not used in CMakeLists.txt:
|
|
macos / build_macos (x64-osx, macos-15-intel, 6.9.3, clang_64, false)
zstd 1.5.7_1 is already installed and up-to-date.
To reinstall 1.5.7_1, run:
brew reinstall zstd
|
|
macos / build_macos (x64-osx, macos-15-intel, 6.9.3, clang_64, false)
pkgconf 2.5.1 is already installed and up-to-date.
To reinstall 2.5.1, run:
brew reinstall pkgconf
|
|
macos / build_macos (x64-osx, macos-15-intel, 6.9.3, clang_64, false)
libtool 2.5.4 is already installed and up-to-date.
To reinstall 2.5.4, run:
brew reinstall libtool
|
|
macos / build_macos (x64-osx, macos-15-intel, 6.9.3, clang_64, false)
ninja 1.13.2 is already installed and up-to-date.
To reinstall 1.13.2, run:
brew reinstall ninja
|
|
macos / build_macos (x64-osx, macos-15-intel, 6.9.3, clang_64, false)
autoconf 2.73 is already installed and up-to-date.
To reinstall 2.73, run:
brew reinstall autoconf
|
|
msvc / build_msvc (x64, x64-windows, v143, Release, 6.10.3, win64_msvc2022_64, qtscxml qtmultimedia qtim...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4, lukka/run-vcpkg@v11. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
msvc / build_msvc (x64, x64-windows, v143, Release, 6.10.3, win64_msvc2022_64, qtscxml qtmultimedia qtim...
By not providing "FindLibDataChannel.cmake" in CMAKE_MODULE_PATH this
|
|
msvc / build_msvc (x64, x64-windows, v143, Release, 6.10.3, win64_msvc2022_64, qtscxml qtmultimedia qtim...
SAVE_TARGET: Target 'Ws2_32' does not exist
|
|
msvc / build_msvc (x64, x64-windows, v143, Release, 6.10.3, win64_msvc2022_64, qtscxml qtmultimedia qtim...
SAVE_TARGET: Target 'netapi32' does not exist
|
|
msvc / build_msvc (x64, x64-windows, v143, Release, 6.10.3, win64_msvc2022_64, qtscxml qtmultimedia qtim...
SAVE_TARGET: Target 'Shell32' does not exist
|
|
msvc / build_msvc (x64, x64-windows, v143, Release, 6.10.3, win64_msvc2022_64, qtscxml qtmultimedia qtim...
SAVE_TARGET: Target 'Ole32' does not exist
|
|
msvc / build_msvc (x64, x64-windows, v143, Release, 6.10.3, win64_msvc2022_64, qtscxml qtmultimedia qtim...
SAVE_TARGET: Target 'Advapi32' does not exist
|
|
msvc / build_msvc (x64, x64-windows, v143, Release, 6.10.3, win64_msvc2022_64, qtscxml qtmultimedia qtim...
SAVE_TARGET: Target 'Dbghelp' does not exist
|
|
msvc / build_msvc (x64, x64-windows, v143, Release, 6.10.3, win64_msvc2022_64, qtscxml qtmultimedia qtim...
By not providing "Findcmark-gfm-extensions.cmake" in CMAKE_MODULE_PATH this
|
|
msvc / build_msvc (x64, x64-windows, v143, Release, 6.10.3, win64_msvc2022_64, qtscxml qtmultimedia qtim...
By not providing "Findcmark-gfm.cmake" in CMAKE_MODULE_PATH this project
|
|
msvc / build_msvc (x64, x64-windows, v143, Release, 6.10.3, win64_msvc2022_64, qtscxml qtmultimedia qtim...:
build/vcpkg_installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_configure.cmake#L344
The following variables are not used in CMakeLists.txt:
|
|
deploy
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
macos_script / build_macos (x64-osx, macos-15-intel)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v3, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
RabbitRemoteControl_v0.1.0-dev_Linux_aarch64-aarch64.flatpak
Expired
|
86.3 MB |
sha256:e1918c0896786a174d7cf630b3292b1eb232e8a9fa714b2e876aef55738ecdc3
|
|
|
RabbitRemoteControl_v0.1.0-dev_Linux_x86_64-x86_64.flatpak
Expired
|
96.9 MB |
sha256:9bdd8f9fa00ac11e2b042d4765c0bd45c4bc78deb47e0adab646c49050bc469d
|
|
|
build_android_6.10.3_android_arm64_v8a
Expired
|
35.1 MB |
sha256:a41100ab633beb8726b486cf85d06ef79d0f9c9ffe9880ca8512b8387f669093
|
|
|
build_android_6.10.3_android_x86_64
Expired
|
34.8 MB |
sha256:dd2d3a53198d0560330581a9e5c9f35bfc2475006979a1cb8e10692b72d0c664
|
|
|
build_android_6.11.0_android_arm64_v8a
Expired
|
33.7 MB |
sha256:a4fa361781fec6abeee7de1e071a22f460cd5360efd5593a441e611e0a505d2b
|
|
|
build_android_6.11.0_android_x86_64
Expired
|
33.9 MB |
sha256:a5c13973de2aa913abe2e559dd610538d59df9404ed6a5a773a407a58e341bfe
|
|
|
build_docker_appimage_ubuntu_25.04_ubuntu-24.04
Expired
|
204 MB |
sha256:c52e66152f2e400cfb82940d41c463c7402143ebafc117d6c84ae95f520177aa
|
|
|
build_docker_appimage_ubuntu_25.04_ubuntu-24.04-arm
Expired
|
189 MB |
sha256:8e25667db70a34b528678e364ac5a3c9ca179abba99b7977c1c207354546fb58
|
|
|
build_docker_deb_debian_12_ubuntu-24.04
Expired
|
2.52 MB |
sha256:0325668d6dca1d1f049237ca5fa8869a3d19b8e6578fbb6c16b5c5bb831e64b5
|
|
|
build_docker_deb_debian_12_ubuntu-24.04-arm
Expired
|
2.27 MB |
sha256:83ef21817124fd00412812505e21f67ca40a2939f948eecb3ceed0e6c6c7398b
|
|
|
build_docker_deb_debian_13_ubuntu-24.04
Expired
|
2.67 MB |
sha256:867bb3d5e68650792af040034e9d302638c877dd2ad4ffd3526740f41dcef836
|
|
|
build_docker_deb_debian_13_ubuntu-24.04-arm
Expired
|
2.39 MB |
sha256:65a6ba6f87b30b1f958b4303bfc0a6251d5a52cdb4e3b30ad52ae393bb4ff6fa
|
|
|
build_docker_deb_ubuntu_25.04_ubuntu-24.04
Expired
|
2.84 MB |
sha256:eb500559089148e961bb555ba76521d0b6c1ce6a0f245dbaeef6a95affc5afae
|
|
|
build_docker_deb_ubuntu_25.04_ubuntu-24.04-arm
Expired
|
2.69 MB |
sha256:1a091b6ffcd9f5bdab31d23b2a0a40963aff6b1c9e64fcee4e9f3d120397aff7
|
|
|
build_docker_deb_ubuntu_26.04_ubuntu-24.04
Expired
|
2.9 MB |
sha256:913f59a8239ba53e4327648a36f0e0a7692d708902793f872aa3a33025f485bc
|
|
|
build_docker_deb_ubuntu_26.04_ubuntu-24.04-arm
Expired
|
2.75 MB |
sha256:24cb109ae3ebd196c8126e9546f77df3c6abd479c4e254ff8d9b075acb022d5c
|
|
|
build_docker_rpm_fedora_41_ubuntu-24.04
Expired
|
2.64 MB |
sha256:c844f9589d926c7de1d228ef893e3173a0c1771578d7959ae509b40ce7017cff
|
|
|
build_docker_rpm_fedora_41_ubuntu-24.04-arm
Expired
|
2.49 MB |
sha256:d236f2df4766bc4906cb2534a2b4dd9b8b42084e881c80ba42e520ea35779580
|
|
|
build_docker_rpm_fedora_42_ubuntu-24.04
Expired
|
2.69 MB |
sha256:5e560a175b12d8212e50efc74f68bdcba502830296c5e70e6a6d4c8a39ebd8df
|
|
|
build_docker_rpm_fedora_42_ubuntu-24.04-arm
Expired
|
2.54 MB |
sha256:a3d50161c535f66237cc783e3dcb2d9b873a7a54680d6974b234cd026c0e190d
|
|
|
build_docker_rpm_fedora_43_ubuntu-24.04
Expired
|
2.69 MB |
sha256:548109887ac0f6194d43520ef8bb68ed91e2cb4384664dfe924efcfda9031033
|
|
|
build_docker_rpm_fedora_43_ubuntu-24.04-arm
Expired
|
2.54 MB |
sha256:677b4f7b072b41ffb27105aa76a31ab0ef392c662cae1e71345113d7d04ffb3d
|
|
|
build_doxygen
Expired
|
74.5 MB |
sha256:2820dc4dce2dcfa145ed1000c33bd5756da2694ea1891c4b76aa8eaf7b40aac1
|
|
|
build_linux_ubuntu-24.04-arm_deb
Expired
|
2.55 MB |
sha256:9c96134ba0c1744522e04a66f760c881e8d79e48c8266bfa9195372cd978b79b
|
|
|
build_linux_ubuntu-24.04_deb
Expired
|
2.71 MB |
sha256:d21c3c01a62dd5bf59d7bb39e6970be75f14d8ec6686723ff44fab61eedbea1e
|
|
|
build_macos_6.9.3_clang_64_macos-14_false
Expired
|
539 MB |
sha256:6dbdbc8298edf7c82ae891e7b3b853de3c93abb6e8ba828063a149f8625f21a5
|
|
|
build_macos_6.9.3_clang_64_macos-15-intel_false
Expired
|
539 MB |
sha256:2af4f5f6443487b00f0af25803120557b30617c7f1a032b5f02b3d82e5ddb656
|
|
|
build_macos_6.9.3_clang_64_macos-15_false
Expired
|
540 MB |
sha256:70329a81913f216e5b2610f0c1dda712be9135632d1d41d8afc8af4c4c4c2164
|
|
|
build_macos_macos-14
Expired
|
3.42 MB |
sha256:08e9e3a383eaa1b8e2631d03a4cfdda9539665138106ced184d0f77b8ad34c60
|
|
|
build_macos_macos-15
Expired
|
3.41 MB |
sha256:b07a31ac1bd515cffea271831a0bcdb841c61dfa9684c71fe9003933b8ac9b18
|
|
|
build_macos_macos-15-intel
Expired
|
3.49 MB |
sha256:b772ebb0398ea00ed73ecf36b2116e9deb8f5fc8072e1722ee63bf86d913b0e4
|
|
|
build_msvc_5.15.2_win32_msvc2019
Expired
|
63.2 MB |
sha256:3e942001698ccb31cdd52d64ce725e744c83d4c1ecb7e7fbfc3d59e22ebc5238
|
|
|
build_msvc_6.10.3_win64_msvc2022_64
Expired
|
136 MB |
sha256:24079fb45b5edde63c24163c1423ed331140d3af24181dc85838e92b6f298aab
|
|
|
build_msvc_6.10.3_win64_msvc2022_arm64
Expired
|
28.9 MB |
sha256:c0238c33c88d2e0c84e7f79c509b7a85ee5068907e983ccd169c44e0d76c78fd
|
|