Bug#1072357: pkg-kde-tools: FTBFS on armhf/mips64el/riscv64: Broken tests due to 0.17.2 changes
Source: pkg-kde-tools
Version: 0.17.2
Severity: grave
X-Debbugs-CC: mity...@debian.org
Dear Debian pkg-kde-tools maintainers,
It became clear that the fix in 0.17.2 broke some of the tests related to
time_t on several architectures, and the FTBFS is caused by mixing {time_t}
and {int64_t}. Please check the build logs for more information.
*
https://buildd.debian.org/status/fetch.php?pkg=pkg-kde-tools=armhf=0.17.2=1716721655=0
*
https://buildd.debian.org/status/fetch.php?pkg=pkg-kde-tools=mips64el=0.17.2=1716721905=0
*
https://buildd.debian.org/status/fetch.php?pkg=pkg-kde-tools=riscv64=0.17.2=1716721753=0
Another similar failure in the ports arch (loong64):
*
https://buildd.debian.org/status/fetch.php?pkg=pkg-kde-tools=loong64=0.17.2=1716722208=0
Thanks,
Boyuan Yang
signature.asc
Description: This is a digitally signed message part
Bug#1071279: pkg-kde-tools: Nondeterministic, broken batchpatch outcome
Source: pkg-kde-tools Version: 0.17.1 Severity: important X-Debbugs-CC: p...@debian.org mity...@debian.org delta...@debian.org Dear Debian pkg-kde-tools developers, As discussed in OFTC #debian-qt-kde, while utilizing pkg-kde-tools in the packaging of src:taglib, I found that the batchpatch functionality is not yielding deterministic results: = [~/src/debian/multimedia-team/taglib] [debian/experimental *] -> % git rev-parse HEAD ; for i in 1 2 3 4 5 6 7 8 9; do git restore debian/libtag2.symbols ; pkgkde-symbolshelper batchpatch -v 2.0.1 < ./taglib_experimental_logs/* > /dev/null 2> /dev/null ; git diff | wc -l ; done 3609f305d309fe0dd4e24b9579ed80ec06555f69 0 22 22 13 31 22 0 36 31 == Steps to reproduce: 1. git clone https://salsa.debian.org/multimedia-team/taglib 2. cd taglib/ 3. wget 'https://salsa.debian.org/byang/pkg-kde-tools-bugreport-20240517/-/raw/main/taglib_experimental_logs_20240517.tar.xz?ref_type=heads=false' -O a.xz 4. tar xavf a.xz 5. git checkout 3609f305d309fe0dd4e24b9579ed80ec06555f69 6. git rev-parse HEAD ; for i in 1 2 3 4 5 6 7 8 9; do git restore debian/libtag2.symbols ; taskset 1 pkgkde-symbolshelper batchpatch -v 2.0.1 < ./taglib_experimental_logs/* > /dev/null 2> /dev/null ; git diff | wc -l ; done Expected behavior: The batchpatch invocations always yield the same result (and line numbers). The current behavior: The batchpatch invocations yield different outputs (different line numbers). Please consider looking into it. Thanks! Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Joining the Debian Qt/KDE Team and requesting Salsa access
Hi all, I am looking to join Debian's Qt/KDE Team and see what I can do here. My Salsa username is byang. I have multiple packages that involves the Qt and KDE software stack, and handling them from inside the team could be a better choice. To start with, I am looking at handling the libkimageannotator transition [1][2]. It involves src:gwenview, which will need some tweak from the gwenview side (maintainer in CC list). Since KDE software is already depending on the ibkcolorpicker / libkimageannotator / ksnip series of projects, I am wondering if moving their package maintenance under KDE Extras umbrella would be reasonable. There is a "k" in their names but no libkf* libraries are used. Thanks, Boyuan Yang [1] https://release.debian.org/transitions/html/auto-kimageannotator.html [2] https://github.com/ksnip/kColorPicker/issues/13 signature.asc Description: This is a digitally signed message part
Bug#1054379: prison-kf5: Please migrate away from transitional pkg libzxingcore-dev
Source: prison-kf5 X-Debbugs-Cc: by...@debian.org couc...@debian.org Version: 5.107.0-1 Severity: normal Tags: patch sid Usertags: libzxingcore-dev-removal Dear Maintainer, Your package prison-kf5 build-depends on package libzxingcore-dev, which is a transitional package replaced by libzxing-dev. Package libzxing-dev is present in Debian Bookworm, Debian Sid and Debian Testing. Please replace libzxingcore-dev with libzxing-dev in debian/control file for your next package upload. Thanks! Best Regards, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1054378: kitinerary: Please migrate away from transitional pkg libzxingcore-dev
Source: kitinerary X-Debbugs-Cc: by...@debian.org delta...@debian.org Version: 22.12.3-2 Severity: normal Tags: patch Usertags: libzxingcore-dev-removal Dear Maintainer, Your package kitinerary build-depends on package libzxingcore-dev, which is a transitional package replaced by libzxing-dev. Package libzxing-dev is present in Debian Bookworm, Debian Sid and Debian Testing. Please replace libzxingcore-dev with libzxing-dev in debian/control file for your next package upload. Thanks! Best Regards, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1053830: kimageformats: diff for NMU version 5.107.0-3.1
Control: tags 1053830 + pending X-Debbugs-CC: couc...@debian.org p...@debian.org Dear maintainer, I've prepared an NMU for kimageformats (versioned as 5.107.0-3.1) and uploaded it to DELAYED/7. Please feel free to tell me if I should delay it longer. Regards. diff -Nru kimageformats-5.107.0/debian/changelog kimageformats-5.107.0/debian/changelog --- kimageformats-5.107.0/debian/changelog 2023-07-05 14:08:33.0 -0400 +++ kimageformats-5.107.0/debian/changelog 2023-10-15 16:16:43.0 -0400 @@ -1,3 +1,13 @@ +kimageformats (5.107.0-3.1) unstable; urgency=medium + + * Non-maintainer upload. + + [ Adrian Bunk ] + * debian/rules: Specify -fexcess-precision=fast for i386 to avoid FTBFS +due to GCC 13 changing its default behavior. (Closes: #1053830) + + -- Boyuan Yang Sun, 15 Oct 2023 16:16:43 -0400 + kimageformats (5.107.0-3) unstable; urgency=medium * Team upload. diff -Nru kimageformats-5.107.0/debian/rules kimageformats-5.107.0/debian/rules --- kimageformats-5.107.0/debian/rules 2023-07-05 13:40:08.0 -0400 +++ kimageformats-5.107.0/debian/rules 2023-10-15 16:16:40.0 -0400 @@ -5,7 +5,7 @@ export DEB_BUILD_MAINT_OPTIONS = hardening=+all reproducible=-fixfilepath ifeq ($(DEB_HOST_ARCH_CPU),i386) - export DEB_CXXFLAGS_MAINT_APPEND += -ffloat-store + export DEB_CXXFLAGS_MAINT_APPEND += -ffloat-store -fexcess-precision=fast endif %: signature.asc Description: This is a digitally signed message part
Bug#1042821: Installing libkf5purpose5 (indirectly) brings in kdeconnect package, invalidating related avoidance
Package: qml-module-org-kde-purpose Severity: normal Version: 5.107.0-1 X-Debbugs-CC: couc...@debian.org p...@debian.org Dear Debian KDE/Plasma package maintainers, I know it is not be a pleasant bug, but I believe the current behavior of package qml-module-org-kde-purpose and libkf5purpose5 is a little bit tricky since installing either of them will bring in package kde-connect by default, which may be undesirable. Details below: * Installing okular will brings in kde-connect (!) by default, which may be unfavorable. Reason: -> % LC_ALL=C aptitude why kdeconnect i okular Dependslibkf5purpose5 (>= 5.68.0~) i A libkf5purpose5 Recommends qml-module-org-kde-purpose (= 5.107.0-1) i A qml-module-org-kde-purpose Recommends kdeconnect * It is caused by https://salsa.debian.org/qt-kde-team/kde/purpose/-/commit/1ba9a778588bf66250fd079e674c2c96abd50991 in 2016, which already tries to downgrade hard dependency to recommendation, but obviously did not work. * There was a later 2020 attempt to avoid such behavior by Pino at https://salsa.debian.org/qt-kde-team/kde/purpose/-/commit/b107335c579e3576a109515a37f277b54e4627d6 , yet the behavior of qml-module-org-kde-purpose invalidated this effort. See previous "aptitude why" result. As such, I believe b107335c was an insufficient fix. Package qml-module-org- kde-purpose should further demote recommendation of kde-connect to suggestion. While this may not be an ideal fix, please let me know if you have further thoughts. Thanks! Best, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1002192: kitinerary: diff for NMU version 21.08.1-1.1
Control: tags 1002192 + pending Dear maintainer, I've prepared an NMU for kitinerary (versioned as 21.08.1-1.1) and uploaded it to DELAYED/3. Please feel free to tell me if I should delay it longer. Regards. diff -Nru kitinerary-21.08.1/debian/changelog kitinerary- 21.08.1/debian/changelog --- kitinerary-21.08.1/debian/changelog 2021-09-10 18:21:58.0 -0400 +++ kitinerary-21.08.1/debian/changelog 2022-01-30 21:09:15.0 -0500 @@ -1,3 +1,11 @@ +kitinerary (21.08.1-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * debian/control: Add missing build-dependency iso-codes to fix +FTBFS. (Closes: #1002192) + + -- Boyuan Yang Sun, 30 Jan 2022 21:09:15 -0500 + kitinerary (21.08.1-1) unstable; urgency=medium [ Norbert Preining ] diff -Nru kitinerary-21.08.1/debian/control kitinerary-21.08.1/debian/control --- kitinerary-21.08.1/debian/control 2021-09-10 18:21:58.0 -0400 +++ kitinerary-21.08.1/debian/control 2022-01-30 21:09:12.0 -0500 @@ -8,6 +8,7 @@ debhelper-compat (= 13), extra-cmake-modules (>= 5.83.0~), gettext, + iso-codes, libkf5archive-dev (>= 5.71.0~), libkf5calendarcore-dev (>= 5:5.83.0~), libkf5contacts-dev (>= 5:5.83.0~), signature.asc Description: This is a digitally signed message part
Bug#978459: plasma-base: diff for NMU version 5.20.0+nmu1
Control: tags -1 -pending -patch Hi, 在 2021-01-27星期三的 08:28 +0900，Norbert Preining写道： > On Tue, 26 Jan 2021, Boyuan Yang wrote: > > I've prepared an NMU for plasma-base (versioned as 5.20.0+nmu1) and > > uploaded it to DELAYED/7. Please feel free to tell me if I > > No, please stop that. > > I will request removal of this package. > > It should NOT transition to testing, as I have already stated. > > Thanks Thanks for the info. I have already removed it from the DELAYED queue. Regards, Boyuan Yang
Bug#978459: plasma-base: diff for NMU version 5.20.0+nmu1
Control: tags 978459 + patch Control: tags 978459 + pending Dear maintainer, I've prepared an NMU for plasma-base (versioned as 5.20.0+nmu1) and uploaded it to DELAYED/7. Please feel free to tell me if I should delay it longer. Regards, Boyuan Yang diff -Nru plasma-base-5.20.0/debian/changelog plasma-base- 5.20.0+nmu1/debian/changelog --- plasma-base-5.20.0/debian/changelog 2020-12-02 18:32:56.0 -0500 +++ plasma-base-5.20.0+nmu1/debian/changelog2021-01-26 17:45:28.0 -0500 @@ -1,3 +1,11 @@ +plasma-base (5.20.0+nmu1) unstable; urgency=medium + + * Non-maintainer upload. + * No change source-only upload for testing migration. +(Closes: #978459) + + -- Boyuan Yang Tue, 26 Jan 2021 17:45:28 -0500 + plasma-base (5.20.0) unstable; urgency=medium [ Norbert Preining ] signature.asc Description: This is a digitally signed message part
Bug#978459: plasma-base: A source-only upload is needed
Source: plasma-base Version: 5.20.0 Severity: important X-Debbugs-CC: norb...@preining.info patfr...@gmail.com sgmo...@kde.org Dear Debian plasma-base package maintainer, Just to let you know that we need an extra source-only upload for package plasma-base ( https://tracker.debian.org/pkg/plasma-base ) in Debian to allow it to migrate to Debian Testing. Please fix it following instructions on https://wiki.debian.org/SourceOnlyUpload . Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#949681: kitinerary: Consider adding ZXing-C++ build-dependency
Source: kitinerary Version: 19.08.3-1 Severity: normal X-Debbugs-CC: he...@debian.org Dear kitinerary maintainers, I just had zxing-cpp packaged and put into Debian: https://tracker.debian.org/pkg/zxing-cpp . Since kitinerary has an optional build dependency on this library, you are welcome to add it as a build-dependency and test the functionality. Co- maintenance is also welcome. -- Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#948439: Please switch to enchant-2 instead of enchant(1)
Control: tags -1 + patch X-Debbugs-CC: sgmo...@kde.org I am preparing a patch for this bug. On top of current git HEAD code, this actually builds successfully. Feel free to let me know if you have any issues. -- Thanks, Boyuan Yang On Wed, 08 Jan 2020 18:15:10 +0100 Laurent Bigonville wrote: > Source: qtspell > Version: 0.8.5-2 > Severity: wishlist > Control: block 947979 by -1 > > Hi, > > Could you please switch qtspell to enchant-2? > > Quickly looking at the code, it only requires to change libenchant-dev > to libenchant-2-dev > > Kind regards, > > Laurent Bigonville > > -- System Information: > Debian Release: bullseye/sid > APT prefers unstable-debug > APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental- debug'), (1, 'experimental') > Architecture: amd64 (x86_64) > > Kernel: Linux 5.4.0-2-amd64 (SMP w/8 CPU cores) > Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr (charmap=UTF-8) > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy From 8c0852f37e8414dce2d7d16b95cfa1b630396282 Mon Sep 17 00:00:00 2001 From: Boyuan Yang Date: Fri, 10 Jan 2020 14:48:02 -0500 Subject: [PATCH] debian/changelog: Document changes --- debian/changelog| 11 +++ debian/control | 2 +- debian/libqtspell-qt5-0.symbols | 4 ++-- 3 files changed, 14 insertions(+), 3 deletions(-) diff --git a/debian/changelog b/debian/changelog index 03b39ef..2cf0de9 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,14 @@ +qtspell (0.8.5-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * debian/control: ++ Switch build-dependency from enchant 1.x to enchant + 2.x. + * debian/libqtspell-qt5-0.symbols: Refresh symbols after +switching to enchant 2.x. + + -- Boyuan Yang Fri, 10 Jan 2020 15:06:26 -0500 + qtspell (0.8.5-2) unstable; urgency=medium * Fix duplicate short descriptions. diff --git a/debian/control b/debian/control index 1bd7d7a..781ce95 100644 --- a/debian/control +++ b/debian/control @@ -7,7 +7,7 @@ Build-Depends: cmake, debhelper (>=12), doc-base, doxygen, - libenchant-dev, + libenchant-2-dev, pkg-config, pkg-kde-tools, qtbase5-dev, diff --git a/debian/libqtspell-qt5-0.symbols b/debian/libqtspell-qt5-0.symbols index 54de5ed..891d305 100644 --- a/debian/libqtspell-qt5-0.symbols +++ b/debian/libqtspell-qt5-0.symbols @@ -125,11 +125,10 @@ libqtspell-qt5.so.0 libqtspell-qt5-0 #MINVER# _ZN7QtSpell9CodetableC2Ev@Base 0.8.5 _ZN7QtSpell9CodetableD1Ev@Base 0.8.5 _ZN7QtSpell9CodetableD2Ev@Base 0.8.5 + (optional=templinst)_ZN7enchant14set_prefix_dirENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 0.8.5 _ZN7enchant4Dict13s_describe_fnEPKcS2_S2_S2_Pv@Base 0.8.5 - _ZN7enchant6Broker10m_instanceE@Base 0.8.5 _ZN7enchant6BrokerD1Ev@Base 0.8.5 _ZN7enchant6BrokerD2Ev@Base 0.8.5 - _ZN7enchant9Exception4whatEv@Base 0.8.5 _ZN7enchant9ExceptionC1EPKc@Base 0.8.5 _ZN7enchant9ExceptionC2EPKc@Base 0.8.5 _ZN7enchant9ExceptionD0Ev@Base 0.8.5 @@ -161,6 +160,7 @@ libqtspell-qt5.so.0 libqtspell-qt5-0 #MINVER# _ZNK7QtSpell7Checker22getSpellingSuggestionsERK7QString@Base 0.8.5 _ZNK7QtSpell7Checker9checkWordERK7QString@Base 0.8.5 _ZNK7QtSpell9Codetable6lookupERK7QStringRS1_S4_S4_@Base 0.8.5 + _ZNK7enchant9Exception4whatEv@Base 0.8.5 (optional=templinst)_ZNK8QMapDataI7QStringS0_E8findNodeERKS0_@Base 0.8.5 (optional=templinst)_ZNK8QMapNodeI7QStringS0_E4copyEP8QMapDataIS0_S0_E@Base 0.8.5 (optional=templinst)_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE17_M_realloc_insertIJS5_EEEvN9__gnu_cxx17__normal_iteratorIPS5_S7_EEDpOT_@Base 0.8.5 -- 2.25.0.rc2 signature.asc Description: This is a digitally signed message part
Your Debian package(s) will not migrate to testing
> From: Lisandro Damián Nicanor Pérez Meyer > > I asked for a binNMU days ago and it was scheduled. I'll take a look when I get home, but seems odd. I thought there's an arch:all binary package that can never be binNMU-ed. This looks like a known deficiency of binNMU. Is there any possiblilty to make another sourceful (and probably no-change) rebuild & upload? As a passer-by that happened to read this message, I can also help make an upload if you don't mind. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#923056: systemsettings: diff for NMU version 4:5.14.5-1.1
Package: systemsettings Version: 4:5.14.5-1 Severity: normal Tags: patch pending Dear maintainer, I've prepared an NMU for systemsettings (versioned as 4:5.14.5-1.1) and uploaded it to DELAYED/3. Please feel free to tell me if I should delay it longer. On behalf of Debian Chinese Team and KDE translation team for zh_CN (Simplified Chinese), I'm proposing a patch to fix a zh_CN translation error within systemsettings.desktop. Nothing else is touched. This issue is fixed upstream with the release of Plasma 5.15. Please drop this patch after we package Plasma 5.15 into Debian. Regards. diff -Nru systemsettings-5.14.5/debian/changelog systemsettings- 5.14.5/debian/changelog --- systemsettings-5.14.5/debian/changelog 2019-01-24 07:26:17.0 -0500 +++ systemsettings-5.14.5/debian/changelog 2019-02-23 12:45:05.0 -0500 @@ -1,3 +1,11 @@ +systemsettings (4:5.14.5-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Cherry-pick from upstream trunk to fix a bug in zh_CN +(Simplified Chinese) .desktop file translation. + + -- Boyuan Yang Sat, 23 Feb 2019 12:45:05 -0500 + systemsettings (4:5.14.5-1) unstable; urgency=medium * New upstream release (5.14.5). diff -Nru systemsettings-5.14.5/debian/patches/0001-systemsettings.desktop- Fix-zh_CN-translation-bug-in-.patch systemsettings-5.14.5/debian/patches/0001- systemsettings.desktop-Fix-zh_CN-translation-bug-in-.patch --- systemsettings-5.14.5/debian/patches/0001-systemsettings.desktop-Fix- zh_CN-translation-bug-in-.patch 1969-12-31 19:00:00.0 -0500 +++ systemsettings-5.14.5/debian/patches/0001-systemsettings.desktop-Fix- zh_CN-translation-bug-in-.patch 2019-02-23 12:44:59.0 -0500 @@ -0,0 +1,39 @@ +From: Boyuan Yang +Date: Sat, 23 Feb 2019 12:36:41 -0500 +Subject: Fix 5.14.x zh_CN translation bug in desktop file + +Applied-Upstream: https://cgit.kde.org/systemsettings.git/commit/?id=da729d548b78c6d32c44e7769337901c989cf1d4 + +The Simplified Chinese translation for systemsettings.desktop has two major +translation errors in GenericName[zh_CN] and Name[zh_CN]. They exist in +Plasma 5.14.x branch but are fixed in trunk and 5.15.x branch. +This patch cherry-picks the fix. + +Signed-off-by: Boyuan Yang + +--- + app/systemsettings.desktop | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/app/systemsettings.desktop b/app/systemsettings.desktop +index 5a1faf5..dfe9833 100755 +--- a/app/systemsettings.desktop b/app/systemsettings.desktop +@@ -84,7 +84,7 @@ GenericName[uz]=Tizim moslamalari + GenericName[uz@cyrillic]=Тизим мосламалари + GenericName[wa]=Apontiaedjes do sistinme + GenericName[x-test]=xxSystem Settingsxx +-GenericName[zh_CN]=System Settings,系统设置 ++GenericName[zh_CN]=系统设置 + GenericName[zh_TW]=系統設定 + + Name=System Settings +@@ -169,7 +169,7 @@ Name[uz]=Tizim moslamalari + Name[uz@cyrillic]=Тизим мосламалари + Name[wa]=Apontiaedjes do sistinme + Name[x-test]=xxSystem Settingsxx +-Name[zh_CN]=System Settings,系统设置 ++Name[zh_CN]=系统设置 + Name[zh_TW]=系統設定 + + Comment=Configuration tools for your computer diff -Nru systemsettings-5.14.5/debian/patches/series systemsettings- 5.14.5/debian/patches/series --- systemsettings-5.14.5/debian/patches/series 1969-12-31 19:00:00.0 -0500 +++ systemsettings-5.14.5/debian/patches/series 2019-02-23 12:37:00.0 -0500 @@ -0,0 +1 @@ +0001-systemsettings.desktop-Fix-zh_CN-translation-bug-in-.patch signature.asc Description: This is a digitally signed message part
Bug#910317: QtWebEngine in unstable is constantly crashing
Package: python3-pyqt5.qtwebengine
Version: 5.11.2+dfsg-1
Severity: serious
X-Debbugs-CC: debian-qt-kde@lists.debian.org
Control: affects -1 + libqt5webengine5
Dear Debian Qt/KDE maintainers and pyqt5.qtwebengine maintainers,
Current QtWebEngine in Debian Unstable would easily crash. That
happens after recent upgrade of libkf5.
For example, run the following script under python3:
$ export LC_ALL=C.UTF-8
$ export LANG=C
$ cat ./test.py
import sys
from PyQt5.QtWidgets import QApplication
from PyQt5.QtWidgets import QMainWindow
from PyQt5.QtWebEngineWidgets import QWebEngineView
from PyQt5.QtCore import QUrl
def main():
app = QApplication(sys.argv)
window = QMainWindow()
window.setWindowTitle('PyQt Demo')
window.setGeometry(320, 180, 960, 540)
view = QWebEngineView()
view.load(QUrl('http://leafletjs.com/')) # error here
window.setCentralWidget(view)
window.show()
sys.exit(app.exec_())
if __name__ == '__main__':
main()
$ python3 ./test.py
[1004/140404.438632:WARNING:stack_trace_posix.cc(699)] Failed to open
file: /tmp/.glBfSxZo (deleted)
Error: No such file or directory
[8494:8515:1004/140404.647050:ERROR:nss_util.cc(727)] After loading
Root Certs, loaded==false: NSS error code: -8018
Received signal 11 SEGV_MAPERR 0010
#0 0x7fc98c03e76e
#1 0x7fc98c03e880
#2 0x7fc98c03eeb7
#3 0x7fc9969db8e0
#4 0x7fc990771604
#5 0x7fc98aa8d660
#6 0x7fc98aabde3c
#7 0x7fc98a0af500 QQuickWindowPrivate::updateDirtyNode()
#8 0x7fc98a0af963 QQuickWindowPrivate::updateDirtyNodes()
#9 0x7fc98a0b0e22 QQuickWindowPrivate::syncSceneGraph()
#10 0x7fc98a16ce49 QQuickRenderControl::sync()
#11 0x7fc989c7e0c6
#12 0x7fc989c7e2a6
#13 0x7fc994b0003b QObject::event()
#14 0x7fc99548ac6b QWidget::event()
#15 0x7fc989c81e2d QQuickWidget::event()
#16 0x7fc990771bf0
#17 0x7fc99544c4a1 QApplicationPrivate::notify_helper()
#18 0x7fc995453ae0 QApplication::notify()
#19 0x7fc995d1f11e
#20 0x7fc994ad6589 QCoreApplication::notifyInternal2()
#21 0x7fc994b27648 QTimerInfoList::activateTimers()
#22 0x7fc994b27ea4
#23 0x7fc9939acc3e g_main_context_dispatch
#24 0x7fc9939aced8
#25 0x7fc9939acf6c g_main_context_iteration
#26 0x7fc994b28233 QEventDispatcherGlib::processEvents()
#27 0x7fc97df51ee1
#28 0x7fc994ad525b QEventLoop::exec()
#29 0x7fc994add3d2 QCoreApplication::exec()
#30 0x7fc995ce214b
#31 0x005068bf
#32 0x0050a4e9 _PyEval_EvalFrameDefault
#33 0x00505d58
#34 0x00506a8d
#35 0x0050a4e9 _PyEval_EvalFrameDefault
#36 0x005088b8
#37 0x0050a023 PyEval_EvalCode
#38 0x00635f82
#39 0x0063603a PyRun_FileExFlags
#40 0x006397f8 PyRun_SimpleFileExFlags
#41 0x0063a38a Py_Main
#42 0x004ac090 main
#43 0x7fc996433b17 __libc_start_main
#44 0x005b35aa _start
r8: 17281b04 r9: 017ae3e0 r10: 17281b04
r11: 0001
r12: r13: 017651c0 r14: 7fc994b91660
r15: 017650e0
di: 01728da0 si: bp: 7ffc01652bc0
bx: 01713dd0
dx: 7fc994b91660 ax: 01082000 cx: 7fc994b91678
sp: 7ffc016527e0
ip: 7fc990771604 efl: 00010202 cgf: 002b0033
erf: 0004
trp: 000e msk: cr2: 0010
[end of stack trace]
Calling _exit(1). Core file will not be generated.
$
--
Thanks,
Boyuan Yang
Re: Bug#905129: im-config: Wrongly run shell scripts with user's shell interpreter, raises error with zsh
Osamu Aoki 于2018年7月31日周二 下午11:55写道：
>
> Hi,
>
> On Tue, Jul 31, 2018 at 10:29:11PM +0800, Boyuan Yang wrote:
> > Package: im-config
> > Severity: important
> > Version: 0.30-1
> > X-Debbugs-CC: os...@debian.org
> >
> > Hi Osamu and debian-input-method team members,
> >
> > TL;DR: file /etc/X11/Xsession.d/70im-config_launch is *not* called by
> > /bin/sh,
> > as written in shabang; it is called by user's shell interpreter
> > instead, which may
> > result in unexpected outcome when user's default shell is neither
> > /bin/dash nor /bin/bash.
>
> I am aware ... but This is actually problem on how X startup calls in
> /etc/X11/Xsession.d/* are called by desktop environment. It should use
> /bin/sh ...
>
> Which which DE do you use?
>
> But this is annoying. Maybe I should force dash as work around until
> alll DE startup codes are fixed.
I'm using SDDM. Just read some sddm code and I found that sddm seems to
have made things work like this on purpose. Haven't read others' code (like gdm)
yet. Maybe it is a convention?
Sending mail copy to s...@packages.debian.org for help.
I doubt that we could ever push all DM upstream to use /bin/sh to call
/etc/X11/Xsession. Writing workaround at im-config side seems more reasonable.
Besides, is it possible to force some /etc/X11/Xsession.d/* scripts to
be called by
/bin/sh? The Xsession file calls all snippets with "." ("source"),
which made it almost
impossible to switch shell interpreter.
--
Regards,
Boyuan Yang
> > Solution
> > ===
> >
> > While the zsh-incompatible grammar can be fixed (perhaps with a thorough
> > examination of all im-config source code), the problem that
> > Xsession.d scripts are executed by user shell interpreter is a big problem
> > and should receive further examination.
>
> Yes. Please file bug to DE otherwise you may be breaking other part of
> X startup.
>
> Osamu
Bug#904090: expeyes: Build-depends on Qt4 toolchain
Source: expeyes User: debian-qt-kde@lists.debian.org Usertags: qt4-removal X-Debbugs-CC: debian-qt-kde@lists.debian.org Severity: normal Tags: patch mail template starts Hi! As you might know we the Qt/KDE team are preparing to remove Qt4 as announced in: [announced] <https://lists.debian.org/debian-devel-announce/2017/08/msg6.html> Currently Qt4 has been dead upstream and we are starting to have problems maintaining it. In order to make this move, all packages directly or indirectly depending on the Qt4 libraries have to either get ported to Qt5 or eventually get removed from the Debian repositories. Therefore, please take the time and: - contact your upstream (if existing) and ask about the state of a Qt5 port of your application - if there are no activities regarding porting, investigate whether there are suitable alternatives for your users - if there is a Qt5 port that is not yet packaged, consider packaging it - if both the Qt4 and the Qt5 versions already coexist in the Debian archives, consider removing the Qt4 version = Porting = Some of us where involved in various Qt4 to Qt5 migrations [migration] and we know for sure that porting stuff from Qt4 to Qt5 is much much easier and less painful than it was from Qt3 to Qt4. We also understand that there is still a lot of software still using Qt4. Don't forget to take a look at the C++ API changes page [apichanges] whenever you start porting your application. [migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html [apichanges] http://doc.qt.io/qt-5/sourcebreaks.html For any questions and issues, do not hesitate to contact the Debian Qt/KDE team at debian-qt-kde@lists.debian.org The removal is being tracked in <https://wiki.debian.org/Qt4Removal> . mail template ends I noticed that your package is using Qt4 toolchain in build dependencies but has Qt5 as runtime dependency. This often indicates that some leftover remains for the Qt4 -> Qt5 migration and it would be great if we could fully use Qt5 toolchain. According to https://salsa.debian.org/georgesk/expeyes/blob/a562190dff060868f92a341af2198928d36e56a0/debian/control#L9 , the package is using pyqt4-dev-tools and qt4-linguist-tools. Please consider replacing them with pyqt5-dev-tools and qttools5-dev-tools. Patch provided: diff --git a/debian/control b/debian/control index 821e0f1..ea94087 100644 --- a/debian/control +++ b/debian/control @@ -6,7 +6,7 @@ Build-Depends: debhelper (>= 10), quilt, python3-all, python-all, dh-python, gcc-avr, binutils-avr, avr-libc (>=1:1.8.0+Atmel3.5.0), pkg-config, libgtk2.0-dev, x11proto-randr-dev (>= 1.5.0), - pyqt4-dev-tools, qt4-linguist-tools + pyqt5-dev-tools, qttools5-dev-tools Standards-Version: 4.1.5 Homepage: http://expeyes.in/ Vcs-Browser: https://salsa.debian.org/georgesk/expeyes -- Regards, Boyuan Yang signature.asc Description: This is a digitally signed message part.
Bug#886048: plasma-pa: Depends on gconf
On Mon, 01 Jan 2018 17:31:55 -0500 Jeremy Bicha wrote: > Source: plasma-pa > Version: 4:5.10.5-2 > Severity: important > User: pkg-gnome-maintain...@lists.alioth.debian.org > Usertags: oldlibs gconf > Tags: sid buster > > Your package depends or build-depends on gconf, but gconf will be > removed from Debian soon. > > gconf's last release was about 5 years ago. It has been replaced by > gsettings (provided in Debian by source glib2.0 ) > > I assume this depends on pulseaudio. > > References > -- > https://developer.gnome.org/gio/stable/ch34.html > https://developer.gnome.org/gio/stable/GSettings.html > > On behalf of the Debian GNOME team, > Jeremy Bicha Dear Debian KDE Developers, With Debian's pulseaudio 12.0 upload, pulseaudio has removed pulseaudio- module-gconf in favour of pulseaudio-module-gsettings, which would break current plasma-pa. (See also pulseaudio's bug https://bugs.debian.org/902181) This raises the urgency of dealing with the bug in plasma-pa to remove gconf dependency. Please look into this issue (Debian Bug #886048) again and solve it ASAP. -- Regards, Boyuan Yang signature.asc Description: This is a digitally signed message part.
Bug#894587: kdepim-addons: File conflict with akonadi-contacts-data 4:17.08.3-2
2018-04-02 8:16 GMT+08:00 Boyuan Yang <073p...@gmail.com>: > Source: kdepim-addons > Version: 17.12.3-1 > Severity: grave > Justification: renders package unusable > > Preparing to unpack .../6-kdepim-addons_17.12.3-1_amd64.deb ... > Unpacking kdepim-addons:amd64 (17.12.3-1) over (17.08.3-2) ... > dpkg: error processing archive /tmp/apt-dpkg-install-zBVare/6-kdepim- > addons_17.12.3-1_amd64.deb (--unpack): > trying to overwrite > '/usr/share/contacteditor/grantleetheme/default/addresseslocation.css', which > is also in package akonadi-contacts-data 4:17.08.3-2 > dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) > Errors were encountered while processing: > /tmp/apt-dpkg-install-zBVare/6-kdepim-addons_17.12.3-1_amd64.deb After enabling "--force-overwrite", the output is as follows: Preparing to unpack .../kdepim-addons_17.12.3-1_amd64.deb ... Unpacking kdepim-addons:amd64 (17.12.3-1) over (17.08.3-2) ... dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/usr/share/contacteditor/grantleetheme/default/addresseslocation.css', which is also in package akonadi-contacts-data 4:17.08.3-2 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/usr/share/contacteditor/grantleetheme/default/addresseslocation.html', which is also in package akonadi-contacts-data 4:17.08.3-2 -- Regards, Boyuan Yang
Bug#894587: kdepim-addons: File conflict with akonadi-contacts-data 4:17.08.3-2
Source: kdepim-addons Version: 17.12.3-1 Severity: grave Justification: renders package unusable Preparing to unpack .../6-kdepim-addons_17.12.3-1_amd64.deb ... Unpacking kdepim-addons:amd64 (17.12.3-1) over (17.08.3-2) ... dpkg: error processing archive /tmp/apt-dpkg-install-zBVare/6-kdepim- addons_17.12.3-1_amd64.deb (--unpack): trying to overwrite '/usr/share/contacteditor/grantleetheme/default/addresseslocation.css', which is also in package akonadi-contacts-data 4:17.08.3-2 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /tmp/apt-dpkg-install-zBVare/6-kdepim-addons_17.12.3-1_amd64.deb -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'buildd-unstable'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.15.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- no debconf information
Bug#893836: kdelibs4support: FTBFS on all architectures; missing symbols
Source: kdelibs4support Version: 5.44.0-1 Severity: grave Justification: renders package unusable Dear Maintainer, kdelibs4support FTBFS on all architectures (except "all"): https://buildd.debian.org/status/package.php?p=kdelibs4support Some symbols are missing: +#MISSING: 5.44.0-1# _ZTSN5KMenu12KMenuPrivateE@Base 4.96.0 _ZTSN5Solid10Networking8NotifierE@Base 4.99.0 _ZTSN5Solid15PowerManagement8NotifierE@Base 4.99.0 _ZTSN6KParts7FactoryE@Base 4.96.0 @@ -4204,7 +4204,7 @@ _ZTVN3KIO11MetaInfoJobE@Base 4.96.0 _ZTVN3KIO14PasswordDialogE@Base 4.96.0 _ZTVN3KIO9NetAccessE@Base 4.96.0 - _ZTVN5KMenu12KMenuPrivateE@Base 4.96.0 +#MISSING: 5.44.0-1# _ZTVN5KMenu12KMenuPrivateE@Base 4.96.0 _ZTVN5Solid10Networking8NotifierE@Base 4.99.0 _ZTVN5Solid15PowerManagement8NotifierE@Base 4.99.0 _ZTVN6KParts7FactoryE@Base 4.96.0 dh_makeshlibs: failing due to earlier errors make: *** [debian/rules:7: binary-arch] Error 2 -- Regards, Boyuan Yang -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'buildd-unstable'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.15.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#887835: qt5ct just *doesn't* work - The QT_QPA_PLATFORMTHEME environment variable is not set correctly
Control: reopen -1 No, I can confirm that this bug is not fixed at all. Here's how to reproduce it: 1. Completely remove qt5ct from system (if installed before) 2. Reboot, possibly enter a GNOME-based system (like GNOME Shell) 3. Ensure that "echo $QT_QPA_PLATFORMTHEME" will return null 4. apt install qt5ct 5. **immediately** type "qt5ct" in a previously-opened terminal emulator Okay, qt5ct will now crash since $QT_QPA_PLATFORMTHEME is not set. However, a reboot of system will fix the problem. I think this should be considered as a bug. Regards, Boyuan Yang
Bug#888088: qt5ct: Invalid Vcs-* URL
Package: qt5ct Version: 0.34-1 Severity: important Vcswatch utility reported error when scanning VCS repository: https://anonscm.debian.org/cgit/pkg-kde/qt-extras/qt5ct.git The url above would return 404. Please fix this problem in the next upload. -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'buildd-unstable'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages qt5ct depends on: ii libc62.26-4 ii libgcc1 1:7.2.0-19 ii libgl1 1.0.0-1.1 ii libqt5core5a [qtbase-abi-5-9-2] 5.9.2+dfsg-7 ii libqt5dbus5 5.9.2+dfsg-7 ii libqt5gui5 5.9.2+dfsg-7 ii libqt5widgets5 5.9.2+dfsg-7 ii libstdc++6 7.2.0-19 qt5ct recommends no packages. Versions of packages qt5ct suggests: ii qt5-style-plugins 5.0.0+git23.g335dbec-2+b2 -- no debconf information
Bug#874928: [kalternatives] Future Qt4 removal from Buster
X-Debbugs-CC: p...@kde.org debian-qt-kde@lists.debian.org 在 2017年11月28日星期二 CST 上午9:55:54，Boyuan Yang 写道： > X-Debbugs-CC: p...@kde.org debian-qt-kde@lists.debian.org > > Hello all, > > I'm wondering about the future of package "kalternatives" in Debian. It has > not been updated for 7 years, now affected by Qt4 removal and I cannot find > the upstream VCS for it. > > Will there be any porting efforts? If yes, please let me know; if not, we > could consider submitting removal request to get this out of Debian > unstable. > > PS: I'm the current maintainer of package "galternatives" in Debian. > > Thanks, > Boyuan Yang Hello, Since there's no response, I'm going to file an RM bug for package kalternatives within one month. Please let me know if anyone is willing to work on it and port it to Qt5. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part.
Bug#883375: qtbase-opensource-src: Please add private headers in /src/plugins/platforms/xcb/
Source: qtbase-opensource-src Version: 5.9.2+dfsg-4 Severity: wishlist X-Debbugs-CC: pkg-deepin-de...@lists.alioth.debian.org Dear Qt maintainers, I'm working inside pkg-deepin team [1] to push Deepin applications into Debian. Deepin use Qt and Golang heavily in their applications. There's a special dependency for Deepin applications: package "qt5dxcb-plugin" uses some really private Qt headers. Currently they bundle the header files inside src repository [2] but that is apparently not optimal approach for Debian packaging. Those header files come from /src/plugins/platforms/xcb/ directory in qtbase-opensource-src source tree. Deepin applications (alongside Deepin Desktop Environment, DDE) need it to work properly. In other distributions like Arch Linux and Fedora, package maintainers already included them, either in a separate package ([4], in package qt5-xcb-private-headers) or together in the qt5 private devel package ([5], in package qt5-qtbase-private-devel). My question is, is it possible for us to include (copy) those header files and distribute them inside package "qtbase5-private-dev" so that package "qt5dxcb-plugin" could build-dep on qtbase5-private-dev instead of bundling them inside repository (like what Fedora did)? Thanks, Boyuan Yang [1] https://alioth.debian.org/projects/pkg-deepin/ [2] https://github.com/linuxdeepin/qt5dxcb-plugin/tree/master/platformplugin/libqt5xcbqpa-dev/5.9.2/ [3] https://sources.debian.org/src/qtbase-opensource-src/5.9.2+dfsg-4/src/plugins/platforms/xcb/ [4] https://www.archlinux.org/packages/extra/x86_64/qt5-xcb-private-headers/ [5] https://fedora.pkgs.org/rawhide/fedora-x86_64/qt5-qtbase-devel-5.9.3-3.fc28.x86_64.rpm.html signature.asc Description: This is a digitally signed message part.
Re: Question about testing migration for Qt-related packages
在 2017年12月1日星期五 CST 上午9:05:37，Emilio Pozuelo Monfort 写道： > On 01/12/17 03:18, Boyuan Yang wrote: > > Hello all, > > > > I'm maintaining several Qt-based applications in Debian and quite curious > > about current testing migration status for Qt-related packages. When > > looking at migration excuses there seems to be no blocker now (as of > > 2017-12-01) however no migration happened recently. > > > > I tried to dig into britney raw output > > (https://release.debian.org/britney/update_output.txt) > > but that turns out to be too difficult for me to understand :-/ > > The britney output for the qt easy hint: > > start: 68+0: a-9:i-31:a-3:a-3:a-3:m-3:m-6:m-3:p-3:s-4 > orig: 68+0: a-9:i-31:a-3:a-3:a-3:m-3:m-6:m-3:p-3:s-4 > easy: 168+0: a-24:i-46:a-12:a-11:a-11:m-12:m-15:m-12:p-12:s-13 > * amd64: libpythonqt-dev, libuim-plugins, plasma-widget-uim, > uim-applet-gnome, uim-byeoru, uim-dict-gtk, uim-dict-gtk3, uim-ipa-x-sampa, > uim-latin, uim-look, uim-m17nlib, uim-pinyin, uim-qt, uim-utils, uim-viqr * > i386: libpythonqt-dev, libuim-plugins, plasma-widget-uim, uim-applet-gnome, > uim-byeoru, uim-dict-gtk, uim-dict-gtk3, uim-ipa-x-sampa, uim-latin, > uim-look, uim-m17nlib, uim-pinyin, uim-qt, uim-utils, uim-viqr * arm64: > libpythonqt-dev, libuim-plugins, plasma-widget-uim, uim-applet-gnome, > uim-dict-gtk, uim-dict-gtk3, uim-m17nlib, uim-qt, uim-utils * armel: > libuim-plugins, plasma-widget-uim, uim-applet-gnome, uim-dict-gtk, > uim-dict-gtk3, uim-m17nlib, uim-qt, uim-utils * armhf: libuim-plugins, > plasma-widget-uim, uim-applet-gnome, uim-dict-gtk, uim-dict-gtk3, > uim-m17nlib, uim-qt, uim-utils * mips: libpythonqt-dev, libuim-plugins, > plasma-widget-uim, uim-applet-gnome, uim-dict-gtk, uim-dict-gtk3, > uim-m17nlib, uim-qt, uim-utils * mips64el: libpythonqt-dev, libuim-plugins, > plasma-widget-uim, uim-applet-gnome, uim-dict-gtk, uim-dict-gtk3, > uim-m17nlib, uim-qt, uim-utils * mipsel: libpythonqt-dev, libuim-plugins, > plasma-widget-uim, uim-applet-gnome, uim-dict-gtk, uim-dict-gtk3, > uim-m17nlib, uim-qt, uim-utils * ppc64el: libpythonqt-dev, libuim-plugins, > plasma-widget-uim, uim-applet-gnome, uim-dict-gtk, uim-dict-gtk3, > uim-m17nlib, uim-qt, uim-utils * s390x: libpythonqt-dev, libuim-plugins, > plasma-widget-uim, uim-applet-gnome, uim-dict-gtk, uim-dict-gtk3, > uim-m17nlib, uim-qt, uim-utils FAILED > > Those are packages that become uninstallable in testing when britney > attempts to migrate all the Qt stuff and related packages. Most of those > are cruft packages, meaning they don't have updated versions in unstable > that britney could migrate. The solution here is to decruft them (see [1]). > I have asked the ftp team to decruft uim and pythonqt, but so far that > hasn't happened. Once it does, the transition should end. Thanks for the information. I didn't find any public record about this decruft report so filing a bug against pseudo-package ftp.debian.org might be a good option to track its progress. [2] [2] https://bugs.debian.org/ftp.debian.org Regards, Boyuan Yang > > Cheers, > Emilio > > [1] https://ftp-master.debian.org/cruft-report-daily.txt signature.asc Description: This is a digitally signed message part.
Question about testing migration for Qt-related packages
Hello all, I'm maintaining several Qt-based applications in Debian and quite curious about current testing migration status for Qt-related packages. When looking at migration excuses there seems to be no blocker now (as of 2017-12-01) however no migration happened recently. I tried to dig into britney raw output (https://release.debian.org/britney/update_output.txt) but that turns out to be too difficult for me to understand :-/ Hope this problem could be solved soon. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part.
Bug#874928: [kalternatives] Future Qt4 removal from Buster
X-Debbugs-CC: p...@kde.org debian-qt-kde@lists.debian.org Hello all, I'm wondering about the future of package "kalternatives" in Debian. It has not been updated for 7 years, now affected by Qt4 removal and I cannot find the upstream VCS for it. Will there be any porting efforts? If yes, please let me know; if not, we could consider submitting removal request to get this out of Debian unstable. PS: I'm the current maintainer of package "galternatives" in Debian. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part.
Bug#880159: qtchooser: Make plain "qmake" invocation fail
Package: qtchooser Version: 64-ga1b6736-3 Severity: grave Justification: renders package unusable Dear Maintainer, With latest "qtchooser" installed, plain call of "qmake" will fail on Debian unstable: % qmake qmake: could not exec '/usr/lib/x86_64-linux-gnu/qt5/bin/qmake' since it links to qmake itself. Check your installation. % file $(which qmake) /usr/bin/qmake: symbolic link to qtchooser Please fix this problem. Regards, Boyuan Yang -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8), LANGUAGE=zh_CN.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages qtchooser depends on: ii libc6 2.24-17 ii libgcc1 1:7.2.0-12 ii libstdc++6 7.2.0-12 qtchooser recommends no packages. qtchooser suggests no packages. -- no debconf information
Bug#877631: krita: Please update package description about calligra
Source: krita Version: 1:3.3.0+dfsg-1 Severity: minor Krita 3 is no longer part of Calligra suite. Please update package description accordingly. Thanks, Boyuan Yang -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.12.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Re: Bug#870042: RFS: gsettings-qt/0.1+16.04.20170729-1 [ITP]
2017-07-31 9:07 GMT+08:00 Boyuan Yang <073p...@gmail.com>: > 2017-07-31 9:04 GMT+08:00 Lisandro Damián Nicanor Pérez Meyer > <perezme...@gmail.com>: >> On sábado, 29 de julio de 2017 11:21:40 -03 Pino Toscano wrote: >>> Hi, >>> >>> I'm not uploading it myself, >> >> Neither me, but I wanted to add some more info to what Pino already provided. >> >>> but there are various things that ought to >>> be fixed: >>> >>> a) qtchooser is not needed in Build-Depends, it's an "implementation >>>detail" >> >> You might want to take a look at >> >> <http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html> >> >>> b) we don't use a "qtdeclarative5-" prefix for QML modules, but >>>"qml-module-" >> >> See <http://pkg-kde.alioth.debian.org/qmlmodulesnaming.html> >> >> >> >> -- >> Alas, I am dying beyond my means. >> Oscar Wilde, as he sipped champagne on his deathbed >> >> Lisandro Damián Nicanor Pérez Meyer >> http://perezmeyer.com.ar/ >> http://perezmeyer.blogspot.com/ > > Thank you all for the detailed review, which really helps. > > I'm not really familiar with C++/Qt/KDE packaging but this package > falls in this range as a dependency unfortunately. > I will read those instructions and fix problems. > > Regards, > Boyuan Yang OK. All problems mentioned above should be fixed now, both in git repo and source package on mentors.debian.net. (Many thanks to pino@ and perezmeyer.) Future development and upstream maintenance is likely be taken by Deepin Co.,Ltd. if Canonical quits since Deepin software depends on this package heavily. Pkg-deepin team is working together with deepin upstream on it. As a result I believe n) should not be a blocker for package uploading. Package maintainer was set back to pkg-deepin since we are taking care of it in reality. Thanks for the suggestion. After enabling the test, this package would fail one test in Debian Unstable. Investigations show that it is a bug of Qt 5.7. [1][2] This bug has been fixed since Qt 5.8. Qt in Ubuntu already have this bug fixed by backporting upstream patch. With no visible time schedule for new Qt in Debian, I choose to disable that test for now and re-enable it after Qt 5.9 enters unstable. Meanwhile, anyone interested please consider reviewing the package again and help sponsor this package if you feel comfortable. This package is blocking the workflow of pkg-deepin team and it would be great if we could get the problem fixed in a reasonable time period. * https://anonscm.debian.org/git/collab-maint/gsettings-qt.git * https://mentors.debian.net/package/gsettings-qt [1] https://bugs.launchpad.net/ubuntu/+source/gsettings-qt/+bug/1624251 [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871265 Regards, Boyuan Yang
Bug#871265: qtdeclarative-opensource-src: please backport patch to fix failing tests with gsettings-qt
Source: qtdeclarative-opensource-src Version: 5.7.1-2 Severity: important X-Debbugs-CC: pkg-deepin-de...@lists.alioth.debian.org Hello, I would like to request backporting a patch from Qt 5.8+ back to Qt 5.7.1 in Stretch (and probably currrent Testing) in order to fix FTBFS for (currently ITP) package gsettings-qt [1] (LP: #1624251 #1706682) Package "gsettings-qt" is a base dependency for various Deepin software, on which pkg-deepin team is working. This bug is blocking our work process now. Ubuntu already backported this patch in 5.7.1-1ubuntu1~7. The patch (and the unittest attached with it) can be found on Qt Code Review: https://codereview.qt-project.org/#/c/177422 For Debian Unstable/Testing, it would be great if you could add the patch from upstream so that we could continue with the ITP process for package "gsettings-qt". Since Qt 5.9 might be uploaded onto unstable at some certain time, you may instead close this bug when Qt 5.9 enters unstable. For Debian Stretch, I would suggest making a stretch-pu so that this bug would not block future backporting. Thanks, and please let me know your opinion on it. [1] https://bugs.launchpad.net/ubuntu/+source/gsettings-qt/+bug/1624251 Regards, Boyuan Yang
Re: Bug#870042: RFS: gsettings-qt/0.1+16.04.20170729-1 [ITP]
2017-07-31 9:04 GMT+08:00 Lisandro Damián Nicanor Pérez Meyer <perezme...@gmail.com>: > On sábado, 29 de julio de 2017 11:21:40 -03 Pino Toscano wrote: >> Hi, >> >> I'm not uploading it myself, > > Neither me, but I wanted to add some more info to what Pino already provided. > >> but there are various things that ought to >> be fixed: >> >> a) qtchooser is not needed in Build-Depends, it's an "implementation >>detail" > > You might want to take a look at > > <http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html> > >> b) we don't use a "qtdeclarative5-" prefix for QML modules, but >>"qml-module-" > > See <http://pkg-kde.alioth.debian.org/qmlmodulesnaming.html> > > > > -- > Alas, I am dying beyond my means. > Oscar Wilde, as he sipped champagne on his deathbed > > Lisandro Damián Nicanor Pérez Meyer > http://perezmeyer.com.ar/ > http://perezmeyer.blogspot.com/ Thank you all for the detailed review, which really helps. I'm not really familiar with C++/Qt/KDE packaging but this package falls in this range as a dependency unfortunately. I will read those instructions and fix problems. Regards, Boyuan Yang
Bug#870042: RFS: gsettings-qt/0.1+16.04.20170729-1 [ITP]
Package: sponsorship-requests Severity: wishlist X-Debbugs-CC: czc...@debian.org debian-qt-kde@lists.debian.org Dear mentors, I am looking for a sponsor for my package "gsettings-qt". * Package name: gsettings-qt Version : 0.1+16.04.20170729-1 Upstream Author : Canonical Ltd. * URL : https://launchpad.net/gsettings-qt * License : LGPL-3 Section : libs It builds those binary packages: libgsettings-qt-dev - Library to access GSettings from Qt - devel libgsettings-qt1 - Library to access GSettings from Qt qtdeclarative5-gsettings1.0 - QML Bindings for GSettings To access further information about this package, please visit the following URL: https://mentors.debian.net/package/gsettings-qt Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/g/gsettings-qt/ gsettings-qt_0.1+16.04.20170729-1.dsc Alternatively, one can view build status on deb-o-matic amd64: dget -x http://debomatic-amd64.debian.net/debomatic/unstable/pool/ gsettings-qt_0.1+16.04.20170729-1/gsettings-qt_0.1+16.04.20170729-1.dsc Git packaging repository can be found on Alioth: https://anonscm.debian.org/git/collab-maint/gsettings-qt.git Changes since last upload: gsettings-qt (0.1+16.04.20170729-1) unstable; urgency=medium . * Initial Release in Debian. (Closes: #870031) * Fix FTBFS problem due to incorrect link path. (LP: #1706682) Regards, Boyuan Yang signature.asc Description: This is a digitally signed message part.
Bug#870031: ITP: gsettings-qt -- QML bindings for GSettings
Package: wnpp Severity: wishlist Owner: Boyuan Yang <073p...@gmail.com> * Package name: gsettings-qt Version : 0.1+16.04+bzr20170110 Upstream Author : Canonical Ltd. * URL : https://launchpad.net/gsettings-qt * License : LGPL-3 Programming Lang: C++ Description : QML bindings for GSettings This package provides a QML binding for GSettings. This package is the build-dependency of various Deepin software to be packaged by pkg-deepin team. Gsettings-qt was a Ubuntu-only package. I intend to put it into Debian and fix any problem encountered. I intend to co-maintain this package inside debian-qt-kde team and put its packaging repository (converted to Git with the help of git-bzr) into collab- maint to ease external contribution and co-maintenance. Anyone interested is welcomed to co-maintain and review the status of this library package.
Bug#854884: #854884: baloo: is this obsoleted by src:baloo-kf5?
In my understanding, perhaps baloo4 is completely useless in Debian Stretch with Plasma 5. Why don't we remove it from unstable/testing *now*? Should anyone file a RM request for src:baloo immediately? -- Regards, Boyuan Yang signature.asc Description: This is a digitally signed message part.
Bug#858584: konsole: please backport font rendering fix for noto-sans
Hello? Ping? Are you still working on this issue to get the fix into Stretch? The fixed version is still stuck in unstable due to migration blocking. Please file an unblock request against release.debian.org on konsole/ 4:16.12.0-3 if you find that possible. Thanks! -- Sincerely, Boyuan Yang signature.asc Description: This is a digitally signed message part.
Bug#858584: #858584: konsole: please backport font rendering fix for noto-sans
I can confirm version 4:16.12.0-2 has this bug (#868584) fixed. Thanks. One more question: since konsole 16.12.3 is already available as a bugfix release, why not upgrade to 16.12.3 instead of backporting bunches of upstream patches? Such upgrade should be suitable for stable release. -- Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part.
Bug#858584: konsole: please backport font rendering fix for noto-sans
Package: konsole
Version: 4:16.12.0-1
Severity: normal
Tags: patch
Font rendering for Noto Sans CJK in konsole has long been broken. This made
users of konsole + Noto Sans CJK painful.
Upstream committed a fix in git HEAD recently:
https://git.reviewboard.kde.org/r/129281/diff/2/
It would be great if konsole in Stretch would include this fix.
A raw diff file will be sent as well as attachment.
-- System Information:
Debian Release: 9.0
APT prefers testing
APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages konsole depends on:
ii kio 5.28.0-1
ii konsole-kpart 4:16.12.0-1
ii libc6 2.24-9
ii libkf5completion5 5.28.0-1
ii libkf5configcore5 5.28.0-1+b2
ii libkf5configgui5 5.28.0-1+b2
ii libkf5configwidgets5 5.28.0-1
ii libkf5coreaddons5 5.28.0-1+b2
ii libkf5crash5 5.28.0-1
ii libkf5dbusaddons5 5.28.0-1
ii libkf5i18n5 5.28.0-1+b2
ii libkf5iconthemes5 5.28.0-1
ii libkf5kiowidgets5 5.28.0-1
ii libkf5notifyconfig5 5.28.0-1
ii libkf5widgetsaddons5 5.28.0-1
ii libkf5windowsystem5 5.28.0-1
ii libkf5xmlgui5 5.28.0-1
ii libqt5core5a 5.7.1+dfsg-3+b1
ii libqt5gui55.7.1+dfsg-3+b1
ii libqt5widgets55.7.1+dfsg-3+b1
ii libstdc++66.3.0-6
konsole recommends no packages.
konsole suggests no packages.
-- no debconf information
diff --git a/src/TerminalDisplay.cpp b/src/TerminalDisplay.cpp
index 39a8b84..dc991ef 100644
--- a/src/TerminalDisplay.cpp
+++ b/src/TerminalDisplay.cpp
@@ -856,18 +856,10 @@ void TerminalDisplay::drawCharacters(QPainter& painter,
// This still allows RTL characters to be rendered in the RTL way.
painter.setLayoutDirection(Qt::LeftToRight);
-// the drawText(rect,flags,string) overload is used here with null
flags
-// instead of drawText(rect,string) because the (rect,string) overload
causes
-// the application's default layout direction to be used instead of
-// the widget-specific layout direction, which should always be
-// Qt::LeftToRight for this widget
-//
-// This was discussed in:
http://lists.kde.org/?t=12055222362=1=2
if (_bidiEnabled) {
-painter.drawText(rect, 0, text);
+painter.drawText(rect.x(), rect.y() + QFontMetrics(font).ascent(),
text);
} else {
-// See bug 280896 for more info
-painter.drawText(rect, Qt::AlignBottom, LTR_OVERRIDE_CHAR + text);
+painter.drawText(rect.x(), rect.y() + QFontMetrics(font).ascent(),
LTR_OVERRIDE_CHAR + text);
}
}
}
Bug#849794: qtwebengine-opensource-src: FTBFS on buildd machines
Source: qtwebengine-opensource-src Severity: important Version: 5.7.1+dfsg-1 Hi, (temporarily not raising this bug to RC-level to allow initial testing migration) This package could not be built on (any) official buildd machine other than amd64 (which was a binary upload). This problem needs to be solved sooner or later. I tried to build it on my own x86_64 VPS (1GB mem + 4GB swap) and it is still experiencing FTBFS (OOM?). Build logs can be found on buildd [0]. The root of FTBFS seems different on different architectures: * i386: OOM * mips: "#error Please add support for your architecture in build/ build_config.h" * armhf, armel: "fatal error: gnu/stubs-hard.h: No such file or directory" * kfreebsd: "Unknown platform. Qt WebEngine only supports Linux, Windows, and OS X." * mipsel: "collect2: fatal error: ld terminated with signal 6 [Aborted] compilation terminated. terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc" I would suggest making a source-only upload (to experimental, maybe) after applying fixes to test if the fixes are working correctly. [0] https://buildd.debian.org/status/package.php?p=qtwebengine-opensource-src -- Sincerely, Boyuan Yang signature.asc Description: This is a digitally signed message part.
Bug#849301: qtwebengine-opensource-src: bad VCS links in debian/control
Source: qtwebengine-opensource-src Severity: wishlist Version: 5.7.1+dfsg-1 Hi, The VCS link is broken. Currently: https://anonscm.debian.org/cgit/pkg-kde/qt/qt5webengine.git Correct one: https://anonscm.debian.org/git/pkg-kde/qt/qtwebengine.git (Perhaps we should rename cgit -> git in case Debian move away from cgit in the future.) P.S. Making another upload may make the package miss the deadline 2016-01-05, so maybe we should either update it after the package enter testing, or ask the release team for an immediate testing transition? I'm not quite sure about it, but this problem should be put into consideration. -- Sincerely, Boyuan Yang signature.asc Description: This is a digitally signed message part.
Bug#849245: krita: segfault on startup
2016-12-24 15:55 GMT+08:00 Pino Toscano <p...@debian.org>: > Everything seems to happen in this libxfreeimage.so image plugin of qt5; > I don't see it provided by any package in the Debian archive, so please > paste the output of: > $ dpkg -S /usr/lib/x86_64-linux-gnu/qt5/plugins/imageformats/libxfreeimage.so > Is it https://github.com/linuxdeepin/deepin-image-viewer by chance? Exactly. Sorry for bothering you with some third-party software. > Another option is that the issue is in libfreeimage (src:freeimage), > which does not seem to do proper error checking in its usage of I/O > handlers... > > Anyway: does krita start fine if you remove the package installing that > file, or simpy manually move that plugin away? Yes. -- Sincerely, Boyuan Yang
Bug#849245: krita: segfault on startup
rnel/qtimerinfo_unix.cpp:91 #6 0x7efe2a0eb185 in QTimerInfoList::timerWait (this=0x7efe08002ed0, tm=...) at kernel/qtimerinfo_unix.cpp:388 #7 0x7efe2a0ec52e in timerSourcePrepareHelper (timeout=0x7efe0ea8ab04, src=) at kernel/qeventdispatcher_glib.cpp:132 #8 timerSourcePrepare (source=, timeout=timeout@entry=0x7efe0ea8ab04) at kernel/qeventdispatcher_glib.cpp:165 #9 0x7efe22a44edd in g_main_context_prepare (context=context@entry=0x7efe08000990, priority=priority@entry=0x7efe0ea8ab90) at ././glib/gmain.c:3501 #10 0x7efe22a4591b in g_main_context_iterate (context=context@entry=0x7efe08000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ././glib/gmain.c:3909 #11 0x7efe22a45b0c in g_main_context_iteration (context=0x7efe08000990, may_block=may_block@entry=1) at ././glib/gmain.c:3990 #12 0x7efe2a0ecf5b in QEventDispatcherGlib::processEvents (this=0x7efe080008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #13 0x7efe2a0968da in QEventLoop::exec (this=this@entry=0x7efe0ea8acd0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #14 0x7efe29ec40f3 in QThread::exec (this=this@entry=0x7efe2c1a6d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/ qthread.cpp:507 #15 0x7efe2c1316d5 in QDBusConnectionManager::run (this=0x7efe2c1a6d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #16 0x7efe29ec8da8 in QThreadPrivate::start (arg=0x7efe2c1a6d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/ qthread_unix.cpp:368 #17 0x7efe242c2464 in start_thread (arg=0x7efe0ea8b700) at pthread_create.c:333 #18 0x7efe295cb9df in clone () at ../sysdeps/unix/sysv/linux/x86_64/ clone.S:105 Thread 2 (Thread 0x7efe190ad700 (LWP 18388)): #0 0x7efe295c256d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7efe27ec2150 in poll (__timeout=-1, __nfds=1, __fds=0x7efe190acc00) at /usr/include/x86_64-linux-gnu/bits/poll2.h:46 #2 _xcb_conn_wait (c=c@entry=0x56260a2c5de0, cond=cond@entry=0x56260a2c5e20, vector=vector@entry=0x0, count=count@entry=0x0) at ../../src/xcb_conn.c:479 #3 0x7efe27ec3ee9 in xcb_wait_for_event (c=0x56260a2c5de0) at ../../src/ xcb_in.c:693 #4 0x7efe1b3fcb69 in QXcbEventReader::run (this=0x56260a2d0470) at qxcbconnection.cpp:1343 #5 0x7efe29ec8da8 in QThreadPrivate::start (arg=0x56260a2d0470) at thread/qthread_unix.cpp:368 #6 0x7efe242c2464 in start_thread (arg=0x7efe190ad700) at pthread_create.c:333 #7 0x7efe295cb9df in clone () at ../sysdeps/unix/sysv/linux/x86_64/ clone.S:105 Thread 1 (Thread 0x7efe1b6fd8c0 (LWP 18387)): [KCrash Handler] #6 __memmove_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove- vec-unaligned-erms.S:284 #7 0x7efe29fe9a22 in memcpy (__len=18, __src=, __dest=0x5626110d4b68) at /usr/include/x86_64-linux-gnu/bits/string3.h:53 #8 QResourceFileEngine::read (this=0x562610e477d0, data=0x5626110d4b68 "@K\r \021", len=18) at io/qresource.cpp:1287 #9 0x7efe29fbb83f in QFileDevice::readData (this=this@entry=0x5626110737f0, data=0x5626110d4b68 "@K\r\021", len=len@entry=16384) at io/qfiledevice.cpp:460 #10 0x7efe29fc452e in QIODevice::read (this=0x5626110737f0, data=0x7ffc43fc8f70 "", maxSize=18) at io/qiodevice.cpp:1076 #11 0x7efe066030d4 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/ imageformats/libxfreeimage.so #12 0x7efe063a3805 in isTARGA20 (io=io@entry=0x7efe06807020, handle=handle@entry=0x5626110737f0) at Source/FreeImage/PluginTARGA.cpp:371 #13 0x7efe063a39aa in Validate (io=0x7efe06807020, handle=0x5626110737f0) at Source/FreeImage/PluginTARGA.cpp:380 #14 0x7efe06383940 in FreeImage_Validate (fif=fif@entry=FIF_TARGA, io=io@entry=0x7efe06807020, handle=handle@entry=0x5626110737f0) at Source/ FreeImage/Plugin.cpp:831 #15 0x7efe06377ded in FreeImage_GetFileTypeFromHandle (io=0x7efe06807020, handle=0x5626110737f0, size=) at Source/FreeImage/GetType.cpp: 41 #16 0x7efe0660313c in FreeImageHandler::GetFIF(QIODevice*, QByteArray const&) () from /usr/lib/x86_64-linux-gnu/qt5/plugins/imageformats/ libxfreeimage.so #17 0x7efe0660496c in FreeimageQt5Plugin::capabilities(QIODevice*, QByteArray const&) const () from /usr/lib/x86_64-linux-gnu/qt5/plugins/ imageformats/libxfreeimage.so #18 0x7efe2a4432c2 in createReadHandlerHelper (device=0x5626110737f0, format=..., autoDetectImageFormat=, ignoresFormatAndExtension=) at image/qimagereader.cpp:405 #19 0x7efe2a443fbc in QImageReaderPrivate::initHandler (this=0x5626110123d0) at image/qimagereader.cpp:623 #20 0x00007efe2a44409e in QImageReader::format (this=this@entry=0x7ffc43fc9490) at image/qimagereader.cpp:726 #21 0x7efe2a465c17 in (anonymous namespace)::ImageReader::format (this=0x7ffc43fc9490) at image/qicon.cpp:388 #22 QPixmapIconEngine::addFile (this=0x5626110d0cb0, fileName=..., size=..., mode=QIcon::Normal, state=QIcon::Off) at image/qicon.cpp:416 #23 0x7efe2a46932b in QIcon::addFile (this=0x7ffc43fc9830, fileName=..., size=..., mode=QIcon::Normal, state=QIcon::Off) at image/qicon.cpp:1044 #24 0x7efe2a4695ea in QIcon::QIcon (this=, fileName=...) at image/qicon.cpp:667 #25 0x7efe2b11c5b5 in KisIconUtils::loadIcon(QString const&) () from /usr/ lib/x86_64-linux-gnu/libkritawidgetutils.so.16 #26 0x7efe2b127038 in KisActionRegistry::propertizeAction(QString const&, QAction*) () from /usr/lib/x86_64-linux-gnu/libkritawidgetutils.so.16 #27 0x7efe2b9d61cf in KisActionManager::createAction(QString const&) () from /usr/lib/x86_64-linux-gnu/libkritaui.so.16 #28 0x7efe2bbd42f7 in KisViewManager::createActions() () from /usr/lib/ x86_64-linux-gnu/libkritaui.so.16 #29 0x7efe2bbd4e02 in KisViewManager::KisViewManager(QWidget*, KActionCollection*) () from /usr/lib/x86_64-linux-gnu/libkritaui.so.16 #30 0x7efe2bba502a in KisMainWindow::KisMainWindow() () from /usr/lib/ x86_64-linux-gnu/libkritaui.so.16 #31 0x7efe2bbb0de6 in KisPart::createMainWindow() () from /usr/lib/x86_64- linux-gnu/libkritaui.so.16 #32 0x7efe2bb6c33c in KisApplication::start(KisApplicationArguments const&) () from /usr/lib/x86_64-linux-gnu/libkritaui.so.16 #33 0x5626096a908b in main () -- Sincerely, Boyuan Yang signature.asc Description: This is a digitally signed message part.
Bug#840246: RFP: krita -- Krita is a professional FREE and open source painting program.
X-Debbugs-CC: debian-de...@lists.debian.org X-Debbugs-CC: debian-qt-kde@lists.debian.org > Package: wnpp > Severity: wishlist > > * Package name: krita > Version : 3.0 > Upstream Author : Boudewijn Rempt <b...@valdyas.org> and others > * URL : https://krita.org > * License : GPL2+, LGPL2+ > Programming Lang: C++ > Description : Krita is a professional FREE and open source painting program. https://ftp-master.debian.org/new/krita_1:3.0.1+dfsg-1.html Due to BD-missing in ports architecture for calligra 2.9 [1], the old calligra 2.8 still has leftovers. What would happen if krita 3.x gets accepted into experimental while old calligra-owned krita still exists? :p Anyway I also hope that this problem can be solved soon and we get krita 3.x into stretch. [1] https://buildd.debian.org/status/package.php?p=calligra -- Regards, Boyuan Yang
Bug#840300: sddm: conffiles not marked in /usr/share thus cannot reliably customize
Package: sddm Version: 0.13.0-1 Severity: normal There are a lot of configuration files in /usr/share/sddm/* but edits will be overridden after the upgrade. Please consider writing them (at least some of them, such as /usr/share/sddm/scripts/* and /usr/share/sddm/themes/*/*.conf.*) into debian/conffiles, or patch upstream and let sddm accept multiple config files (both in /etc/sddm/ and /usr/share/sddm). That would greatly help those who want to customize sddm via config files. Thanks! -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages sddm depends on: ii adduser 3.115 ii debconf [debconf-2.0] 1.5.59 ii libc6 2.24-3 ii libgcc1 1:6.2.0-5 ii libpam0g1.1.8-3.3 ii libqt5core5a5.6.1+dfsg-3+b1 ii libqt5dbus5 5.6.1+dfsg-3+b1 ii libqt5gui5 5.6.1+dfsg-3+b1 ii libqt5network5 5.6.1+dfsg-3+b1 ii libqt5qml5 5.6.1-11 ii libqt5quick55.6.1-11 ii libstdc++6 6.2.0-5 ii libsystemd0 231-9 ii libxcb-xkb1 1.12-1 ii libxcb1 1.12-1 ii qml-module-qtquick2 5.6.1-11 ii sddm-theme-breeze [sddm-theme] 4:5.8.0-1 Versions of packages sddm recommends: ii libpam-systemd 231-9 Versions of packages sddm suggests: ii libpam-kwallet5 5.8.0-1 -- debconf information: * shared/default-x-display-manager: sddm sddm/daemon_name: /usr/bin/sddm
