Processed: RC Bug #1031438: Forward to upstream fix
Processing commands for cont...@bugs.debian.org: > # Failing test has been disabled upstream. > # I've rebuilt your package without issues with the commit applied. > # Thanks for your work. > forwarded 1031438 https://invent.kde.org/libraries/qca/-/merge_requests/93 Bug #1031438 [src:qca2] qca2: FTBFS: dh_auto_test: error: cd build && make -j8 test ARGS\+=--verbose ARGS\+=-j8 returned exit code 2 Set Bug forwarded-to-address to 'https://invent.kde.org/libraries/qca/-/merge_requests/93'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1031438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031438 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1030980: marked as done (Qt6::qmake IMPORTED_LOCATION points to build architecture qmake6)
Your message dated Mon, 20 Feb 2023 19:47:15 -0300
with message-id <2829431.mvXUDI8C0e@minerva>
and subject line
has caused the Debian Bug report #1030980,
regarding Qt6::qmake IMPORTED_LOCATION points to build architecture qmake6
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1030980: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030980
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qt6-base-dev
User: debian-cr...@lists.debian.org
Usertags: ftcbfs
Control: affects -1 + src:fcitx-qt5
Hi,
thanks for adding the -qmake6 wrapper. This piece seems to work
fine. The next step is making packages actually use it and this is where
it gets difficult.
fcitx-qt6 extracts the Qt6::qmake IMPORTED_LOCATION and expects to find
a working qmake there. What it gets is the build architecture qmake
instead of our lovely wrapper. Bummer.
I looked into how this could be fixed and got entangled in the mess of
cmake files until I completely lost track. What I found is that the
imported location is (wrongly) defined in
/usr/lib//cmake/Qt6CoreTools/Qt6CoreToolsTargets-none.cmake as
${_IMPORT_PREFIX}/lib/qt6/libexec/qmake aka /usr/lib/qt6/libexec/qmake
while it should be /usr/bin/-qmake6. Tracking down how this
file is generated is where I failed. Would someone be available to
support me with that task?
Thanks in advance
Helmut
--- End Message ---
--- Begin Message ---
Version: 6.4.2+dfsg-4
Closed the wrong bug, so fixing here.
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
Processed: Reopening
Processing commands for cont...@bugs.debian.org:
> reopen 1030895
Bug #1030895 {Done: Lisandro Damián Nicanor Pérez Meyer }
[src:qt6-webengine] qt6-webengine: Enable riscv64 support
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions qt6-base/6.4.2+dfsg-4.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1030895: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030895
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
sddm_0.19.0-5_source.changes ACCEPTED into unstable
Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 20 Feb 2023 22:51:20 +0100 Source: sddm Architecture: source Version: 0.19.0-5 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Aurélien COUDERC Changes: sddm (0.19.0-5) unstable; urgency=medium . * Drop haveged from recommends, it used to be necessary to gather enough entropy to avoid freezes during boot but this hasn’t been the case anymore for many kernel releases. Checksums-Sha1: 4e6743b47620848b8ac71948c51a1c73b27ceb51 2638 sddm_0.19.0-5.dsc 4a2a5b4325c05c12b49ef53d2ec1da1be6337325 59352 sddm_0.19.0-5.debian.tar.xz 080982093f3f77db49b95ea8aa57b09680ce43ea 15018 sddm_0.19.0-5_amd64.buildinfo Checksums-Sha256: 39cfd2a1695af304ac44164090b6e02e419051abee021efb28929b3ddea2ab44 2638 sddm_0.19.0-5.dsc e0460c9eafb5f1825ddf5069dac01c22e26243dddea8bdac2ccf943c71742569 59352 sddm_0.19.0-5.debian.tar.xz 817a49620e1cfa5fc27e190f8932096cf3069a56f137bd5d5f53c1734868941d 15018 sddm_0.19.0-5_amd64.buildinfo Files: fcb18d02da28979b8a051a7dc42d56c2 2638 kde optional sddm_0.19.0-5.dsc 07d39bdefd980287b219a026d011323f 59352 kde optional sddm_0.19.0-5.debian.tar.xz 43e27ae2a7e0dcf5a80e34009e92 15018 kde optional sddm_0.19.0-5_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEEIW//QAAaDgcOKDsfcaflM/KRoyQFAmPz688THGNvdWNvdWZA ZGViaWFuLm9yZwAKCRBxp+Uz8pGjJKZYD/48WMa14XE+VkLmou6sOiUNmnn4w0IK uqU6AmaOtUEAVOvGsPIpQvlR9jj1uCLjFx3NMkAFieE+ud2FMwtH374+6HRCkbSF Na9CcYQJm3r0+GEmEl3YR3GRumaWMvlHjRFFc4XB0zgbNQcx2zbnY7cgMboxH3Zf neCc/hu6xowvBdNscfAKsjfTTyRxNmruBxcWZjFlPjiSTMSB/g2+Ijf8bk2r/P07 LL5F0VeJz9Ct9DearmKmv5b0wYUtQ7VaPC1hyUuOvy5V2uYXzNy1nZ/0F2xrSpDP eK7mpVpiOYScYZiLQv+RXs7UApKYmPMW3WF0Jf/ej8Yx7hmWGn7e/LFcpY7nu75x GXDgv0e/msvGRbNM6ctz4tpZFPEOuQjVX++k9+ubO8iHSr4XszkwBDZ4UiEcyvtI VZl68cm7lK3Dyaywwvoljg6McbRuMKTmk5l73K5NTWOLKm6U8zA7xysZvUrtQMqR LuM5Y0tGk8mlZ0XX/FXkFutzwzmkH4TiwMNpqf8NHoMJsZreGZECNhUa45XvrAPI y7WLaa7DrhWWxqTeHXvqxOj3Qj1xRdt9C22kE+Ijjb1XMWlrngFJkTdEfnD0h4QR LTp7NZoeE25GtiTn7OlilLzElAEC873R6MsoLkyWEfXQeVyHwIA79U/cDbDDBdy/ TmBiOygxLjuqqg== =xT0H -END PGP SIGNATURE-
Processing of sddm_0.19.0-5_source.changes
sddm_0.19.0-5_source.changes uploaded successfully to localhost along with the files: sddm_0.19.0-5.dsc sddm_0.19.0-5.debian.tar.xz sddm_0.19.0-5_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
Processed: Bug#1031658 marked as pending in plasma-desktop
Processing control commands: > tag -1 pending Bug #1031658 [plasma-desktop] plasma-desktop: Depends on plasma-workspace-wayland looks wrong Added tag(s) pending. -- 1031658: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031658 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1031243: marked as done (plasma-workspace: mute icon on task bar appears on wrong applications)
Your message dated Mon, 20 Feb 2023 22:21:24 +0100 with message-id <688ac029-06c3-f13a-1fec-1b6a2d1ae...@gmail.com> and subject line Re: plasma-workspace: mute icon on task bar appears on wrong applications has caused the Debian Bug report #1031243, regarding plasma-workspace: mute icon on task bar appears on wrong applications to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1031243: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031243 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: plasma-workspace Version: 4:5.26.90-1 Severity: minor Tags: patch fixed-upstream Dear Maintainer, STEPS TO REPRODUCE 1. Install plasma-desktop 5.26.90 2. Open an application that plays audio and other applications to fill up the task bar with several applications OBSERVED RESULT The mute icon appears on unrelated applications and/or pinned, not launched, applications. See screenshot in attachment where only spotify is playing audio but other applications also get the mute icon. EXPECTED RESULT The mute icon should appear only on applications that plays audio (as it was in 5.26.5) This issue was fixed upstream in this commit: https://invent.kde.org/plasma/plasma-workspace/-/commit/c27fb3c0d25a0ad7af44acd1d9e957cdaae8802e It is included in the 5.27 release (which is not released yet). -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-3-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr:en_US Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages plasma-workspace depends on: ii dbus-user-session [default-dbus-session-bus]1.14.4-1 ii drkonqi 5.26.90-1 ii frameworkintegration5.102.0-1 ii gdb 12.1-4+b1 ii init-system-helpers 1.65.2 ii iso-codes 4.12.0-1 ii kactivitymanagerd 5.26.90-1 ii kded5 5.102.0-1 ii kinit 5.102.0-1 ii kio 5.102.0-1 ii kpackagetool5 5.102.0-1 ii kwin-common 4:5.26.90-1 ii libappstreamqt2 0.16.0-1 ii libc6 2.36-8 ii libcolorcorrect54:5.26.90-1 ii libcrypt1 1:4.4.33-2 ii libfontconfig1 2.14.1-4 ii libfreetype62.12.1+dfsg-4 ii libgcc-s1 12.2.0-14 ii libgps283.22-4.1+b1 ii libice6 2:1.0.10-1 ii libicu7272.1-3 ii libkf5activities5 5.102.0-1 ii libkf5activitiesstats1 5.102.0-1 ii libkf5archive5 5.102.0-1 ii libkf5authcore5 5.102.0-1 ii libkf5baloo55.102.0-1 ii libkf5bookmarks55.102.0-1 ii libkf5calendarevents5 5.102.0-1 ii libkf5completion5 5.102.0-1 ii libkf5config-bin5.102.0-1 ii libkf5configcore5 5.102.0-1 ii libkf5configgui55.102.0-1 ii libkf5configwidgets55.102.0-1 ii libkf5coreaddons5 5.102.0-1 ii libkf5crash55.102.0-1 ii libkf5dbusaddons5 5.102.0-1 ii libkf5declarative5 5.102.0-1 ii libkf5globalaccel-bin 5.102.0-1 ii libkf5globalaccel5 5.102.0-1 ii libkf5guiaddons5
qt6-base_6.4.2+dfsg-4_source.changes ACCEPTED into unstable
Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 20 Feb 2023 16:54:52 -0300 Source: qt6-base Architecture: source Version: 6.4.2+dfsg-4 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Lisandro Damián Nicanor Pérez Meyer Closes: 1030895 Changes: qt6-base (6.4.2+dfsg-4) unstable; urgency=medium . * Team upload. * Workaround wrong path in CMake file, Qt6::qmake IMPORTED_LOCATION by modifying the path (Closes: #1030895). Thanks Helmut Grohne and Dmitry Shachnev for the bug and solution. Checksums-Sha1: debf375868c7304aa69c6e51d9264433da712de6 4859 qt6-base_6.4.2+dfsg-4.dsc 11bc003ea2f6d34dd522db8a62e791b7a2eb3bfd 174536 qt6-base_6.4.2+dfsg-4.debian.tar.xz 1570bc332d4bf43e33c6d355412960af468b31bc 18580 qt6-base_6.4.2+dfsg-4_source.buildinfo Checksums-Sha256: 6c83ad5b165a9724ccf12118bb28c91bf30aeff43eeef496577684e229ebe9d9 4859 qt6-base_6.4.2+dfsg-4.dsc 88fd40d35cdca3f8be9a160792db85db5d54d0f4534faaa17531517430a49bdd 174536 qt6-base_6.4.2+dfsg-4.debian.tar.xz 39d911ecb75206a8b32ceb3e386f0edd7d29cb1ed21122355187655852ce2064 18580 qt6-base_6.4.2+dfsg-4_source.buildinfo Files: 8bc81e2930f3b9cf7e306e5cb2882b22 4859 libs optional qt6-base_6.4.2+dfsg-4.dsc 7750e8ceed85877b5adde61b360c3447 174536 libs optional qt6-base_6.4.2+dfsg-4.debian.tar.xz 96d5f966512a8a4a3845fb5940669f9a 18580 libs optional qt6-base_6.4.2+dfsg-4_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEEt36hKwjsrvwSzE8q2RfQGKGp9AFAmPz0EUUHGxpc2FuZHJv QGRlYmlhbi5vcmcACgkQq2RfQGKGp9AArxAAhpzYhawatSpgRJiMK5EDFtxZVrJT 3B9pHDiS/29jk+Y5IkwLDDDA6hdsa59pNGxUTcrpq529U3cBTVzVMY3ygojNdcoD c6qKwvt5OGbEGHI7X52RteiTEA2r0ve3ZitdgIqsEK/WctaVqnbZNdPAqsm7Skuz PD+9CLpwjblimvaDuoDL+VoimlPkXfxC1L89/jNKm/KtgH73ZxCWhyGS344gyREH 2BjBJFc44g2cwAigYpciku6FFXWqXqkG9jqwKeky+e+/FeGxko/3Fop2PxnXtDN4 X2raW75qSpuiZ95RXWqTnbUKxoS5a49tb6ukE64s6jPyz5ON8aOJpK4RwblFq1EP hQbJEQdsY2dVpLWp//87OLkft/3imUGGUVb+dHvdz3E0VYU2ddLTaefzKk6odX5S /L4YmzVyaZw0WhIBt/5hpHpn9vdWCFUt5BDMcU/VqV2ijoqOR62R7KxR9A7qQXm0 gaLWrebW3BAGDDHzfHj9lDNMIwl96yKCNyOIonQ2x08VXSBfTevVbPXBv7sBzGKb K7qnPU84RWa1MY68N4S0FE048WGm0L9OlHWUjqMs1ZQdWxDAAjhojgkfaRJSg5jn fdzuSwRHS/n6emanym7Ym+HiPmUepBcie/3J6WZ3vPTB/kStnPj4PbonOrCqluKk khmFM/YLvu3FC7U= =AGIM -END PGP SIGNATURE-
Processing of qt6-base_6.4.2+dfsg-4_source.changes
qt6-base_6.4.2+dfsg-4_source.changes uploaded successfully to localhost along with the files: qt6-base_6.4.2+dfsg-4.dsc qt6-base_6.4.2+dfsg-4.debian.tar.xz qt6-base_6.4.2+dfsg-4_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
Bug#1030980: Qt6::qmake IMPORTED_LOCATION points to build architecture qmake6
Hi Dmitry and Lisandro,
thanks for working on this.
On Mon, Feb 20, 2023 at 10:49:52AM +0300, Dmitry Shachnev wrote:
> On Sun, Feb 19, 2023 at 08:20:43PM -0300, Lisandro Damián Nicanor Pérez Meyer
> wrote:
> > On Sun, 19 Feb 2023 at 16:59, Dmitry Shachnev wrote:
> > > What are these paths?
> > >
> > > I think one that Helmut mentioned is the most important and should cover
> > > most
> > > cases.
> >
> > Paths to uic. moc et all.
>
> IIRC, uic and moc produce the same output on all architectures, so we do not
> need cross wrappers for them.
>
> So calling the native /usr/lib/qt6/bin/{uic,moc} should be absolutely fine.
I agree with all of that.
Lisandro also asked:
| sbuild -host arm64 -sAd unstable some_qt6_app.dsc a good way to test this?
I's --host rather than -host.
Do not pass -A. To simplify matters, cross builds are always assumed to
be arch-only.
Other than that, this should work.
Maybe you should check that qemu's binfmt integration is disabled.
Otherwise, you may be a successful build that only happened to work due
to using qemu. You can run "update-binfmts --disable" to disable all
binfmts and reenable them afterwards.
Helmut
Bug#1031690: Regression in wayland mixed DPI setups
Package: plasma-workspace-wayland Version: 4:5.27.0-1 Severity: important Tags: upstream Hello there, it looks like there's a regression in mixed DPI setups (one hiDPI screen at "150%", a lower-DPI screen at "100%"), on Wayland, for some non-KDE applications. In my case, flatpak firefox has too small tabs depending on which screen it initially got launched. This was working much better pre-5.27. It looks like upstream is on this; * https://bugs.kde.org/show_bug.cgi?id=443215 * https://bugs.kde.org/show_bug.cgi?id=465733 But I couldn't really identify directly which patch, and on which software, to test. Happy to build/test here. Best, OdyX -- System Information: Debian Release: bookworm/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (500, 'testing'), (1, 'buildd-experimental'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-3-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=fr_CH.UTF-8, LC_CTYPE=fr_CH.UTF-8 (charmap=UTF-8), LANGUAGE=fr_CH:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages plasma-workspace-wayland depends on: ii kpackagetool5 5.103.0-1 ii kwayland-integration 5.27.0-1 ii kwin-wayland 4:5.27.0-1 ii libc6 2.36-8 ii libkf5configcore5 5.103.0-1 ii libkf5configgui5 5.103.0-1 ii libkf5configwidgets5 5.103.0-1 ii libkf5coreaddons5 5.103.0-1 ii libkf5guiaddons5 5.103.0-1 ii libkf5kcmutils5 5.103.0-1 ii libkf5kiogui5 5.103.0-1 ii libkf5notifications5 5.103.0-1 ii libkf5package55.103.0-1 ii libkf5service-bin 5.103.0-1 ii libkf5service55.103.0-1 ii libkworkspace5-5 4:5.27.0-1 ii libphonon4qt5-4 4:4.11.1-4 ii libqt5core5a 5.15.8+dfsg-2 ii libqt5dbus5 5.15.8+dfsg-2 ii libqt5gui55.15.8+dfsg-2 ii libstdc++612.2.0-14 ii phonon4qt54:4.11.1-4 ii plasma-workspace 4:5.27.0-1 ii qtwayland55.15.8-2 plasma-workspace-wayland recommends no packages. plasma-workspace-wayland suggests no packages. -- no debconf information
Bug#1030980: Qt6::qmake IMPORTED_LOCATION points to build architecture qmake6
El lun, 20 de feb. de 2023 04:49, Dmitry Shachnev
escribió:
> On Sun, Feb 19, 2023 at 08:20:43PM -0300, Lisandro Damián Nicanor Pérez
> Meyer wrote:
> > On Sun, 19 Feb 2023 at 16:59, Dmitry Shachnev
> wrote:
> > > What are these paths?
> > >
> > > I think one that Helmut mentioned is the most important and should
> cover most
> > > cases.
> >
> > Paths to uic. moc et all.
>
> IIRC, uic and moc produce the same output on all architectures, so we do
> not
> need cross wrappers for them.
>
> So calling the native /usr/lib/qt6/bin/{uic,moc} should be absolutely fine.
Exactly, and that's what I'm trying to check
Bug#1026062: Upstream bugs
https://bugs.kde.org/show_bug.cgi?id=463576 and https://bugs.kde.org/show_bug.cgi?id=462706 appears to be the obvious upstream kde bug. which implicates PackageKit: https://github.com/PackageKit/PackageKit-Qt/issues/42 which has https://github.com/PackageKit/PackageKit-Qt/pull/45 as a potential fix. Also as a hacky workaround, the bug seems to occur when updating the package lists, if you've recently refreshed the package lists (eg via "apt update") then the bug isn't triggered.
