Bug#994787: pymilter: Milter.config is not Python3 ready
Source: pymilter Version: 1.0.4-2+b4 Severity: normal Tags: patch Importing Milter.config fails with ModuleNotFoundError: File "/usr/lib/python3/dist-packages/Milter/config.py", line 1, in from ConfigParser import ConfigParser ModuleNotFoundError: No module named 'ConfigParser' This is fixed already upstream with c098f9df6beacf1b4623d359d2f5d409fff0bf8b: https://github.com/sdgathman/pymilter/commit/c098f9df6beacf1b4623d359d2f5d409fff0bf8b It affects the test suite of pysrs. See: https://github.com/sdgathman/pymilter/commit/c098f9df6beacf1b4623d359d2f5d409fff0bf8b Regards, hefee -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'oldstable-updates'), (500, 'oldoldstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (400, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU threads) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#993546: kmail: KMail sees different signing key on same mail when enabling debian-keyring
Hey, I'm quite sure, that this is not the issue of Kmail, as Kmail is using the GPGME to talk to gpg. So it will be an issue of libqgpgme7. But first make sue, that you are really have an valid bug. Please verify the signature in a konsole via gpg --verify. I expect, that it will fail with the same error. Keep in mind that Joot's using a subkey to sign ( 0x54F1A66317486713), this subkey needs to be available also to verify the signature. > When doing "gpg --list-keys 0x57930DAB0B86B067" (or long key ID) > (with "list-options show-keyring=yes" in my gpg.conf) I see the same key > present in my keyring (pubring.kbx) and in Debian's debian-keyring.gpg. As I was told you alsoways have to use --with-colons when using gpg --list-keys --with-colons to get ideas about the key status. > I have no clue how this can happen or be explained, > but it sounds like a bug to me. So far I know gnupg does want to get rid of multiple keyrings statched together. So maybe you find one of the bugs with statching. But you may get more up-to-date news from gnupg mantainers in Debian. hefee signature.asc Description: This is a digitally signed message part.
Bug#989846: CVE-2021-22895
Hey,
> > > What about Buster? Is 2.5 also affected?
> >
> > yes 2.5 is also affected. At least the source files look the same.
>
> Ack, can you also prepare an update for buster-security, please?
I have here a proposed debdiff. I added a third patch, so users have the
possiblility to accept invalid certs otherwise they would fail silently. At
least for me this sounds like not a proper solution.
* Do I need to upload also with sources? How can I check this myself?
Cheers,
hefee
diff -Nru nextcloud-desktop-2.5.1/debian/changelog nextcloud-desktop-2.5.1/debian/changelog
--- nextcloud-desktop-2.5.1/debian/changelog 2019-08-29 18:57:38.0 +0200
+++ nextcloud-desktop-2.5.1/debian/changelog 2021-09-11 11:53:28.0 +0200
@@ -1,3 +1,12 @@
+nextcloud-desktop (2.5.1-3+deb10u2) buster; urgency=high
+
+ * Add backported patch to fix CVE-2021-22895. (Closes: #989846)
+ * Add backported patch to fix CVE-2021-32728.
+ * Update patch for CVE-2021-32728 for v2.5.1.
+ * Add patch to make it possible to accept invalid SSL certificates.
+
+ -- Sandro Knauß Sat, 11 Sep 2021 11:53:28 +0200
+
nextcloud-desktop (2.5.1-3+deb10u1) buster; urgency=medium
* Make nextcloud-desktop-cmd depend on nextcloud-desktop-common.
diff -Nru nextcloud-desktop-2.5.1/debian/patches/0006-Validate-the-providers-ssl-certificate.patch nextcloud-desktop-2.5.1/debian/patches/0006-Validate-the-providers-ssl-certificate.patch
--- nextcloud-desktop-2.5.1/debian/patches/0006-Validate-the-providers-ssl-certificate.patch 1970-01-01 01:00:00.0 +0100
+++ nextcloud-desktop-2.5.1/debian/patches/0006-Validate-the-providers-ssl-certificate.patch 2021-09-10 22:17:16.0 +0200
@@ -0,0 +1,37 @@
+From 142180c0e297ef500daf8328e7ea3020e33a3639 Mon Sep 17 00:00:00 2001
+From: Felix Weilbach
+Date: Wed, 10 Feb 2021 09:53:57 +0100
+Subject: [PATCH] Validate the providers ssl certificate
+
+Signed-off-by: Felix Weilbach
+---
+ src/gui/wizard/webview.cpp | 12 ++--
+ 1 file changed, 2 insertions(+), 10 deletions(-)
+
+--- a/src/gui/wizard/webview.cpp
b/src/gui/wizard/webview.cpp
+@@ -45,9 +45,6 @@ public:
+
+ protected:
+ bool certificateError(const QWebEngineCertificateError ) override;
+-
+-private:
+-QUrl _rootUrl;
+ };
+
+ // We need a separate class here, since we cannot simply return the same WebEnginePage object
+@@ -157,14 +154,9 @@ QWebEnginePage * WebEnginePage::createWi
+
+ void WebEnginePage::setUrl(const QUrl ) {
+ QWebEnginePage::setUrl(url);
+-_rootUrl = url;
+ }
+
+ bool WebEnginePage::certificateError(const QWebEngineCertificateError ) {
+-if (certificateError.error() == QWebEngineCertificateError::CertificateAuthorityInvalid) {
+-return certificateError.url().host() == _rootUrl.host();
+-}
+-
+ return false;
+ }
+
diff -Nru nextcloud-desktop-2.5.1/debian/patches/0007-check-e2ee-public-key-against-private-one.patch nextcloud-desktop-2.5.1/debian/patches/0007-check-e2ee-public-key-against-private-one.patch
--- nextcloud-desktop-2.5.1/debian/patches/0007-check-e2ee-public-key-against-private-one.patch 1970-01-01 01:00:00.0 +0100
+++ nextcloud-desktop-2.5.1/debian/patches/0007-check-e2ee-public-key-against-private-one.patch 2021-09-11 11:28:54.0 +0200
@@ -0,0 +1,88 @@
+From 7fb09a81632de6066e55def20308d6e61cadbc48 Mon Sep 17 00:00:00 2001
+From: Matthieu Gallien
+Date: Wed, 19 May 2021 15:36:47 +0200
+Subject: [PATCH] check e2ee public key against private one
+
+should ensure we have matching private/public keys
+
+Signed-off-by: Matthieu Gallien
+---
+ src/libsync/clientsideencryption.cpp | 30 +++-
+ src/libsync/clientsideencryption.h | 1 +
+ 2 files changed, 30 insertions(+), 1 deletion(-)
+
+--- a/src/libsync/clientsideencryption.cpp
b/src/libsync/clientsideencryption.cpp
+@@ -15,6 +15,7 @@
+ #include "creds/abstractcredentials.h"
+
+ #include
++#include
+
+ #include
+
+@@ -30,6 +31,7 @@
+ #include
+ #include
+ #include
++#include
+
+ #include
+
+@@ -644,6 +646,37 @@ void ClientSideEncryption::fetchFromKeyC
+ job->start();
+ }
+
++ bool ClientSideEncryption::checkPublicKeyValidity() const
++ {
++ QByteArray data = EncryptionHelper::generateRandom(64);
++
++ BIO *publicKeyBio = BIO_new(BIO_s_mem());
++ QByteArray publicKeyPem = _account->e2e()->_publicKey.toPem();
++ BIO_write(publicKeyBio, publicKeyPem.constData(), publicKeyPem.size());
++ EVP_PKEY *publicKey = PEM_read_bio_PUBKEY(publicKeyBio, nullptr, nullptr, nullptr);
++ BIO_free_all(publicKeyBio);
++
++ auto encryptedData = EncryptionHelper::encryptStringAsymmetric(publicKey, data.toBase64());
++
++ BIO *privateKeyBio = BIO_new(BIO_s_mem());
++ QByteArray privateKeyPem = _account->e2e()->_privateKey;
++ BIO_write(privateKeyBio, privateKeyPem.constData(), privateKeyPem.size());
++ EVP_PKEY *key = PEM_read_bio_PrivateKey(privateKey
Bug#989846: CVE-2021-22895
Hey, > Looks good! Please build with -sa (since nextcloud-desktop is new in > bullseye-security and ftp.d.o and security.d.o don't share tarballs). done. > What about Buster? Is 2.5 also affected? yes 2.5 is also affected. At least the source files look the same. hefee signature.asc Description: This is a digitally signed message part.
Bug#989846: CVE-2021-22895
Hey,
finally, I managed to prepare a patched version of nextcloud-desktop.
I fixed both open isses for nextcloud-desktop for bullseye. See my attached
debdiff.
* CVE-2021-22895
* CVE-2021-32728
Did I managed all field correctly (codename and urgency)?
sid with be fixed with a new upload the next hours of 3.3.1-1.
regards,
hefee
diff -Nru nextcloud-desktop-3.1.1/debian/changelog nextcloud-desktop-3.1.1/debian/changelog
--- nextcloud-desktop-3.1.1/debian/changelog 2021-05-08 19:39:35.0 +0200
+++ nextcloud-desktop-3.1.1/debian/changelog 2021-08-22 19:59:32.0 +0200
@@ -1,3 +1,11 @@
+nextcloud-desktop (3.1.1-2+deb11u1) bullseye-security; urgency=high
+
+ * Add backported patch to fix CVE-2021-22895 (Closes: #989846).
+ * Add backported patch to fix CVE-2021-32728 with small modifications to
+match for Debian.
+
+ -- Sandro Knauß Sun, 22 Aug 2021 19:59:32 +0200
+
nextcloud-desktop (3.1.1-2) unstable; urgency=medium
* Add two upstream patches to fix CVE-2021-22879 (Closes: #987274):
diff -Nru nextcloud-desktop-3.1.1/debian/patches/0007-Validate-the-providers-ssl-certificate.patch nextcloud-desktop-3.1.1/debian/patches/0007-Validate-the-providers-ssl-certificate.patch
--- nextcloud-desktop-3.1.1/debian/patches/0007-Validate-the-providers-ssl-certificate.patch 1970-01-01 01:00:00.0 +0100
+++ nextcloud-desktop-3.1.1/debian/patches/0007-Validate-the-providers-ssl-certificate.patch 2021-08-22 19:59:32.0 +0200
@@ -0,0 +1,45 @@
+From 142180c0e297ef500daf8328e7ea3020e33a3639 Mon Sep 17 00:00:00 2001
+From: Felix Weilbach
+Date: Wed, 10 Feb 2021 09:53:57 +0100
+Subject: [PATCH] Validate the providers ssl certificate
+
+Signed-off-by: Felix Weilbach
+---
+ src/gui/wizard/webview.cpp | 12 ++--
+ 1 file changed, 2 insertions(+), 10 deletions(-)
+
+diff --git a/src/gui/wizard/webview.cpp b/src/gui/wizard/webview.cpp
+index e03f86509..6c2207f48 100644
+--- a/src/gui/wizard/webview.cpp
b/src/gui/wizard/webview.cpp
+@@ -52,9 +52,6 @@ public:
+
+ protected:
+ bool certificateError(const QWebEngineCertificateError ) override;
+-
+-private:
+-QUrl _rootUrl;
+ };
+
+ // We need a separate class here, since we cannot simply return the same WebEnginePage object
+@@ -191,15 +188,10 @@ QWebEnginePage * WebEnginePage::createWindow(QWebEnginePage::WebWindowType type)
+
+ void WebEnginePage::setUrl(const QUrl ) {
+ QWebEnginePage::setUrl(url);
+-_rootUrl = url;
+ }
+
+-bool WebEnginePage::certificateError(const QWebEngineCertificateError ) {
+-if (certificateError.error() == QWebEngineCertificateError::CertificateAuthorityInvalid &&
+-certificateError.url().host() == _rootUrl.host()) {
+-return true;
+-}
+-
++bool WebEnginePage::certificateError(const QWebEngineCertificateError )
++{
+ /**
+ * TODO properly improve this.
+ * The certificate should be displayed.
+--
+2.33.0
+
diff -Nru nextcloud-desktop-3.1.1/debian/patches/0008-check-e2ee-public-key-against-private-one.patch nextcloud-desktop-3.1.1/debian/patches/0008-check-e2ee-public-key-against-private-one.patch
--- nextcloud-desktop-3.1.1/debian/patches/0008-check-e2ee-public-key-against-private-one.patch 1970-01-01 01:00:00.0 +0100
+++ nextcloud-desktop-3.1.1/debian/patches/0008-check-e2ee-public-key-against-private-one.patch 2021-08-22 19:59:32.0 +0200
@@ -0,0 +1,83 @@
+From 7fb09a81632de6066e55def20308d6e61cadbc48 Mon Sep 17 00:00:00 2001
+From: Matthieu Gallien
+Date: Wed, 19 May 2021 15:36:47 +0200
+Subject: [PATCH] check e2ee public key against private one
+
+should ensure we have matching private/public keys
+
+Signed-off-by: Matthieu Gallien
+---
+ src/libsync/clientsideencryption.cpp | 30 +++-
+ src/libsync/clientsideencryption.h | 1 +
+ 2 files changed, 30 insertions(+), 1 deletion(-)
+
+--- a/src/libsync/clientsideencryption.cpp
b/src/libsync/clientsideencryption.cpp
+@@ -16,6 +16,7 @@
+
+ #include
+ #include
++#include
+
+ #include
+
+@@ -32,6 +33,7 @@
+ #include
+ #include
+ #include
++#include
+
+ #include
+ #include "common/utility.h"
+@@ -797,6 +799,32 @@ void ClientSideEncryption::fetchFromKeyC
+ job->start();
+ }
+
++ bool ClientSideEncryption::checkPublicKeyValidity() const
++ {
++ QByteArray data = EncryptionHelper::generateRandom(64);
++
++ Bio publicKeyBio;
++ QByteArray publicKeyPem = _account->e2e()->_publicKey.toPem();
++ BIO_write(publicKeyBio, publicKeyPem.constData(), publicKeyPem.size());
++ auto publicKey = PKey::readPublicKey(publicKeyBio);
++
++ auto encryptedData = EncryptionHelper::encryptStringAsymmetric(publicKey, data.toBase64());
++
++ Bio privateKeyBio;
++ QByteArray privateKeyPem = _account->e2e()->_privateKey;
++ BIO_write(privateKeyBio, privateKeyPem.constData(), privateKeyPem.size());
++ auto key = PKey::readPrivateKey(privateKeyBio);
++
++ QByteArray decryptResult = QByteA
Bug#990773: unblock: kf5-messagelib/4:20.08.3-5
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: debian-qt-...@lists.debian.org Please unblock package kf5-messagelib [ Reason ] The -5 just fixes the CVE-2021-31855 handled in #989438: If a user deletes an attachment of a encrypted mail, that this step will trigger an upload of the encrypted mail to the IMAP server. [ Impact ] The software has a known CVE. [ Tests ] Uploaded the -5 several days ago without any bad user response. The upstream bugfix also did not triggered any bad user expierience on other linux distros. [ Risks ] The fix is very simple just a single line. Myself has reviewd the upstream bugfix, so I'm quite confident, that I'm sure that this fixes the CVE properly [ Checklist ] [ x ] all changes are documented in the d/changelog [ x ] I reviewed all changes and I approve them [ x ] attach debdiff against the package in testing [ Other info ] Forgotten to mention the bugnumber in d/changelog. unblock kf5-messagelib/4:20.08.3-5 diff -Nru kf5-messagelib-20.08.3/debian/changelog kf5-messagelib-20.08.3/debian/changelog --- kf5-messagelib-20.08.3/debian/changelog 2021-04-06 16:22:38.0 +0200 +++ kf5-messagelib-20.08.3/debian/changelog 2021-06-23 12:48:07.0 +0200 @@ -1,3 +1,10 @@ +kf5-messagelib (4:20.08.3-5) unstable; urgency=high + + [ Norbert Preining ] + * Backport upstream fix for CVE-2021-31855. + + -- Sandro Knauß Wed, 23 Jun 2021 12:48:07 +0200 + kf5-messagelib (4:20.08.3-4) unstable; urgency=medium * Fix broken patch series file (Closes: #986452). diff -Nru kf5-messagelib-20.08.3/debian/patches/series kf5-messagelib-20.08.3/debian/patches/series --- kf5-messagelib-20.08.3/debian/patches/series2021-04-06 16:11:15.0 +0200 +++ kf5-messagelib-20.08.3/debian/patches/series2021-06-10 16:33:14.0 +0200 @@ -4,3 +4,4 @@ messagecomposer-Move-protected-headers-to-signed-par.patch mail-thread-ignored-and-mail-thread-watched-exist-in.patch KeyResolver-Enable-ContactPreferences-again.patch +upstream-3b5b171e-cv-2021-31855.patch diff -Nru kf5-messagelib-20.08.3/debian/patches/upstream-3b5b171e-cv-2021-31855.patch kf5-messagelib-20.08.3/debian/patches/upstream-3b5b171e-cv-2021-31855.patch --- kf5-messagelib-20.08.3/debian/patches/upstream-3b5b171e-cv-2021-31855.patch 1970-01-01 01:00:00.0 +0100 +++ kf5-messagelib-20.08.3/debian/patches/upstream-3b5b171e-cv-2021-31855.patch 2021-06-10 16:33:14.0 +0200 @@ -0,0 +1,24 @@ +From 3b5b171e91ce78b966c98b1292a1bcbc8d984799 Mon Sep 17 00:00:00 2001 +From: =?UTF-8?q?Ingo=20Kl=C3=B6cker?= +Date: Thu, 29 Apr 2021 22:13:38 +0200 +Subject: [PATCH] Fix CVE-2021-31855 + +Deleting an attachment of a decrypted encrypted message stored on a remote server +(e.g. an IMAP server) causes KMail to upload the decrypted content of the message +to the remote server. This is not easily noticeable by the user because KMail does +not display the decrypted content. +--- + messageviewer/src/viewer/viewer_p.cpp | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +--- a/messageviewer/src/viewer/viewer_p.cpp b/messageviewer/src/viewer/viewer_p.cpp +@@ -418,7 +418,7 @@ bool ViewerPrivate::deleteAttachment(KMi + #ifndef QT_NO_TREEVIEW + mMimePartTree->mimePartModel()->setRoot(modifiedMessage); + #endif +-mMessageItem.setPayloadFromData(modifiedMessage->encodedContent()); ++mMessageItem.setPayloadFromData(mMessage->encodedContent()); + Akonadi::ItemModifyJob *job = new Akonadi::ItemModifyJob(mMessageItem, mSession); + job->disableRevisionCheck(); + connect(job, ::result, this, ::itemModifiedResult);
Bug#988545: unblock: nextcloud-desktop/3.1.1-2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: pkg-owncloud-maintain...@lists.alioth.debian.org
Please unblock package nextcloud-desktop
[ Reason ]
#987274: Fix CVE-2021-22879
[ Tests ]
Installed it locally for several days, without issues.
Did not got any reponse that things are broken.
[ Risks ]
nextcloud-desktop is a leaf package, so no other package can break.
The diff is straight forward and small.
[ Checklist ]
[ x ] all changes are documented in the d/changelog
[ x ] I reviewed all changes and I approve them
[ x ] attach debdiff against the package in testing
unblock nextcloud-desktop/3.1.1-2
diff -Nru nextcloud-desktop-3.1.1/debian/changelog
nextcloud-desktop-3.1.1/debian/changelog
--- nextcloud-desktop-3.1.1/debian/changelog2021-01-19 14:56:40.0
+0100
+++ nextcloud-desktop-3.1.1/debian/changelog2021-05-08 19:39:35.0
+0200
@@ -1,3 +1,13 @@
+nextcloud-desktop (3.1.1-2) unstable; urgency=medium
+
+ * Add two upstream patches to fix CVE-2021-22879 (Closes: #987274):
+013f3cea70acfe7b701cb73c93744d5ff5c0c213
+e97b7d8a25d3ef0d8c52b6399f304a42a5d4f212
+into Validate-sensitive-URLs-to-onle-allow-http-s-schemes.patch
+with small modifications to apply to the version in Debian
+
+ -- Sandro Knauß Sat, 08 May 2021 19:39:35 +0200
+
nextcloud-desktop (3.1.1-1) unstable; urgency=medium
[ Christian Göttsche ]
diff -Nru
nextcloud-desktop-3.1.1/debian/patches/0006-Validate-sensitive-URLs-to-onle-allow-http-s-schemes.patch
nextcloud-desktop-3.1.1/debian/patches/0006-Validate-sensitive-URLs-to-onle-allow-http-s-schemes.patch
---
nextcloud-desktop-3.1.1/debian/patches/0006-Validate-sensitive-URLs-to-onle-allow-http-s-schemes.patch
1970-01-01 01:00:00.0 +0100
+++
nextcloud-desktop-3.1.1/debian/patches/0006-Validate-sensitive-URLs-to-onle-allow-http-s-schemes.patch
2021-05-08 19:39:35.0 +0200
@@ -0,0 +1,268 @@
+From 013f3cea70acfe7b701cb73c93744d5ff5c0c213 Fri Feb 5 10:06:25 2021
+From: allexzander
+Date: Fri, 5 Feb 2021 10:06:25 +0200
+Subject: [PATCH] Validate sensitive URLs to onle allow http(s) schemes.
+
+Signed-off-by: allexzander
+---
+ src/gui/accountsettings.cpp | 5 +++--
+ src/gui/creds/flow2auth.cpp | 3 ++-
+ src/gui/creds/oauth.cpp | 3 ++-
+ src/gui/guiutility.cpp | 11 +++
+ src/gui/owncloudgui.cpp | 3 ++-
+ src/gui/socketapi.cpp | 4 ++--
+ src/gui/tray/ActivityListModel.cpp | 5 +++--
+ src/gui/tray/UserModel.cpp | 10 ++
+ src/gui/wizard/owncloudwizardresultpage.cpp | 3 ++-
+ src/gui/wizard/webview.cpp | 3 ++-
+ 10 files changed, 35 insertions(+), 15 deletions(-)
+
+--- a/src/gui/accountsettings.cpp
b/src/gui/accountsettings.cpp
+@@ -36,6 +36,7 @@
+ #include "encryptfolderjob.h"
+ #include "syncresult.h"
+ #include "ignorelisttablewidget.h"
++#include "guiutility.h"
+
+ #include
+
+@@ -705,8 +706,9 @@ void AccountSettings::slotForceSyncCurre
+
+ void AccountSettings::slotOpenOC()
+ {
+-if (_OCUrl.isValid())
+-QDesktopServices::openUrl(_OCUrl);
++if (_OCUrl.isValid()) {
++Utility::openBrowser(_OCUrl);
++}
+ }
+
+ void AccountSettings::slotUpdateQuota(qint64 total, qint64 used)
+--- a/src/gui/creds/flow2auth.cpp
b/src/gui/creds/flow2auth.cpp
+@@ -25,6 +25,7 @@
+ #include "theme.h"
+ #include "networkjobs.h"
+ #include "configfile.h"
++#include "guiutility.h"
+
+ namespace OCC {
+
+@@ -146,7 +147,7 @@ void Flow2Auth::fetchNewToken(const Toke
+ {
+ case actionOpenBrowser:
+ // Try to open Browser
+-if (!QDesktopServices::openUrl(authorisationLink())) {
++if (!Utility::openBrowser(authorisationLink())) {
+ // We cannot open the browser, then we claim we don't support
Flow2Auth.
+ // Our UI callee will ask the user to copy and open the link.
+ emit result(NotSupported);
+--- a/src/gui/creds/oauth.cpp
b/src/gui/creds/oauth.cpp
+@@ -22,6 +22,7 @@
+ #include
+ #include "theme.h"
+ #include "networkjobs.h"
++#include "guiutility.h"
+
+ namespace OCC {
+
+@@ -165,7 +166,7 @@ QUrl OAuth::authorisationLink() const
+
+ bool OAuth::openBrowser()
+ {
+-if (!QDesktopServices::openUrl(authorisationLink())) {
++if (!Utility::openBrowser(authorisationLink())) {
+ // We cannot open the browser, then we claim we don't support OAuth.
+ emit result(NotSupported, QString());
+ return false;
+--- a/src/gui/guiutility.cpp
b/src/gui/guiutility.cpp
+@@ -27,6 +27,17 @@ Q_LOGGING_CATEGORY(lcUtility, "nextcloud
+
+ bool Utility::openBrowser(const QUrl , QWidget *errorWidget
Bug#988235: unblock: kf5-messagelib/4:20.08.3-4
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: pkg-kde-t...@alioth-lists.debian.net
Please unblock package kf5-messagelib
#986404 (KeyResolver-Enable-ContactPreferences-again.patch):
When using encryption you also want to be able to save and reuse
contact preferences, to hanble case where a GPG Key does not match
with the email address of a recipient. This patch was applied at
upstream in Feburary without any issue.
[ Impact ]
For users it is frustrating not to be able to save contact
preferences and also rises the barrier to use encryption.
[ Tests ]
The patch exist for more than 30 days in unstable without any bad
expierence also not bad response form upstream. Run kmail in daily
life.
[ Risks ]
The patch is easy and no other packes are affected by this.
The alternative is to do the selection of keys every time you write an
email, what is annoying.
#964963 (mail-thread-ignored-and-mail-thread-watched-exist-in.patch):
Fixing two not shown icons.
[ Impact ]
Two missing icons.
[ Tests ]
see above.
[ Risks ]
Patch is trival and no other packages are affected.
#986452:
Fixing just a packaging failure, that happend because I was not
focused. This fixes the debdiff to what I wanted to commit.
[ Checklist ]
[ x ] all changes are documented in the d/changelog
[ x ] I reviewed all changes and I approve them
[ x ] attach debdiff against the package in testing
[ Other info ]
(Anything else the release team should know.)
unblock kf5-messagelib/4:20.08.3-4
diff -Nru kf5-messagelib-20.08.3/debian/changelog
kf5-messagelib-20.08.3/debian/changelog
--- kf5-messagelib-20.08.3/debian/changelog 2021-02-01 20:34:19.0
+0100
+++ kf5-messagelib-20.08.3/debian/changelog 2021-04-06 16:22:38.0
+0200
@@ -1,3 +1,17 @@
+kf5-messagelib (4:20.08.3-4) unstable; urgency=medium
+
+ * Fix broken patch series file (Closes: #986452).
+
+ -- Sandro Knauß Tue, 06 Apr 2021 16:22:38 +0200
+
+kf5-messagelib (4:20.08.3-3) unstable; urgency=medium
+
+ * Add upstream patch to show correct icons (Closes: #964963).
+ * Add upstream patch to reenable contact preferences again
+(Closes: #986404).
+
+ -- Sandro Knauß Mon, 05 Apr 2021 13:06:12 +0200
+
kf5-messagelib (4:20.08.3-2) unstable; urgency=medium
* Add upstream patch to not break the signature of mails.
diff -Nru
kf5-messagelib-20.08.3/debian/patches/KeyResolver-Enable-ContactPreferences-again.patch
kf5-messagelib-20.08.3/debian/patches/KeyResolver-Enable-ContactPreferences-again.patch
---
kf5-messagelib-20.08.3/debian/patches/KeyResolver-Enable-ContactPreferences-again.patch
1970-01-01 01:00:00.0 +0100
+++
kf5-messagelib-20.08.3/debian/patches/KeyResolver-Enable-ContactPreferences-again.patch
2021-04-05 12:39:55.0 +0200
@@ -0,0 +1,38 @@
+From a347940b23b438da02aa5437baa8d2a70184b4ca Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Sandro=20Knau=C3=9F?=
+Date: Thu, 4 Feb 2021 23:23:30 +0100
+Subject: [PATCH 3/3] KeyResolver: Enable ContactPreferences again.
+
+It was disabled in 2018, but without any further notice. The code itself
+does not seems like it can lock.
+
+CCMAIL: mon...@kde.org
+
+This reverts commit 409e75042323d5fa104c864b155081ed8e94bcbe.
+
+(cherry picked from commit 9285ece174b41beb4ea00744cc702329e05520dd)
+---
+ messagecomposer/src/composer/keyresolver.cpp | 5 -
+ 1 file changed, 5 deletions(-)
+
+--- a/messagecomposer/src/composer/keyresolver.cpp
b/messagecomposer/src/composer/keyresolver.cpp
+@@ -1887,7 +1887,6 @@ void Kleo::KeyResolver::addKeys(const st
+
+ Kleo::KeyResolver::ContactPreferences
Kleo::KeyResolver::lookupContactPreferences(const QString ) const
+ {
+-#ifdef HAVE_A_FIX_FOR_LOCK
+ const Private::ContactPreferencesMap::iterator it
+ = d->mContactPreferencesMap.find(address);
+ if (it != d->mContactPreferencesMap.end()) {
+@@ -1923,10 +1922,6 @@ Kleo::KeyResolver::ContactPreferences Kl
+ // insert into map and grab resulting iterator
+ d->mContactPreferencesMap.insert(std::make_pair(address, pref));
+ return pref;
+-#else
+-Q_UNUSED(address)
+-return ContactPreferences();
+-#endif
+ }
+
+ void Kleo::KeyResolver::saveContactPreference(const QString , const
ContactPreferences ) const
diff -Nru
kf5-messagelib-20.08.3/debian/patches/mail-thread-ignored-and-mail-thread-watched-exist-in.patch
kf5-messagelib-20.08.3/debian/patches/mail-thread-ignored-and-mail-thread-watched-exist-in.patch
---
kf5-messagelib-20.08.3/debian/patches/mail-thread-ignored-and-mail-thread-watched-exist-in.patch
1970-01-01 01:00:00.0 +0100
+++
kf5-messagelib-20.08.3/debian/patches/mail-thread-ignored-and-mail-thread-watched-exist-in.patch
2021-04-05 12:29:53.0 +0200
@@ -0,0 +1,50 @@
+From f96638fe15b6073838f561d37183832e0548f179 Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Sandro=20Knau=C3=9F?=
+Date: W
Bug#988233: unblock: akonadi/4:20.08.3-3
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: pkg-kde-t...@alioth-lists.debian.net
Please unblock package akonadi
[ Reason ]
Akonadi ships AppArmor profiles and those should be extendable for
users. To do so there is a local folder for every AppArmor profile to
modify the existing AppArmor profiles. With -1 Akonadi ignores those
local modified AppArmor profiles.
[ Impact ]
Users cannot modifiy their AppArmor pofiles without much work when
upgrading.
[ Tests ]
The patch exist now for more than 20 days in unstable without any issue.
with -2 i got fast reply that I missed to mark mariadb_akonadi as
AppAromr profile, that also shows, that users are testing Akonadi and
AppArmor together. Also run it on my own machine successfully.
[ Risks ]
The code is very simple and there are no side effects.
[ Checklist ]
[ x ] all changes are documented in the d/changelog
[ x ] I reviewed all changes and I approve them
[ x ] attach debdiff against the package in testing
unblock akonadi/4:20.08.3-3
diff -Nru akonadi-20.08.3/debian/changelog akonadi-20.08.3/debian/changelog
--- akonadi-20.08.3/debian/changelog2020-12-16 01:38:46.0 +0100
+++ akonadi-20.08.3/debian/changelog2021-04-13 22:30:46.0 +0200
@@ -1,3 +1,15 @@
+akonadi (4:20.08.3-3) unstable; urgency=medium
+
+ * Handle mariadbd_akonadi with dh_apparmor (Closes: #986635).
+
+ -- Sandro Knauß Tue, 13 Apr 2021 22:30:46 +0200
+
+akonadi (4:20.08.3-2) unstable; urgency=medium
+
+ * Add patch to load local apparmor rules (Closes: #985080).
+
+ -- Sandro Knauß Mon, 05 Apr 2021 13:09:40 +0200
+
akonadi (4:20.08.3-1) unstable; urgency=medium
[ Sandro Knauß ]
diff -Nru akonadi-20.08.3/debian/patches/load_local_apparmor_rules.diff
akonadi-20.08.3/debian/patches/load_local_apparmor_rules.diff
--- akonadi-20.08.3/debian/patches/load_local_apparmor_rules.diff
1970-01-01 01:00:00.0 +0100
+++ akonadi-20.08.3/debian/patches/load_local_apparmor_rules.diff
2021-04-13 22:29:58.0 +0200
@@ -0,0 +1,51 @@
+Description: Load Apparmor site-specific additions and overrides.
+ Debian allows users to add site-specific additions and overrides via local
+ apparmor rule files. Those local rule files are created and handled by
+ dh_apparmor.
+Author: Hefee
+Origin: Debian
+Bug-Debian: https://bugs.debian.org/985080
+Last-Update: 2021-04-13
+Forwarded: Not-needed
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/apparmor/mariadbd_akonadi
b/apparmor/mariadbd_akonadi
+@@ -36,4 +36,7 @@ profile mariadbd_akonadi {
+ owner @{xdg_data_home}/akonadi/** rwk,
+ owner @{PROC}/@{pid}/loginuid r,
+ owner /{,var/}run/user/@{uid}/akonadi** rwk,
++
++ # Site-specific additions and overrides. See local/README for details.
++ #include
+ }
+--- a/apparmor/mysqld_akonadi
b/apparmor/mysqld_akonadi
+@@ -36,4 +36,7 @@ profile mysqld_akonadi {
+ owner @{xdg_data_home}/akonadi/** rwk,
+ owner @{PROC}/@{pid}/loginuid r,
+ owner /{,var/}run/user/@{uid}/akonadi** rwk,
++
++ # Site-specific additions and overrides. See local/README for details.
++ #include
+ }
+--- a/apparmor/postgresql_akonadi
b/apparmor/postgresql_akonadi
+@@ -38,4 +38,7 @@ profile postgresql_akonadi {
+ /{usr/,usr/lib/postgresql/*/,opt/pgsql*/}bin/psql mrix,
+ /{usr/,usr/lib/postgresql/*/,opt/pgsql*/}bin/pg_restore mrix,
+ /{usr/,}bin/cp mrix,
++
++ # Site-specific additions and overrides. See local/README for details.
++ #include
+ }
+--- a/apparmor/usr.bin.akonadiserver
b/apparmor/usr.bin.akonadiserver
+@@ -77,4 +77,7 @@
+ owner /{,var/}run/user/@{uid}/kdeinit** rwk,
+ owner /{,var/}run/user/@{uid}/kcrash** rwk,
+ owner /tmp/#[0-9]* m,
++
++ # Site-specific additions and overrides. See local/README for details.
++ #include
+ }
diff -Nru akonadi-20.08.3/debian/patches/series
akonadi-20.08.3/debian/patches/series
--- akonadi-20.08.3/debian/patches/series 2020-10-19 23:54:01.0
+0200
+++ akonadi-20.08.3/debian/patches/series 2021-04-05 13:07:39.0
+0200
@@ -1,3 +1,4 @@
enable_debianabimanager.diff
postgresql-data-checksums.patch
disable_secure_file_priv_check.diff
+load_local_apparmor_rules.diff
diff -Nru akonadi-20.08.3/debian/rules akonadi-20.08.3/debian/rules
--- akonadi-20.08.3/debian/rules2020-10-13 19:45:34.0 +0200
+++ akonadi-20.08.3/debian/rules2021-04-13 22:10:12.0 +0200
@@ -22,6 +22,7 @@
-DBUILD_DESIGNERPLUGIN=ON
execute_after_dh_install:
+ dh_apparmor -pakonadi-server --profile-name=mariadbd_akonadi
dh_apparmor -pakonadi-server --profile-name=mysqld_akonadi
dh_apparmor -pakonadi-server --profile-name=postgresql_akonadi
dh_apparmor -pakonadi-server --profile-name=usr.bin.akonadiserver
Bug#970450: akonadi-server: akonadi fails to start if the XDG variables point outside of $HOME
Hey,
Apparmor does not know any environmental variables, so it cannot handle your
case. In your usecase you have to update the @{xdg_data_home} and
@{xdg_config_home} inside usr.bin.akonadiserver to point to the correct
directories, than Apparmor should be fine with your setup. Or update /etc/
apparmor/tunables/home.
As this is not a default setup and I see no way how Apparmor rules could be
better written to support your usecase. It seems it is more like a general
user request for Apparmor.
Regards,
hefee
signature.asc
Description: This is a digitally signed message part.
Bug#986404: libkf5messagecomposer5abi1: Explicit saved encryption setting are not reused
Package: libkf5messagecomposer5abi1 Version: 4:20.08.3-2 Severity: normal When you select a explicit PGP Key for a emailaddress (Contact Preferences) those should be taken into account, when sending the next mail. Those setting are totally ignored at the moment. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'oldstable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (400, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-5-amd64 (SMP w/4 CPU threads) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libkf5messagecomposer5abi1 depends on: ii kf5-messagelib-data 4:20.08.3-2 ii kio 5.78.0-4 ii libc6 2.31-11 ii libgcc-s1 10.2.1-6 ii libgpgmepp6 1.14.0-1+b2 ii libkf5akonadicontact5 [libkf5akonadicontact5-20.08] 4:20.08.3-1 ii libkf5akonadicore5abi2 [libkf5akonadicore5-20.08] 4:20.08.3-1 ii libkf5akonadimime5 [libkf5akonadimime5-20.08] 4:20.08.3-1 ii libkf5akonadiwidgets5abi1 [libkf5akonadiwidgets5-20.08] 4:20.08.3-1 ii libkf5calendarcore5abi2 5:5.78.0-2 ii libkf5codecs5 5.78.0-2 ii libkf5completion5 5.78.0-3 ii libkf5configcore5 5.78.0-4 ii libkf5configgui5 5.78.0-4 ii libkf5contacts5 5:5.78.0-2 ii libkf5coreaddons5 5.78.0-4 ii libkf5i18n5 5.78.0-2 ii libkf5identitymanagement5 [libkf5identitymanagement5-20.08] 20.08.3-1 ii libkf5jobwidgets5 5.78.0-2 ii libkf5kiocore55.78.0-4 ii libkf5kiofilewidgets5 5.78.0-4 ii libkf5kiogui5 5.78.0-4 ii libkf5kiowidgets5 5.78.0-4 ii libkf5libkdepim5 [libkf5libkdepim5-20.08] 4:20.08.3-1 ii libkf5libkleo5 [libkf5libkleo5-20.08] 4:20.08.3-1 ii libkf5mailtransport5 [libkf5mailtransport5-20.08] 20.08.3-1 ii libkf5mailtransportakonadi5 [libkf5mailtransportakonadi5-20. 20.08.3-1 ii libkf5messagecore5abi1 [libkf5messagecore5-20.08] 4:20.08.3-2 ii libkf5messageviewer5abi1 [libkf5messageviewer5-20.08] 4:20.08.3-2 ii libkf5mime5abi1 [libkf5mime5-20.08] 20.08.3-1 ii libkf5mimetreeparser5abi1 [libkf5mimetreeparser5-20.08] 4:20.08.3-2 ii libkf5pimcommon5abi2 [libkf5pimcommon5-20.08] 4:20.08.3-1 ii libkf5pimcommonakonadi5abi1 [libkf5pimcommonakonadi5-20.08] 4:20.08.3-1 ii libkf5pimtextedit5abi2 [libkf5pimtextedit5-20.08] 20.08.3-1 ii libkf5sonnetui5 5.78.0-2 ii libkf5templateparser5 [libkf5templateparser5-20.08] 4:20.08.3-2 ii libkf5widgetsaddons5 5.78.0-2 ii libkf5xmlgui5 5.78.0-2 ii libqgpgme71.14.0-1+b2 ii libqt5core5a 5.15.2+dfsg-5 ii libqt5dbus5 5.15.2+dfsg-5 ii libqt5gui55.15.2+dfsg-5 ii libqt5network55.15.2+dfsg-5 ii libqt5widgets55.15.2+dfsg-5 ii libstdc++610.2.1-6 libkf5messagecomposer5abi1 recommends no packages. libkf5messagecomposer5abi1 suggests no packages. -- debconf-show failed
Bug#964963: Icons mail-thread-ignored.png and mail-thread-watched.png not correctly displayed
Control: tags -1 + fixed-upstream
Patch was merged within 20.12.
--
On Montag, 13. Juli 2020 15:44:08 CEST Sven Bartscher wrote:
> Package: libkf5messagelist5abi1
> Version: 4:20.04.1-1
> Severity: minor
>
> kmail apparently doesn't display icons for ignored or watched threads
> in message lists or the design editor for message lists. The icon
> seems to be missing, because libkf5messagelist loads the icons in
> messagelist/core/theme.cppL1267 as follows:
>
> << new
> QPixmap(QIcon::fromTheme(QStringLiteral("messagelist/pics/mail-thread-watch
> .png")).pixmap(mIconSize, mIconSize)) << new
> QPixmap(QIcon::fromTheme(QStringLiteral("messagelist/pics/mail-thread-ignor
> ed.png")).pixmap(mIconSize, mIconSize))
>
> However, I could find no theme in the Debian repository providing this
> path. Instead I found these close fits:
>
> $ apt-file search mail-thread-ignored
> breeze-icon-theme:
> /usr/share/icons/breeze-dark/actions/16/mail-thread-ignored.svg
> breeze-icon-theme:
> /usr/share/icons/breeze-dark/actions/22/mail-thread-ignored.svg
> breeze-icon-theme:
> /usr/share/icons/breeze-dark/actions/24/mail-thread-ignored.svg
> breeze-icon-theme:
> /usr/share/icons/breeze/actions/16/mail-thread-ignored.svg
> breeze-icon-theme:
> /usr/share/icons/breeze/actions/22/mail-thread-ignored.svg
> breeze-icon-theme:
> /usr/share/icons/breeze/actions/24/mail-thread-ignored.svg
> deepin-icon-theme:
> /usr/share/icons/bloom/actions/24/mail-thread-ignored.svg kmail:
> /usr/share/doc/HTML/en/kmail2/mail-thread-ignored.png
> numix-icon-theme: /usr/share/icons/Numix/16/actions/mail-thread-ignored.svg
> numix-icon-theme: /usr/share/icons/Numix/22/actions/mail-thread-ignored.svg
> papirus-icon-theme:
> /usr/share/icons/Papirus-Dark/16x16/actions/mail-thread-ignored.svg
> papirus-icon-theme:
> /usr/share/icons/Papirus-Dark/22x22/actions/mail-thread-ignored.svg
> papirus-icon-theme:
> /usr/share/icons/Papirus-Dark/24x24/actions/mail-thread-ignored.svg
> papirus-icon-theme:
> /usr/share/icons/Papirus/16x16/actions/mail-thread-ignored.svg
> papirus-icon-theme:
> /usr/share/icons/Papirus/22x22/actions/mail-thread-ignored.svg
> papirus-icon-theme:
> /usr/share/icons/Papirus/24x24/actions/mail-thread-ignored.svg
> papirus-icon-theme:
> /usr/share/icons/ePapirus/16x16/actions/mail-thread-ignored.svg
> papirus-icon-theme:
> /usr/share/icons/ePapirus/22x22/actions/mail-thread-ignored.svg
> papirus-icon-theme:
> /usr/share/icons/ePapirus/24x24/actions/mail-thread-ignored.svg
>
> My guess is, that the paths for these icons need to be adjusted to
> match one of these icons.
>
> -- System Information:
> Debian Release: bullseye/sid
> APT prefers testing-debug
> APT policy: (990, 'testing-debug'), (990, 'testing'), (102,
> 'unstable-debug'), (102, 'unstable'), (101, 'experimental-debug'), (101,
> 'experimental') Architecture: amd64 (x86_64)
>
> Kernel: Linux 5.7.0-1-amd64 (SMP w/12 CPU cores)
> Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE,
> TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8
> (charmap=UTF-8), LANGUAGE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked
> to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages libkf5messagelist5abi1 depends on:
> ii kf5-messagelib-data 4:20.04.1-1
> ii kio 5.70.1-1
> ii libc62.30-8 ii
> libgcc-s110.1.0-4 ii
> libkf5akonadicore5abi2 [libkf5akonadicore5-20.04]4:20.04.1-2+b1
> ii libkf5akonadimime5 [libkf5akonadimime5-20.04]
> 4:20.04.1-1 ii libkf5akonadisearchpim5 [libkf5akonadisearchpim5-20.04]
> 4:20.04.1-1 ii libkf5completion5
> 5.70.0-1 ii libkf5configcore5
> 5.70.0-1 ii libkf5configgui5
> 5.70.0-1 ii libkf5configwidgets5
> 5.70.0-1 ii libkf5coreaddons5
> 5.70.0-1 ii libkf5i18n5
> 5.70.0-1 ii libkf5iconthemes5
> 5.70.0-1 ii libkf5itemmodels5
> 5.70.0-1.1 ii libkf5kiocore5
> 5.70.1-1 ii libkf5messagecore5abi1 [libkf5messagecore5-20.04]
> 4:20.04.1-1 ii libkf5mime5abi1 [libkf5mime5-20.04]
> 20.04.1-1 ii libkf5pimcommon5abi2 [libkf5pimcommon5-20.04]
> 4:20.04.1-1 ii libkf5pimcommonakonadi5abi1 [libkf5pimcommonakonadi5-20.04]
> 4:20.04.1-1 ii libkf5textwidgets5
> 5.70.0-1 ii libkf5widgetsaddons5
> 5.70.0-1 ii
Bug#985080: Akonadi server crashes because of Apparmor rules
Hi, > the Akonadi server permanently crashes on login after upgrading to Bullseye. I cannot reproduce this on my setup an using Akonadi server the whole time. So I'm interested, why this happens for you and not for me. What resources are you using? I use only a private IMAP server with MariaDB as Akonadi backend and using X11 (not Wayland). > It would be good if the Apparmor rules of the Akonadi server were > functional. In the current state, the Akonadi server is unfortunately not > usable without user adjustments. This is not true for me and also other distros use these Apparmor rules and are happy ( at least I did not got any negative feedback/patches for around 6 months). So it seems like you triggered a test case other did not catch, so it would be helpful if you describe your setup, to get this patch upstream. regards, hefee signature.asc Description: This is a digitally signed message part.
Bug#982221: k3b: please stop using cdrkit
Hey, Upstream k3b is searching for new maintainers, k3b is currently only in low level bugfixing and such a big change like switching away from cdrkit is out of scrope [1]. And it is too much work for the current Debian maintainers. Any help is welcomed. The discussion started, as Debian won't ship cdrkit ( wodim and genisoimage) anymore in bookworm [#982221]. hefee [1] https://bugs.kde.org/show_bug.cgi?id=432684 [#982221] https://bugs.debian.org/982221 -- On Sonntag, 7. Februar 2021 16:27:19 CET Chris Hofstaedtler wrote: > Package: k3b > Version: 20.12.2-1 > Severity: important > > Dear k3b Maintainers, > > your package depends on wodim and genisoimage, both built from > cdrkit sources. cdrkit does not have a path forward, please switch > away from it rather soon. I'm told xorriso and libburnia are > alternatives and are alive and doing well. > > It's been suggested cdrkit should not be in bookworm. > > Chris signature.asc Description: This is a digitally signed message part.
Bug#942078: [high quality bug] baloo crash, can't recover; forced reindex does not fix; unusable via dolphin C-f
Hey, > The crash is not specific to jack_capture_90.mp3; except for a period of > time a couple of weeks long leading up to the original bug. But do you see any pattern? I cannot reproduce it, too. > Has anyone on the team tried testing baloo with a large $HOME? Yes I think myself. Baloo indexed 1.387.086 files (mixed content) ; 650GB source file =>10GB baloo database. According your description of the bug, that is bigger than your dataset and be enough to reproduce. Why do you think we do not use the software they maintain? Baloo is working great for me, I haven't seen issues for a long long time. Okay what can you do to tackle down the bug: * debug symbols for libKF5BalooEngine.so.5 and liblmdb.so.0, so that we know what line triggers the segfault. because the interesting part is without debug symbols. * can you reproducible trigger the crash with jack_capture_90.mp3, or any other file? * did you checked upstream bug tracker - to find any matching bug? As this is an upstream issue, it needs to be fixed by upstream anyways, so we need to clarify if the issue is still at a current version. Otherwise create a bugreport at bugs.kde.org, they should also know better what infos they need to fix the issue. * start a Debian unstable VM/ KDE neon VM and try to reproduce the issue > It could take up to a month to reproduce this bug, and by then the reply will be "ignore for bullseye". This is a contributing factor to why baloo is in perpetual beta (I'd argue alpha, but subjectivity ;-)) Yes I know the timeframe small between the freeze and release to tackle down complicated issues. But please don't forget the other side. What should maintainers do if, they cannot reproduce the issue and upstream does not have stable LTS branches and doing monthly releases? The first thing is checking the current version: If it is fixed, than one can search for the bugfix to backport it or file the bug upstream otherwise. But without checking against the current version upstream reply most of the time: please update first. So I cannot reproduce it nor Norbert. Mark the bug as "unreproducible" is a valid approach, as we cannot tell if it is fixed or not. With more information it may be possible to decide. That's why the question is so important: Can you reproduce it somehow, so we are able to see the same issue? hefee signature.asc Description: This is a digitally signed message part.
Bug#980543: nextcloud-desktop: nextcloud started to create huge log files in 1min intervals
Hey, yepp debug is now enabled by default [1]. Upstream says, it should not be too much. I reproduce your behaviour that it does log debug messages, but not that much on my side, so I do not worry But for sure this is not a packaging issue. So please report your bug upstream: https://github.com/nextcloud/desktop/issues Btw. you can disable logging via the configfile ~/.config/Nextcloud/nextcloud.cfg under the General section: logDebug=false hefee [1] https://github.com/nextcloud/desktop/commit/ b0a38816fc507c8f06f38c2bc2ecae8c153b8b87 signature.asc Description: This is a digitally signed message part.
Bug#980025: nextcloud-desktop: Nextcloud-desktop starts but window doesn't display properly and disappears in GNOME
Control: Severity -1 important Control: reassign -1 gnome-shell Control: affects -1 nextcloud-desktop This sounds not like the fault of nextcloud-desktop and I cannot reproduce it under a KDE environment. that's why lowering the severity and forward to gnome-shell. It also may makes sense to search in the upstream issue tracker if you find a patch or any explanation: https://github.com/nextcloud/desktop/issues. Please report back, if you found anything. For me it very hard to track every issue for different desktop environments, that I do not use myself, so I need help from your side. regards, hefee On Mittwoch, 13. Januar 2021 05:48:30 CET you wrote: > Package: nextcloud-desktop > Version: 3.0.1-3 > Severity: grave > Justification: renders package unusable > X-Debbugs-Cc: dlake...@street-artists.org > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate > *** > >* What led up to the situation? >* What exactly did you do (or not do) that was effective (or > ineffective)? >* What was the outcome of this action? >* What outcome did you expect instead? > > start nextcloud from terminal or click button in GNOME. A window seems to > appear, but it doesn't do anything, and freezes... > > See a screenshot that clearly shows the "torn away" pixels from behind where > the window used to be (after I move the window to overlap a white > background area on a search page). > > This is causing data loss because without nextcloud running on the desktop I > have "split brain" between nextcloud files and local files. > > When I run from the command line I get the following output: > > 2021-01-12 20:43:29:531 [ debug default ] [ unknown ]:static bool > LibSecretKeyring::findPassword(const QString&, const QString&, > QKeychain::JobPrivate*) 2021-01-12 20:43:30:766 [ debug > nextcloud.gui.systray ] [ OCC::Systray::computeWindowReferencePoint > ]:screenRect: QRect(0,0 3840x2160) 2021-01-12 20:43:30:766 [ debug > nextcloud.gui.systray ] [ OCC::Systray::computeWindowReferencePoint > ]:taskbarRect: QRect(0,0 3840x32) 2021-01-12 20:43:30:766 [ debug > nextcloud.gui.systray ] [ OCC::Systray::computeWindowReferencePoint > ]:taskbarScreenEdge: OCC::Systray::TaskBarPosition::Bottom 2021-01-12 > 20:43:30:766 [ debug nextcloud.gui.systray ] [ > OCC::Systray::computeWindowReferencePoint ]: trayIconCenter: > QPoint(1141,1238) 2021-01-12 20:43:30:766 [ debug nextcloud.gui.systray ] > [ > OCC::Systray::computeWindowPosition ]:taskbarScreenEdge: > OCC::Systray::TaskBarPosition::Bottom 2021-01-12 20:43:30:766 [ debug > nextcloud.gui.systray ] [ OCC::Systray::computeWindowPosition > ]:screenRect: QRect(0,0 3840x2160) 2021-01-12 20:43:30:766 [ debug > nextcloud.gui.systray ] [ OCC::Systray::computeWindowPosition ]: windowRect > (reference) QRect(941,1613 401x511) 2021-01-12 20:43:30:766 [ debug > nextcloud.gui.systray ] [ OCC::Systray::computeWindowPosition ]: windowRect > (adjusted ) QRect(941,1613 401x511) 2021-01-12 20:43:30:773 [ debug default > ] [ unknown ]:static bool LibSecretKeyring::findPassword(const QString&, > const QString&, QKeychain::JobPrivate*) 2021-01-12 20:43:30:776 [ debug > default ] [ unknown ]:static bool LibSecretKeyring::findPassword(const > QString&, const QString&, QKeychain::JobPrivate*) 2021-01-12 20:43:30:777 [ > debug default ] [ unknown ]:static bool > LibSecretKeyring::findPassword(const QString&, const QString&, > QKeychain::JobPrivate*) 2021-01-12 20:43:30:778 [ debug default ] [ unknown > ]:static bool LibSecretKeyring::findPassword(const QString&, const > QString&, QKeychain::JobPrivate*) 2021-01-12 20:43:30:866 [ debug default > ] [ unknown ]:static bool LibSecretKeyring::writePassword(const QString&, > const QString&, const QString&, QKeychain::JobPrivate::Mode, const > QByteArray&, QKeychain::JobPrivate*) 2021-01-12 20:43:31:284 [ debug > default ] [ unknown ]:static bool > LibSecretKeyring::writePassword(const > QString&, const QString&, const QString&, QKeychain::JobPrivate::Mode, > const QByteArray&, QKeychain::JobPrivate*) 2021-01-12 20:43:31:568 [ debug > default ] [ unknown ]:static bool > LibSecretKeyring::writePassword(const > QString&, const QString&, const QString&, QKeychain::JobPrivate::Mode, > const QByteArray&, QKeychain::JobPrivate*) 2021-01-12 20:43:31:874 [ debug > default ] [ unknown ]:static bool > LibSecretKeyring::writePassword(const > QString&, const QString&, const QString&, QKeychain::JobPrivate::Mode, > const QByteArray&, QKeychain::JobPrivate*) 2021-01-12 20:43:32:367 [ debug > default ] [ unknown ]:static bool > LibSecretKeyring::writePassword(const > QString&, const QString&, const QString&, QKeychain::JobPrivate::Mode, > const QByteArray&, QKeychain::JobPrivate*) 2021-01-12 20:43:32:669 [ debug > default ] [ unknown
Bug#980319: "Use Monochrome Icons" without function
Control: tags -1 +moreinfo +upstream Hi, > Ticking "Use Monochrome Icons" used to make the icon black & white, but some > time in the last weeks this functionality broke (Icon just stays coloured). > Since I haven't seen a nextcloud-desktop update in the last weeks, I'm > guessing that it broke in some of the underlying libs. This sounds not like the fault of owncloud-client and I cannot reproduce it und a KDE environment. So I think it more related to your Display manager / Desktop Environment. But nether the less, this is an issue, that should be reported upstream: https://github.com/nextcloud/desktop If you have created an issue. Please leave a notice here with an url to the bugreport write in the first line, than BTS is doing the linkage: Control: forwarded -1 URL regards, hefee signature.asc Description: This is a digitally signed message part.
Bug#979191: Missing dependency for nautilus-nextcloud
Control: tags -1 +moreinfo Hey, > I feel like the package 'nautilus-nextcloud' should have a dependency > on 'nextcloud-desktop-cmd'. > > If I install only the package 'nautilus-nextcloud' it also install > 'nextcloud-desktop' as a dependency, so I can setup an account an sync > files but I have none of the features that it should bring to nautilus > event though the extension seems to be loaded without errors: > > $ nautilus > Initializing Nextcloud-client-nautilus extension > ... > > If I manually install 'nextcloud-desktop-cmd' then everything seems to > work as expected. This is interessting and strange. 'nextcloud-desktop-cmd' only install usr/ bin/nextcloudcmd and that is not used by the nautilus extension. The extension is using a socket to reach Nextcloud get the status: $XDG_RUNTIME_DIR/Nextcloud/socket and this socket is provided by nextcloud-desktop: lsof | grep $XDG_RUNTIME_DIR/Nextcloud/socket That's why expect that 'nextcloud-desktop-cmd' depends on something, that is missing is your case. Please try to remove nextcloud-desktop-cmd than the extension should still working and apt should list some packages, that are not needed anymore, those are the candidates of the missing dependency. Can you give me the list of those packages? hefee signature.asc Description: This is a digitally signed message part.
Bug#890833: at-spi2-core: Intermittent 90s shutdown delay: at-spi-dbus-bus.service: State 'stop-sigterm' timed out
Control: found -1 2.38.0-2 Hey, I have a sid system with at-spi2-core 2.38.0-2 running KDE Plasma Desktop. I still can see the problem. One thing I see is that this is only a problem if I start chromium. If I do not use chromium, the log is quite uninteresting. hefee Start chromium: 13:03:58 xxx systemd[5372]: Starting Accessibility services bus... 13:03:58 xxx systemd[5372]: Started Accessibility services bus. 15:16:09 xxx at-spi-bus-launcher[36537]: dbus-daemon[36537]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=1000 pid=36459 comm="/usr/lib/chromium/chromium --sho> 15:16:09 xxx at-spi-bus-launcher[36537]: dbus-daemon[36537]: Successfully activated service 'org.a11y.atspi.Registry' 15:16:09 xxx at-spi-bus-launcher[36552]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry 22:13:48 xxx at-spi-bus-launcher[36552]: X connection to :0 broken (explicit kill or server shutdown). 22:13:51 xxx systemd[5372]: Stopping Accessibility services bus... 22:15:21 xxx systemd[5372]: at-spi-dbus-bus.service: State 'stop-sigterm' timed out. Killing. 22:15:21 xxx systemd[5372]: at-spi-dbus-bus.service: Killing process 5689 (at-spi-bus-laun) with signal SIGKILL. 22:15:21 xxx systemd[5372]: at-spi-dbus-bus.service: Killing process 5696 (gdbus) with signal SIGKILL. 22:15:21 xxx systemd[5372]: at-spi-dbus-bus.service: Main process exited, code=killed, status=9/KILL 22:15:21 xxx systemd[5372]: at-spi-dbus-bus.service: Failed with result 'timeout'. 22:15:21 xxx systemd[5372]: Stopped Accessibility services bus. 22:15:21 xxx systemd[5372]: at-spi-dbus-bus.service: Consumed 4.294s CPU time. Without chromium: 22:25:26 xxx systemd[5284]: Starting Accessibility services bus... 22:25:27 xxx systemd[5284]: Started Accessibility services bus. 22:27:36 xxx systemd[5284]: Stopping Accessibility services bus... 22:27:36 xxx systemd[5284]: at-spi-dbus-bus.service: Succeeded. 22:27:36 xxx systemd[5284]: Stopped Accessibility services bus. signature.asc Description: This is a digitally signed message part.
Bug#951588: kontact: akonadi is not operational
control: tags -1 + moreinfo control: severity -1 important Hey, please retry with the current version in testing/unstable and give us more information what you have tried to do before kontact returns with a segfault. Maybe this issue is more for the Akonadi package? At least from what I can tell is that is works for a lot of people, so I lower the severity. hefee On Dienstag, 18. Februar 2020 14:34:53 CET Alberto Fuentes wrote: > Package: kontact > Version: 4:19.08.3-1 > Severity: grave > Justification: renders package unusable > > Application: Akonadi Control (akonadi_control), signal: Aborted > Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". > [Current thread is 1 (Thread 0x7ff192558800 (LWP 1433258))] > > Thread 5 (Thread 0x7ff189e1f700 (LWP 1433262)): > #0 0x7ff195d5abef in __GI___poll (fds=0x7ff1800021e0, nfds=1, > timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 > #1 0x7ff19510710e in ?? () from > /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ff19510722f in > g_main_context_iteration () from > /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 > #3 0x7ff1962e381b in > QEventDispatcherGlib::processEvents(QFlags) > () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 > #4 0x7ff19628c71b in > QEventLoop::exec(QFlags) () from > /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 > #5 0x7ff1960cd731 in QThread::exec() () from /usr/lib/x86_64-linux- > gnu/libQt5Core.so.5 > #6 0x7ff196bf14e6 in ?? () from > /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7ff1960ce8b2 in ?? () > from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7ff195c52fb7 in > start_thread (arg=) at > pthread_create.c:486 > #9 0x7ff195d651af in clone () at > ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 > > Thread 4 (Thread 0x7ff18a703700 (LWP 1433261)): > #0 0x7ff195d5abef in __GI___poll (fds=0x55fdcd713ff0, nfds=2, > timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 > #1 0x7ff19510710e in ?? () from > /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ff195107473 in > g_main_loop_run () from /usr/lib/x86_64-linux- gnu/libglib-2.0.so.0 > #3 0x7ff18b9c89e6 in ?? () from > /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x7ff19512fd7d in ?? () > from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7ff195c52fb7 in > start_thread (arg=) at > pthread_create.c:486 > #6 0x7ff195d651af in clone () at > ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 > > Thread 3 (Thread 0x7ff18af04700 (LWP 1433260)): > #0 0x7ff195d5abef in __GI___poll (fds=0x55fdcd6ffb90, nfds=1, > timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 > #1 0x7ff19510710e in ?? () from > /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ff19510722f in > g_main_context_iteration () from > /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 > #3 0x7ff195107281 in ?? () from > /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7ff19512fd7d in ?? () > from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7ff195c52fb7 in > start_thread (arg=) at > pthread_create.c:486 > #6 0x7ff195d651af in clone () at > ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 > > Thread 2 (Thread 0x7ff1912c6700 (LWP 1433259)): > #0 0x7ff195d5abef in __GI___poll (fds=0x7ff1912c5ca8, nfds=1, > timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 > #1 0x7ff194ff1cf7 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 > #2 0x7ff194ff391a in xcb_wait_for_event () from /usr/lib/x86_64-linux- > gnu/libxcb.so.1 > #3 0x7ff191eabca0 in ?? () from /usr/lib/x86_64-linux- > gnu/libQt5XcbQpa.so.5 > #4 0x7ff1960ce8b2 in ?? () from > /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7ff195c52fb7 in > start_thread (arg=) at > pthread_create.c:486 > #6 0x7ff195d651af in clone () at > ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 > > Thread 1 (Thread 0x7ff192558800 (LWP 1433258)): > [KCrash Handler] > #6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 > #7 0x7ff195c90535 in __GI_abort () at abort.c:79 > #8 0x55fdcbc662e2 in akMessageHandler (type=QtFatalMsg, msg=..., > context=...) at ./src/shared/akdebug.cpp:205 > #9 akMessageHandler (type=, context=..., msg=...) at > ./src/shared/akdebug.cpp:194 > #10 0x55fdcbc6834e in (anonymous namespace)::RemoteLogger::dbusLogger > (type=QtFatalMsg, ctx=..., msg=...) at ./src/shared/akremotelog.cpp:178 > #11 0x7ff1960c64b1 in ?? () from > /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7ff1960c65c9 in ?? () > from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7ff196096a44 in > QMessageLogger::fatal(char const*, ...) const () from > /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 > #14 0x55fdcbc3c4e1 in AgentManager::AgentManager (this=0x7ffd636395f0, > verbose=, parent=) at > /usr/include/x86_64-linux- gnu/qt5/QtCore/qlogging.h:91 > #15 0x55fdcbc3e374 in main (argc=, argv=) > at ./src/akonadicontrol/main.cpp:76 > [Inferior 1 (process 1433258) detached] > > > > -- System Information: >
Bug#978551: bls: Update false positive for shlibs-symbol-not-found
Package: qa.debian.org Severity: normal Control: Usertag -1 bls Hey, I see from kglobalaccel[1] that symbols are marked as not found, that are platform specific and are a false positive: dpkg-shlibdeps: warning: symbol __aeabi_atexit@CXXABI_ARM_1.3.3 used by It would be nice when bls could handle this case. Regards, hefee [1] https://buildd.debian.org/status/fetch.php?pkg=kglobalaccel=armel=5.77.0-2=1608613627=0 -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'oldstable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (400, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.0-5-amd64 (SMP w/4 CPU threads) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#974860: Forwarded to upstream
Hey Silvério, thanks for forwanrding the bugs to upstream. I see you tried to update the Debian Bug Tracker(BTS) two times. Pino already properly updated your bugs. Okay I was not exactly clear about the correct syntax. There are two way to interact with BTS. You can use sending mails to cont...@debian.org, than you have to send: Forwarded 974860 https://bugs.kde.org/show_bug.cgi?id=430719 Or you send the mail to the bug itself ( 974...@bugs.debian.org) than you have to prefix the command with Control: Control: Forwarded 974860 https://bugs.kde.org/show_bug.cgi?id=430719 Additionally you are able to replace the current bugnumber with -1 so you can shorten this to: Control: Forwarded -1 https://bugs.kde.org/show_bug.cgi?id=430719 and please use only text-only mails. In the beginning it is hard to remember the differences and make a lot a failures. Sorry for not being that precise. You can find the documentation at https://bugs.debian.org. There is also a CLI from devscripts package the command is called bts. hefee signature.asc Description: This is a digitally signed message part.
Bug#973656: [Pkg-kde-extras] Bug#973656: digikam-private-libs wants libkf5akonadicontact5-20.08, but only libkf5akonadicontact5 is available
Hey, > digikam-private-libs can not be installed because of unmet dependencies. There is no problem anymore installing digikam-private-libs 4:7.1.0-1. libkf5akonadicontact5 provides , as libkf5akonadicontact5-20.08 is a virtual package, that is provided by libkf5akonadicontact5 4:20.08.3-1 provides the virtual package libkf5akonadicontact5-20.08. You can see this looking at: apt show libkf5akonadicontact5 At least on my sid system, I have digikam installed, so everything is fine. But if you still have issues installing digikam, than please provide the output of the error. hefee signature.asc Description: This is a digitally signed message part.
Bug#977693: gtk+3.0: Wayland primary selection interoperability with GTK clients on Plasma Desktop
Hey, > > Upstream GTK developer Emmanuele Bassi said that there are no more gtk3 > > dot releases planned (at least not before GTK 4.0 is released). > > That seems to be outdated information: GTK 4.0.0 has been released now > (I uploaded it to experimental NEW since it has a new SONAME and needs > a newer version of Pango), and a 3.24.24 point release also happened. great. > > Emmanuale recommends cherry-picking this patch from the gtk-3-24 stable > > branch to distro packages: > > > > https://gitlab.gnome.org/GNOME/gtk/-/commit/9a693c7228a88b76a007aed41b101d > > 89d084cf9b > That's included in 3.24.24, in testing since 2020-12-14. Thanks for this info. > > > To verify that the patch works: > > 1. Log into a Plasma Wayland session > > I'll try to test this at some point, but it's very likely to be quicker > for a Plasma user to upgrade their GTK 3 version than it is for me to > install Plasma. I tested it on my machine (Debian unstable with libgtk-3-common 3.24.24-1) and still I cannot copy text from Firefox to other clients. I'll forward your text to the distributions mailinglist, as I'm not an upstream developer of Plasma. And the primary mail with the request for backport came from the plasma team. regards, hefee signature.asc Description: This is a digitally signed message part.
Bug#977693: gtk+3.0: Wayland primary selection interoperability with GTK clients on Plasma Desktop
Source: gtk+3.0 Version: 3.24.24-1 Severity: normal Tags: patch, upstream Forwarded: https://gitlab.gnome.org/GNOME/gtk/-/issues/2591 X-Debbugs-Cc: debian-qt-...@lists.debian.org Hey, currently it is impossible to use middle click pasting between Wayland clients and GTK clients running on XWayland, like for example Chromium and Firefox on Plasma Desktop. KDE implemented the standard protocol (zwp_primary_selection) a while ago: https://bugs.kde.org/show_bug.cgi?id=422426 Whereas GTK support landed only last month, missing the 3.24.23 dot release: https://gitlab.gnome.org/GNOME/gtk/-/issues/2591 Upstream GTK developer Emmanuele Bassi said that there are no more gtk3 dot releases planned (at least not before GTK 4.0 is released). Emmanuale recommends cherry-picking this patch from the gtk-3-24 stable branch to distro packages: https://gitlab.gnome.org/GNOME/gtk/-/commit/9a693c7228a88b76a007aed41b101d89d084cf9b Can you do this backport? To verify that the patch works: 1. Log into a Plasma Wayland session 2. Open a gtk3 client using X11, such as Chromium or Firefox 3. Select some text 4. Open any Wayland client, for example Konsole 5. Try pasting the text with the middle mouse button Regards hefee Link to original email of the KDE distributions list: https://mail.kde.org/pipermail/distributions/2020-November/000890.html -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'oldstable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (400, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.0-4-amd64 (SMP w/4 CPU threads) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#974860: kmail: When moving an email into a subfolder on KDE Plasma Wayland the context menu does not appear at the target subfolder
Hey,
The bug is not a Debian specific one, so it should be reported and fixed
upstream at KDE:
https://bugs.kde.org
Please also leave a comment here at this bugreport with the url of the
upstream bug, so we are able to track the upstream bug status. To do this
properly add a line to the mail with:
Control: Forwarded -1 {url}
at the beginning of your response, than BTS (Debian Bugtracker) will do its
magic.
hefee
--
On Sonntag, 15. November 2020 17:36:31 CET Silvério Santos wrote:
> Package: kmail
> Version: 4:20.08.2-4
> Severity: minor
>
> Dear Maintainer,
>
> On KDE Plasma Wayland: Drag and drop an email into a subfolder. A context
> menu appears to choose whether to move here, copy here or cancel. This
> context menu appears where the email was located before/where it was
> clicked to drag it into the target folder. This of course is misleading
> because of the expression "... here" twice in the options, as they do not
> match the place they are referring to.
> The menu should appear at the target folder instead, where the mouse button
> is released.
>
>
>
> -- System Information:
> Debian Release: bullseye/sid
> APT prefers testing
> APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 5.9.0-1-amd64 (SMP w/4 CPU threads)
> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages kmail depends on:
> ii akonadi-server
> 4:20.08.2-3+b1 ii kdepim-runtime
> 4:20.08.2-4 ii kio
> 5.74.0-2 ii libc6
>2.31-4 ii libgcc-s1
> 10.2.0-16 ii libgpgmepp6
> 1.14.0-1+b1 ii libkf5akonadiagentbase5 [libkf5akonadiagentbase5-20.08]
> 4:20.08.2-3+b1 ii libkf5akonadicontact5 [libkf5akonadicontact5-20.08]
> 4:20.08.2-3 ii libkf5akonadicore5abi2 [libkf5akonadicore5-20.08]
> 4:20.08.2-3+b1 ii libkf5akonadimime5 [libkf5akonadimime5-20.08]
> 4:20.08.2-2 ii libkf5akonadisearch-bin
>4:20.08.2-2 ii libkf5akonadisearch-plugins
> 4:20.08.2-2 ii libkf5akonadisearchdebug5
> [libkf5akonadisearchdebug5-20.08] 4:20.08.2-2 ii libkf5akonadisearchpim5
> [libkf5akonadisearchpim5-20.08] 4:20.08.2-2 ii
> libkf5akonadiwidgets5abi1 [libkf5akonadiwidgets5-20.08] 4:20.08.2-3+b1
> ii libkf5bookmarks5 5.74.0-2
> ii libkf5calendarcore5abi2 5:5.74.0-2
> ii libkf5calendarutils5 [libkf5calendarutils5-20.08]
> 4:20.08.2-2 ii libkf5codecs5
> 5.74.0-2 ii libkf5completion5
> 5.74.0-2 ii libkf5configcore5
> 5.74.0-2 ii libkf5configgui5
> 5.74.0-2 ii libkf5configwidgets5
> 5.74.0-2 ii libkf5contacts5
> 5:5.74.0-2 ii libkf5coreaddons5
> 5.74.0-2 ii libkf5crash5
> 5.74.0-2 ii libkf5dbusaddons5
> 5.74.0-2 ii libkf5grantleetheme-plugins
> 20.08.2-2 ii libkf5gravatar5abi2 [libkf5gravatar5-20.08]
> 4:20.08.2-2 ii libkf5guiaddons5
> 5.74.0-3 ii libkf5i18n5
> 5.74.0-3 ii libkf5iconthemes5
> 5.74.0-2 ii libkf5identitymanagement5 [libkf5identitymanagement5-20.08]
> 20.08.2-2 ii libkf5itemmodels5
> 5.74.0-2 ii libkf5itemviews5
> 5.74.0-2 ii libkf5jobwidgets5
> 5.74.0-2 ii libkf5kcmutils5
> 5.74.0-2 ii libkf5kiocore5
> 5.74.0-2 ii libkf5kiofilewidgets5
> 5.74.0-2 ii libkf5kiogui5
> 5.74.0-2 ii libkf5kiowidgets5
> 5.74.0-2 ii libkf5kontactinterface5 [libkf5kontactinterface5-20.08]
> 20.08.2-2 ii libkf5ksieveui5 [libkf5ksieveui5-20.08]
> 4:20.08.2-2 ii libkf5ldap5abi1 [libkf5ldap5-20.08]
> 20.08.2-2 ii libkf5libkdepim5
Bug#974827: kmail: Navigate through emails in email message windows: next, previous, next unread, previous unread
Hey,
The bug is not a Debian specific one, so it should be reported and fixed
upstream at KDE:
https://bugs.kde.org
Please also leave a comment here at this bugreport with the url of the
upstream bug, so we are able to track the upstream bug status. To do this
properly add a line to the mail with:
Control: Forwarded -1 {url}
at the beginning of your response, than BTS (Debian Bugtracker) will do its
magic.
hefee
--
> when opening emails in windows on their own the next email has to opened by
> closing the current window, selecting the next one in the folder and opening
> it in another window. It would be desirable to be able to navigate through
> email from within the email window.
> Fun fact, this was an unanswered question on stackexchange 4 years and 9
> mtónths ago: https://unix.stackexchange.com/questions/259812/next-unread->
> message-shortcut-in-kmail-message-window
>
> This is amplified by kmail's misbehaviour on KDE Wayland. Through the
> inability to show the email in the preview pane, emails have to be opened
> in email message windows on Wayland (see
> https://bugs.kde.org/show_bug.cgi?id=414955)
>
>
>
> -- System Information:
> Debian Release: bullseye/sid
> APT prefers testing
> APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 5.9.0-1-amd64 (SMP w/4 CPU threads)
> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages kmail depends on:
> ii akonadi-server
> 4:20.08.2-3+b1 ii kdepim-runtime
> 4:20.08.2-4 ii kio
> 5.74.0-2 ii libc6
>2.31-4 ii libgcc-s1
> 10.2.0-16 ii libgpgmepp6
> 1.14.0-1+b1 ii libkf5akonadiagentbase5 [libkf5akonadiagentbase5-20.08]
> 4:20.08.2-3+b1 ii libkf5akonadicontact5 [libkf5akonadicontact5-20.08]
> 4:20.08.2-3 ii libkf5akonadicore5abi2 [libkf5akonadicore5-20.08]
> 4:20.08.2-3+b1 ii libkf5akonadimime5 [libkf5akonadimime5-20.08]
> 4:20.08.2-2 ii libkf5akonadisearch-bin
>4:20.08.2-2 ii libkf5akonadisearch-plugins
> 4:20.08.2-2 ii libkf5akonadisearchdebug5
> [libkf5akonadisearchdebug5-20.08] 4:20.08.2-2 ii libkf5akonadisearchpim5
> [libkf5akonadisearchpim5-20.08] 4:20.08.2-2 ii
> libkf5akonadiwidgets5abi1 [libkf5akonadiwidgets5-20.08] 4:20.08.2-3+b1
> ii libkf5bookmarks5 5.74.0-2
> ii libkf5calendarcore5abi2 5:5.74.0-2
> ii libkf5calendarutils5 [libkf5calendarutils5-20.08]
> 4:20.08.2-2 ii libkf5codecs5
> 5.74.0-2 ii libkf5completion5
> 5.74.0-2 ii libkf5configcore5
> 5.74.0-2 ii libkf5configgui5
> 5.74.0-2 ii libkf5configwidgets5
> 5.74.0-2 ii libkf5contacts5
> 5:5.74.0-2 ii libkf5coreaddons5
> 5.74.0-2 ii libkf5crash5
> 5.74.0-2 ii libkf5dbusaddons5
> 5.74.0-2 ii libkf5grantleetheme-plugins
> 20.08.2-2 ii libkf5gravatar5abi2 [libkf5gravatar5-20.08]
> 4:20.08.2-2 ii libkf5guiaddons5
> 5.74.0-3 ii libkf5i18n5
> 5.74.0-3 ii libkf5iconthemes5
> 5.74.0-2 ii libkf5identitymanagement5 [libkf5identitymanagement5-20.08]
> 20.08.2-2 ii libkf5itemmodels5
> 5.74.0-2 ii libkf5itemviews5
> 5.74.0-2 ii libkf5jobwidgets5
> 5.74.0-2 ii libkf5kcmutils5
> 5.74.0-2 ii libkf5kiocore5
> 5.74.0-2 ii libkf5kiofilewidgets5
> 5.74.0-2 ii libkf5kiogui5
> 5.74.0-2 ii libkf5kiowidgets5
> 5.74.0-2 ii libkf5kontactinterface5 [libkf5kontactinterface5-20.08]
> 20.08.2-2 ii libkf5ksieveui5 [libkf5ksieveui5-20.08]
> 4:20.08.2-2 ii libkf5ldap5abi1 [libkf5ldap5-20.08]
Bug#974821: kmail: some attachments are not shown with setting header/standard in eMail window
Hey,
The bug is not a Debian specific one, so it should be reported and fixed
upstream at KDE:
https://bugs.kde.org
Please also leave a comment here at this bugreport with the url of the
upstream bug, so we are able to track the upstream bug status. To do this
properly add a line to the mail with:
Control: Forwarded -1 {url}
at the beginning of your response, than BTS (Debian Bugtracker) will do its
magic.
hefee
On Sonntag, 15. November 2020 09:50:09 CET Silvério Santos wrote:
> Package: kmail
> Version: 4:20.08.2-4
> Severity: normal
>
> Dear Maintainer,
>
> when view/header/standard is configured some attachments are not shown in
> the email window, so that there is no indication of an attachment there.
> Switching to view/header/decorative shows the attachments in the same email
> window's header section.
>
> Example code for not shown attachment with standard header ([UUID] is a
> placeholder):
> --Apple-Mail=_[UUID]
> Content-Disposition: inline;
> filename="filename.pdf"
> Content-Type: application/pdf;
> x-unix-mode=0644;
> name="filename.pdf"
> Content-Transfer-Encoding: base64
>
> [code]
>
> Example code for shown attachment with standard header:
> --multipart_alternative.123456789--
>
> --multipart_mixed.987654321
> Content-Type: application/pdf
> Content-Length: 42000
> Content-Disposition: attachment; filename="filename.pdf"
> Content-Transfer-Encoding: base64
>
> [code]
>
>
>
> -- System Information:
> Debian Release: bullseye/sid
> APT prefers testing
> APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 5.9.0-1-amd64 (SMP w/4 CPU threads)
> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages kmail depends on:
> ii akonadi-server
> 4:20.08.2-3+b1 ii kdepim-runtime
> 4:20.08.2-4 ii kio
> 5.74.0-2 ii libc6
>2.31-4 ii libgcc-s1
> 10.2.0-16 ii libgpgmepp6
> 1.14.0-1+b1 ii libkf5akonadiagentbase5 [libkf5akonadiagentbase5-20.08]
> 4:20.08.2-3+b1 ii libkf5akonadicontact5 [libkf5akonadicontact5-20.08]
> 4:20.08.2-3 ii libkf5akonadicore5abi2 [libkf5akonadicore5-20.08]
> 4:20.08.2-3+b1 ii libkf5akonadimime5 [libkf5akonadimime5-20.08]
> 4:20.08.2-2 ii libkf5akonadisearch-bin
>4:20.08.2-2 ii libkf5akonadisearch-plugins
> 4:20.08.2-2 ii libkf5akonadisearchdebug5
> [libkf5akonadisearchdebug5-20.08] 4:20.08.2-2 ii libkf5akonadisearchpim5
> [libkf5akonadisearchpim5-20.08] 4:20.08.2-2 ii
> libkf5akonadiwidgets5abi1 [libkf5akonadiwidgets5-20.08] 4:20.08.2-3+b1
> ii libkf5bookmarks5 5.74.0-2
> ii libkf5calendarcore5abi2 5:5.74.0-2
> ii libkf5calendarutils5 [libkf5calendarutils5-20.08]
> 4:20.08.2-2 ii libkf5codecs5
> 5.74.0-2 ii libkf5completion5
> 5.74.0-2 ii libkf5configcore5
> 5.74.0-2 ii libkf5configgui5
> 5.74.0-2 ii libkf5configwidgets5
> 5.74.0-2 ii libkf5contacts5
> 5:5.74.0-2 ii libkf5coreaddons5
> 5.74.0-2 ii libkf5crash5
> 5.74.0-2 ii libkf5dbusaddons5
> 5.74.0-2 ii libkf5grantleetheme-plugins
> 20.08.2-2 ii libkf5gravatar5abi2 [libkf5gravatar5-20.08]
> 4:20.08.2-2 ii libkf5guiaddons5
> 5.74.0-3 ii libkf5i18n5
> 5.74.0-3 ii libkf5iconthemes5
> 5.74.0-2 ii libkf5identitymanagement5 [libkf5identitymanagement5-20.08]
> 20.08.2-2 ii libkf5itemmodels5
> 5.74.0-2 ii libkf5itemviews5
> 5.74.0-2 ii libkf5jobwidgets5
> 5.74.0-2 ii libkf5kcmutils5
> 5.74.0-2 ii libkf5kiocore5
> 5.74.0-2 ii libkf5kiofilewidgets5
> 5.74.0-2 ii libkf5kiogui5
Bug#973505: akregator: Feeds no longer update
control: tags -1 + moreinfo control: severity -1 normal Hey, > library /usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so: > (/lib/x86_64-linux-gnu/libQt5Core.so.5: version `Qt_5.15' not found > (required by /lib/x86_64-linux-gnu/libQt5Network.so.5)) I cannot reproduce the issue you described. And from my side it seems, like you mixed packages, that are build against different qt versions. Can you verify that it is still an issue? Regards, hefee signature.asc Description: This is a digitally signed message part.
Bug#976289: libkolabxml: please mark some symbols as optional
Hey, > Hello, when built with -O3, some symbols are disappearing on s390x. > Is it possible to mark them as optional? I'm happy to merge this patch, but please explain first, why this would improve the package? From my side it looks like this: The buildds are happy with s390x symbols[1], so why I should support these random build flags? hefee [1] https://buildd.debian.org/status/fetch.php? pkg=libkolabxml=s390x=1.2.0-1=1606861476=0 signature.asc Description: This is a digitally signed message part.
Bug#970127: kmail: Kmail depends on libsasl2-modules to send out mails via SMTP
reassign 970127 kdepim-runtime 4:20.08.2-3 thanks signature.asc Description: This is a digitally signed message part.
Bug#972606: plasma-workspace FTFBS: cmake error / some missing dependency
Hey, > Sandro removed it (again) in 5.74.0-1 :-/ I'll fix it soon. sorry for that, I looked via git log and havn't seen your patch, sorry for that. > Sandro: when planning to remove dependencies from a -dev file, please > rebuild the reverse dependencies to check everything still works > (currently kdelibs4support has only 12 users in unstable). That is also a good thing to do. Now I also learned that kdelibs4support is the only one in Frameworks, that have dependencies at the dev package, that are not part of the build dependencies. I will surly remember that. hefee signature.asc Description: This is a digitally signed message part.
Bug#972404: transition: KDEPIM 20.08 and Frameworks 5.74.0
Control: severity 972224 serious Control: severity 972226 serious Hey, I uploaded Frameworks 5.74.0 and KDEPIM 20.08 completely, so you can do the binNMUs. hefee -- On Sonntag, 18. Oktober 2020 12:39:20 CEST Sebastian Ramacher wrote: > Control: forwarded -1 > https://release.debian.org/transitions/html/kdepim-20.08.html Control: tags > -1 + confirmed > > On 2020-10-18 01:35:12 +0200, Sandro Knauß wrote: > > Package: release.debian.org > > User: release.debian@packages.debian.org > > Usertags: transition > > X-Debbugs-Cc: pkg-kde-t...@alioth-lists.debian.net > > Severity: normal > > Control: Block -1 by 972224 972226 > > > > Dear Release team, > > > > We would like to request a transition for KDEPIM 20.08 and Frameworks > > 5.74.0. We request both in one shot, because KDEPIM depends on the new > > Frameworks, so we need to upload Frameworks anyways. For Framework in > > itself no transition is needed, as it gives ABI stability, that is not > > broken. But this time KDAV has moved from KDEPIM to KDE Frameworks. And > > inside KDEPIM there was no ABI stability, that's why we need to binNMU > > for packages depending on libkf5dav5. In this case it is only > > kdepim-runtime that is part of KDEPIM, what is the reason why I think we > > shoud upload KDEPIM and Frameworks together. > > > > Outside KDEPIM and KDE Frameworks there are only some other packages, that > > needs a normal binNMU. Additionally KDEPIM 20.08 removed 4 libraries: > > * libkf5libkdepimakonadi5 > > * libkf5followupreminder5 > > * libkf5kdepimdbusinterfaces5 > > * libkf5followupreminder5 > > > > I checked the packages the need a binNMU, if they build successfully or > > filed issues when not. The complete list of packages outside KDEPIM and > > Frameworks are: > > > > * digikam > > * kgpg > > * kio-gdrive > > > > * kjots (#972226) MR is already provided: > >https://salsa.debian.org/qt-kde-team/extras/kjots/-/merge_requests/1 > > > > * kmymoney > > * kraft > > > > * zanshin (#972224) MR is already provided: > > https://salsa.debian.org/qt-kde-team/extras/zanshin/-/merge_requests/2 > > > > > >From my side every is ready for the transition. > > Trackers are at > https://release.debian.org/transitions/html/kdepim-20.08.html and > https://release.debian.org/transitions/html/kdav.html > > Please go ahead with the uploads to unstable. > > Cheers > > > hefee > > > > Here is the ben file that is based on one from the previous transition: > > https://salsa.debian.org/release-team/transition-data/-/blob/master/old/kd > > epim-20.04.ben > > > > Ben file: > > > > title = "KDEPIM 20.08"; > > is_affected = .depends ~ > > /libkf.*-20\.04|libkf5libkdepimakonadi5|libkf5followupreminder5|libkf5kde > > pimdbusinterfaces5|libkf5followupreminder5/ | .depends ~ /libk.*-20\.08/; > > is_good = .depends ~ /libk.*-20\.08/; > > is_bad = .depends ~ > > /libkf.*-20\.04|libkf5libkdepimakonadi5|libkf5followupreminder5|libkf5kde > > pimdbusinterfaces5|libkf5followupreminder5/; > > > > title = "KDAV moved to Frameworks 5.74.0" > > is_affected = .depends ~ /libkf5dav5/; > > is_good = .depends ~ /libkf5dav5 \(>= 1:5\.74/; > > is_bad = .depends ~ /libkf.*-20\.04/; signature.asc Description: This is a digitally signed message part.
Bug#972404: transition: KDEPIM 20.08 and Frameworks 5.74.0
Package: release.debian.org User: release.debian@packages.debian.org Usertags: transition X-Debbugs-Cc: pkg-kde-t...@alioth-lists.debian.net Severity: normal Control: Block -1 by 972224 972226 Dear Release team, We would like to request a transition for KDEPIM 20.08 and Frameworks 5.74.0. We request both in one shot, because KDEPIM depends on the new Frameworks, so we need to upload Frameworks anyways. For Framework in itself no transition is needed, as it gives ABI stability, that is not broken. But this time KDAV has moved from KDEPIM to KDE Frameworks. And inside KDEPIM there was no ABI stability, that's why we need to binNMU for packages depending on libkf5dav5. In this case it is only kdepim-runtime that is part of KDEPIM, what is the reason why I think we shoud upload KDEPIM and Frameworks together. Outside KDEPIM and KDE Frameworks there are only some other packages, that needs a normal binNMU. Additionally KDEPIM 20.08 removed 4 libraries: * libkf5libkdepimakonadi5 * libkf5followupreminder5 * libkf5kdepimdbusinterfaces5 * libkf5followupreminder5 I checked the packages the need a binNMU, if they build successfully or filed issues when not. The complete list of packages outside KDEPIM and Frameworks are: * digikam * kgpg * kio-gdrive * kjots (#972226) MR is already provided: https://salsa.debian.org/qt-kde-team/extras/kjots/-/merge_requests/1 * kmymoney * kraft * zanshin (#972224) MR is already provided: https://salsa.debian.org/qt-kde-team/extras/zanshin/-/merge_requests/2 >From my side every is ready for the transition. hefee Here is the ben file that is based on one from the previous transition: https://salsa.debian.org/release-team/transition-data/-/blob/master/old/kdepim-20.04.ben Ben file: title = "KDEPIM 20.08"; is_affected = .depends ~ /libkf.*-20\.04|libkf5libkdepimakonadi5|libkf5followupreminder5|libkf5kdepimdbusinterfaces5|libkf5followupreminder5/ | .depends ~ /libk.*-20\.08/; is_good = .depends ~ /libk.*-20\.08/; is_bad = .depends ~ /libkf.*-20\.04|libkf5libkdepimakonadi5|libkf5followupreminder5|libkf5kdepimdbusinterfaces5|libkf5followupreminder5/; title = "KDAV moved to Frameworks 5.74.0" is_affected = .depends ~ /libkf5dav5/; is_good = .depends ~ /libkf5dav5 \(>= 1:5\.74/; is_bad = .depends ~ /libkf.*-20\.04/; signature.asc Description: This is a digitally signed message part.
Bug#972226: kjots: FTBFS with KDEPIM 20.08
Package: kjots Version: 4:5.0.2-2 Severity: normal Tags: ftbfs Hey, kjots failed to build against KDEPIM 20.08: /<>/obj-x86_64-linux-gnu/src/kontact_plugin/kontact_kjotsplugin_autogen/EWIEGA46WW/../../../../../src/kontact_plugin/kjots_plugin.h:66:13: error: ‘ReadOnlyPart’ in namespace ‘KParts’ does not name a type 66 | KParts::ReadOnlyPart *createPart() Q_DECL_OVERRIDE; | ^~~~ there is alaready an patch upstream to fix this: https://invent.kde.org/pim/kjots/-/commit/bcf49fb95bee12bbc4bef0578285ad296deafcae You can build against new KDEPIM 20.08 with the repo: http://qt-kde-team.debian.net/ hefee
Bug#972224: zanshin: FTBFS against KDEPIM 20.08
Package: zanshin Version: 0.5.71-1 Severity: normal Tags: ftbfs Hey, I built zanshin against new KDEPIM 20.08 and it fails with: /<>/obj-x86_64-linux-gnu/src/zanshin/kontact/kontact_zanshinplugin_autogen/EWIEGA46WW/../../../../../../src/zanshin/kontact/kontact_plugin.h:39:13: error: ‘ReadOnlyPart’ in namespace ‘KParts’ does not name a type 39 | KParts::ReadOnlyPart *createPart() override; | ^~~~ There is already a patch in the upstream repository: https://invent.kde.org/pim/zanshin/-/commit/4850c08998b33b37af99c3312d19 To build against kdepim 20.08 you can use the http://qt-kde-team.debian.net/ repo. I'll upload kdepim the next days to experimental. hefee
Bug#828021: extra-cmake-modules: please make the build reproducible (umask, toolchain)
control: Forwarded -1 https://invent.kde.org/frameworks/extra-cmake-modules/-/merge_requests/35 Hey, finally after some years I pushed the patch upstream (hopefully it gets accepted). hefee signature.asc Description: This is a digitally signed message part.
Bug#954448: Bug resolved with new nextcloud.desktop file
Hi, > I resolved the runtime error condition with attached .desktop file, to > be stripped off the .MATE and > put in ~/.config/autostart or in /usr/share/applications/ > > mate should have its own directory in the debian package hierarchy, just > as gnome or kde have their own. I can't see any difference against the shipped desktop file /usr/share/applications/com.nextcloud.desktopclient.nextcloud.desktop anyways the desktop file is not KDE or Gnome specific, so MATE should also process it. hefee signature.asc Description: This is a digitally signed message part.
Bug#955174: further information
Control: tags -1 + upstream Hey, this is an upstream issue, so please report it upstream and provide us the url, so we can track the status: https://github.com/nextcloud/desktop/issues hefee signature.asc Description: This is a digitally signed message part.
Bug#964434: nextcloud-desktop: Please move the menu entry of nextcloud-dektop to internet
Control: tags -1 +upstream > in order to make the program more accessible for the common user I would > suggest to move it to the menupoine Internet. This is the place where most > other desktop clients for internet services reside. This is not a Debian specific issue, so please report upstream and report back the issue id of upstream, so we can track the upstream issue: https://github.com/nextcloud/desktop/issues hefee signature.asc Description: This is a digitally signed message part.
Bug#970433: ITP: kuserfeedback -- Framework for collecting user feedback for applications via telemetry and surveys.
Package: wnpp Severity: wishlist Owner: Sandro Knauß X-Debbugs-Cc: debian-de...@lists.debian.org, debian-qt-...@lists.debian.org * Package name: kuserfeedback Version : 1.0.0 Upstream Author : Volker Krause * URL : https://invent.kde.org/libraries/kuserfeedback * License : MIT Programming Lang: C++, QML Description : Framework for collecting user feedback for applications via telemetry and surveys. Telemetry * Extensible set of data sources for telemetry. * Full control for the user on what data to contribute. Surveys * Distribute surveys and offer users to participate in them. * Survey targeting based on telemetry data. * Allow the user to configure how often they want to participate in surveys. . This package contains the management and analytics applications. KDE is usring this Framework to get statistics form users. It is planned to mantain it under the QT/KDE Maintainers team. hefee
Bug#951388: [akonadi-backend-postgresql] apparmor profile unsuitable
Forwarded: https://invent.kde.org/pim/akonadi/-/merge_requests/32 Hey, I have pushed the needed changes to upstream. The AppArmor profile is living there. hefee -- On Samstag, 15. Februar 2020 21:08:15 CEST Bastien Roucariès wrote: > Package: akonadi-backend-postgresql > Version: 4:19.08.3-1 > Severity: grave > Justification: renders package unusable > Tags: patch > > Dear Maintainer, > > Please find the following update for apparmor > > Please apply > > Bastien signature.asc Description: This is a digitally signed message part.
Bug#969422: RM: owncloud-client -- ROM; Unmantained
Package: ftp.debian.org Severity: normal X-Debbugs-Cc: pkg-owncloud-maintain...@alioth-lists.debian.net Hey, for over two years owncloud-client did not get any update from our side. Because upstream told us, that the do not support Nextcloud server anymore and all maintainer are using Nextcloud server to use the client. Let's make it official, that we do not support this package anymore and remove it from the archive. Manybe others step up and take over ownership. For most users nextcloud-desktop is a drop-in replacement as far they use Nextcloud server. See #969421 for the request that we are searching a new maintainer for the package. hefee
Bug#969421: O: owncloud-client -- folder synchronization with an ownCloud server - GUI
Package: wnpp Severity: normal X-Debbugs-Cc: pkg-owncloud-maintain...@alioth-lists.debian.net We intend to orphan the owncloud-client package, as our team is not using ownCloud Servers anymore and have switched to Nextcloud and their client nextcloud-desktop. The package description is: The ownCloudSync system lets you always have your latest files wherever you are. Just specify one or more folders on the local machine to and a server to synchronize to. You can configure more computers to synchronize to the same server and any change to the files on one computer will silently and reliably flow across to every other. . owncloud-client provides the graphical client specialising in synchronizing with cloud storage provided by ownCloud. The ownCloudSync system lets you always have your latest files wherever you are. Just specify one or more folders on the local machine to and a server to synchronize to. You can configure more computers to synchronize to the same server and any change to the files on one computer will silently and reliably flow across to every other. . owncloud-client provides the graphical client specialising in synchronizing with cloud storage provided by ownCloud. The ownCloudSync system lets you always have your latest files wherever you are. Just specify one or more folders on the local machine to and a server to synchronize to. You can configure more computers to synchronize to the same server and any change to the files on one computer will silently and reliably flow across to every other. . owncloud-client provides the graphical client specialising in synchronizing with cloud storage provided by ownCloud.
Bug#961647: akonadi: FTBFS on armel: missing -latomic
Hey, Whoo I'm quite impressed to have two different solutions that fast! Thank you both for proposing me solutions. You made my day! > The easy workaround is in debian/rules: > > ifneq (,$(filter $(DEB_HOST_ARCH), armel m68k mipsel powerpc sh4)) > export DEB_LDFLAGS_MAINT_APPEND = -Wl,--no-as-needed -latomic > -Wl,--as-needed endif thanks for this easy workaround! I implemented that one for now. > It might, but due to gcc defaulting to -Wl,--as-needed it wouldn't be an issue. There is also https://phabricator.kde.org/D16184 that only links libatomic if necessary. I will propose a proper patch upstream based on the patch you proposed. Maybe we integrate CheckAtomic into extra-cmake-modules. hefee signature.asc Description: This is a digitally signed message part.
Bug#961647: akonadi: FTBFS on armel: missing -latomic
Hey, > This is caused by a missing -latmoic. See also > https://buildd.debian.org/status/fetch.php?pkg=akonadi=armel=4%3A20 > .04.1-1=1590553675=0 thanks for this fast scan and also proposing a solution. But I have no example of how I need to modify cmake to end up having -latomic for armel being added. Do you know anything? I found one solution to add atomic everywhere, but this may be an overkill: https://github.com/mavlink/mavros/pull/790/files So far I see the libboost-atomic1.67-dev is already installed, that means I don't have to install anything additionally. So at least I don't have to modify build-depends. hefee signature.asc Description: This is a digitally signed message part.
Bug#841762: kdeconnect: More information about kedconnectd crashing
Hey, > I've been quite surprised to find that this bug report was first filled > in 2016 because I've only began experiencing it for about a week. Using > testing I waited for a week to see if a fix would come. Now's the time > for the BR. well this is a bug, that needs to be solved by upstream, so please file a bugreport at https://bugs.kde.org > It's also sad that we can't strace which system call causes the crash > nor use gdb (even without debugging information). > > --8<--8<--8<--8<--8<--8<--8<--8<-- > ~$ LC_ALL=C strace /usr/lib/x86_64-linux-gnu/libexec/kdeconnectd > strace: test_ptrace_get_syscall_info: PTRACE_TRACEME: Operation not > permitted strace: ptrace(PTRACE_TRACEME, ...): Operation not permitted > +++ exited with 1 +++ > ~$ gdb /usr/lib/x86_64-linux-gnu/libexec/kdeconnectd > [...] > (No debugging symbols found in > /usr/lib/x86_64-linux-gnu/libexec/kdeconnectd) (gdb) run > Starting program: /usr/lib/x86_64-linux-gnu/libexec/kdeconnectd > warning: Could not trace the inferior process. > warning: ptrace: Operation not permitted > During startup program exited with code 127. > --8<--8<--8<--8<--8<--8<--8<--8<-- Your user needs to have the ptrace permission in order to use gdb successfully [1]. And you need to install the symbols files: kdeconnect-dbgsym from the repo: deb http://debug.mirrors.debian.org/debian-debug/ unstable-debug main hefee [1] https://wiki.ubuntu.com/SecurityTeam/Roadmap/ KernelHardening#ptrace_Protection signature.asc Description: This is a digitally signed message part.
Bug#960534: transition: KDEPIM and KDE Frameworks
Hey Sebastian, > On 2020-05-22 11:52:27 +0200, Sandro Knauß wrote: > > I forgot about the the auto-kdav transition that is also part of KDEPIM & > > KDE Frameworks transition. That means that auto-kdav is automatically > > solved together with kdepim 20.04 transition. > > Feel free to go ahead with this. Please let us know once the uploads to > unstable are all done. I'll schedule binNMUs for the remaining packages > afterwards. Okay I've uploaded everything, so you can schedule binNMUs with version dependencies. The buildds are still busy to finish the set of packages I uploaded. hefee signature.asc Description: This is a digitally signed message part.
Bug#961558: libkf5xmlgui5: removes KGestureMap, which breaks older kdebugdialog5 (package: libkf5kdelibs4support5-bin)
Hey, > It's nice you uploaded a new version, but you picked 5.59 as the breaks > version, while 5.62 is surely still affected. nrgh, that was a typo. hefee signature.asc Description: This is a digitally signed message part.
Bug#961558: libkf5xmlgui5: removes KGestureMap, which breaks older kdebugdialog5 (package: libkf5kdelibs4support5-bin)
Hey Jiri, please do report such an issue on the package, that breaks and not at the source of the problem, that would gives us automatically the version of libkf5kdelibs4support5-bin. If not always make sure that both versions are included in the bugreport. I expect, that you use the version still on unstable. as the version on experimental runs fine. hefee signature.asc Description: This is a digitally signed message part.
Bug#960302: [Pkg-roundcube-maintainers] Bug#960302: imap retry must be tunable
Control: forwarded -1 https://github.com/roundcube/roundcubemail/pull/7402 hey, > Could you please have a look at this regression report? You authored > the patch and my PHP-fu is failing me :-P It should definitely not > retry the very same incorrect credentials. Even on systems without > anti-bruteforce logic that locks the user out, Roundcube still takes 5 > times longer to complain a about a failed login — which is not > negligible when an expensive PBKDF is used for credential verification. ACK > I think it's rather unfortunate that > debian/patches/retry_to_reach_imap_server.patch was AFAICT never submitted > upstream and landed into stable through -p-u. I dunno whether > program/lib/Roundcube/rcube_imap.php:connect() has access to the IMAP state > machine to determine whether a greeting was seen (AFAICT your intention was > to retry on missing greeting lines, not on NO/BYE greeting conditions let > alone failed authentication attempts) or to another interface returning > whether the error is transient or not. Either way it'd be good to have > upstream's blessing before adopting such patches to Debian :-) Well I tried several times to reach upstream and they are often not answering. Never the less I created a pull request with an updated version, that does no retry for unrecoverable failures like authentication failure, no password, configuration failure. That should improve the situation already in this issue. @Matus UHLAR: please try the patch attached to the pull request if this fixes your issue: https://github.com/roundcube/roundcubemail/pull/7402 Cheers, hefee signature.asc Description: This is a digitally signed message part.
Bug#960534: Acknowledgement (transition: KDEPIM and KDE Frameworks)
Hey, I forgot about the the auto-kdav transition that is also part of KDEPIM & KDE Frameworks transition. That means that auto-kdav is automatically solved together with kdepim 20.04 transition. hefee signature.asc Description: This is a digitally signed message part.
Bug#960534: transition: KDEPIM and KDE Frameworks
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition KCalCore and KContacts have moved from KDEPIM to KDE Frameworks. In Frameworks KDE guarantees ABI stability, so it is possible to get rid of the virtual packages approach and use normal symbols files to track dependencies. I will upload KDE Frameworks together with KDEPIM. As KDEPIM needs the new Frameworks anyways. Outside KDEPIM and KDE Frameworks there are only some other packages, that needs a normal binary upload. I checked these packages already, that they build successfully: digikam kgpg kio-gdrive kjots kmymoney kraft zanshin Ben file: title = "kdepim 20.04"; is_affected = .depends ~ /libk.*5-19\.08/ | .depends ~ /libk.*5-20\.04/; is_good = .depends ~ /libk.*5-20\.04/; is_bad = .depends ~ /libk.*5-19\.08/; title = "KCalCore to Frameworks"; is_affected = .depends ~ /libkf5calendarcore5abi2/; is_good = ! .depends ~ /libkf5calendarcore5-19\.08/; is_bad = .depends ~ /libkf5calendarcore5-19\.08/; title = "KContacts to Frameworks"; is_affected = .depends ~ /libkf5contacts5/; is_good = ! .depends ~ /libkf5contacts5-19\.08/; is_bad = .depends ~ /libkf5contacts5-19\.08/;
Bug#960278: python-debian: Don't loose whitespace information when editing Copyright.files
Source: python-debian Version: 0.1.37 Severity: normal Hey, currently whitespace information is lost, when modifing Copyright.files and entries will joined with a simple space. That is correct syntax, but not the expected behavior for a developer. Especially that the workaround needs to access the private data element _RestrictedWrapper__data and that is bad Python practice to access private class members. It would be nice to have a proper way edit and store parts without losing the whitespace information. Here is my workaround: for paragraph in copyright.all_files_paragraphs(): files = list() for f in paragraph._RestrictedWrapper__data['Files'].splitlines(): if match(f.strip()): if files: files.append(f) else: files.append(f.strip()) files_entry = "\n".join(files) paragraph._RestrictedWrapper__data['Files'] = files_entry -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'oldstable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (100, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.6.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#947776: [Pkg-owncloud-maintainers] Bug#947776: Same problem also with nautilus-nextcloud 2.6.4-1
Control: reassign -1 python3-nautilus 1.2.3-1 Control: affects -1 nautilus-nextcloud Hey, Thanks for digging into this deeper. > When I start nautilus from the command line I get this warning: > > ** (org.gnome.Nautilus:36227): WARNING **: 21:34:08.527: > /usr/lib/x86_64-linux-gnu/nautilus/extensions-3.0/libnautilus- > python.so: undefined symbol: _PyNautilusInfoProvider_Type > > Maybe this indicates the root of the problem? If python3-natuilus has undefined symbols this properly the root cause for this, because the nautilus integration is only a python script. I reassigned the bug to python3-nautilus, so they can have a look. hefee signature.asc Description: This is a digitally signed message part.
Bug#959207: ITP: kquickcharts -- A QtQuick plugin providing high-performance charts.
Package: wnpp Severity: wishlist Owner: Sandro Knauß * Package name: kquickcharts Version : 5.69.0 Upstream Author : KDE * URL : https://invent.kde.org/kde/kquickcharts * License : LGPL-2.1+3+KDEeV Programming Lang: C++, QML Description : A QtQuick plugin providing high-performance charts. A module to Render gpu-accelerated charts. It supports three different chart types: pie, line and bar, which can be fed from multiple types of data sources. There is also support for axis labels, an axis grid and a legend. Additionally, there is a submodule that contains some convenience items. The pie and line charts are rendered using a technique called signed distance fields, which allows efficient GPU-accelerated rendering of 2D shapes without loss of quality. kquickcharts was added to KDE Frameworks in December and is intended to replace kqtquickcharts on the long run. It is intended to package within the "Debian/Kubuntu Qt/KDE Maintainers" team.
Bug#948729: python3-sphinx: Sphinx breaks with docutils 0.16~rc1
Package: python3-sphinx Version: 1.8.5-4 Severity: important Tags: upstream patch sid Control: affects -1 nextcloud-desktop Control: forwarded -1 https://github.com/sphinx-doc/sphinx/issues/6887 Hey, Sphinx is currently unusable to build documentation anymore. As always sphinx breaks with: https://buildd.debian.org/status/fetch.php?pkg=nextcloud-desktop=amd64=2.6.2-1=1578830658=0 Exception occurred: File "/usr/lib/python3/dist-packages/sphinx/util/nodes.py", line 97, in apply_source_workaround for classifier in reversed(node.parent.traverse(nodes.classifier)): TypeError: '_traversal_list' object is not reversible The full traceback has been saved in /tmp/sphinx-err-lppsk4sf.log, if you want to report the issue to the developers. The upstream bugreport issues/6887 tell, that this was caused by the upload of docutils 1.6.1~rc1. Upstream has already a patch to fix this: https://github.com/sphinx-doc/sphinx/pull/6918 hefee -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'oldstable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-sphinx depends on: ii python33.7.5-3 ii python3-alabaster 0.7.8-1 ii python3-babel 2.6.0+dfsg.1-1 ii python3-distutils 3.8.0-1 ii python3-docutils 0.15.2+dfsg-2 ii python3-imagesize 1.2.0-1 ii python3-jinja2 2.10.1-1 ii python3-lib2to33.8.0-1 ii python3-packaging 19.1-2 ii python3-pygments 2.3.1+dfsg-1 ii python3-requests 2.22.0-2 ii python3-six1.13.0-1 ii sphinx-common 1.8.5-4 Versions of packages python3-sphinx recommends: ii make 4.2.1-1.2 ii python3-pil 7.0.0-2 Versions of packages python3-sphinx suggests: pn dvipng ii imagemagick-6.q16 8:6.9.10.23+dfsg-2.1+b2 pn latexmk ii libjs-mathjax 2.7.4+dfsg-1 ii python3-sphinx-rtd-theme 0.4.3+dfsg-2 pn python3-stemmer pn sphinx-doc ii texlive-fonts-recommended 2019.20191208-4 ii texlive-latex-extra2019.20191208-1 ii texlive-latex-recommended 2019.20191208-4 ii texlive-plain-generic 2019.20191208-1 -- no debconf information
Bug#947331: buster-pu: package roundcube/1.3.8+dfsg.1-2
Hey, > + * Add patch to Fix "Retry to connect to IMAP server" (Closes: #947320) #947320 is fixed in unstable with 1.4.1+dfsg.1-2. hefee signature.asc Description: This is a digitally signed message part.
Bug#947320: roundcube-core: Retry to connect to IMAP server
Hi Guilhem, > Did you try to upstream that patch? Also FWIW the code snippet seems to > be unchanged since <1.0.0, AFAICT no one complained so far so I'm unsure > that Severity: important is really appropriate here, or if it's worth > fixing in stable :-P I know, that the code snipped is unchanged for a long time. I created that patch a long time ago. It is worth fixing it in stable, as it really can break things, if that patch is missing under specific circumstances. Last year I had a lot load on my IMAP Server, so the IMAP server was sometimes too slow to answer and that patch fixes that. Yes it should go upstream, but first I wanted to fix the Debian package ;P hefee signature.asc Description: This is a digitally signed message part.
Bug#947331: buster-pu: package roundcube/1.3.8+dfsg.1-2
Control: tags -1 - moreinfo > +roundcube (1.3.10+dfsg.1-1~deb10u1) buster; urgency=medium > + > + * d/control: revert bump of Standards-Version, as we want to release to > +stable. > + * d/upstream/signing-key.asc: revert Minimize OpenPGP certificate. > + * Add patch to Fix "Retry to connect to IMAP server" (Closes: #947320) > > I'm assuming both from the position of the latter change in the > changelog, and the metadata of the referenced bug, that it isn't > actually applied in unstable yet? The two reverts I did just to minimize the debdiff, but think they won't harm to ship them to stable. Yes #947320 isn't fixed in unstable nor experimental yet. But I will make sure, that the next version 1.4.1, that will hit unstable in the next days will have this patch applied. I created that patch in 2017 and had applied it locally to test and than I forgotten as the bug was actually fixed to add it to Debian. But that's why I'm very certain, that it doesn't beak anything. hefee signature.asc Description: This is a digitally signed message part.
Bug#947331: buster-pu: package roundcube/1.3.8+dfsg.1-2
Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu
upstream releases only bugfix releases for the 1.3 branch. As they,
do not add any new feature IMO it would makes sense to ship the newest
1.3.10 for Debian Buster users. I have packaged 1.3.10 for Debian.
This was also requested for stetch, but I had not find time to do the
actual work: #887507.
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500,
'oldstable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'),
(500, 'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.3.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru roundcube-1.3.8+dfsg.1/CHANGELOG roundcube-1.3.10+dfsg.1/CHANGELOG
--- roundcube-1.3.8+dfsg.1/CHANGELOG2018-10-23 13:12:53.0 +0200
+++ roundcube-1.3.10+dfsg.1/CHANGELOG 2019-08-28 13:24:49.0 +0200
@@ -1,6 +1,40 @@
CHANGELOG Roundcube Webmail
===
+RELEASE 1.3.10
+--
+- Managesieve: Fix so "Create filter" option does not show up when Filters
menu is disabled (#6723)
+- Enigma: Fix bug where revoked users/keys were not greyed out in key info
+- Enigma: Fix error message when trying to encrypt with a revoked key (#6607)
+- Enigma: Fix "decryption oracle" bug [CVE-2019-10740] (#6638)
+- Fix compatibility with kolab/net_ldap3 > 1.0.7 (#6785)
+- Fix bug where bmp images couldn't be displayed on some systems (#6728)
+- Fix bug in parsing vCard data using PHP 7.3 due to an invalid regexp (#6744)
+- Fix bug where bold/strong text was converted to upper-case on html-to-text
conversion (6758)
+- Fix bug in rcube_utils::parse_hosts() where %t, %d, %z could return only tld
(#6746)
+- Fix bug where Next/Prev button in mail view didn't work with multi-folder
search result (#6793)
+- Fix bug where selection of columns on messages list wasn't working
+- Fix bug in converting multi-page Tiff images to Jpeg (#6824)
+- Fix wrong messages order after returning to a multi-folder search result
(#6836)
+- Fix PHP 7.4 deprecation: implode() wrong parameter order (#6866)
+- Fix bug where it was possible to bypass the position:fixed CSS check in
received messages (#6898)
+- Fix bug where some strict remote URIs in url() style were unintentionally
blocked (#6899)
+- Fix bug where it was possible to bypass the CSS jail in HTML messages using
:root pseudo-class (#6897)
+- Fix bug where it was possible to bypass href URI check with
data:application/xhtml+xml URIs (#6896)
+
+RELEASE 1.3.9
+-
+- Fix TinyMCE download location (#6694)
+- Fix bug where a message/rfc822 part without a filename wasn't listed on the
attachments list (#6494)
+- Fix handling of empty entries in vCard import (#6564)
+- Fix bug in parsing some IMAP command responses that include unsolicited
replies (#6577)
+- Fix PHP 7.2 compatibility in debug_logger plugin (#6586)
+- Fix so ANY record is not used for email domain validation, use A, MX, CNAME,
instead (#6581)
+- Fix so mime_content_type check in Installer uses files that should always be
available (i.e. from program/resources) (#6599)
+- Fix missing CSRF token on a link to download too-big message part (#6621)
+- Fix bug when aborting dragging with ESC key didn't stop the move action
(#6623)
+- Fix bug where next row wasn't selected after deleting a collapsed thread
(#6655)
+
RELEASE 1.3.8
-
- Fix PHP warnings on dummy QUOTA responses in Courier-IMAP 4.17.1 (#6374)
diff -Nru roundcube-1.3.8+dfsg.1/composer.json-dist
roundcube-1.3.10+dfsg.1/composer.json-dist
--- roundcube-1.3.8+dfsg.1/composer.json-dist 2018-10-23 13:12:54.0
+0200
+++ roundcube-1.3.10+dfsg.1/composer.json-dist 2019-08-28 13:24:50.0
+0200
@@ -30,6 +30,6 @@
},
"suggest": {
"pear/net_ldap2": "~2.2.0 required for connecting to LDAP",
-"kolab/Net_LDAP3": "dev-master required for connecting to LDAP"
+"kolab/net_ldap3": "dev-master required for connecting to LDAP"
}
}
diff -Nru roundcube-1.3.8+dfsg.1/debian/changelog
roundcube-1.3.10+dfsg.1/debian/changelog
--- roundcube-1.3.8+dfsg.1/debian/changelog 2018-11-05 04:38:45.0
+0100
+++ roundcube-1.3.10+dfsg.1/debian/changelog2019-12-23 22:59:40.0
+0100
@@ -1,3 +1,33 @@
+roundcube (1.3.10+dfsg.1-1~deb10u1) buster; urgency=medium
+
+ * d/control: revert bump of Standards-Version, as we want to release to
+stable.
+ * d/upstream/signing-key.asc: revert Minimize OpenPGP certificate.
+ * Add patch to Fix "Retry to connect to IMAP server&qu
Bug#947320: roundcube-core: Retry to connect to IMAP server
Package: roundcube-core
Version: 1.3.8+dfsg.1-2
Severity: important
Tags: patch
Hey,
An IMAP server may have temporally issues, like to much load and roundcube
fails with
"Empty startup gretting".
Hefee
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500,
'oldstable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'),
(500, 'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.3.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages roundcube-core depends on:
ii dbconfig-common 2.0.13
ii debconf [debconf-2.0] 1.5.73
ii dpkg1.19.7
ii libapache2-mod-php 2:7.3+69
ii libapache2-mod-php7.3 [libapache2-mod-php] 7.3.12-1
pn libjs-bootstrap4
ii libjs-codemirror5.49.2-1
ii libjs-jquery3.3.1~dfsg-3
pn libjs-jquery-minicolors
ii libjs-jquery-ui 1.12.1+dfsg-5
pn libjs-jstimezonedetect
ii libmagic1 1:5.37-6
pn php-auth-sasl
ii php-cli 2:7.3+69
ii php-common 2:69
pn php-intl
pn php-mail-mime
pn php-masterminds-html5
pn php-mbstring
pn php-mcrypt
pn php-net-sieve
pn php-net-smtp
pn php-net-socket
ii php-pear1:1.10.9+submodules+notgz-1
ii php7.0-cli [php-cli]7.0.33-0+deb9u6
ii php7.0-json [php-json] 7.0.33-0+deb9u6
ii php7.2-cli [php-cli]7.2.9-1
ii php7.2-json [php-json] 7.2.9-1
ii php7.3-cli [php-cli]7.3.12-1
ii php7.3-json [php-json] 7.3.12-1
pn roundcube-mysql | roundcube-sqlite3 | roundcub
ii ucf 3.0038+nmu1
Versions of packages roundcube-core recommends:
ii apache2 [httpd-cgi] 2.4.41-1
pn php-gd
pn php-pspell
Versions of packages roundcube-core suggests:
pn php-crypt-gpg
pn php-mkopinsky-zxcvbn-php
pn php-net-ldap2
pn php-net-ldap3
pn roundcube-plugins
Description: Retries to connect to IMAP server.
As it may happen, that an IMAP server will have temporally issues and answers
with "Empty startup greeting".
Author: Hefee
Last-Update: 2019-12-24
---
--- a/program/lib/Roundcube/rcube_imap.php
+++ b/program/lib/Roundcube/rcube_imap.php
@@ -144,7 +144,11 @@ class rcube_imap extends rcube_storage
$attempt = 0;
do {
-$data = $this->plugins->exec_hook('storage_connect',
+if ($attempt > 0) {
+usleep(rand(1000, 10));
+}
+rcube::write_log('imap','Connecting to IMAP server
attempt:'.$attempt);
+$data = $this->plugins->exec_hook('storage_connect',
array_merge($this->options, array('host' => $host, 'user' =>
$user,
'attempt' => ++$attempt)));
@@ -156,7 +160,7 @@ class rcube_imap extends rcube_storage
rcube_utils::parse_socket_options($data['socket_options'],
$data['host']);
$this->conn->connect($data['host'], $data['user'], $pass, $data);
-} while(!$this->conn->connected() && $data['retry']);
+} while(!$this->conn->connected() && $data['attempt'] < 6);
$config = array(
'host' => $data['host'],
Bug#935305: [Pkg-roundcube-maintainers] Bug#935305: roundcube: comments in defaults.inc.php specify incorrect IMAP domain replacement variable %z
Hey, thanks for your bugreport. I am also a little bit puzzled what is the difference between %z and %t. But this should be fixed by roundcube itself. Please report this bug in upstream bug tracker: https://github.com/roundcube/roundcubemail/issues and report back the issue number, if you created a upstream bug. hefee > More or less just a documentation issue: > > Comments in /etc/roundcube/defaults.inc.php (as well as > /usr/share/doc/roundcube-core/config.inc.php.sample) say: > // SMTP server host (for sending mails). > ... > // %z - IMAP domain (IMAP hostname without the first part) > // For example %n = mail.domain.tld, %t = domain.tld > > i.e. the comment claims %z is the IMAP domain, but the example says %t. > In fact, %z does not work, while %t does. > -- System Information: > Debian Release: 10.0 > APT prefers stable > APT policy: (500, 'stable') > Architecture: amd64 (x86_64) > > Kernel: Linux 5.2.8milan2 (SMP w/6 CPU cores) > Kernel taint flags: TAINT_UNSIGNED_MODULE > Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 > (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages roundcube depends on: > ii dpkg1.19.7 > ii roundcube-core 1.3.8+dfsg.1-2 > > roundcube recommends no packages. > > roundcube suggests no packages. > > Versions of packages roundcube-core depends on: > ii dbconfig-common 2.0.11 > ii debconf [debconf-2.0] 1.5.71 > ii dpkg1.19.7 > ii libapache2-mod-php 2:7.3+69 > ii libapache2-mod-php7.0 [libapache2-mod-php] 7.0.33-0+deb9u3 > ii libapache2-mod-php7.3 [libapache2-mod-php] 7.3.4-2 > ii libmagic1 1:5.35-4 > ii php-auth-sasl 1.0.6-3 > ii php-common 2:69 > ii php-intl2:7.3+69 > ii php-mail-mime 1.10.2-0.1 > ii php-net-sieve 1.4.1-1 > ii php-net-smtp1.8.0-1 > ii php-net-socket 1.0.14-2 > ii php-pear > 1:1.10.6+submodules+notgz-1.1 ii php7.0-cli [php-cli] > 7.0.33-0+deb9u3 > ii php7.0-intl [php-intl] 7.0.33-0+deb9u3 > ii php7.0-json [php-json] 7.0.33-0+deb9u3 > ii php7.3-cli [php-cli]7.3.4-2 > ii php7.3-intl [php-intl] 7.3.4-2 > ii php7.3-json [php-json] 7.3.4-2 > ii roundcube-sqlite3 1.3.8+dfsg.1-2 > ii ucf 3.0038+nmu1 > > Versions of packages roundcube-core recommends: > ii lighttpd [httpd-cgi] 1.4.53-4 > pn php-gd > pn php-pspell > ii spawn-fcgi1.6.4-2 > > Versions of packages roundcube-core suggests: > pn php-crypt-gpg > pn php-net-ldap2 > pn php-net-ldap3 > pn roundcube-plugins > > -- debconf information excluded > > ___ > Pkg-roundcube-maintainers mailing list > pkg-roundcube-maintain...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-roundcube-maint > ainers signature.asc Description: This is a digitally signed message part.
Bug#931909: [Pkg-roundcube-maintainers] Bug#931909: Typo: spellshecking
Hey, > I just noticed a typo in the word spellchecker (:-)) in > /etc/roundcube/config.inc.php. > > s/spellshecking/spellchecking/ This is an upstream bug, so please report this bug in upstream bug tracker: https://github.com/roundcube/roundcubemail/issues and report back the issue number, if you created a upstream bug. hefee signature.asc Description: This is a digitally signed message part.
Bug#847312: [Pkg-roundcube-maintainers] Bug#847312: Bug#847312: Bug#847312: roundcube: maintainer address bounces
Hey, the maintainer address changed to pkg-roundcube-maintainers@alioth- lists.debian.net and that should fix this issue. hefee -- On Freitag, 16. Dezember 2016 13:07:44 CET Sandro Knauß wrote: > Hey, > > I tried to reach toots on 8.Dec 2016 first time, but do not get any answer. > So far i searched a little bit in the Debian db and saw that toots is > marked as retired. > ad...@alioth.debian.org please add hefee@d.o and bernat@d.o as new Admins or > give us an password for the lists: > Pkg-roundcube-maintainers > Pkg-roundcube-devel > > You can verify that Vincent Bernat and Sandro Knauß are Admins of the pkg- > roundcube. > > Best Regards, > > sandro > > PS: I've currently issues sending mails from hefee@d.o, that's why I use > b...@sandroknauss.de and my GPG-Key for b...@sandroknauss.de is the same > than for hefee@d.o > > -- > > Am Mittwoch, 7. Dezember 2016, 13:28:52 CET schrieb Sandro Knauß: > > Hey, > > > > I've wrote the admin of the list a mail with the concerns, than we can > > change the settings of the list. > > > > Btw. also someone from backports team also couldn't wrote to the list. > > > > Best Regards, > > > > sandro > > > > > ❦ 7 décembre 2016 09:52 +0100, Chris Lamb : > > > > I tried to send an email to this package address, and I got: > > > >Is being held until the list moderator can review it for approval. > > > > > > > > The reason it is being held: > > > > Post by non-member to a members-only list > > > > > > > > As per Policy §3.3: “The email address given in the ‘Maintainer’ > > > > control > > > > field must accept mail from those role accounts in Debian used to send > > > > automated mails regarding the package. This includes non-spam mail > > > > from > > > > the bug-tracking system, […].” > > > > > > Well, this is the case. The BTS is able to post in the mailing > > > list. And many other people seem to be able to post to it. I don't have > > > access to the administration interface of this mailing list, so I can't > > > check what are the rules exactly. I know there is some level of > > > filtering since I receive daily reminders for spam (but I can't process > > > them, and I don't want to either). signature.asc Description: This is a digitally signed message part.
Bug#946405: nextcloud-desktop: Nextcloud desktop client crash when trying to enter login/password
Control: severity -1 important Control: reassign -1 libqt5webenginewidgets5 5.12.5+dfsg-3+b1 Control: affects -1 nextcloud-desktop As this is looks like that it is only nvidia specific, I reassign to important. It is properly a bug inside Qt stack so reassign to Qt package. hefee -- On Montag, 9. Dezember 2019 23:33:52 CET Bernhard Übelacker wrote: > Hello Ludovic, > I tried to collect some more information from your crash dump. > With debug symbols this backtrace should look like below. > > I guess you are running a nvidia graphics card > with the nouveau drivers? > > As a workaround it may work if you start the client > from a terminal by following: > > export LIBGL_ALWAYS_SOFTWARE=1 > nextcloud > > Or maybe this: > > export QT_XCB_FORCE_SOFTWARE_OPENGL=1 > nextcloud > > > Maybe you can confirm my findings, and forward the output of > following commands to this bug: > > lspci | grep VGA > glxinfo | grep -i -E "GLX_MESA_query_renderer.:" -A5 > > > Kind regards, > Bernhard > > > > From submitter | > Reconstructed #0 0x7fe16d9b6bde | > 0x7f1811853bde > #1 0x7fe16d9b6cf0 | > 0x7f1811853cf0 namespace)::StackDumpSignalHandler(int, siginfo_t*, void*) [clone > .part.77]+219> #2 0x7fe16d9b7327 | > 0x7f1811854327 namespace)::StackDumpSignalHandler(int, siginfo_t*, void*)+130> #3 > 0x7fe166ea4840 | 0x7f180ad41840 > <__restore_rt+0>: mov$0xf,%rax #4 0x7fe152142a8c > | 0x7f17f754ca8c in list_del at ../src/util/list.h:91 > #5 0x7fe152142c87 | > 0x7f17f754cc87 in nouveau_fence_update at > ../src/gallium/drivers/nouveau/nouveau_fence.c:128 #6 0x7fe152142f83 > | 0x7f17f754cf83 in > nouveau_fence_wait at ../src/gallium/drivers/nouveau/nouveau_fence.c:219 #7 > 0x7fe1523cf490 | 0x7f17f77d9490 > in st_finish (st=st@entry=0x562393326c90) at > ../src/mesa/state_tracker/st_cb_flush.c:69 #8 0x7fe1523cf4e0 > | 0x7f17f77d94e0 in st_glFinish (ctx= out>) at ../src/mesa/state_tracker/st_cb_flush.c:104 #9 0x7fe166a5f156 > | 0x7f180a8fc156 in > QQuickWidgetPrivate::render (this=0x562392ccb0b0, needsSync= out>) at qquickwidget.cpp:295 #10 0x7fe166a5f2b6 >| 0x7f180a8fc2b6 in QQuickWidgetPrivate::renderSceneGraph > (this=0x562392ccb0b0) at qquickwidget.cpp:339 #11 0x7fe1675e509b > QObject::event() | 0x7f180b48209b in > QObject::event (this=this@entry=0x5623930a2130, e=e@entry=0x7ffcf1848bb0) > at kernel/qobject.cpp:1232 #12 0x7fe167f7496b QWidget::event() > | 0x7f180be1196b in QWidget::event > (this=this@entry=0x5623930a2130, event=event@entry=0x7ffcf1848bb0) at > kernel/qwidget.cpp:9353 #13 0x7fe166a62e5d QQuickWidget::event() > | 0x7f180a8ffe5d in QQuickWidget::event (this=0x5623930a2130, > e=0x7ffcf1848bb0) at qquickwidget.cpp:1525 #14 0x7fe17207cb50 > | 0x7f1815f19b50 in > QtWebEngineCore::RenderWidgetHostViewQtDelegateWidget::event(QEvent*) () > from /lib/x86_64-linux-gnu/libQt5WebEngineWidgets.so.5 #15 0x7fe167f364c1 > QApplicationPrivate::notify_helper() | 0x7f180bdd34c1 in > QApplicationPrivate::notify_helper (this=this@entry=0x562392919dd0, > receiver=receiver@entry=0x5623930a2130, e=e@entry=0x7ffcf1848bb0) at > kernel/qapplication.cpp:3726 #16 0x7fe167f3d970 QApplication::notify() > | 0x7f180bdda970 in QApplication::notify > (this=0x7ffcf1848ef0, receiver=0x5623930a2130, e=0x7ffcf1848bb0) at > kernel/qapplication.cpp:3485 #17 0x7fe1675bb4f9 > QCoreApplication::notifyInternal2() | 0x7f180b4584f9 in > QCoreApplication::notifyInternal2 (receiver=0x5623930a2130, > event=event@entry=0x7ffcf1848bb0) at > ../../include/QtCore/5.11.3/QtCore/private/../../../../../src/corelib/threa > d/qthread_p.h:307 > | 0x7f180b4a8b > | a8 in > | QCoreApplicatio > | n::sendEvent > | (event=0x7ffcf1 > | 848bb0, > | receiver= | ized out>) at > | ../../include/Q > | tCore/../../src/ > | corelib/kernel/q >
Bug#946365: kmail becomes unresponsive with active preview pane on wayland-plasma
Control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=414955
Thanks for forwarding to upstream. But you have to send this mail to the bug
report to the 946...@bugs.debian.org address not to me - I'm not the BTS ;D
Forwarding your mail to BTS.
hefee
On Sonntag, 8. Dezember 2019 17:06:49 CET Silvério Santos wrote:
> Control: Forwarded -1 https://bugs.kde.org/show_bug.cgi?id=414955[1]
> Done.
>
> Am Sonntag, 8. Dezember 2019, 12:08:46 CET schrieben Sie:
> > Hey,
> >
> > Currently a next KDE PIM version is hitting testing, so please give the
> > new
> > version (19.08.3) a try and if the bug is not fixed report it upstream:
> > https://bugs.kde.org
> >
> > Please also leave a comment here at this bugreport with the upstream bug,
> > so we are able to track the upstream bug status. To do this properly add
> > a line with:
> > Control: Forwarded -1 {url}
> >
> > at the beginning of your response, than BTS (Debian Bugtracker) will do
> > its
> > magic.
> >
> > hefee
>
>
> [1] https://bugs.kde.org/show_bug.cgi?id=414955
signature.asc
Description: This is a digitally signed message part.
Bug#946365: kmail becomes unresponsive with active preview pane on wayland-plasma
Control: reassign -1 libkf5webengineviewer5abi1 4:18.08.3-5
Control: affects -1 kmail
Hey,
Currently a next KDE PIM version is hitting testing, so please give the new
version (19.08.3) a try and if the bug is not fixed report it upstream:
https://bugs.kde.org
Please also leave a comment here at this bugreport with the upstream bug, so
we are able to track the upstream bug status. To do this properly add a line
with:
Control: Forwarded -1 {url}
at the beginning of your response, than BTS (Debian Bugtracker) will do its
magic.
hefee
--
On Sonntag, 8. Dezember 2019 00:05:25 CET Silvério Santos wrote:
> Package: kmail
> Version: 4:18.08.3-4
> Severity: important
>
> Dear Maintainer,
>
> Started kmail on wayland-plasma with active preview pane. The preview stays
> black at the beginning. When e.g. hovering with the mouse over the preview,
> clicking on a different email or changing the folder the whole kmail
> software stops reacting and the title bar shows an unresponsive
> notification. No crash notification.
>
> When not interacting with the enabled preview pane the software stays
> responsive, even the settings can be reached to disable preview, which makes
> kmail work fine. EMail content can then be viewed in separately opened
> windows by doubleclicking them. Disabling HTML preference does not help.
>
> This problem does not happen with the preview pane disabled and in either
> configuration on X-Window.
>
> Running Debian testing, KMail 18.08.3-4
>
>
>
>
> -- System Information:
> Debian Release: bullseye/sid
> APT prefers testing
> APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 5.3.0-2-amd64 (SMP w/4 CPU cores)
> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de
> (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages kmail depends on:
> ii akonadi-server
> 4:18.08.3-11 ii kdepim-runtime
>4:18.08.3-6 ii kio
> 5.62.1-2+b1 ii libc6
>2.29-3 ii libgcc1
> 1:9.2.1-21 ii libgpgmepp6
> 1.13.1-1 ii libkf5akonadiagentbase5 [libkf5akonadiagentbase5-18.08]
> 4:18.08.3-11 ii libkf5akonadicontact5 [libkf5akonadicontact5-18.08]
>4:18.08.3-4 ii libkf5akonadicore5abi2 [libkf5akonadicore5-18.08]
> 4:18.08.3-11 ii libkf5akonadimime5 [libkf5akonadimime5-18.08]
> 4:18.08.3-3 ii libkf5akonadisearch-bin
> 4:18.08.3-3 ii libkf5akonadisearch-plugins
> 4:18.08.3-3 ii libkf5akonadisearchdebug5
> [libkf5akonadisearchdebug5-18.08] 4:18.08.3-3 ii libkf5akonadisearchpim5
> [libkf5akonadisearchpim5-18.08] 4:18.08.3-3 ii
> libkf5akonadiwidgets5abi1 [libkf5akonadiwidgets5-18.08] 4:18.08.3-11
> ii libkf5bookmarks5
> 5.62.0-1+b1 ii libkf5calendarcore5abi2 [libkf5calendarcore5-18.08]
> 4:18.08.3-3 ii libkf5calendarutils5 [libkf5calendarutils5-18.08]
> 4:18.08.3-4 ii libkf5codecs5
> 5.62.0-1 ii libkf5completion5
> 5.62.0-1+b1 ii libkf5configcore5
>5.62.0-1+b1 ii libkf5configgui5
> 5.62.0-1+b1 ii libkf5configwidgets5
>5.62.0-1+b1 ii libkf5contacts5 [libkf5contacts5-18.08]
> 4:18.08.3-4 ii libkf5coreaddons5
>5.62.0-1 ii libkf5crash5
> 5.62.0-1+b1 ii libkf5dbusaddons5
> 5.62.0-1 ii libkf5followupreminder5
> [libkf5followupreminder5-18.08] 4:18.08.3-4 ii
> libkf5grantleetheme-plugins 18.08.3-3 ii
> libkf5gravatar5abi2 [libkf5gravatar5-18.08] 4:18.08.3-3
> ii libkf5guiaddons5 5.62.0-2
> ii libkf5i18n5 5.62.0-1
> ii libkf5iconthemes5
> 5.62.0-1+b1 ii libkf5identitymanagement5 [libkf5identitymanagement5-18.08]
> 18.08.3-4 ii libkf5itemmodels5
> 5.62.0-1 ii libkf5itemviews5
> 5.62.0-1+b1 ii libkf5jobwidgets5
>5.62.0-1+b1 ii libkf5kcmutils5
> 5.62.0-1+b1 ii
Bug#946141: [akonadi-backend-sqlite] Failed to commit transaction for database update
Hey, so youupgrading Akonadi, what version you had before? To use akonadiserver directly is not recommended. Please use akonadictl and enable debugging via .config/QtProject/qtlogging.ini. And one line is not in English: > org.kde.pim.akonadiserver: Creating socket directory with name "" > failed: Выполнено can you please translate this, or un with LANG=C [cmd], so everthing is in English. hefee -- > Akonadi failed to start: > > $ akonadiserver --start-without-control --verbose > org.kde.pim.akonadiserver: Starting up the Akonadi Server... > QSqlDatabasePrivate::addDatabase: duplicate connection name > 'initConnection', old connection removed. > org.kde.pim.akonadiserver: sqlite version is "3.30.1" > org.kde.pim.akonadiserver: sqlite journal mode is "wal" > org.kde.pim.akonadiprivate: StandardDirs::saveDir: failed to create > directory ' "/run/user/1000/akonadi" ' > QDir::mkpath: Empty or null file name > org.kde.pim.akonadiserver: Creating socket directory with name "" > failed: Выполнено > org.kde.pim.akonadiserver: Could not create socket directory for Akonadi. > org.kde.pim.akonadiserver: Database > "/home/alexs/.local/share/akonadi/akonadi.db" opened using driver "QSQLITE3" > org.kde.pim.akonadiserver: Running DB initializer > org.kde.pim.akonadiserver: checking table "SchemaVersionTable" > org.kde.pim.akonadiserver: checking table "ResourceTable" > org.kde.pim.akonadiserver: checking table "CollectionTable" > org.kde.pim.akonadiserver: checking table "MimeTypeTable" > org.kde.pim.akonadiserver: checking table "PimItemTable" > org.kde.pim.akonadiserver: checking table "FlagTable" > org.kde.pim.akonadiserver: checking table "PartTypeTable" > org.kde.pim.akonadiserver: checking table "PartTable" > org.kde.pim.akonadiserver: checking table "CollectionAttributeTable" > org.kde.pim.akonadiserver: checking table "TagTypeTable" > org.kde.pim.akonadiserver: checking table "TagTable" > org.kde.pim.akonadiserver: checking table "TagAttributeTable" > org.kde.pim.akonadiserver: checking table > "TagRemoteIdResourceRelationTable" > org.kde.pim.akonadiserver: checking table "RelationTypeTable" > org.kde.pim.akonadiserver: checking table "RelationTable" > org.kde.pim.akonadiserver: checking table "PimItemFlagRelation" > org.kde.pim.akonadiserver: checking table "PimItemTagRelation" > org.kde.pim.akonadiserver: checking table "CollectionMimeTypeRelation" > org.kde.pim.akonadiserver: checking table "CollectionPimItemRelation" > org.kde.pim.akonadiserver: DB initializer done > org.kde.pim.akonadiserver: skipping update 2 > org.kde.pim.akonadiserver: skipping update 3 > org.kde.pim.akonadiserver: skipping update 4 > org.kde.pim.akonadiserver: skipping update 8 > org.kde.pim.akonadiserver: skipping update 10 > org.kde.pim.akonadiserver: skipping update 12 > org.kde.pim.akonadiserver: skipping update 13 > org.kde.pim.akonadiserver: skipping update 14 > org.kde.pim.akonadiserver: skipping update 15 > org.kde.pim.akonadiserver: skipping update 16 > org.kde.pim.akonadiserver: skipping update 17 > org.kde.pim.akonadiserver: skipping update 18 > org.kde.pim.akonadiserver: skipping update 19 > org.kde.pim.akonadiserver: skipping update 20 > org.kde.pim.akonadiserver: skipping update 21 > org.kde.pim.akonadiserver: skipping update 22 > org.kde.pim.akonadiserver: skipping update 23 > org.kde.pim.akonadiserver: skipping update 24 > org.kde.pim.akonadiserver: skipping update 25 > org.kde.pim.akonadiserver: skipping update 26 > org.kde.pim.akonadiserver: skipping update 28 > org.kde.pim.akonadiserver: skipping update 30 > org.kde.pim.akonadiserver: skipping update 31 > org.kde.pim.akonadiserver: skipping update 33 > org.kde.pim.akonadiserver: skipping update 35 > org.kde.pim.akonadiserver: DbUpdater: update to version: 36 mandatory: true > org.kde.pim.akonadiserver: Starting database update to version 36 > org.kde.pim.akonadiserver: Updating foreign keys in table "CollectionTable" > org.kde.pim.akonadiserver: Creating table CollectionTable_new with > foreign keys > org.kde.pim.akonadiserver: Copying values from CollectionTable to > CollectionTable_new (this may take a very long of time...) > org.kde.pim.akonadiserver: SQL error when updating table CollectionTable > org.kde.pim.akonadiserver: Query: CREATE TABLE CollectionTable_new (id > INTEGER PRIMARY KEY AUTOINCREMENT NOT NULL, remoteId TEXT, > remoteRevision TEXT, name TEXT NOT NULL, parentId BIGINT, resourceId > BIGINT NOT NULL, enabled BOOL NOT NULL DEFAULT 1, syncPref TINYINT > DEFAULT 2, displayPref TINYINT DEFAULT 2, indexPref TINYINT DEFAULT 2, > cachePolicyInherit BOOL NOT NULL DEFAULT 1, cachePolicyCheckInterval > INTEGER NOT NULL DEFAULT -1, cachePolicyCacheTimeout INTEGER NOT NULL > DEFAULT -1, cachePolicySyncOnDemand BOOL NOT NULL DEFAULT 0, > cachePolicyLocalParts TEXT, queryString TEXT, queryAttributes TEXT, > queryCollections TEXT, isVirtual BOOL DEFAULT 0, CONSTRAINT > CollectionTable_newparentId_Collectionid_fk FOREIGN
Bug#946199: akonadi-backend-postgresql: akonadictl fails to start with postgresql backend
control: severity -1 important Hey, I'm lowering the severity, as this package is not unfit for testing. It was used for serveral moths in experimental, where people used also Postgresql backend without any issues. hefee -- On Freitag, 6. Dezember 2019 12:57:03 CET Diederik de Haas wrote: > On donderdag 5 december 2019 15:34:37 CET Sandro Knauß wrote: > > do you have apparmor enabled? Maybe the Apparmor profile does not match > > anymore. Can you give it a try with aa-disable postgresql_akonadi? > > I have akonadi-backend-postgresql and apparmor enabled and it is working for > me. I only have PostgreSQL 12 though. > https://lists.debian.org/debian-kde/2019/11/msg0.html shows the way I > upgraded to PSQL 12 (and purged PSQL 11) > > If you have both, but didn't upgrade your cluster (ie transfer your akonadi > database to PSQL 12) and rebooted, then I think PSQL 12 uses the default > PSQL port. If you didn't change your config, then akonadi is asking PSQL 12 > for its data, but it can't find it. > That could be an explanation why it isn't working for Vincent-Xavier. signature.asc Description: This is a digitally signed message part.
Bug#946199: akonadi-backend-postgresql: akonadictl fails to start with postgresql backend
Hey, do you have apparmor enabled? Maybe the Apparmor profile does not match anymore. Can you give it a try with aa-disable postgresql_akonadi? hefee -- >* What led up to the situation? >akonadi-backend-postgresql upgrade > >* What exactly did you do (or not do) that was effective (or > ineffective)? > >restart akonadictl, withou any effect, restart postgresql, on different >system with version 11 and 12. Postgresql connection is still available > >* What was the outcome of this action? >None >* What outcome did you expect instead? >Akonadi working > > > > -- System Information: > Debian Release: bullseye/sid > APT prefers unstable-debug > APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, > 'stable-updates'), (500, 'stable-debug'), (500, 'buster-fasttrack'), (500, > 'unstable'), (500, 'testing'), (500, 'stable'), (100, 'buster-backports') > Architecture: amd64 (x86_64) > > Kernel: Linux 5.3.0-2-amd64 (SMP w/4 CPU cores) > Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr > (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages akonadi-backend-postgresql depends on: > ii libqt5sql5-psql 5.12.5+dfsg-2 > > Versions of packages akonadi-backend-postgresql recommends: > ii akonadi-server 4:19.08.3-1 > ii postgresql 12+210 > > akonadi-backend-postgresql suggests no packages. > > -- no debconf information signature.asc Description: This is a digitally signed message part.
Bug#945619: transition: kdepim 19.08
Hey Paul, from my point of view it seems that the transition is finished. every reveres dependency has been built for sid. Now we only need to wait till it migrates to bullseye. hefee -- On Samstag, 30. November 2019 21:34:52 CET Paul Gevers wrote: > Control: tags -1 confirmed > > Hi Sandro, > > On 30-11-2019 00:08, Sandro Knauß wrote: > > I prepared a patch for zanshin [!1]. That means I could now built every > > > > reverse dependency with KDEPIM 19.08 and nothing is stopping me to start > > with the transition (except the ACK from your side). > > Please, go ahead. > > Paul signature.asc Description: This is a digitally signed message part.
Bug#945161: accountwizard: Broken dependencies (KLineEdit)
Hey, I can't reproduce your issue, so I need your input. First can try to replace KLineEdit with QLineEdit the file (you need root permission to do that): /usr/share/akonadi/accountwizard/kolab/kolabwizard.ui Does this already fix the issue? Is kdepim-runtime installed and/or libkf5completion5? hefee -- > The accountwizard tries to instantiate widgets that are not installed when I > try to setup a Kolab client, so this seems to be a dependency issue. The > output from the program is: > > $ accountwizard > org.kde.knewstuff.core: Using a deprecated location for the knsrc file > "accountwizard.knsrc" - please contact the author of the software which > provides th "QFormBuilder was unable to create a widget of the class > 'KLineEdit'." "Empty widget item in QFormLayout 'formLayout'." > "QFormBuilder was unable to create a widget of the class 'KLineEdit'." > "Empty widget item in QFormLayout 'formLayout'." > "QFormBuilder was unable to create a custom widget of the class > 'KPasswordLineEdit'; defaulting to base class 'QWidget'." Kross: "Error > error=TypeError: Result of expression 'page.widget().nameEdit' [undefined] > is not an object. lineno=27 trace=\n() at /usr/share/akona > > This means that I cannot enter the name, nor the password, due to the > widgets not being properly instantiated. > > > -- System Information: > Debian Release: bullseye/sid > APT prefers testing > APT policy: (600, 'testing'), (500, 'unstable') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 5.2.0-3-amd64 (SMP w/8 CPU cores) > Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE > Locale: LANG=en_US.UTF-8, LC_CTYPE=C.UTF-8 (charmap=locale: Cannot set > LC_ALL to default locale: No such file or directory UTF-8), > LANGUAGE=en_US:en (charmap=locale: Cannot set LC_ALL to default locale: No > such file or directory UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages accountwizard depends on: > ii kio 5.62.1-2 > ii libc6 2.29-3 > ii libgcc1 1:9.2.1-19 > ii libgpgmepp6 1.13.1-1 > ii libkf5akonadicore5abi2 [libkf5akonadicore5-18.08] > 4:18.08.3-11 ii libkf5akonadimime5 [libkf5akonadimime5-18.08] >4:18.08.3-3 ii libkf5akonadiwidgets5abi1 [libkf5akonadiwidgets5-18.08] > 4:18.08.3-11 ii libkf5codecs5 > 5.62.0-1 ii libkf5configcore5 >5.62.0-1 ii libkf5coreaddons5 > 5.62.0-1 ii libkf5crash5 > 5.62.0-1 ii libkf5dbusaddons5 > 5.62.0-1 ii libkf5i18n5 >5.62.0-1 ii libkf5identitymanagement5 [libkf5identitymanagement5-18.08] > 18.08.3-4 ii libkf5itemviews5 > 5.62.0-1 ii libkf5kcmutils5 > 5.62.0-1 ii libkf5kiocore5 > 5.62.1-2 ii libkf5krosscore5 > 5.62.0-1 ii libkf5ldap5abi1 [libkf5ldap5-18.08] > 18.08.3-3 ii libkf5libkdepim5 [libkf5libkdepim5-18.08] > 4:18.08.3-4 ii libkf5libkleo5 [libkf5libkleo5-18.08] > 4:18.08.3-4 ii libkf5mailtransport5 [libkf5mailtransport5-18.08] > 18.08.3-4 ii libkf5mailtransportakonadi5 > [libkf5mailtransportakonadi5-18. 18.08.3-4 ii libkf5mime5abi1 > [libkf5mime5-18.08] 18.08.3-3 ii > libkf5newstuffcore5 5.62.0-1 ii > libkf5notifications5 5.62.0-1 ii > libkf5pimcommon5abi2 [libkf5pimcommon5-18.08] 4:18.08.3-4 > ii libkf5wallet-bin 5.62.0-1 > ii libkf5wallet5 5.62.0-1 > ii libkf5widgetsaddons5 5.62.0-1 > ii libkf5xmlgui5 > 5.62.0-1+b1 ii libqgpgme7 > 1.13.1-1 ii libqt5core5a > 5.12.5+dfsg-2 ii libqt5dbus5 > 5.12.5+dfsg-2 ii libqt5gui5 > 5.12.5+dfsg-2 ii libqt5widgets5 > 5.12.5+dfsg-2 ii libqt5xml5 > 5.12.5+dfsg-2 ii libstdc++6
Bug#945619: transition: kdepim 19.08
Hey Paul, We need another binNMU as kitinerary it was built too early on mips64el: nmu kitinerary_19.08.3-1 . mips64el . unstable . -m "rebuild for KDEPIM 19.08." --extra-depends "libkpimpkpass-dev (>> 19.08.3-1~)" hefee signature.asc Description: This is a digitally signed message part.
Bug#945619: transition: kdepim 19.08
Hey Paul, As now the first archs have built everything the reverse dependencies can be triggered: nmu kio-gdrive_1.2.7-1 . ANY . unstable . -m "rebuild for KDEPIM 19.08." --extra-depends "libkpimgapi-dev (>> 19.08.3-1~)" nmu kjots_4:5.0.2-1 . ANY . unstable . -m "rebuild for KDEPIM 19.08." --extra-depends "libkf5akonadi-dev (>> 4:19.08.3-1~), libkf5kontactinterface-dev (>> 19.08.3-1~), libkf5akonadinotes-dev (>> 4:19.08.3-1~), libkf5mime-dev (>> 19.08.3-1~), libkf5pimtextedit-dev (>> 19.08.3-1~)" nmu kmymoney_5.0.7-1 . ANY . unstable . -m "rebuild for KDEPIM 19.08." --extra-depends "libkf5contacts-dev (>> 4:19.08.3-1~), libkf5akonadi-dev (>> 4:19.08.3-1~), libkf5identitymanagement-dev (>> 19.08.3-1~)" nmu kraft_0.82-1 . ANY . unstable . -m "rebuild for KDEPIM 19.08." --extra-depends "libkf5contacts-dev (>> 4:19.08.3-1~), libkf5akonadi-dev (>> 4:19.08.3-1~), libkf5akonadicontact-dev (>> 4:19.08.3-1~)" Btw. I havn't found any documentation about this --extra-depends flag. I only could guess the syntax by examples I found. Maybe the documentation needs to be updated: https://release.debian.org/wanna-build.html hefee -- On Samstag, 30. November 2019 21:34:52 CET Paul Gevers wrote: > Control: tags -1 confirmed > > Hi Sandro, > > On 30-11-2019 00:08, Sandro Knauß wrote: > > I prepared a patch for zanshin [!1]. That means I could now built every > > > > reverse dependency with KDEPIM 19.08 and nothing is stopping me to start > > with the transition (except the ACK from your side). > > Please, go ahead. > > Paul signature.asc Description: This is a digitally signed message part.
Bug#945836: zanshin does not built with new KDEPIM 19.08
Control: severity -1 serious Hey, the KDEPIM 19.08 transition [1] got accepted. That's why I raise the severity to serious. hefee [1] https://release.debian.org/transitions/html/kdepim-19.08.html -- On Freitag, 29. November 2019 15:54:18 CET Sandro Knauß wrote: > Package: zanshin > Version: 0.5.0-2+b1 > Severity: normal > Tags: patch > Control: block 945619 by -1 > > Hey, > > zanshin doesn't built with KDEPIM 19.08 (currently waiting in experimental). > Mostly because KCalCore got a cleanup and API change in order to move to > KDE Frameworks. I requested a merge request (!1) on salsa to fix that. > > hefee > > !1: https://salsa.debian.org/qt-kde-team/extras/zanshin/merge_requests/1 > > > -- System Information: > Debian Release: bullseye/sid > APT prefers unstable-debug > APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, > 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, > 'experimental') Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 5.3.0-2-amd64 (SMP w/4 CPU cores) > Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), > LANGUAGE=en_US (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages zanshin depends on: > ii kio 5.62.1-2 > ii libc62.29-3 > ii libgcc1 1:9.2.1-19 > pn libkf5akonadicalendar5 > pn libkf5akonadicalendar5-18.08 > ii libkf5akonadicalendar5abi1 4:19.08.2-1~ > ii libkf5akonadicontact54:19.08.2-1~ > pn libkf5akonadicontact5-18.08 > pn libkf5akonadicore5 > pn libkf5akonadicore5-18.08 > ii libkf5akonadicore5abi2 4:19.08.2-1~ > ii libkf5akonadinotes5 4:19.08.2-1~ > pn libkf5akonadinotes5-18.08 > ii libkf5akonadisearchpim5 4:19.08.2-1~ > pn libkf5akonadisearchpim5-18.08 > pn libkf5akonadiwidgets5 > pn libkf5akonadiwidgets5-18.08 > ii libkf5akonadiwidgets5abi14:19.08.2-1~ > pn libkf5calendarcore5 > pn libkf5calendarcore5-18.08 > ii libkf5calendarcore5abi2 4:19.08.2-1~ > ii libkf5codecs55.62.0-1 > ii libkf5completion55.62.0-1 > ii libkf5configcore55.62.0-1 > ii libkf5configgui5 5.62.0-1 > ii libkf5configwidgets5 5.62.0-1 > ii libkf5contacts5 4:19.08.2-1~ > pn libkf5contacts5-18.08 > ii libkf5coreaddons55.62.0-1 > ii libkf5i18n5 5.62.0-1 > ii libkf5identitymanagement519.08.2-1~ > pn libkf5identitymanagement5-18.08 > ii libkf5itemmodels55.62.0-1 > ii libkf5itemviews5 5.62.0-1 > ii libkf5jobwidgets55.62.0-1 > ii libkf5kdelibs4support5 5.62.0-2 > ii libkf5kiocore5 5.62.1-2 > ii libkf5kontactinterface5 19.08.2-1~ > pn libkf5kontactinterface5-18.08 > pn libkf5ldap5 > pn libkf5ldap5-18.08 > ii libkf5ldap5abi1 19.08.2-1~ > pn libkf5mime5 > pn libkf5mime5-18.08 > ii libkf5mime5abi1 19.08.2-1~ > ii libkf5parts5 5.62.0-1 > ii libkf5runner55.62.0-1 > ii libkf5wallet-bin 5.62.0-1 > ii libkf5wallet55.62.0-1 > ii libkf5widgetsaddons5 5.62.0-1 > ii libkf5windowsystem5 5.62.0-2 > ii libkf5xmlgui55.62.0-1+b1 > ii libqt5core5a 5.12.5+dfsg-2 > ii libqt5dbus5 5.12.5+dfsg-2 > ii libqt5gui5 5.12.5+dfsg-2 > ii libqt5network5 5.12.5+dfsg-2 > ii libqt5widgets5 5.12.5+dfsg-2 > ii libstdc++6 9.2.1-19 > > zanshin recommends no packages. > > zanshin suggests no packages. signature.asc Description: This is a digitally signed message part.
Bug#945863: python-caja: Build python3 bindings for Caja components
Source: python-caja Version: 1.22.1-2 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Control: block 945674 by -1 Control: block 937628 by -1 I can not replace python-caja with a python3 package, as this package, don't provide a Python3 binding. Vlad mentioned in #937628 that 1.22.0 is compatible for Python2 and Python3. So please built a PYthon3 binding, so reverse dependencies can switch to the Python3 binding. hefee -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.3.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#945619: transition: kdepim 19.08
Hey, I prepared a patch for zanshin [!1]. That means I could now built every reverse dependency with KDEPIM 19.08 and nothing is stopping me to start with the transition (except the ACK from your side). hefee !1: https://salsa.debian.org/qt-kde-team/extras/zanshin/merge_requests/1 signature.asc Description: This is a digitally signed message part.
Bug#945836: zanshin does not built with new KDEPIM 19.08
Package: zanshin Version: 0.5.0-2+b1 Severity: normal Tags: patch Control: block 945619 by -1 Hey, zanshin doesn't built with KDEPIM 19.08 (currently waiting in experimental). Mostly because KCalCore got a cleanup and API change in order to move to KDE Frameworks. I requested a merge request (!1) on salsa to fix that. hefee !1: https://salsa.debian.org/qt-kde-team/extras/zanshin/merge_requests/1 -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.3.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages zanshin depends on: ii kio 5.62.1-2 ii libc62.29-3 ii libgcc1 1:9.2.1-19 pn libkf5akonadicalendar5 pn libkf5akonadicalendar5-18.08 ii libkf5akonadicalendar5abi1 4:19.08.2-1~ ii libkf5akonadicontact54:19.08.2-1~ pn libkf5akonadicontact5-18.08 pn libkf5akonadicore5 pn libkf5akonadicore5-18.08 ii libkf5akonadicore5abi2 4:19.08.2-1~ ii libkf5akonadinotes5 4:19.08.2-1~ pn libkf5akonadinotes5-18.08 ii libkf5akonadisearchpim5 4:19.08.2-1~ pn libkf5akonadisearchpim5-18.08 pn libkf5akonadiwidgets5 pn libkf5akonadiwidgets5-18.08 ii libkf5akonadiwidgets5abi14:19.08.2-1~ pn libkf5calendarcore5 pn libkf5calendarcore5-18.08 ii libkf5calendarcore5abi2 4:19.08.2-1~ ii libkf5codecs55.62.0-1 ii libkf5completion55.62.0-1 ii libkf5configcore55.62.0-1 ii libkf5configgui5 5.62.0-1 ii libkf5configwidgets5 5.62.0-1 ii libkf5contacts5 4:19.08.2-1~ pn libkf5contacts5-18.08 ii libkf5coreaddons55.62.0-1 ii libkf5i18n5 5.62.0-1 ii libkf5identitymanagement519.08.2-1~ pn libkf5identitymanagement5-18.08 ii libkf5itemmodels55.62.0-1 ii libkf5itemviews5 5.62.0-1 ii libkf5jobwidgets55.62.0-1 ii libkf5kdelibs4support5 5.62.0-2 ii libkf5kiocore5 5.62.1-2 ii libkf5kontactinterface5 19.08.2-1~ pn libkf5kontactinterface5-18.08 pn libkf5ldap5 pn libkf5ldap5-18.08 ii libkf5ldap5abi1 19.08.2-1~ pn libkf5mime5 pn libkf5mime5-18.08 ii libkf5mime5abi1 19.08.2-1~ ii libkf5parts5 5.62.0-1 ii libkf5runner55.62.0-1 ii libkf5wallet-bin 5.62.0-1 ii libkf5wallet55.62.0-1 ii libkf5widgetsaddons5 5.62.0-1 ii libkf5windowsystem5 5.62.0-2 ii libkf5xmlgui55.62.0-1+b1 ii libqt5core5a 5.12.5+dfsg-2 ii libqt5dbus5 5.12.5+dfsg-2 ii libqt5gui5 5.12.5+dfsg-2 ii libqt5network5 5.12.5+dfsg-2 ii libqt5widgets5 5.12.5+dfsg-2 ii libstdc++6 9.2.1-19 zanshin recommends no packages. zanshin suggests no packages.
Bug#942415: Calligra and Akonadi
Hey pino,
> > Why this is not built and shipped and still we have the dependency?
>
> I do not see any akonadi dependency in the binary packages, can you
> please explain exactly what you see?
what I mean is, if it is only checked at buildtime but no binary package
depend on it, why it was added to Build-Depends in first place?
Why we do not ship the calligra_semanticitem_{contact,event} plugins?
> This is because the tracker for the transition is partially wrong:
> - it considers "affected" all the sources that only build-depend on PIM
> packages: while this is generally correct, it ought to check both the
> actual bad _and_ good runtime dependencies instead
You are totally right, the ben file is not that exact that it could be. But
first it is one of my first transition that I triggered, so I'm not that
familiar with the ben syntax.
> - the "good" check seems correctly checking for the "new library names"
> - the "bad" check is basically "everything that does not depend on
> depend on the new names"... which is wrong -- it ought to explicitly
> check for the _old_ names instead
the bad state is the hard one to describe.
bad state:
a package depend on libfoo5
good state:
a package depend on libfoo5 and libfoo-18.08
> - calligra is considered "bad"
> - libkf5sieve, kf5-messagelib, kmail, libkf5mailcommon, and kmail are
> considered "bad" in all the architectures where they are not actually
> built
> - maybe (although I'm not sure about this) also all the "?!" states
>
> Please fix the ben file for this transition, so its status can be
> checked properly.
Well the next kdepim transition is easier as bad is libfoo-18.08 and good is
libfoo-19.08.
hefee
signature.asc
Description: This is a digitally signed message part.
Bug#942415: transition: meta-kdepim
Hey, calligra is identified as fake candidate (for the moment) every reverse dependency is built correctly and it is nothing to do left expect for wait till kdepim will go to testing. Just for the record, for thise who are not familiar with the other red crosses: libkf5sieve, kf5-messagelib, kmail, libkf5mailcommon and kmail can only be built for 5 archs, that are supported by qtwebengine. blogilo is FTBFS for a long time #908869. feel free to ask, if you have anything. hefee signature.asc Description: This is a digitally signed message part.
Bug#942415: Calligra and Akonadi
Hey pino,
thanks for your last update of calligra! That at least makes it build again
*yeah* But for me it seems like, the whole Akonadi dependency isn't used at
all. So far my digging into calligra code:
Akoandi and CalCore, Contacts is only used for plugins/semanticitems/
{contact,event} but as far I scanned though the build log these two plugins
are not built at all. I only can see the
calligra_semanticitem_{contact,event}.mo but those files are explitly deleted
with the comment
"# Remove translations of stuff not shipped"
Why this is not built and shipped and still we have the dependency?
hefee
signature.asc
Description: This is a digitally signed message part.
Bug#944853: calligra: FTBFS with Qt 5.12
Source: calligra Version: 1:3.1.0+dfsg-5 Severity: normal Hey, calligra can't be build anmore within the sid enviornment. It fails with: /<>/sheets/plugins/calendar/CalendarToolWidget.cpp:47:39: error: incomplete type ‘QDate’ used in nested name specifier 47 | QDate first_day_in_month = QDate::currentDate(); see https://buildd.debian.org/status/fetch.php?pkg=calligra=amd64=1%3A3.1.0%2Bdfsg-5%2Bb2=1573859614=0 hefee -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.3.0-2-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#942415: transition: meta-kdepim
Hi Graham, As now the first archs have built everything the reverse dependencies can be triggered: nmu kio-gdrive_1.2.7-1 . ANY . unstable . -m "rebuild for virtual package based dependency management" dw kio-gdrive_1.2.7-1 . ANY . unstable . -m 'libkpimgapi-dev (>= 18.08.3-3)' nmu kjots_4:5.0.2-1 . ANY . unstable . -m "rebuild for virtual package based dependency management" dw kjots_4:5.0.2-1 . ANY . unstable . -m 'libkf5akonadinotes-dev (>= 4:18.08.3-2), libkf5mime-dev (>= 18.08.3-2), libkf5pimtextedit-dev (>= 18.08.3-2)' mnu kmymoney_5.0.7-1 . ANY . unstable . -m "rebuild for virtual package based dependency management" dw kmymoney_5.0.7-1 . ANY . unstable . -m 'libkf5akonadi-dev (>= 4:18.08.3-10), libkf5identitymanagement-dev (>= 18.08.3-3), libkf5contacts-dev (>= 4:18.08.3-3)' nmu calligra_1:3.1.0+dfsg-5 . ANY . unstable . -m "rebuild for virtual package based dependency management" dw calligra_1:3.1.0+dfsg-5 . ANY . unstable . -m 'libkf5akonadicontact-dev (>= 4:18.08.3-3)' nmu kraft_0.82-1 . ANY . unstable . -m "rebuild for virtual package based dependency management" dw kraft_0.82-1 . ANY . unstable . -m 'libkf5akonadicontact-dev (>= 4:18.08.3-3), libkf5contacts-dev (>= 4:18.08.3-3)' mnu zanshin_0.5.0-2 . ANY . unstable . -m "rebuild for virtual package based dependency management" dw zanshin_0.5.0-2 . ANY . unstable . -m 'libkf5akonadicontact-dev (>= 4:18.08.3-3), libkf5akonadisearch-dev (>= 4:18.08.3-2), libkf5identitymanagement-dev (>= 18.08.3-3), libkf5kontactinterface-dev (>= 18.08.3-2), libkf5ldap-dev (>= 18.08.3-2)' Regards hefee signature.asc Description: This is a digitally signed message part.
Bug#943760: akregator: Cannot copy text from akregator
Control: reassign -1 qtwebengine-opensource-src 5.11.3+dfsg-2 Control: severity -1 normal Control: affects -1 akregator Hey, I can't reproduce this. And this sound not really like an big issue, that's why I lowered the severity to normal. I expect, that this is mostly an issue within QtWebEngine, as akregator only using that for the internal web browser. What Desktop Environment you are using? I'm using KDE Plasma Desktop. Do you also have issues to copy text within other applications like kmail? hefee -- On Dienstag, 29. Oktober 2019 13:39:39 CET Leos Pohl wrote: > Package: akregator > Version: 4:18.08.3-2 > Severity: important > > Dear Maintainer, > When i try to copy selected text inside akregator, the text does > not get copied. I can use either ctrl+c or right-click mouse and click > copy. Then I try to paste it to e.g. a web browser, the clipboard is > either empty or its content is from some previous copy action in other > program. > > > -- System Information: > Debian Release: 10.1 > APT prefers stable-updates > APT policy: (500, 'stable-updates'), (500, 'stable-debug'), (500, > 'stable') Architecture: amd64 (x86_64) > > Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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 akregator depends on: > ii kinit5.54.0-1 > ii kio 5.54.1-1 > ii libc62.28-10 > ii libgcc1 1:8.3.0-6 > ii libkf5codecs55.54.0-1 > ii libkf5completion55.54.0-1 > ii libkf5configcore55.54.0-1+deb10u1 > ii libkf5configgui5 5.54.0-1+deb10u1 > ii libkf5configwidgets5 5.54.0-1 > ii libkf5coreaddons55.54.0-1 > ii libkf5crash5 5.54.0-1 > ii libkf5grantleetheme-plugins 18.08.3-1 > ii libkf5grantleetheme5 18.08.3-1 > ii libkf5i18n5 5.54.0-1 > ii libkf5iconthemes55.54.0-1 > ii libkf5jobwidgets55.54.0-1 > ii libkf5kcmutils5 5.54.0-1 > ii libkf5kiocore5 5.54.1-1 > ii libkf5kiogui55.54.1-1 > ii libkf5kiowidgets55.54.1-1 > ii libkf5kontactinterface5 18.08.3-1 > ii libkf5libkdepim-plugins 4:18.08.3-2 > ii libkf5libkdepim5 4:18.08.3-2 > ii libkf5messageviewer5abi1 4:18.08.3-2 > ii libkf5mimetreeparser5abi14:18.08.3-2 > ii libkf5notifications5 5.54.0-1 > ii libkf5notifyconfig5 5.54.0-1 > ii libkf5parts5 5.54.0-1 > ii libkf5pimcommon5abi2 4:18.08.3-2 > ii libkf5pimtextedit5abi2 18.08.3-1 > ii libkf5service-bin5.54.0-1 > ii libkf5service5 5.54.0-1 > ii libkf5syndication5abi1 18.08.3-1 > ii libkf5textwidgets5 5.54.0-1 > ii libkf5webengineviewer5abi1 4:18.08.3-2 > ii libkf5widgetsaddons5 5.54.0-1 > ii libkf5xmlgui55.54.0-1 > ii libqt5core5a 5.11.3+dfsg1-1 > ii libqt5dbus5 5.11.3+dfsg1-1 > ii libqt5gui5 5.11.3+dfsg1-1 > ii libqt5network5 5.11.3+dfsg1-1 > ii libqt5printsupport5 5.11.3+dfsg1-1 > ii libqt5webenginecore5 5.11.3+dfsg-2+b1 > ii libqt5webenginewidgets5 5.11.3+dfsg-2+b1 > ii libqt5widgets5 5.11.3+dfsg1-1 > ii libqt5xml5 5.11.3+dfsg1-1 > ii libstdc++6 8.3.0-6 > > akregator recommends no packages. > > akregator suggests no packages. > > -- no debconf information signature.asc Description: This is a digitally signed message part.
Bug#886428: Crashes on nouveau with mesa 17.3.1
Control: reassign -1 libkf5webengineviewer5abi1 4:18.08.3-2 Control: affects -1 kmail Hey, I think, that the issue is QtWebEngine and not kmail in itself. That's why I reassign to QtWebEngine. Russell Coker using a little bit different workaround to solve this issue: https://etbe.coker.com.au/2019/11/03/kmail-crashing-libgl/ Can someone reproduce the issue with testing or unstable, as there is Qt 5.12 and still the same kmail version than in stable? Regards, hefee -- On Sonntag, 3. November 2019 10:26:28 CET Dmitriy Istselemov wrote: > Package: kmail > Version: 4:18.08.3-1 > Followup-For: Bug #886428 > > Dear Maintainer, > The problem still exist. The workaround with setting the environment > QT_XCB_FORCE_SOFTWARE_OPENGL=1 works for me. > > Here is what is found in dmesg: > [ 71.515660] nouveau :01:00.0: Xorg[1012]: Unknown handle 0x005a > [ 71.515664] nouveau :01:00.0: Xorg[1012]: validate_init > [ 71.515666] nouveau :01:00.0: Xorg[1012]: validate: -2 > > And here is the output from the terminal: > > geser@WORKSTATION-Deb ~ $ kmail > No text-to-speech plug-ins were found. > qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 2949, > resource id: 10485826, major code: 130 (Unknown), minor code: 3 > qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 2961, > resource id: 10485826, major code: 130 (Unknown), minor code: 3 > qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 2975, > resource id: 10485826, major code: 130 (Unknown), minor code: 3 > qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 2991, > resource id: 10485826, major code: 130 (Unknown), minor code: 3 > qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 5764, > resource id: 10485826, major code: 130 (Unknown), minor code: 3 > qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 5784, > resource id: 10485826, major code: 130 (Unknown), minor code: 3 > qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 5788, > resource id: 10485826, major code: 130 (Unknown), minor code: 3 > *** KMail got signal 11 (Exiting) > *** Dead letters dumped. > /tmp/messageviewer_ByYTXj.index.2 was removed . > /tmp/messageviewer_oJnWHg.index.2 was removed . > nouveau: kernel rejected pushbuf: Неправильный дескриптор файла > nouveau: ch13: krec 0 pushes 1 bufs 10 relocs 0 > nouveau: ch13: buf 0002 0004 0004 > nouveau: ch13: buf 0001 0016 0002 0002 > nouveau: ch13: buf 0002 0014 0002 0002 > nouveau: ch13: buf 0003 0007 0002 0002 > nouveau: ch13: buf 0004 000a 0002 0002 > nouveau: ch13: buf 0005 000b 0002 0002 > nouveau: ch13: buf 0006 0008 0002 0002 > nouveau: ch13: buf 0007 0006 0004 0004 > nouveau: ch13: buf 0008 0015 0002 0002 > nouveau: ch13: buf 0009 000f 0002 0002 > nouveau: ch13: psh 039aec 03a738 > nouveau:0x0004721c > nouveau:0x0fac6881 > nouveau:0x00086ff4 > nouveau:0x0780 > nouveau:0x0416 > nouveau:0x00146200 > nouveau:0x > nouveau:0x20ec > nouveau:0x00e6 > nouveau:0x0040 > nouveau:0x > nouveau:0x00087240 > nouveau:0x0780 > nouveau:0x0416 > nouveau:0x00047224 > nouveau:0x0001 > nouveau:0x00047538 > nouveau:0x > nouveau:0x000475d0 > nouveau:0x > nouveau:0x00086c00 > nouveau:0x0780 > nouveau:0x0416 > nouveau:0x00086e04 > nouveau:0x0780 > nouveau:0x0416 > nouveau:0x00086e14 > nouveau:0x > nouveau:0x > nouveau:0x00086e24 > nouveau:0x > nouveau:0x > nouveau:0x00086e34 > nouveau:0x > nouveau:0x > nouveau:0x00086e44 > nouveau:0x > nouveau:0x > nouveau:0x00086e54 > nouveau:0x > nouveau:0x > nouveau:0x00086e64 > nouveau:0x > nouveau:0x > nouveau:0x00086e74 > nouveau:0x > nouveau:0x > nouveau:0x00086e84 > nouveau:0x > nouveau:0x > nouveau:0x00086e94 > nouveau:0x > nouveau:0x > nouveau:0x00086ea4 > nouveau:0x > nouveau:0x > nouveau:0x00086eb4 > nouveau:0x > nouveau:0x > nouveau:0x00086ec4 > nouveau:0x > nouveau:0x > nouveau:0x00086ed4 > nouveau:0x > nouveau:0x > nouveau:0x00086ee4 >
Bug#944210: aqbanking-tools: Add note about rename settings to settings6
Package: aqbanking-tools Version: 5.99.43beta-1 Severity: important Hey, the version 5.99.43 is already using the new AqBanking6 settings layout. In order to reuse old settings like accounts etc. you need to rename the settings folders. Like it is described at this page: https://www.aquamaniac.de/rdm/projects/aqbanking/wiki/AqBanking6 Please add a section in NEWS.Debian to inform unsers, that it is needed to copy the settings, if they want to reuse anything. Something like this: AqBanking6 can reuse the configuration from AqBanking5 in a semi automatic way. To trigger this reuse, you need to copy those data: cd ~/.aqbanking mkdir -p settings6 cp -r settings/* settings6 AqBanking6 will use only the new directory "settings6". This means, that it is possible to use apps, that use ApBanking5 (still using the "settings" directory) in parallel with those that use AqBanking6. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.3.0-1-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages aqbanking-tools depends on: ii libaqbanking43 5.99.43beta-1 ii libc62.29-3 ii libgwenhywfar78 4.99.24rc8-1 aqbanking-tools recommends no packages. Versions of packages aqbanking-tools suggests: pn gwenhywfar-tools -- no debconf information
Bug#942415: transition: meta-kde
Hey, the merged ben file: is_affected = .build-depends ~ /lib(kf5akonadi|kf5akonadicalendar| kf5akonadicontact|kf5akonadimime|kf5akonadinotes|kf5akonadisearch| kf5akonadiserver|kf5akonadisocialutils|kf5alarmcalendar|kf5blog| kf5calendarcore|kf5calendarsupport|kf5calendarutils|kf5contacteditor| kf5contacts|kf5eventviews|kf5followupreminder|kf5grantleetheme|kf5gravatar| kf5identitymanagement|kf5imap|kf5incidenceeditor|kf5kaddressbookgrantlee| kf5kaddressbookimportexport|kf5kdepimdbusinterfaces|kf5kontactinterface| kf5ksieve|kf5ldap|kf5libkdepim|kf5libkleo|kf5mailcommon|kf5mailimporter| kf5mailtransport|kf5mbox|kf5messagecomposer|kf5messagecore|kf5messagelist| kf5messageviewer|kf5mime|kf5mimetreeparser|kf5pimcommon|kf5pimtextedit| kf5sendlater|kf5templateparser|kf5tnef|kf5webengineviewer|kpimgapi| kpimimportwizard|kpimitinerary|kpimkdav|kpimpkpass|kpimsmtp)-dev/ is_bad = !.depends ~ /lib(kf5akonadiagentbase5|kf5akonadicalendar5| kf5akonadicontact5|kf5akonadicore5|kf5akonadimime5|kf5akonadinotes5| kf5akonadiprivate5|kf5akonadisearchcore5|kf5akonadisea rchdebug5|kf5akonadisearchpim5|kf5akonadisearchxapian5|kf5akonadiwidgets5| kf5akonadixml5|kf5alarmcalendar5|kf5blog5|kf5calendarcore5| kf5calendarsupport5|kf5calendarutils5|kf5contacteditor5|kf5contact s5|kf5eventviews5|kf5followupreminder5|kf5grantleetheme5|kf5gravatar5| kf5identitymanagement5|kf5imap5|kf5incidenceeditor5|kf5kaddressbookgrantlee5| kf5kaddressbookimportexport5|kf5kdepimdbusinterfaces 5|kf5kmanagesieve5|kf5kontactinterface5|kf5ksieve5|kf5ksieveui5|kf5ldap5| kf5libkdepim5|kf5libkdepimakonadi5|kf5libkleo5|kf5mailcommon5| kf5mailimporter5|kf5mailimporterakonadi5|kf5mailtransport5|kf5ma iltransportakonadi5|kf5mbox5|kf5messagecomposer5|kf5messagecore5| kf5messagelist5|kf5messageviewer5|kf5mime5|kf5mimetreeparser5|kf5pimcommon5| kf5pimcommonakonadi5|kf5pimtextedit5|kf5sendlater5|kf5temp lateparser5|kf5tnef5|kf5webengineviewer5|kpimgapiblogger5|kpimgapicalendar5| kpimgapicontacts5|kpimgapicore5|kpimgapidrive5|kpimgapilatitude5| kpimgapimaps5|kpimgapitasks5|kpimimportwizard5|kpimitinera ry5|kpimkdav5|kpimpkpass5|kpimsmtp5)-18.08/ is_good = .depends ~ /lib(kf5akonadiagentbase5|kf5akonadicalendar5| kf5akonadicontact5|kf5akonadicore5|kf5akonadimime5|kf5akonadinotes5| kf5akonadiprivate5|kf5akonadisearchcore5|kf5akonadisea rchdebug5|kf5akonadisearchpim5|kf5akonadisearchxapian5|kf5akonadiwidgets5| kf5akonadixml5|kf5alarmcalendar5|kf5blog5|kf5calendarcore5| kf5calendarsupport5|kf5calendarutils5|kf5contacteditor5|kf5contact s5|kf5eventviews5|kf5followupreminder5|kf5grantleetheme5|kf5gravatar5| kf5identitymanagement5|kf5imap5|kf5incidenceeditor5|kf5kaddressbookgrantlee5| kf5kaddressbookimportexport5|kf5kdepimdbusinterfaces 5|kf5kmanagesieve5|kf5kontactinterface5|kf5ksieve5|kf5ksieveui5|kf5ldap5| kf5libkdepim5|kf5libkdepimakonadi5|kf5libkleo5|kf5mailcommon5| kf5mailimporter5|kf5mailimporterakonadi5|kf5mailtransport5|kf5ma iltransportakonadi5|kf5mbox5|kf5messagecomposer5|kf5messagecore5| kf5messagelist5|kf5messageviewer5|kf5mime5|kf5mimetreeparser5|kf5pimcommon5| kf5pimcommonakonadi5|kf5pimtextedit5|kf5sendlater5|kf5temp lateparser5|kf5tnef5|kf5webengineviewer5|kpimgapiblogger5|kpimgapicalendar5| kpimgapicontacts5|kpimgapicore5|kpimgapidrive5|kpimgapilatitude5| kpimgapimaps5|kpimgapitasks5|kpimimportwizard5|kpimitinera ry5|kpimkdav5|kpimpkpass5|kpimsmtp5)-18.08/ On Dienstag, 22. Oktober 2019 21:43:28 CET Paul Gevers wrote: > Control: tags -1 moreinfo > > Hi Sandro, > > On 15-10-2019 23:53, Sandro Knauß wrote: > > I'm not sure, what ben rules you want, I can create ben rules for all > > 38 packages, but as the 57 packages are get a new upload anyways, > > those get recompiled anyways. > > This sounds like one transition, so I think we want *one* ben file. > Don't you want all is_affected/is_good/is_bad or-ed together? > > > So I decided to start with those 18 packages, that affects by the > > external packages, those are: > > blogilo (broken in sid anyways / upstream is dead) > > calligra > > calligraplan > > kio-gdrive > > kjots > > kmymoney > > kraft > > zanshin > > I'm not sure I understand what you meant. Let me rephrase what I think > you wanted to say. You created the ben files for 18 source packages. > Those 18 source packages provide the 8 listed source packages above with > (build) dependencies. The other KDEPIM source packages in this > transition don't have reverse dependencies that need rebuilding outside > of the KDEPIM packages? > > Paul signature.asc Description: This is a digitally signed message part.
Bug#942415: transition: meta-kde
Control: tags -1 -moreinfo Hi Paul, > On 15-10-2019 23:53, Sandro Knauß wrote: > > I'm not sure, what ben rules you want, I can create ben rules for all > > 38 packages, but as the 57 packages are get a new upload anyways, > > those get recompiled anyways. > > This sounds like one transition, so I think we want *one* ben file. > Don't you want all is_affected/is_good/is_bad or-ed together? Well I can merge those is_affected/is_bad/is_good lines together, but from my point of view that means, that the status is not tracked correctly. As a reverse dependency may depend on two or more packages in KDEPIM and the is_good line would be true if the package get built against any of those packages. But maybe this is normal for transitions because in the end it is only a question of when to request the binnmu. > > So I decided to start with those 18 packages, that affects by the > > external packages, those are: > > blogilo (broken in sid anyways / upstream is dead) > > calligra > > calligraplan > > kio-gdrive > > kjots > > kmymoney > > kraft > > zanshin > > I'm not sure I understand what you meant. Let me rephrase what I think > you wanted to say. You created the ben files for 18 source packages. > Those 18 source packages provide the 8 listed source packages above with > (build) dependencies. The other KDEPIM source packages in this > transition don't have reverse dependencies that need rebuilding outside > of the KDEPIM packages? Right, all others don't have any (build) reverse dependencies outside KDEPIM. > > Paul signature.asc Description: This is a digitally signed message part.
Bug#942134: dh_shlibdeps: Generating strict local shlibs on packages
Hey, > Ok, getting dependencies "right by default" is as good a reason as any > to support it the conceptual idea (among other because strictly-equal > version dependencies are fine between same-source binaries). great, that you understand what I want and why this is helpful. I have often problems describing my problem for others. > However, I am not going to fiddle with debian/shlibs.local because it > is fragile and it would break horribly if people need that file for > other reasons (plus it would complicating clean up). > > So a prerequisite for this is that dpkg-shlibdeps support multiple > shlibs.local files. @Guillem: What is your take on this bit? Preference > order would be "d/shlibs.local", "file(s) passed via this new option", > . > If it is any easier, I am also fine with the option neutering > d/shlibs.local as long as I can pass multiple files (so I can emulate it > with the option). I like your proposed solution, to be able to fix it in dpkg-shlibdeps . And this should be more robust than our solution with regexing in debian/ *.substvars. Also we need to think about Architecture:all/any dependency that are not handled correctly with our solution. hefee signature.asc Description: This is a digitally signed message part.
Bug#942134: dh_shlibdeps: Generating strict local shlibs on packages
Hey, > Ok, getting dependencies "right by default" is as good a reason as any > to support it the conceptual idea (among other because strictly-equal > version dependencies are fine between same-source binaries). great, that you understand what I want and why this is helpful. I have often problems describing my problem for others. > However, I am not going to fiddle with debian/shlibs.local because it > is fragile and it would break horribly if people need that file for > other reasons (plus it would complicating clean up). > > So a prerequisite for this is that dpkg-shlibdeps support multiple > shlibs.local files. @Guillem: What is your take on this bit? Preference > order would be "d/shlibs.local", "file(s) passed via this new option", > . > If it is any easier, I am also fine with the option neutering > d/shlibs.local as long as I can pass multiple files (so I can emulate it > with the option). I like your proposed solution, to be able to fix it in dpkg-shlibdeps . And this should be more robust than our solution with regexing in debian/ *.substvars. Also we need to think about Architecture:all/any dependency that are not handled correctly with our solution. hefee signature.asc Description: This is a digitally signed message part.
Bug#941120: akonadi-backend-postgresql: fails to stop postgresql 11
Hey, thanks for your reply. > I am not sure how many Debian users use stable Akonadi with PostgreSQL > and PostgreSQL even appears to pick up the running processes after a > subsequent "akonadictl start". Considering all this, the only annoyance > and confusion is that some PostgreSQL processes keep lingering around. > Some users may be confused about this. > > Okay, all in all, not all that convincing arguments for stable. I just > thought if you do all the other fixes, you could put this one in as well. > I considered it to be low risk. well the prepared version for stable got already accepted, so there is no open end. All in all it seems for me like you say, it is just annoying. I fixed it for debian/buster branch already, but let's see if we need to bundle it with other fixes. > As the fix is in Akonadi 19.04, you may consider to close the bug right > away or close it when uploading Akonadi 19.08 or newer packages. Please do not close the bug, as it is not fixed! this should be done if 19.08+ packages enters Debian. hefee signature.asc Description: This is a digitally signed message part.
Bug#942134: dh_shlibdeps: Generating strict local shlibs on packages
Control: tags -1 - moreinfo
Hey,
> Can you expand a bit on the use case here or the problem you want to
> solve? At the moment, I cannot see how it is different from having the
> following in your d/control file
>
> """
> Depends: other-package (= ${binary:Version}), ...
> """
>
> (Except this one goes in d/control and the case you point to goes in
> d/rules)
you are right, that you can solve the issue with adding this dependency in d/
control explicitly. The approach I described also works with with any kind of
dependency that end up in the Depends via a variable like ${shlibs:Depends} or
${misc:Depends}. So you can rely on the dh to get the correct dependencies and
updates it to a equal version dependency for package internal ones and don't
need to list the inter package ones explicitly.
hefee
signature.asc
Description: This is a digitally signed message part.
Bug#942415: transition: meta-kde
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Hey, KDEPIM doesn't garantee ABI stability within there libraries only for one release. Our current system is to bump the ABI, when KDEPIM break their ABI. But this has the downside, that we mix different library versions in testing while a new version is populating to testing and doesn't make our users happy. That's why we want to switch from a symbols based approach to a approach, where we use virtual packages to bundle KDEPIM as one product. That should also help britney to move KDEPIM only to testing if everything is ready to move to testing. I prepared the 57 source package of KDEPIM in experimental (38 library packages and 19 leaf packages). Additionally to those packages, there are 10 "external" packages, that are not part of KDEPIM, but needs to be recompiled, to have dependencies against those virtual packages. From my point of view this needs a transition. I'm not sure, what ben rules you want, I can create ben rules for all 38 packages, but as the 57 packages are get a new upload anyways, those get recompiled anyways. So I decided to start with those 18 packages, that affects by the external packages, those are: blogilo (broken in sid anyways / upstream is dead) calligra calligraplan kio-gdrive kjots kmymoney kraft zanshin Ben files title = "akonadicalendar"; is_affected = .build-depends ~ /libkf5akonadicalendar-dev/; is_good = .depends ~ /libkf5akonadicalendar5-18.08/; is_bad = !.depends ~ /libkf5akonadicalendar5-18.08/; title = "kldap"; is_affected = .build-depends ~ /libkf5ldap-dev/; is_good = .depends ~ /libkf5ldap5-18.08/; is_bad = !.depends ~ /libkf5ldap5-18.08/; title = "akonadi"; is_affected = .build-depends ~ /libkf5akonadi-dev|libkf5akonadiserver-dev/; is_good = .depends ~ /libkf5akonadiagentbase5-18.08|libkf5akonadicore5-18.08|libkf5akonadiprivate5-18.08|libkf5akonadiwidgets5-18.08|libkf5akonadixml5-18.08/; is_bad = !.depends ~ /libkf5akonadiagentbase5-18.08|libkf5akonadicore5-18.08|libkf5akonadiprivate5-18.08|libkf5akonadiwidgets5-18.08|libkf5akonadixml5-18.08/; title = "akonadisearch"; is_affected = .build-depends ~ /libkf5akonadisearch-dev/; is_good = .depends ~ /libkf5akonadisearchcore5-18.08|libkf5akonadisearchdebug5-18.08|libkf5akonadisearchpim5-18.08|libkf5akonadisearchxapian5-18.08/; is_bad = !.depends ~ /libkf5akonadisearchcore5-18.08|libkf5akonadisearchdebug5-18.08|libkf5akonadisearchpim5-18.08|libkf5akonadisearchxapian5-18.08/; title = "messagelib"; is_affected = .build-depends ~ /libkf5messagecomposer-dev|libkf5messagecore-dev|libkf5messagelist-dev|libkf5messageviewer-dev|libkf5mimetreeparser-dev|libkf5templateparser-dev|libkf5webengineviewer-d ev/; is_good = .depends ~ /libkf5messagecomposer5-18.08|libkf5messagecore5-18.08|libkf5messagelist5-18.08|libkf5messageviewer5-18.08|libkf5mimetreeparser5-18.08|libkf5templateparser5-18.08|libkf5webengine viewer5-18.08/; is_bad = !.depends ~ /libkf5messagecomposer5-18.08|libkf5messagecore5-18.08|libkf5messagelist5-18.08|libkf5messageviewer5-18.08|libkf5mimetreeparser5-18.08|libkf5templateparser5-18.08|libkf5webengin$ viewer5-18.08/; title = "kimap"; is_affected = .build-depends ~ /libkf5imap-dev/; is_good = .depends ~ /libkf5imap5-18.08/; is_bad = !.depends ~ /libkf5imap5-18.08/; title = "akonadicontact"; is_affected = .build-depends ~ /libkf5akonadicontact-dev|libkf5contacteditor-dev/; is_good = .depends ~ /libkf5akonadicontact5-18.08|libkf5contacteditor5-18.08/; is_bad = !.depends ~ /libkf5akonadicontact5-18.08|libkf5contacteditor5-18.08/; title = "kontactinterface"; is_affected = .build-depends ~ /libkf5kontactinterface-dev/; is_good = .depends ~ /libkf5kontactinterface5-18.08/; is_bad = !.depends ~ /libkf5kontactinterface5-18.08/; title = "pimtextedit"; is_affected = .build-depends ~ /libkf5pimtextedit-dev/; is_good = .depends ~ /libkf5pimtextedit5-18.08/; is_bad = !.depends ~ /libkf5pimtextedit5-18.08/; title = "calendarcore"; is_affected = .build-depends ~ /libkf5calendarcore-dev/; is_good = .depends ~ /libkf5calendarcore5-18.08/; is_bad = !.depends ~ /libkf5calendarcore5-18.08/; title = "libkdepim"; is_affected = .build-depends ~ /libkf5akonadisocialutils-dev|libkf5libkdepim-dev/; is_good = .depends ~ /libkf5libkdepim5-18.08|libkf5libkdepimakonadi5-18.08/; is_bad = !.depends ~ /libkf5libkdepim5-18.08|libkf5libkdepimakonadi5-18.08/; title = "pimgapi"; is_affected = .build-depends ~ /libkpimgapi-dev/; is_good = .depends ~ /libkpimgapiblogger5-18.08|libkpimgapicalendar5-18.08|libkpimgapicontacts5-18.08|libkpimgapicore5-18.08|libkpimgapidrive5-18.08|libkpimgapilatitude5-18.08|libkpimgapimaps5-18.08| libkpimgapitasks5-18.08/; is_bad = !.depends ~ /libkpimgapiblogger5-18.08|libkpimgapicalendar5-18.08|libkpimgapicontacts5-18.08|libkpimgapicore5-18.08|libkpimgapidrive5-18.08|libkpimgapilatitude5-18.08|libkpimgapimaps5-18.08| libkpimgapitasks5-18.08/; title = "kblog"; is_affected
Bug#942134: dh_shlibdeps: Generating strict local shlibs on packages
Package: debhelper Version: 12.6.1 Severity: wishlist You may end up in a situation, where you want a very strict dependency the binary packages of a related packages. This feature is currently developed in pkg-kde-tools, but may also be interesting for other library packages. The code is developed here: https://salsa.debian.org/qt-kde-team/pkg-kde-tools/blob/master/qt-kde-team/3/library-packages.mk the usage for d/rules: include /usr/share/pkg-kde-tools/qt-kde-team/3/library-packages.mk libpkgs_gen_strict_local_shlibs = $(libpkgs_all_packages) codesearch give following results: https://codesearch.debian.net/search?q=libpkgs_gen_strict_local_shlibs=1=1 Regards, hefee -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.2.0-3-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages debhelper depends on: ii autotools-dev20180224.1 ii dh-autoreconf19 ii dh-strip-nondeterminism 1.6.0-1 ii dpkg 1.19.7 ii dpkg-dev 1.19.7 ii dwz 0.13-1 ii file 1:5.37-5 ii libdebhelper-perl12.6.1 ii libdpkg-perl 1.19.7 ii man-db 2.8.7-3 ii perl 5.28.1-6 ii po-debconf 1.0.21 debhelper recommends no packages. Versions of packages debhelper suggests: ii dh-make 2.201902 -- no debconf information
Bug#941120: akonadi-backend-postgresql: fails to stop postgresql 11
Control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=386173#c20 Hey Martin, as I don't use postgresql as backend, can you explain, why this bug it that annoying, so I should fix that also for stable? Thanks, hefee btw. please use forwarded and other features directly, while you create bug reports, so they more metadata right away. By the syntax with Control: -1 ... This make it easier to track status later on. -- On Mittwoch, 25. September 2019 09:41:48 CEST Martin Steigerwald wrote: > Package: akonadi-backend-postgresql > Version: 4:18.08.3-8 > Severity: normal > > Dear Sandro, > > you may like to consider > > Git commit 565700f7fc1d73e337600109867fc01cc647cf13 by Daniel Vrátil. > Committed on 20/06/2019 at 09:51. > Pushed by dvratil into branch 'Applications/19.04'. > > Check Postgres status by checking return code of pg_ctl > > Summary: > The current code which was checking the standard output of "pg_ctl status", > doesn't work with non-English locale, causing Akonadi to leave Postgres > running after shutdown, because it thinks the db is no longer running. > FIXED-IN: 5.11.3 > > https://bugs.kde.org/show_bug.cgi?id=386173#c20 > > for Akonadi for buster. > > Thanks, > Martin > > -- System Information: > Debian Release: bullseye/sid > APT prefers unstable-debug > APT policy: (500, 'unstable-debug'), (500, 'unstable'), (200, > 'experimental') Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 5.2.16-tp520 (SMP w/4 CPU cores; PREEMPT) > Kernel taint flags: TAINT_OOT_MODULE > Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de > (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash > Init: sysvinit (via /sbin/init) > LSM: AppArmor: enabled > > Versions of packages akonadi-backend-postgresql depends on: > ii libqt5sql5-psql 5.11.3+dfsg1-4 > > Versions of packages akonadi-backend-postgresql recommends: > ii akonadi-server 4:18.08.3-8 > ii postgresql 11+207 > > akonadi-backend-postgresql suggests no packages. > > -- no debconf information signature.asc Description: This is a digitally signed message part.
Bug#941481: kalarm: The Akonadi personal information management service is not running
Control: tags -1 moreinfo Hey, > When installing kalarm on mate desktop environment, program is not working. > It shows just message > "The Akonadi personal information management service is not running. This > application cannot be used without it". Pressing button Start does nothing. > In console there is output > > $ LC_ALL=C kalarm > org.kde.pim.kidentitymanagement: IdentityManager: There was no default > identity. Marking first one as default. > org.kde.pim.akonadicore: Unable to execute akonadi_control, falling back to > D-Bus auto-launch > [...] > > There are probably missing dependencies for kalarm package - when I install > also package kontact with its dependencies, kalarm starts working well. can you try if this is fixed, if you only install akoandiserver or do you need kdepim-runtime, too? hefee signature.asc Description: This is a digitally signed message part.
Bug#941763: libqt5sql5-psql: basic support postgresql-12
Package: libqt5sql5-psql Version: 5.12.5+dfsg-1 Severity: important Control: affects -1 akonadi-backend-postgresql Today, I installed Postgresql 12 and akonadi refuses to start. Two years ago, a similar issue (bug #876421, #879960) with postgresql 10. >From the code it seems that Postgres 12 isn't supprted at all: https://code.qt.io/cgit/qt/qtbase.git/tree/src/plugins/sqldrivers/psql/qsql_psql.cpp#n1080 -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.2.0-3-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libqt5sql5-psql depends on: ii libc6 2.29-2 ii libpq512.0-1 ii libqt5core5a [qtbase-abi-5-11-3] 5.11.3+dfsg1-4 ii libqt5sql55.11.3+dfsg1-4 ii libstdc++69.2.1-8 pn qtbase-abi-5-12-5 pn qtbase-abi-5-7-1 libqt5sql5-psql recommends no packages. libqt5sql5-psql suggests no packages.
Bug#941118: akonadi-server: fails to start after upgrade to 4:18.08.3-8: apparmor denied access to pg_ctl
Hey intrigeri, I now pushed a first version of Akonadi with the new AppArmor profile, but as you see down here it fails and I'm not sure, what went wrong. What we need to do to debug this? Those AppArmor profiles are in place: https://salsa.debian.org/qt-kde-team/kde/akonadi/blob/master/debian/apparmor/ usr.bin.akonadiserver https://salsa.debian.org/qt-kde-team/kde/akonadi/blob/master/debian/apparmor/ postgresql_akonadi hefee -- On Mittwoch, 25. September 2019 09:58:24 CEST Martin Steigerwald wrote: > > I upgraded and then rebooted the system. > > > > After upgrading to Akonadi 4:18.08.3-8, Akonadi does not start > > anymore: > > > > % akonadictl start > > Connecting to deprecated signal > > QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString > > ) org.kde.pim.akonadicontrol: Application 'akonadiserver' exited > > normally... > > > > I believe the failure may be due to this: > > > > Sep 25 09:21:06 merkaba kernel: [ 266.556167][ T37] audit: > > type=1400 audit(1569396066.434:45): apparmor="DENIED" > > operation="exec" profile="postgresql_akonadi" name="/bin/dash" > > pid=3833 comm="pg_ctl" requested_mask="x" denied_mask="x" fsuid=1000 > > ouid=0 > > […] > > > Also setting to complain mode does not help: > > > > % aa-complain postgresql_akonadi > > Setting /etc/apparmor.d/postgresql_akonadi to complain mode. > > > > Although access does get allowed then: > > > > Sep 25 09:30:14 merkaba kernel: [ 814.345508][ T37] audit: > > type=1400 audit(1569396614.227:51): apparmor="ALLOWED" > > operation="exec" profile="postgresql_akonadi" name="/bin/dash" > > pid=5328 comm="pg_ctl" requested_mask="x" denied_mask="x" fsuid=1000 > > ouid=0 target="postgresql_akonadi//null-/bin/dash" > > Oh, it does help. Akonadi starts again, just did not notice it > initially. > > The pattern in > > % grep pg_ctl /etc/apparmor.d/postgresql_akonadi > /usr/lib/postgresql/*/bin/pg_ctl mrix, > > seems to be okay tough: > > % ls -l /usr/lib/postgresql/*/bin/pg_ctl > -rwxr-xr-x 1 root root 59888 Sep 24 22:09 /usr/lib/postgresql/11/bin/ > pg_ctl > > However I am no AppArmor expert… > > Best, signature.asc Description: This is a digitally signed message part.
