Processed: Mark as pending
Processing control commands: > tag -1 pending Bug #976274 [libqt5gui5] libqt5gui5: Please build Qt5 with configure option -xcb-native-painting Added tag(s) pending. -- 976274: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976274 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#976274: Mark as pending
Control: tag -1 pending Hi! This is already fixed in the current experimental branch, for which we are only waiting for the RT to allow us to push to unstable. -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/
Processed: Bug#875847 marked as pending in qttools-opensource-src
Processing control commands: > tag -1 pending Bug #875847 [qttools5-dev-tools] qttools5-dev-tools: .qhc files not reproducible Added tag(s) pending. -- 875847: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875847 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#976389: libqt5quick5-gles: With libqt5quick5-gles KDE icons & widgets don't appear, with libqt5quick5 it works
Package: libqt5quick5-gles Version: 5.15.1+dfsg-2 Severity: normal When I had a system running with libqt5quick5-gles the display was horribly messed up with missing icons and KDE window controls. I could work around it by setting MESA_EXTENSION_OVERRIDE=”-GL_EXT_bgra -GL_EXT_texture_format_BGRA″ in the environment for the user (which didn't affect SDDM which still had mangled display). When I ran "apt remove libqt5quick5-gles" (which installed libqt5quick5) and rebooted (I could have just restarted sddm but wanted to get the new kernel) it worked without setting any environment variables. Using the MESA_EXTENSION_OVERRIDE variable broke Warzone2100 (for reasons I have not figured out), but using libqt5quick5 KDE and Warzone2100 both work perfectly. https://etbe.coker.com.au/2020/12/04/kde-icons-disappearing-unstable/ I wrote a blog post about this which has some more details. https://inductive-kickback.com/2017/02/mystery-black-window-workaround-druid-back-in-development/ The above blog post has the most technical detail about this including some test Qt code. In what situations does libqt5quick5-gles work better than libqt5quick5? -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (700, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.0-4-amd64 (SMP w/4 CPU threads) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: default Versions of packages libqt5quick5-gles depends on: ii libc6 2.31-5 ii libqt5core5a [qtbase-abi-5-15-1] 5.15.1+dfsg-4 ii libqt5gui5 5.15.1+dfsg-4 ii libqt5network5 5.15.1+dfsg-4 ii libqt5qml5 [qtdeclarative-abi-5-15-1] 5.15.1+dfsg-3 ii libqt5qmlmodels5 5.15.1+dfsg-3 ii libstdc++6 10.2.0-19 libqt5quick5-gles recommends no packages. libqt5quick5-gles suggests no packages.
Bug#972309: marked as done (libkf5kgeomap: FTBFS with DEB_BUILD_OPTIONS=reproducible=+fixfilepath)
Your message dated Fri, 04 Dec 2020 21:44:36 + with message-id and subject line Bug#974913: Removed package(s) from unstable has caused the Debian Bug report #972309, regarding libkf5kgeomap: FTBFS with DEB_BUILD_OPTIONS=reproducible=+fixfilepath 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.) -- 972309: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972309 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libkf5kgeomap Severity: normal Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: fixfilepath ftbfs X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org When the reproducible=+fixfilepath feature is enabled (either through DEB_BUILD_OPTIONS, or using a dpkg that enables this by default), libkf5kgeomap fails to build from source: http://qa-logs.debian.net/2020/09/26.fixfilepath/libkf5kgeomap_20.04.3-1_unstable_fixfilepath.log While the "fixfilepath" feature is not currently enabled by dpkg-buildflags by default, it may become the default at some point in the future, and can be triggered manually by setting DEB_BUILD_OPTIONS=reproducible=+fixfilepath in the build environment. It is also used in the tests.reproducible-builds.org infrastructure when testing unstable and experimental. More information about this issue is available at: https://tests.reproducible-builds.org/debian/issues/unstable/ftbfs_due_to_f-file-prefix-map_issue.html I have not identified the exact cause of this issue, but a common trigger is test suites expecting __FILE__ to resolve to an absolute path. The attached patch works around this issue by disabling the fixfilepath feature in debian/rules using DEB_BUILD_MAINT_OPTIONS=-fixfilepath. Thanks for maintaining libkf5kgeomap! live well, vagrant From efe57fcf0bd79025ba8e0620ebf9b1e7a25c10d2 Mon Sep 17 00:00:00 2001 From: Vagrant Cascadian Date: Fri, 16 Oct 2020 00:18:39 + Subject: [PATCH] debian/rules: Disable fixfilepath feature, as it triggers build failures when enabled. https://tests.reproducible-builds.org/debian/issues/unstable/ftbfs_due_to_f-file-prefix-map_issue.html --- debian/rules | 2 ++ 1 file changed, 2 insertions(+) diff --git a/debian/rules b/debian/rules index 89aae6a..1aee045 100755 --- a/debian/rules +++ b/debian/rules @@ -1,5 +1,7 @@ #!/usr/bin/make -f +# Disable fixfilepath as it triggers build failures. +export DEB_BUILD_MAINT_OPTIONS=reproducible=-fixfilepath l10npkgs_firstversion_ok := 4:16.04.3-7~ include /usr/share/pkg-kde-tools/qt-kde-team/2/l10n-packages.mk -- 2.28.0 signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Version: 20.04.3-1+rm Dear submitter, as the package libkf5kgeomap has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/974913 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Joerg Jaspert (the ftpmaster behind the curtain)--- End Message ---
Bug#974913: Removed package(s) from unstable
Version: 20.04.3-1+rm Dear submitter, as the package libkf5kgeomap has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/974913 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Joerg Jaspert (the ftpmaster behind the curtain)
Bug#974913: Removed package(s) from unstable
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: libkf5kgeomap | 20.04.3-1 | source libkf5kgeomap-data | 20.04.3-1 | all libkf5kgeomap-dev | 20.04.3-1 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x libkf5kgeomap10.0.0 | 20.04.3-1 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x --- Reason --- ROM; no more used; dead upstream -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 974...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/974913 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Joerg Jaspert (the ftpmaster behind the curtain)
Bug#975397: Removed package(s) from unstable
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: cantor-backend-scilab | 4:20.04.3-1 | armhf, i386 --- Reason --- ROM; no more built on some archs, as no more usable there -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. Bugs which have been reported against this package are not automatically removed from the Bug Tracking System. Please check all open bugs and close them or re-assign them to another package if the removed package was superseded by another one. The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 975...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/975397 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Joerg Jaspert (the ftpmaster behind the curtain)
