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#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#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#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#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#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#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#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#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#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#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#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#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#939015: buster-pu: package akonadi/4:18.08.3-5
Fixed version number to make version smaller than the version in sid: akonadi/4:18.08.3-7~deb10u1 hefeediff -Nru akonadi-18.08.3/debian/changelog akonadi-18.08.3/debian/changelog --- akonadi-18.08.3/debian/changelog 2019-04-29 16:24:10.0 +0200 +++ akonadi-18.08.3/debian/changelog 2019-08-30 22:11:22.0 +0200 @@ -1,3 +1,34 @@ +akonadi (4:18.08.3-7~deb10u1) buster; urgency=medium + + * Rebuild for buster. + + -- Sandro Knauß Fri, 30 Aug 2019 22:11:22 +0200 + +akonadi (4:18.08.3-7) unstable; urgency=medium + + * Team upload. + + [ Sandro Knauß ] + * Add patch to fix: Akonadi components crash on logout. (Closes: #939013) + * Add patch to fix: Automatic recovery from Multiple Merge Candidates +error (Closes: #939012) + * Add patch with files, that are needed for other patches. + * Update symbols from buildds for 4:18.08.3 + + -- Sandro Knauß Fri, 30 Aug 2019 12:59:47 +0200 + +akonadi (4:18.08.3-6) unstable; urgency=medium + + * Team upload. + + [ Sandro Knauß ] + * Fix "Akonadi don't anwser any requests and ends in deadlock" (Closes: #935981) +by adding upstream patches. +- Akonadi-fix-dangling-transaction-after-itemsync-fail.patch +- ItemSync-skip-handling-remote-items-if-local-changes.patch + + -- Sandro Knauß Wed, 28 Aug 2019 19:31:31 +0200 + akonadi (4:18.08.3-5) unstable; urgency=medium * Team upload. diff -Nru akonadi-18.08.3/debian/libkf5akonadiagentbase5.symbols akonadi-18.08.3/debian/libkf5akonadiagentbase5.symbols --- akonadi-18.08.3/debian/libkf5akonadiagentbase5.symbols 2019-02-08 23:19:51.0 +0100 +++ akonadi-18.08.3/debian/libkf5akonadiagentbase5.symbols 2019-08-30 12:58:59.0 +0200 @@ -1,4 +1,4 @@ -# SymbolsHelper-Confirmed: 4:18.07.90 amd64 +# SymbolsHelper-Confirmed: 4:18.08.3 alpha amd64 arm64 armel armhf hppa hurd-i386 i386 m68k mips64el mipsel ppc64 ppc64el riscv64 s390x x32 libKF5AkonadiAgentBase.so.5 libkf5akonadiagentbase5 #MINVER# * Build-Depends-Package: libkf5akonadi-dev _ZN7Akonadi12ResourceBase10cancelTaskERK7QString@Base 4:15.07.90 @@ -197,7 +197,6 @@ _ZNK7Akonadi9AgentBase8isOnlineEv@Base 4:15.07.90 _ZNK7Akonadi9AgentBase8progressEv@Base 4:15.07.90 _ZNK7Akonadi9AgentBase9agentNameEv@Base 4:15.07.90 - (optional=templinst)_ZSt4swapIN7Akonadi10CollectionEENSt9enable_ifIXsrSt6__and_IJSt6__not_ISt15__is_tuple_likeIT_EESt21is_move_constructibleIS6_ESt18is_move_assignableIS6_EEE5valueEvE4typeERS6_SG_@Base 4:18.07.90 _ZTI12QDBusContext@Base 4:15.07.90 _ZTIN7Akonadi12ResourceBaseE@Base 4:15.07.90 _ZTIN7Akonadi16PreprocessorBaseE@Base 4:15.07.90 diff -Nru akonadi-18.08.3/debian/libkf5akonadicore5abi2.symbols akonadi-18.08.3/debian/libkf5akonadicore5abi2.symbols --- akonadi-18.08.3/debian/libkf5akonadicore5abi2.symbols 2019-02-13 19:42:05.0 +0100 +++ akonadi-18.08.3/debian/libkf5akonadicore5abi2.symbols 2019-08-30 12:58:21.0 +0200 @@ -1,4 +1,4 @@ -# SymbolsHelper-Confirmed: 4:18.08.3 alpha amd64 arm64 armel armhf hppa hurd-i386 i386 mips mips64el mipsel powerpc ppc64 ppc64el s390x +# SymbolsHelper-Confirmed: 4:18.08.3 alpha amd64 arm64 armel armhf hppa hurd-i386 i386 m68k mips mips64el mipsel powerpc ppc64 ppc64el riscv64 s390x x32 libKF5AkonadiCore.so.5abi2 libkf5akonadicore5abi2 #MINVER# * Build-Depends-Package: libkf5akonadi-dev ABI_5_2@ABI_5_2 4:18.07.90 @@ -27,7 +27,8 @@ _ZN7Akonadi10Collection7fromUrlERK4QUrl@ABI_5_2 4:18.07.90 _ZN7Akonadi10Collection7setNameERK7QString@ABI_5_2 4:18.07.90 _ZN7Akonadi10Collection8mimeTypeEv@ABI_5_2 4:18.07.90 - (optional=templinst|arch=hurd-i386 i386 m68k)_ZN7Akonadi10Collection9attributeINS_25PersistentSearchAttributeEEEPT_NS0_12CreateOptionE@ABI_5_2 4:18.07.90 + (optional=templinst|arch=!mips !powerpc)_ZN7Akonadi10Collection9attributeINS_22EntityDisplayAttributeEEEPT_NS0_12CreateOptionE@ABI_5_2 4:18.08.3 + (optional=templinst|arch=alpha amd64 arm64 armel armhf hppa hurd-i386 i386 m68k mips64el mipsel ppc64 ppc64el riscv64 s390x x32)_ZN7Akonadi10Collection9attributeINS_25PersistentSearchAttributeEEEPT_NS0_12CreateOptionE@ABI_5_2 4:18.07.90 _ZN7Akonadi10Collection9setRightsE6QFlagsINS0_5RightEE@ABI_5_2 4:18.07.90 _ZN7Akonadi10CollectionC1ERKS0_@ABI_5_2 4:18.07.90 _ZN7Akonadi10CollectionC1Ev@ABI_5_2 4:18.07.90 @@ -1597,7 +1598,7 @@ _ZN7Akonadi9UnlinkJobD2Ev@ABI_5_2 4:18.07.90 _ZN9QHashData9hasShrunkEv@ABI_5_2 4:18.07.90 (optional=templinst)_ZNK12KConfigGroup9readEntryIxEE5QListIT_EPKcRKS3_@ABI_5_2 4:18.07.90 - (optional=templinst|arch=alpha hppa mips64el ppc64 ppc64el s390x)_ZNK12KConfigGroup9readEntryIxEET_PKcRKS1_@ABI_5_2 4:18.07.90 + (optional=templinst|arch=alpha hppa mips64el ppc64 ppc64el riscv64 s390x)_ZNK12KConfigGroup9readEntryIxEET_PKcRKS1_@ABI_5_2 4:18.07.90 _ZNK7Akonadi10Collection10attributesEv@ABI_5_2 4:18.07.90 _ZNK7Akonadi10Collection10referencedEv@ABI_5_2 4:18.07.90 _ZNK7Akonadi10Collection10shouldListENS0_11ListPurposeE@ABI_5_2 4:18.07.90 @@ -1620,7 +1621,9 @@ _ZNK7Akonadi10Collection8remoteIdEv
Bug#939015: buster-pu: package akonadi/4:18.08.3-5
Package: release.debian.org Severity: normal Tags: buster User: release.debian@packages.debian.org Usertags: pu Hey, Akonadi in Buster has some bad issues, that make it nearly impossible for some users to use. I have tested the patches locally and on another friends laptop, who was affected by the unusable Akonadi. As Buster and sid are not that far away, the same patchset is tested by all sid users. I backported an important fix about the mutiple merge candidates issue from Akonadi 19.08 to 18.08. It does not fix the actual issue from happening, but it allows Akonadi to resolve the issue without user interaction (#939012). Than Akonadi components tend to crash, when you shutdown or logout. This is handled by (#939013). Sometime AKonadi gets into a dedlock and not even restarting your computer helps to solve the deadlock (#935981). On top of those patches I fixed the symbolfiles for the stable version. To make sure, that with further updates to Buster, we don't break the ABI. I know, that the patchset is not small. As KDEPIM is not usable for some users without these patches, the severity is grave for them. Other users have the luck of not hitting the bug. Unfortunately it is unclear, what triggers the behavior in first place, so there are no workaround to solve these issues otherwise. -- 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-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 diff -Nru akonadi-18.08.3/debian/changelog akonadi-18.08.3/debian/changelog --- akonadi-18.08.3/debian/changelog2019-04-29 16:24:10.0 +0200 +++ akonadi-18.08.3/debian/changelog2019-08-30 22:11:22.0 +0200 @@ -1,3 +1,34 @@ +akonadi (4:18.08.3-7+deb10u1) buster; urgency=medium + + * Rebuild for buster. + + -- Sandro Knauß Fri, 30 Aug 2019 22:11:22 +0200 + +akonadi (4:18.08.3-7) unstable; urgency=medium + + * Team upload. + + [ Sandro Knauß ] + * Add patch to fix: Akonadi components crash on logout. (Closes: #939013) + * Add patch to fix: Automatic recovery from Multiple Merge Candidates +error (Closes: #939012) + * Add patch with files, that are needed for other patches. + * Update symbols from buildds for 4:18.08.3 + + -- Sandro Knauß Fri, 30 Aug 2019 12:59:47 +0200 + +akonadi (4:18.08.3-6) unstable; urgency=medium + + * Team upload. + + [ Sandro Knauß ] + * Fix "Akonadi don't anwser any requests and ends in deadlock" (Closes: #935981) +by adding upstream patches. +- Akonadi-fix-dangling-transaction-after-itemsync-fail.patch +- ItemSync-skip-handling-remote-items-if-local-changes.patch + + -- Sandro Knauß Wed, 28 Aug 2019 19:31:31 +0200 + akonadi (4:18.08.3-5) unstable; urgency=medium * Team upload. diff -Nru akonadi-18.08.3/debian/libkf5akonadiagentbase5.symbols akonadi-18.08.3/debian/libkf5akonadiagentbase5.symbols --- akonadi-18.08.3/debian/libkf5akonadiagentbase5.symbols 2019-02-08 23:19:51.0 +0100 +++ akonadi-18.08.3/debian/libkf5akonadiagentbase5.symbols 2019-08-30 12:58:59.0 +0200 @@ -1,4 +1,4 @@ -# SymbolsHelper-Confirmed: 4:18.07.90 amd64 +# SymbolsHelper-Confirmed: 4:18.08.3 alpha amd64 arm64 armel armhf hppa hurd-i386 i386 m68k mips64el mipsel ppc64 ppc64el riscv64 s390x x32 libKF5AkonadiAgentBase.so.5 libkf5akonadiagentbase5 #MINVER# * Build-Depends-Package: libkf5akonadi-dev _ZN7Akonadi12ResourceBase10cancelTaskERK7QString@Base 4:15.07.90 @@ -197,7 +197,6 @@ _ZNK7Akonadi9AgentBase8isOnlineEv@Base 4:15.07.90 _ZNK7Akonadi9AgentBase8progressEv@Base 4:15.07.90 _ZNK7Akonadi9AgentBase9agentNameEv@Base 4:15.07.90 - (optional=templinst)_ZSt4swapIN7Akonadi10CollectionEENSt9enable_ifIXsrSt6__and_IJSt6__not_ISt15__is_tuple_likeIT_EESt21is_move_constructibleIS6_ESt18is_move_assignableIS6_EEE5valueEvE4typeERS6_SG_@Base 4:18.07.90 _ZTI12QDBusContext@Base 4:15.07.90 _ZTIN7Akonadi12ResourceBaseE@Base 4:15.07.90 _ZTIN7Akonadi16PreprocessorBaseE@Base 4:15.07.90 diff -Nru akonadi-18.08.3/debian/libkf5akonadicore5abi2.symbols akonadi-18.08.3/debian/libkf5akonadicore5abi2.symbols --- akonadi-18.08.3/debian/libkf5akonadicore5abi2.symbols 2019-02-13 19:42:05.0 +0100 +++ akonadi-18.08.3/debian/libkf5akonadicore5abi2.symbols 2019-08-30 12:58:21.0 +0200 @@ -1,4 +1,4 @@ -# SymbolsHelper-Confirmed: 4:18.08.3 alpha amd64 arm64 armel armhf hppa hurd-i386 i386 mips mips64el mipsel powerpc ppc64 ppc64el s390x +# SymbolsHelper-Confirmed: 4:18.08.3 alpha amd64 arm64 armel armhf hppa hurd-i386
Bug#938954: buster-pu: package nextcloud-desktop/2.5.1-3
Hey,
> +nextcloud-desktop (2.5.1-4) UNRELEASED; urgency=medium
>
> That's wrong in two different ways for stable.
I know ;D that's why I said it is not ready.
It will be
nextcloud-desktop (2.5.1-3+deb10u1) buster; urgency=medium
in the end. That should be correct, as attached.
> > As nextcloud-desktop was
> > removed from testing, it needs 5 days till, the patch entered
> > testing.
> > After that I'll make the package ready for uploading it to buster.
>
> The requirement is that the fix be in unstable. Five days from now will
> be too late for 10.1, for the record.
Oh that is fine, if it only needs to be in unstable, than I can already prepare
the upload, great and don't need to wait for it.
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-05-16 16:14:50.0 +0200
+++ nextcloud-desktop-2.5.1/debian/changelog 2019-08-29 18:57:38.0 +0200
@@ -1,3 +1,10 @@
+nextcloud-desktop (2.5.1-3+deb10u1) buster; urgency=medium
+
+ * Make nextcloud-desktop-cmd depend on nextcloud-desktop-common.
+Thanks to Calogero Lo Leggio (Closes: #932108)
+
+ -- Sandro Knauß Thu, 29 Aug 2019 18:57:38 +0200
+
nextcloud-desktop (2.5.1-3) unstable; urgency=medium
* Fix "Subfolders of moved folders not synced" (Closes: #929079)
diff -Nru nextcloud-desktop-2.5.1/debian/control nextcloud-desktop-2.5.1/debian/control
--- nextcloud-desktop-2.5.1/debian/control 2019-02-13 00:04:42.0 +0100
+++ nextcloud-desktop-2.5.1/debian/control 2019-08-29 18:57:38.0 +0200
@@ -122,6 +122,7 @@
Architecture: any
Depends: libnextcloudsync0 (= ${binary:Version}),
libqt5sql5-sqlite,
+ nextcloud-desktop-common,
nextcloud-desktop-l10n,
${misc:Depends},
${shlibs:Depends}
signature.asc
Description: This is a digitally signed message part.
Bug#938954: buster-pu: package nextcloud-desktop/2.5.1-3
Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu
I would like to fix #932108 in buster, because it hits stable users. The
patch is quite simple. See attached debdiff. As nextcloud-desktop was
removed from testing, it needs 5 days till, the patch entered testing.
After that I'll make the package ready for uploading it to buster.
-- 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-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
diff -Nru nextcloud-desktop-2.5.1/debian/changelog
nextcloud-desktop-2.5.1/debian/changelog
--- nextcloud-desktop-2.5.1/debian/changelog2019-05-16 16:14:50.0
+0200
+++ nextcloud-desktop-2.5.1/debian/changelog2019-08-29 18:57:38.0
+0200
@@ -1,3 +1,10 @@
+nextcloud-desktop (2.5.1-4) UNRELEASED; urgency=medium
+
+ * Make nextcloud-desktop-cmd depend on nextcloud-desktop-common.
+Thanks to Calogero Lo Leggio (Closes: #932108)
+
+ -- Sandro Knauß Thu, 29 Aug 2019 18:57:38 +0200
+
nextcloud-desktop (2.5.1-3) unstable; urgency=medium
* Fix "Subfolders of moved folders not synced" (Closes: #929079)
diff -Nru nextcloud-desktop-2.5.1/debian/control
nextcloud-desktop-2.5.1/debian/control
--- nextcloud-desktop-2.5.1/debian/control 2019-02-13 00:04:42.0
+0100
+++ nextcloud-desktop-2.5.1/debian/control 2019-08-29 18:57:38.0
+0200
@@ -122,6 +122,7 @@
Architecture: any
Depends: libnextcloudsync0 (= ${binary:Version}),
libqt5sql5-sqlite,
+ nextcloud-desktop-common,
nextcloud-desktop-l10n,
${misc:Depends},
${shlibs:Depends}
Bug#930197: unblock: nextcloud-desktop/2.5.1-3
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package nextcloud-desktop
If someone moves a folder into the Nextcloud desktop controlled folder,
Nextcloud desktop didn't upload subfolders. This leads to a wired UX as
users see the complete directory tree localy, but missing those files
and folders on server.
The debdiff 2.5.1-2 - 2.5.1-3 is attached.
unblock nextcloud-desktop/2.5.1-3
-- System Information:
Debian Release: 10.0
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 4.19.0-5-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
diff -Nru nextcloud-desktop-2.5.1/debian/changelog
nextcloud-desktop-2.5.1/debian/changelog
--- nextcloud-desktop-2.5.1/debian/changelog2019-02-12 23:54:02.0
+0100
+++ nextcloud-desktop-2.5.1/debian/changelog2019-05-16 16:14:50.0
+0200
@@ -1,3 +1,10 @@
+nextcloud-desktop (2.5.1-3) unstable; urgency=medium
+
+ * Fix "Subfolders of moved folders not synced" (Closes: #929079)
+Added 0005-Fixed-Issue-1000-Subfolders-of-moved-folders-not-syn.patch
+
+ -- Sandro Knauß Thu, 16 May 2019 16:14:50 +0200
+
nextcloud-desktop (2.5.1-2) unstable; urgency=medium
[ Adrian Heine ]
diff -Nru
nextcloud-desktop-2.5.1/debian/patches/0005-Fixed-Issue-1000-Subfolders-of-moved-folders-not-syn.patch
nextcloud-desktop-2.5.1/debian/patches/0005-Fixed-Issue-1000-Subfolders-of-moved-folders-not-syn.patch
---
nextcloud-desktop-2.5.1/debian/patches/0005-Fixed-Issue-1000-Subfolders-of-moved-folders-not-syn.patch
1970-01-01 01:00:00.0 +0100
+++
nextcloud-desktop-2.5.1/debian/patches/0005-Fixed-Issue-1000-Subfolders-of-moved-folders-not-syn.patch
2019-05-16 15:58:22.0 +0200
@@ -0,0 +1,92 @@
+From b6ff17c50be2339ba1dcfa9a8b0afeccacd6d6e5 Mon Sep 17 00:00:00 2001
+From: Joshua Sterner
+Date: Thu, 9 May 2019 01:05:49 -0700
+Subject: [PATCH] Fixed Issue #1000 - Subfolders of moved folders not synced
+
+Signed-off-by: Joshua Sterner
+---
+ src/gui/folderwatcher.cpp | 18 ++
+ src/gui/folderwatcher.h| 3 +++
+ test/testfolderwatcher.cpp | 13 +
+ 3 files changed, 34 insertions(+)
+
+diff --git a/src/gui/folderwatcher.cpp b/src/gui/folderwatcher.cpp
+index d8136ff36..65e68cb36 100644
+--- a/src/gui/folderwatcher.cpp
b/src/gui/folderwatcher.cpp
+@@ -75,9 +75,27 @@ bool FolderWatcher::isReliable() const
+ return _isReliable;
+ }
+
++void FolderWatcher::appendSubPaths(QDir dir, QStringList& subPaths) {
++QStringList newSubPaths = dir.entryList(QDir::NoDotAndDotDot | QDir::Dirs
| QDir::Files);
++for (int i = 0; i < newSubPaths.size(); i++) {
++QString path = dir.path() + "/" + newSubPaths[i];
++QFileInfo fileInfo(path);
++subPaths.append(path);
++if (fileInfo.isDir()) {
++QDir dir(path);
++appendSubPaths(dir, subPaths);
++}
++}
++}
++
+ void FolderWatcher::changeDetected(const QString )
+ {
++QFileInfo fileInfo(path);
+ QStringList paths(path);
++if (fileInfo.isDir()) {
++QDir dir(path);
++appendSubPaths(dir, paths);
++}
+ changeDetected(paths);
+ }
+
+diff --git a/src/gui/folderwatcher.h b/src/gui/folderwatcher.h
+index a6cf006e2..b07c33a10 100644
+--- a/src/gui/folderwatcher.h
b/src/gui/folderwatcher.h
+@@ -26,6 +26,7 @@
+ #include
+ #include
+ #include
++#include
+
+ class QTimer;
+
+@@ -120,6 +121,8 @@ private:
+ Folder *_folder;
+ bool _isReliable = true;
+
++void appendSubPaths(QDir dir, QStringList& subPaths);
++
+ friend class FolderWatcherPrivate;
+ };
+ }
+diff --git a/test/testfolderwatcher.cpp b/test/testfolderwatcher.cpp
+index d90856828..b5dba5fbc 100644
+--- a/test/testfolderwatcher.cpp
b/test/testfolderwatcher.cpp
+@@ -140,6 +140,19 @@ private slots:
+ QVERIFY(waitForPathChanged(file));
+ }
+
++void testMove3LevelDirWithFile() {
++QString file(_rootPath + "/a0/b/c/empty.txt");
++mkdir(_rootPath + "/a0");
++mkdir(_rootPath + "/a0/b");
++mkdir(_rootPath + "/a0/b/c");
++touch(file);
++QString cmd = QString("mv " + _rootPath + "/a0 " + _rootPath + "/a");
++qDebug() << "Command: " << cmd;
++system(cmd.toLocal8Bit());
++QVERIFY(waitForPathChanged(_rootPath + "/a/b/c/empty.txt"));
++}
++
++
+ void testCreateADir()
Bug#928345: unblock: akonadi/4:18.08.3-5
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package akonadi
Akonadi uses a working database to store all data. Mariadb moved
binaries between mariadb-server-10.3 and mariadb-server-core-10.3, that
made mariadb-server-core-10.3 unfit to be used from Akonadi. To solve
this temporarily Akonadi depends on default-mysql-server with
4:18.08.3-2.
Mariadb has now solved #910902 and 1:10.3.14-1 entered testing, now
mariadb-server-core-10.3 is good enough for Akonadi to start from a fresh
installation. When Akonadi still would depend on mariadb-server-10.3
a not needed database would spin up system wide.
unblock akonadi/4:18.08.3-5
diff -Nru akonadi-18.08.3/debian/changelog
akonadi-18.08.3/debian/changelog
--- akonadi-18.08.3/debian/changelog2019-02-14 21:07:51.0
+0100
+++ akonadi-18.08.3/debian/changelog2019-04-29 16:24:10.0
+0200
@@ -1,3 +1,13 @@
+akonadi (4:18.08.3-5) unstable; urgency=medium
+
+ * Team upload.
+
+ [ Sandro Knauß ]
+ * Switch back to use default-mysql-server-core instead of default-
+mysql-server as dependency (see #910902).
+
+ -- Sandro Knauß Mon, 29 Apr 2019 16:24:10 +0200
+
akonadi (4:18.08.3-4) unstable; urgency=medium
* Team upload.
diff -Nru akonadi-18.08.3/debian/control
akonadi-18.08.3/debian/control
--- akonadi-18.08.3/debian/control 2019-02-05
00:11:57.0 +0100
+++ akonadi-18.08.3/debian/control 2019-04-29
16:07:26.0 +0200
@@ -47,7 +47,7 @@
Section: misc
Architecture: all
Depends: default-mysql-client-core | virtual-mysql-client-core,
- default-mysql-server | virtual-mysql-server,
+ default-mysql-server-core | virtual-mysql-server-core,
libqt5sql5-mysql,
${misc:Depends},
Recommends: akonadi-server
-- System Information:
Debian Release: 10.0
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 4.19.0-4-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#924882: unblock: kaddressbook/4:18.08.3-3
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Control: block 910731 by -1
Please unblock package kaddressbook
The version of KAddressbook in testing is not usable without installing
Akonadi by hand (#910731). The missing dependency is fixed in 4:18.08.3-3 that
already is for 11 days in unstable.
I'll attach the debdiff of 4:18.08.3-1 vs 4:18.08.3-3.
unblock kaddressbook/4:18.08.3-3
-- System Information:
Debian Release: buster/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 4.19.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=en_US
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru kaddressbook-18.08.3/debian/changelog
kaddressbook-18.08.3/debian/changelog
--- kaddressbook-18.08.3/debian/changelog 2019-02-04 16:02:34.0
+0100
+++ kaddressbook-18.08.3/debian/changelog 2019-03-06 20:44:34.0
+0100
@@ -1,3 +1,26 @@
+kaddressbook (4:18.08.3-3) unstable; urgency=medium
+
+ * Team upload.
+
+ [ Sandro Knauß ]
+ * Fix "unnecessary Depends: kdepim-addons, missing Depends: kdepim-
+runtime" (Closes: #923863)
+
+ -- Sandro Knauß Wed, 06 Mar 2019 20:44:34 +0100
+
+kaddressbook (4:18.08.3-2) unstable; urgency=medium
+
+ * Team upload.
+
+ [ Sandro Knauß ]
+ * Add akonadi-server to Depdends, kaddressbook needs a
+running Akonadi server to be usable. (Closes: #910731)
+ * Add kdepim-runtime to depdends, as without akonadi server
+is missing resources.
+ * Add kdepim-addons to Suggests.
+
+ -- Sandro Knauß Tue, 05 Mar 2019 01:06:29 +0100
+
kaddressbook (4:18.08.3-1) unstable; urgency=medium
* Team upload.
diff -Nru kaddressbook-18.08.3/debian/control
kaddressbook-18.08.3/debian/control
--- kaddressbook-18.08.3/debian/control 2019-01-23 01:08:05.0 +0100
+++ kaddressbook-18.08.3/debian/control 2019-03-06 20:41:18.0 +0100
@@ -42,10 +42,13 @@
Architecture: any
Breaks: kontact (<< 4:16.11), ${kde-l10n:all}
Replaces: kontact (<< 4:16.11), ${kde-l10n:all}
-Depends: libkf5akonadisearch-bin,
+Depends: akonadi-server,
+ kdepim-runtime,
+ libkf5akonadisearch-bin,
libkf5akonadisearch-plugins,
${misc:Depends},
${shlibs:Depends},
+Recommends: kdepim-addons
Description: address book and contact data manager
KAddressBook enables you to manage your contacts efficiently and comfortably.
It can load and save your contacts to many different locations, including
Bug#909288: transition: kdepim 18.08
Hey Emilio, > This transition is blocked on blogilo. blogilo is a offline blogpost editor for CMS like wordpress choqok is micro-blogging client for things like twitter IMO choqok is not a replacement for blogilo. blogilo in is dead by upstream since 17.08. and pino made it compiling for 17.12. But now with 18.08 there are more issues get it compiling. I filed a bug against blogilo that it can't be compiled with new 18.08 [#908869]. I recommend to delete blogilo from testing. Do I need to file a own RM request or is [#908869] enough for you to delete it from testing? > Does that mean that blogilo has been superseeded by choqok? If so, should > blogilo be turned into an empty transitional package? I don't think that make sense. > Also any chance you can look at uploading kopete/exp with a fix for the new > libmediastreamer (patch in #890606) to sid? That would help in two > transitions. I'm not into kopete that much. With 18.04 it is KF5 based, so it might be very unstable, why pino descided it to push it to experimental. But we should move this discussion to pkg-kde-t...@lists.alioth.debian.org. As it is not related to the KDEPIM transistion. hefee signature.asc Description: This is a digitally signed message part.
Bug#909288: transition: kdepim 18.08
Hey Emilio, I uploaded kmailtransport_18.08.1-2 that should build on more archs (as it makes libkgapi optional). hefee @pino sorry - I forgotten to pull before starting to work, so your updates are not included in the -2. signature.asc Description: This is a digitally signed message part.
Bug#909288: transition: kdepim 18.08
Hey, > kmailtransport and other packages are in bd-uninst and outdated on several > architectures because they need libkgapi which is blocked on the lack of > qtwebengine5. So either one of those get an optional build-dep so things can > build, or we'll need partial removals from the affected architectures. Can > you look into it? Okay so far as I followed the dependency graphs [1,2] thos bd-unist camoe from the new dependency between libkgapi -> kmailtransport. I think it is save to remove the parts in kmailptransport that are libkgapi dependent, as this only handles the cases, when use want to send a mail via gmail/XAUTH2, where you really need libkgapi. I'll try to upload a patch the next days. But I'm busy next week with sowing rye. But it should not be that difficult to make two blocks optional in plugins/smtp/smtpjob.cpp. hefee [1] https://qt-kde-team.pages.debian.net/images/pim-build-deps-17.12.png [2] https://qt-kde-team.pages.debian.net/images/pim-build-deps-18.08.png signature.asc Description: This is a digitally signed message part.
Bug#909288: transition: kdepim 18.08
Hey, after the first archs have compiled complete kde pim 18.08. Now several packages needs to get recompiled against the new kdepim, they needs to get rebuilt on any architecture: nmu ktorrent . ANY . -m 'Rebuild against kdepim 18.08.1' dw ktorrent . ANY . -m 'libkf5syndication-dev (>= 18.08.0~)' nmu kio-gdrive . ANY . -m 'Rebuild against kdepim 18.08.1' dw kio-gdrive . ANY . -m 'libkpimgapi-dev (>= 18.08.0~)' nmu kjots . ANY . -m 'Rebuild against kdepim 18.08.1' dw kjots . ANY . -m 'libkf5akonadi-dev (>= 4:18.08.0~), libkf5akonadinotes-dev (>= 18.08.0~), libkf5pimtextedit-dev (>= 18.08.0~)' nmu zanshin . ANY . -m 'Rebuild against kdepim 18.08.1' dw zanshin . ANY . -m 'libkf5akonadicalendar-dev (>= 4:18.08.0~), libkf5akonadicontact-dev (>= 4:18.08.0~), libkf5akonadinotes-dev (>= 4:18.08.0~), libkf5akonadisearch-dev (>= 4:18.08.0~), libkf5identitymanagement-dev (>= 18.08.0~), libkf5kontactinterface-dev (>= 18.08.0~), libkf5ldap-dev (>= 18.08.0~)' nmu digikam . ANY . -m 'Rebuild against kdepim 18.08.1' dw digikam . ANY . -m 'libkf5calendarcore-dev (>= 4:18.08.0~)' nmu kraft . ANY . -m 'Rebuild against kdepim 18.08.1' dw kraft . ANY . -m 'libkf5akonadi-dev (>= 4:18.08.0~), libkf5akonadicontact-dev (>= 4:18.08.0~)' hefee signature.asc Description: This is a digitally signed message part.
Bug#909288: transition: kdepim 18.08
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition KDE Pim 18.08 has updated ist API and ABI, that makes it nessasary to bump some ABIs. Most of the packages, that needs to be rebuild are inside KDE Pim itself so only following "external" packages are affected: ktorrent kio-gdrive blogilo kjots zanshin digikam kraft (calligraplan) I build all rdepends and I have only two issues: * blogilo has fallen out of KDE Pim can't be build anymore [#908869] * calligraplan depend on the build packages, but the features that use KDE Pim are disabled, so no need to build them within the transition. This transistion includes/replaces following auto detected transitions: auto-akonadi auto-kalarmcal auto-kcalcore auto-kdav auto-kf5-messagelib auto-kldap auto-kpimtextedit auto-ksmtp auto-libkf5eventviews auto-libkf5gravatar auto-libkf5mailcommon auto-libkf5pimcommon auto-libkgapi auto-syndication These 15 transitions share nearly all rdepdens. I don't see any blocker from my side, to wait. hefee -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.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#902263: Bug#905559: Bug#902263: Affecting Qt transition
Hey, > That's totally understandable from your part. Now the test has clearly > failed. The regression could either be in Qt or in some part of the KDE PIM > stack (not the meta package). ktexteditor is KDE Frameworks and not KDE PIM. For KDE PIM the argument of not being up-to-date and not being ready for Qt 5.11 may be/is valid. But Framworks is uptodate with 5.47 (released in June) and it should be Qt 5.11 ready - So you should considering filing a bug about this regression upstream. hefee signature.asc Description: This is a digitally signed message part.
Bug#894342: transition: kdepim
Control: block -1 by 894913 Hey, anbe found a missing breaks/replaces this time with -dev packages (# 894913). I uploaded a fixed kapptemplate and Akonadi, so users can install both. And add a breaks/replace to Akonadi. hefee -- On Mittwoch, 4. April 2018 15:49:27 CEST Emilio Pozuelo Monfort wrote: > On 04/04/18 15:12, Sandro Knauß wrote: > > Hey, > > > > everything has been rebuilt and the transition is mostly green. > > > > I don't know if the transition will enter testing successfully without > > requesting RM for libkolab before. libkolab is dead, so RM for sid and > > testing is suitable. But as libkolab is currently needed for > > kdepim-runtime 17.08.3 is should not be removed before kdepim 17.12.3 > > enters testing. > > Please file an RM bug against ftp.debian.org. It shouldn't be removed from > testing until the transition happens, so that's not a problem. > > > The other package not recompiled for kdepim 17.12.3 is digikam, if that > > blocks the transition to testing make a temporarily remove in testing. > > The maintainer of digikam suggested this and will upload a new version in > > the next days... > > > > As I forgot one move I needed to update kdepim-addons 17.12.3-2. It failed > > for armhf . I rebuild on a porterbox (abel.d.o) without any issue. So it > > should just rebuilt for armhf. > > > > gb kdepim-addons . armhf > > Given back. > > > As the kdepim transition blocking Qt transition I added lisandro to CC > > list. Maybe after rebuilding kdepim-addons successfully on armhf we do an > > aging to not block Qt transition. > > I will consider that. > > Cheers, > Emilio signature.asc Description: This is a digitally signed message part.
Bug#894342: transition: kdepim
Hey, everything has been rebuilt and the transition is mostly green. I don't know if the transition will enter testing successfully without requesting RM for libkolab before. libkolab is dead, so RM for sid and testing is suitable. But as libkolab is currently needed for kdepim-runtime 17.08.3 is should not be removed before kdepim 17.12.3 enters testing. The other package not recompiled for kdepim 17.12.3 is digikam, if that blocks the transition to testing make a temporarily remove in testing. The maintainer of digikam suggested this and will upload a new version in the next days... As I forgot one move I needed to update kdepim-addons 17.12.3-2. It failed for armhf . I rebuild on a porterbox (abel.d.o) without any issue. So it should just rebuilt for armhf. gb kdepim-addons . armhf As the kdepim transition blocking Qt transition I added lisandro to CC list. Maybe after rebuilding kdepim-addons successfully on armhf we do an aging to not block Qt transition. hefee -- On Montag, 2. April 2018 00:45:18 CEST Emilio Pozuelo Monfort wrote: > On 02/04/18 00:39, Emilio Pozuelo Monfort wrote: > > On 01/04/18 16:14, Sandro Knauß wrote: > >> Hey, > >> > >> after uploading kdepim, the buildds had built KDE Pim 17.12.3 > >> successfully for amd64 and i386 (other archs are still building). > >> > >> Now we needs some binNMUs. I don't know, do I need to use a separate bug > >> for those requests or is it the correct way to file the wb actions just > >> here inside the transition bug? > >> > >> KGPG need to recompiled too as Akonadi has/had some issues with building > >> on many archs (because of the dep to python). So KGPG got compiled > >> against the old kdepim 17.08, just amd64 and armel were fast enough. > >> Still archs do not built kdepim completely, so the BD are not available > >> on the archs yet, so you may want to set dep-wait for those packages.>> > >> nmu kgpg_17.12.3-1 . ANY -amd64 -armel . -m 'rebuilt against kdepim > >> 17.12.3' dw kgpg_17.12.3-1 . ANY -amd64 -armel . -m > >> 'libkf5akonadicontact-dev (>= 4:17.12.3~)'>> > >> and kjots and zanshin needs to get rebuilt. As those are not inside > >> kdepim, they needs to get rebuilt on any architecture.>> > >> nmu kjots_5.0.2-1 . ANY . -m 'rebuilt against kdepim 17.12.3' > >> dw kjots_5.0.2-1 . ANY . -m 'libkf5akonadinotes-dev (>= 4:17.12.3~), > >> libkf5kontactinterface-dev (>= 17.12.3~)' nmu zanshin_5.0-1 . ANY . -m > >> 'rebuilt against kdepim 17.12.3' > >> dw zanshin_5.0.-1 . ANY . -m 'libkf5akonadicalendar-dev (>= 4:17.12.3~)' > > > > Scheduled. > > BTW I had to fix all your commands because of the bad versions... Next time > try to get them right, or don't specify the version at all (it's optional). > > Emilio signature.asc Description: This is a digitally signed message part.
Bug#894342: transition: kdepim
Hey, Thanks a lot! > BTW I had to fix all your commands because of the bad versions... Next time > try to get them right, or don't specify the version at all (it's optional). sorry - I do not have written a lot of them. But I thought I need to specify a version, as in the docu[1] it is not mentioned as optional. Btw. is there a tool to help writing them and check those cmds? hefee [1] https://release.debian.org/wanna-build.txt signature.asc Description: This is a digitally signed message part.
Bug#894342: transition: kdepim
Hey, after uploading kdepim, the buildds had built KDE Pim 17.12.3 successfully for amd64 and i386 (other archs are still building). Now we needs some binNMUs. I don't know, do I need to use a separate bug for those requests or is it the correct way to file the wb actions just here inside the transition bug? KGPG need to recompiled too as Akonadi has/had some issues with building on many archs (because of the dep to python). So KGPG got compiled against the old kdepim 17.08, just amd64 and armel were fast enough. Still archs do not built kdepim completely, so the BD are not available on the archs yet, so you may want to set dep-wait for those packages. nmu kgpg_17.12.3-1 . ANY -amd64 -armel . -m 'rebuilt against kdepim 17.12.3' dw kgpg_17.12.3-1 . ANY -amd64 -armel . -m 'libkf5akonadicontact-dev (>= 4:17.12.3~)' and kjots and zanshin needs to get rebuilt. As those are not inside kdepim, they needs to get rebuilt on any architecture. nmu kjots_5.0.2-1 . ANY . -m 'rebuilt against kdepim 17.12.3' dw kjots_5.0.2-1 . ANY . -m 'libkf5akonadinotes-dev (>= 4:17.12.3~), libkf5kontactinterface-dev (>= 17.12.3~)' nmu zanshin_5.0-1 . ANY . -m 'rebuilt against kdepim 17.12.3' dw zanshin_5.0.-1 . ANY . -m 'libkf5akonadicalendar-dev (>= 4:17.12.3~)' hefee signature.asc Description: This is a digitally signed message part.
Bug#894342: transition: kdepim
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition KDE Pim 17.12 has updated ist API and ABI, that makes it nessasary to bump some ABIs. To track those ABI breakages, we updated the package names to 5abi1. So far most of the packages, that needs to be rebuild are inside KDE Pim itself so only following "external" packages are affected: blogilo digikam kjots libkolab zanshin (calligra, calligraplan) I build all rdepends and came to the conclusion: * kjots and zanshin build nicely with the new KDE Pim * blogilo has fallen out of KDE Pim can't be build anymore -> RM request * libkolab do not build anymore with KDE Pim 17.12 it is dead upstream and not needed anymore for KDE Pim -> RM request [1] * digikam is not ready for KDE Pim 17.12 (see #893515) the mantainer told me in private: " My suggestion is: go ahead with the upload to unstable. I should be able to get digikam uploaded very shortly thereafter." * calligra and calligraplan depdend on the build pacakges, but the featueres that use KDE Pim are disabled, so no need to build them within the transition. This transistion includes/replaces following auto detected transitions: auto-akonadi-calendar auto-akonadi auto-kcalcore auto-kdav auto-kmime auto-kpimtextedit auto-libkf5calendarsupport auto-libkf5gravatar auto-libkf5incidenceeditor auto-libkf5mailcommon auto-libkf5pimcommon These 11 transistions share nearly all rdepdens, that's why I think it is easier to track it in only one transistion and not within 11. But if you belive it is easier to have saperate ones, please tell me. I look at all, and all look correcty so far, but IMO it is not easy keep an overview. After KDE Frameworks 5.44 entered testing successfully, there is no blocker anymore for starting this transition. Please tell me additionally, if I need to request the RMs in advanced or while the transition is going on. hefee [1] https://lists.alioth.debian.org/pipermail/pkg-kolab-devel/2018-March/003733.html Ben file: title = "kdepim"; is_affected = .build-depends ~ /\b(libkf5calendarcore\-dev|libkpimkdav\-dev|libkf5pimtextedit\-dev|libkf5mime\-dev|libkf5calendarsupport\-dev|libkf5gravatar\-dev|libkf5incidenceeditor\-dev|libkf5mailcommon\-dev|libkf5pimcommon\-dev|libkf5akonadi\-dev|libkf5akonadiserver\-dev|libkf5akonadicalendar\-dev)\b/; is_good = .depends ~ /\b(libkf5calendarcore5abi1|libkpimkdav5abi1|libkf5pimtextedit5abi1|libkf5mime5abi1|libkf5calendarsupport5abi1|libkf5gravatar5abi1|libkf5incidenceeditor5abi1|libkf5mailcommon5abi1|libkf5pimcommon5abi1|libkf5akonadicore5abi1|libkf5akonadiprivate5abi1|libkf5akonadiwidgets5abi1|libkf5akonadicalendar5abi1)\b/; is_bad = .depends ~ /\b(libkf5calendarcore5|libkpimkdav5|libkf5pimtextedit5|libkf5mime5|libkf5calendarsupport5|libkf5gravatar5|libkf5incidenceeditor5|libkf5mailcommon5|libkf5pimcommon5|libkf5akonadicore5|libkf5akonadiprivate5|libkf5akonadiwidgets5|libkf5akonadicalendar5)\b/; -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.15.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#892608: nmu: kjots_4:5.0.2-1
Hey, > That's not the problem. > The symbol _ZN7Akonadi3Job16doHandleResponseExRKNS_8Protocol7CommandE > has been removed from libakonadicore5 without bumping the SONAME. I know, we made an mistake and also fixed this, by using Debian ABI Manager and doing proper transitions in future. As you can see there is a new version of Akonadi waiting in NEW queue with ABI bumping [1]. Unfortunately it will take a while till this version will reach users as NEW queue takes time. So please see this nmu request as a intermediate step so users can reuse kjots again. hefee [1] https://ftp-master.debian.org/new/akonadi_4:17.12.2-1.html signature.asc Description: This is a digitally signed message part.
Bug#892608: nmu: kjots_4:5.0.2-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu Hello, Due to a mistake, Akonadi was uploaded with a new symbol but without tracking the ABI breakage. We also have a bug report that documenting the ABI breakage: #885620. That's why kjots needs to be recompiled against the new Akonadi version. Please rebuild kjots against Akonadi 4:17.08.3-2 to bump its dependency on libkf5akonadi*. As it is my first binNMU request, there may be mistakes in the request. If there are any questions, please feel free to ask. nmu kjots_4:5.0.2-1 . ANY . unstable . -m "Rebuild against Akonadi 17.08.3 (Closes: #885620)" -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.15.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#887507: stretch-pu: package roundcube/1.2.3+dfsg.1-4+deb9u1
Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu
Hey,
upstream releases only bugfix releases for the 1.2 branch. As they,
do not add any new feature IMO it would makes sense to ship the newest
1.2.7 for Debian Stretch users. This is a prepackage request, I havn't
packaged 1.2.7 for Debian yet, as I would only put effort into it, if it
can enter stretch in principal. What I can present at the current state
is a diff of the upstream tarballs (excluded the minified files, cause
we create those in the packageing process itself). I don't expect any
changes in the debian folder itself, but I would present a complete
debdiff, if you approved the general idea of shipping 1.2.7 via pu.
Regards,
sandro
-- System Information:
Debian Release: buster/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500,
'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.14.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 -ru -x '*.min.js' -x '*.min.css' roundcubemail-1.2.3/bin/installto.sh
roundcubemail-1.2.7/bin/installto.sh
--- roundcubemail-1.2.3/bin/installto.sh2016-11-27 17:08:57.0
+0100
+++ roundcubemail-1.2.7/bin/installto.sh2017-11-08 19:52:27.0
+0100
@@ -42,7 +42,6 @@
$input = trim(fgets(STDIN));
if (strtolower($input) == 'y') {
- $err = false;
echo "Copying files to target location...";
// Save a copy of original .htaccess file (#1490623)
@@ -56,16 +55,16 @@
}
foreach ($dirs as $dir) {
// @FIXME: should we use --delete for all directories?
-$delete = in_array($dir, array('program', 'installer')) ? '--delete ' : '';
-if (!system("rsync -avC " . $delete . INSTALL_PATH . "$dir/*
$target_dir/$dir/")) {
- $err = true;
- break;
+$delete = in_array($dir, array('program', 'installer')) ? '--delete ' :
'';
+$command = "rsync -aC --out-format \"%n\" " . $delete . INSTALL_PATH .
"$dir/* $target_dir/$dir/";
+if (!system($command, $ret) || $ret > 0) {
+ rcube::raise_error("Failed to execute command: $command", false, true);
}
}
foreach
(array('index.php','.htaccess','config/defaults.inc.php','composer.json-dist','CHANGELOG','README.md','UPGRADING','LICENSE','INSTALL')
as $file) {
-if (!system("rsync -av " . INSTALL_PATH . "$file $target_dir/$file")) {
- $err = true;
- break;
+$command = "rsync -a --out-format \"%n\" " . INSTALL_PATH . "$file
$target_dir/$file";
+if (file_exists(INSTALL_PATH . $file) && (!system($command, $ret) || $ret
> 0)) {
+ rcube::raise_error("Failed to execute command: $command", false, true);
}
}
@@ -96,13 +95,12 @@
echo "done.\n\n";
}
- if (!$err) {
-echo "Running update script at target...\n";
-system("cd $target_dir && php bin/update.sh --version=$oldversion");
-echo "All done.\n";
- }
+ echo "Running update script at target...\n";
+ system("cd $target_dir && php bin/update.sh --version=$oldversion");
+ echo "All done.\n";
}
-else
+else {
echo "Update cancelled. See ya!\n";
+}
?>
diff -ru -x '*.min.js' -x '*.min.css' roundcubemail-1.2.3/CHANGELOG
roundcubemail-1.2.7/CHANGELOG
--- roundcubemail-1.2.3/CHANGELOG 2016-11-27 17:08:57.0 +0100
+++ roundcubemail-1.2.7/CHANGELOG 2017-11-08 19:52:27.0 +0100
@@ -1,6 +1,61 @@
CHANGELOG Roundcube Webmail
===
+RELEASE 1.2.7
+-
+- Fix rewind(): stream does not support seeking (#5950)
+- Fix bug where HTML messages could have been rendered empty on some systems
(#5957)
+- Fix (again) bug where image data URIs in css style were treated as
evil/remote in mail preview (#5580)
+- Managesieve: Fix parsing dot-staffed lines in multiline text (#5838, #5959)
+- Fix file disclosure vulnerability caused by insufficient input validation
[CVE-2017-16651] (#6026)
+
+RELEASE 1.2.6
+-
+- Don't ignore (global) userlogins/sendmail logging in per_user_logging mode
+- Enigma: Fix compatibility with assets_dir
+- Managesieve: Fix AM/PM suffix in vacation time selectors
+- Fix bug where comment notation within style tag would cause the whole style
to be ignored (#5747)
+- Fix bug where it wasn't possible to scroll folders list in Edge (#5750)
+- Fix addressbook searching by gender (#5757)
+- Fix SQL syntax error on MariaDB 10.2 (#5774)
+- Fix bug where it wasn't possible to set timezone to auto-detected value
(#5782)
+- Fix uninitialized string offset in rcube_utils::bin2ascii() and make sure
rcube_utils::random_bytes() result has always requested length (#5788)
+- Fix potential XSS vulnerability with malformed HTML message markup
+
+RELEASE
Re: kdepim 17.08.3 and kde-l10n
Hey, I added the release team list, cause they may help explaining interpret the britney output. And help to find the right buttons to push, to get kdepim migrating to testing. > > I tried to understand, why kdepim hasn't moved to testing, but I don't > > understand the britney output completely. > > I don't either, but let's see. well I looked at the documentation to understand the output better: https://release.debian.org/doc/britney/short-intro-to-migrations.html But still I'm not completely sure how to interpret the output :D If I'm not wrong, than the first try to install complete kdepim as one set is the one we should care about: trying: kleopatra libkf5libkleo kmail-account-wizard libkf5pimcommon akonadi-contacts kf5-kdepim-apps-libs kaddressbook akonadi-search akonadi-mime libkf5mailcommon pim-data-exporter libkf5libkdepim libkf5eventviews libkf5calend arsupport kholidays kalarmcal kcalcore kdepim-runtime kmbox kmime kf5-messagelib kmailtransport akonadi-import-wizard kdepim-addons kimap kpimtextedit kidentitymanagement mbox-importer korganizer kcontacts ktnef kcalutils libkol ab akonadi kalarm kmail libkf5ksieve libkf5gravatar -kdepim kldap syndication kblog akregator libkf5grantleetheme kontact pim-sieve-editor libkf5incidenceeditor akonadi-calendar blogilo knotes akonadi-calendar-tools libkf5mailim porter akonadi-notes akonadiconsole libkgapi skipped: kleopatra libkf5libkleo kmail-account-wizard libkf5pimcommon akonadi-contacts kf5-kdepim-apps-libs kaddressbook akonadi-search akonadi-mime libkf5mailcommon pim-data-exporter libkf5libkdepim libkf5eventviews libkf5calen darsupport kholidays kalarmcal kcalcore kdepim-runtime kmbox kmime kf5-messagelib kmailtransport akonadi-import-wizard kdepim-addons kimap kpimtextedit kidentitymanagement mbox-importer korganizer kcontacts ktnef kcalutils libko lab akonadi kalarm kmail libkf5ksieve libkf5gravatar -kdepim kldap syndication kblog akregator libkf5grantleetheme kontact pim-sieve-editor libkf5incidenceeditor akonadi-calendar blogilo knotes akonadi-calendar-tools libkf5maili mporter akonadi-notes akonadiconsole libkgapi (6, 1706, 170) got: 39+0: a-2:i-24:a-0:a-0:a-0:m-0:m-3:m-0:p-0:s-10 * s390x: education-desktop-kde, kde-full, kde-standard, kdepim, kf5-kdepimlibs-kio-plugins, knotes, konsolekalendar, korganizer, task-pkgs-are-installable-faux - splitting the component into single items and retrying them If I compare the trying line with all packages inside kdepim i see, that grantlee-editor, kdav, kgpg and kontactinterface are missing in that list. kdav is already migrated. From kgpg and grantlee-editor nothing depends on, so we can skip them. The only missing package we care at this migration is kontactinterface, that explains, why korganizer, knotes will be uninstallable in testing. Maybe it is easier to see these dependencies in graphs: https://pkg-kde.alioth.debian.org/applications-17.08-build-deps.html Because both depend on kontactinterface. And because korganzier >= 17.08 won't be in testing konsolecalender can't migrate, because it breaks against korganzier <= 17.08. education-desktop-kde, kde-full, kde-standard look fine for me, possible, because of korganzier and knotes not migrating having issues. kdepim, kf5-kdepimlibs-kio-plugins both getting unstallable is fine, cause they should be removed form testing. Keep in mind I only added here some of the britney output for kdepim, the two other samples are part of the "splitting the component into single items and retrying them", maybe those are not fine to look at... > > For me it looks that we missed the removals for armhf. Only armhf have > > conflicting packages like: > > > > trying: kdepim-addons > > skipped: kdepim-addons (0, 2784, 136) > > > > got: 31+0: a-2:i-24:a-0:a-0:a-1:m-0:m-3:m-0:p-0:s-1 > > * armhf: kdepim-addons > > This does not tell me anything. > > > trying: libkolab > > skipped: libkolab (0, 2762, 158) > > > > got: 47+0: a-2:i-24:a-0:a-0:a-17:m-0:m-3:m-0:p-0:s-1 > > * armhf: education-desktop-kde, kde-full, kde-standard, kdepim, > > kdepim-runtime, kmail, knotes, konsolekalendar, kontact, korganizer, > > libkolab-dev, libkolab1, python-kde4, python-kolab, python3-kolab, > > python3-pykde4, task-pkgs-are-installable-faux > Ditto, although this gives me two hints: > - pykde4 will migrate tomorrow > -
Bug#879599: stretch-pu: package charmtimetracker/1.11.4-1
Hey, > You definitely can't re-upload +deb9u1, no. It's up to you whether you > consider it worth a new upload now, or just want to correct it in your > VCS ready for whenever you next need to upload. (I'd generally suggest > the latter.) me also thinks it is not worth uploading again a version with only these changes. Fixed them in VCS already. > The above output is from running lintian (on the ftp-master mirror) > against the package you uploaded. If it didn't tell you when running it > locally, maybe you somehow didn't run it against all the files? (Or have > an old version?) okay running against sources.changes excludes the changelog. when running against a amd64.changes I see the issues, too. Best Reagrds, sandro signature.asc Description: This is a digitally signed message part.
Bug#879599: stretch-pu: package charmtimetracker/1.11.4-1
Hey, > Apologies for not having spotted them pre-upload, but for reference our > QA checks spotted a couple of typoes in the changelog: > > +W: spelling-error-in-changelog discription description > +W: spelling-error-in-changelog pacakge package okay thx. So I need to fix those and upload a debian/1.11.4-1+deb9u2? or can i reupload deb9u1? Are those automated testes? Why doesn't have linitian told me those? It already warns me about many other typos... Best Regrads, sandro signature.asc Description: This is a digitally signed message part.
Bug#879599: stretch-pu: package charmtimetracker/1.11.4-1
Control: tags -1 - moreinfo > > You also introduced a new issue in the short description: > > -Description: Cross-Platform Time Tracker > +Description: a task based Time Tracker > > The convention is that the description can finish the sentence > "$package (is a|contains)". > I note that #873917 isn't fixed in unstable currently. I realise it's a > trivial change, but we should still ensure that such things are fixed > in unstable, so as not to regress between releases. Well because #873917 is quite trivial i don't want to push a new version with only this patch to unstable. I have nothing more to fix for charmtimetracker at my list at the moment for unstable. I thought it also makes sense to fix the description in pu, but if this adds more issues than solving it, than maybe remove it from pu. I was also wondering: if I change the description then the translations needs to be updated. Does the system behind the translations can handle this? Or are the translations fixed for stretch? Should I rework the description for unstable and pu? And/or remove it from the pu? If you want me first to upload the fix to unstable, I'll do this. I'm happy with all ways :) Best Regards, sandro signature.asc Description: This is a digitally signed message part.
Bug#879599: stretch-pu: package charmtimetracker/1.11.4-1
Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu
Hey,
charmtimetracker is currently not installable in stable (#873918), this
pu fixes this. Additionally I also fixed #873917, to have a better
wording in the short discription. I made sure, that it still builds for stable
on amd64.
Best Regards,
sandro
-- System Information:
Debian Release: buster/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500,
'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.13.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)
diff -Nru charmtimetracker-1.11.4/debian/changelog
charmtimetracker-1.11.4/debian/changelog
--- charmtimetracker-1.11.4/debian/changelog2016-11-10 09:33:30.0
+0100
+++ charmtimetracker-1.11.4/debian/changelog2017-10-23 11:20:46.0
+0200
@@ -1,3 +1,12 @@
+charmtimetracker (1.11.4-1+deb9u1) stretch; urgency=medium
+
+ * Fix "Missing binary dependency on libqt5sql5-sqlite" (Closes: #873918)
+- Adding libqt5sql5-sqlite to depends list of charmtimetracker.
+ * Fix "Please drop "Cross-Platform" from package description" rewrite
+discription for the pacakge (Closes: #873917)
+
+ -- Sandro Knauß <he...@debian.org> Mon, 23 Oct 2017 11:20:46 +0200
+
charmtimetracker (1.11.4-1) unstable; urgency=medium
[ Sandro Knauß ]
diff -Nru charmtimetracker-1.11.4/debian/control
charmtimetracker-1.11.4/debian/control
--- charmtimetracker-1.11.4/debian/control 2016-11-10 09:27:15.0
+0100
+++ charmtimetracker-1.11.4/debian/control 2017-10-23 11:20:46.0
+0200
@@ -20,8 +20,8 @@
Package: charmtimetracker
Architecture: any
-Depends: ${misc:Depends}, ${shlibs:Depends}
-Description: Cross-Platform Time Tracker
+Depends: libqt5sql5-sqlite, ${misc:Depends}, ${shlibs:Depends}
+Description: a task based Time Tracker
It is built around two major ideas - tasks and events.
Tasks are the things time is spend on, repeatedly. Tasks
are done in events.
Bug#869573: Bug#869577: stretch-pu: package kf5-messagelib/4:16.04.3-3
Hello security team, just for you to mention the bug: 869573 when updated will fix CVE-2017-9604 for jessie. and the bugs 869574 869577 will fix CVE-2017-9604 for stretch. I saw at [1] that I've forgotten to send you this message. See the discussion on 864804, why this is handled via pu. Best Regards, sandro [1] https://security-tracker.debian.org/tracker/CVE-2017-9604 -- On Dienstag, 22. August 2017 21:18:23 CEST Adam D. Barratt wrote: > Control: tags -1 + confirmed > > On Mon, 2017-08-21 at 18:04 +0200, Sandro Knauß wrote: > > now I rebuilt the package with the attached debdif on a sbuild -d stretch- > > amd64 and tried kontact under a virtualbox. > > Please go ahead. > > Regards, > > Adam signature.asc Description: This is a digitally signed message part.
Bug#869574: stretch-pu: package kdepim/4:16.04.3-4
Hey,
now I rebuilt the package with the attached debdif on a sbuild -d stretch-
amd64 and tried kontact under a virtualbox.
Best Regards,
sandro
--
On Samstag, 29. Juli 2017 16:16:55 CEST Adam D. Barratt wrote:
> On Sat, 2017-07-29 at 14:24 +0200, Sandro Knauß wrote:
> > Hey,
> >
> > > currently in stretch is 4:16.04.3-3. Thus the version which should
> > > preferably be used would be 4:16.04.3-3+deb9u1.
> >
> > just to understand the process better:
> > * Do I need to send another debdiff with the corrected versionnumber first
> > before uploading?
>
> If by that you mean taking the previously incorrectly generated diff and
> simply changing the version number it contains, then no.
>
> > * Do I need to close this bug within the changelog entry?
>
> No. The bug will be closed by us once the package is actually in stable.
> Until that point, the process is incomplete, so closing the bug would be
> illogical.
>
> > * Are there any further issues with my debdiff?
>
> Besides not being what has been requested multiple times?
>
> The point of the process is to demonstrate that you can build - and have
> built - your proposed upload against the release that you're proposing
> to upload it to and to confirm what the debdiff of the resulting package
> against the target release looks like.
>
> It's entirely possible that it will be the same as the diff between the
> stable and testing packages that you previously provided. That's by no
> means certain, however, and in any case diffing things that aren't what
> you're proposing to upload misses the point of the review step.
>
> This isn't theoretical nitpicking. We've seen there be a distinct
> difference between what people propose and what they actually upload
> enough times in the past that there's no way we'll agree an update based
> on a hypothetical diff rather than an actually built and tested one.
>
> Regards,
>
> Adam
diff -Nru kdepim-16.04.3/debian/changelog kdepim-16.04.3/debian/changelog
--- kdepim-16.04.3/debian/changelog 2016-11-23 14:38:49.0 +0100
+++ kdepim-16.04.3/debian/changelog 2017-06-17 12:12:03.0 +0200
@@ -1,3 +1,13 @@
+kdepim (4:16.04.3-4~deb9u1) stretch; urgency=high
+
+ * Team upload.
+
+ [ Sandro Knauß ]
+ * Fix CVE-2017-9604: Send Later with Delay bypasses OpenPGP (Closes: #864804)
+- Added upstream patch fix-CVE-2017-9604.patch
+
+ -- Sandro Knauß <he...@debian.org> Sat, 17 Jun 2017 12:12:03 +0200
+
kdepim (4:16.04.3-3) unstable; urgency=medium
* Team upload.
diff -Nru kdepim-16.04.3/debian/patches/fix-CVE-2017-9604.patch kdepim-16.04.3/debian/patches/fix-CVE-2017-9604.patch
--- kdepim-16.04.3/debian/patches/fix-CVE-2017-9604.patch 1970-01-01 01:00:00.0 +0100
+++ kdepim-16.04.3/debian/patches/fix-CVE-2017-9604.patch 2017-06-17 12:12:03.0 +0200
@@ -0,0 +1,62 @@
+From 78c5552be2f00a4ac25bd77ca39386522fca70a8 Mon Sep 17 00:00:00 2001
+From: Montel Laurent <mon...@kde.org>
+Date: Fri, 2 Jun 2017 13:59:02 +0200
+Subject: Make sure that we use plugin when we use sendlater feature
+
+---
+ kmail/editor/kmcomposerwin.cpp | 9 +
+ kmail/editor/kmcomposerwin.h | 3 ++-
+ 2 files changed, 7 insertions(+), 5 deletions(-)
+
+--- a/kmail/editor/kmcomposerwin.cpp
b/kmail/editor/kmcomposerwin.cpp
+@@ -2376,7 +2376,7 @@ void KMComposerWin::printComposeResult(K
+ }
+
+ void KMComposerWin::doSend(MessageComposer::MessageSender::SendMethod method,
+- MessageComposer::MessageSender::SaveIn saveIn)
++ MessageComposer::MessageSender::SaveIn saveIn, bool willSendItWithoutReediting)
+ {
+ if (mStorageService->numProgressUpdateFile() > 0) {
+ KMessageBox::sorry(this, i18np("There is %1 file upload in progress.",
+@@ -2391,7 +2391,7 @@ void KMComposerWin::doSend(MessageCompos
+ }
+ }
+
+-if (saveIn == MessageComposer::MessageSender::SaveInNone) { // don't save as draft or template, send immediately
++if (saveIn == MessageComposer::MessageSender::SaveInNone || willSendItWithoutReediting) { // don't save as draft or template, send immediately
+ if (KEmailAddress::firstEmailAddress(from()).isEmpty()) {
+ if (!(mShowHeaders & HDR_FROM)) {
+ mShowHeaders |= HDR_FROM;
+@@ -2558,6 +2558,7 @@ void KMComposerWin::slotSendLater()
+ if (!checkRecipientNumber()) {
+ return;
+ }
++mComposerBase->setSendLaterInfo(nullptr);
+ if (mComposerBase->editor()->checkExternalEditorFinished()) {
+ const bool wasRegistered = (SendLater::SendLaterUtil::sentLaterAgentWasRegistered() && SendLater::SendLaterUtil::sentLaterAgentEnabled());
+ if (wasRegistered) {
+@@ -2580,9 +2581,9 @@ void KMComposerWin::slotSendLater()
+ case S
Bug#869577: stretch-pu: package kf5-messagelib/4:16.04.3-3
Hey,
now I rebuilt the package with the attached debdif on a sbuild -d stretch-
amd64 and tried kontact under a virtualbox.
Best Regards,
sandro
--
On Montag, 24. Juli 2017 16:26:22 CEST Adam D. Barratt wrote:
> On 2017-07-24 15:45, Sandro Knauß wrote:
> > Control: tags -1 - moreinfo
> >
> >> We'll need to see a debdiff of the proposed package, built and tested
> >> on
> >> stretch, before going any further, please.
> >
> > The debdiff is the version, that is currently in testing. The diff was
> > created
> > when testing was in deep freeze, so actually the version state, that is
> > now in
> > stretch. The versionnumber may need to be adjusted.
>
> It *will* need to be adjusted. You can't re-upload with a version number
> that's already been used.
>
> Again, what was requested was a debdiff of the actual proposed package,
> not simply the result of comparing the current unstable/testing package
> against stable.
>
> Regards,
>
> Adam
diff -Nru kf5-messagelib-16.04.3/debian/changelog kf5-messagelib-16.04.3/debian/changelog
--- kf5-messagelib-16.04.3/debian/changelog 2016-08-02 14:07:27.0 +0200
+++ kf5-messagelib-16.04.3/debian/changelog 2017-06-17 09:08:12.0 +0200
@@ -1,3 +1,13 @@
+kf5-messagelib (4:16.04.3-3~deb9u1) stretch; urgency=high
+
+ * Team upload.
+
+ [ Sandro Knauß ]
+ * Fix CVE-2017-9604: Send Later with Delay bypasses OpenPGP (Closes: #864803)
+- Added upstream patch fix-CVE-2017-9604.patch
+
+ -- Sandro Knauß <he...@debian.org> Sat, 17 Jun 2017 09:08:12 +0200
+
kf5-messagelib (4:16.04.3-2) unstable; urgency=high
[ Automatic packaging ]
diff -Nru kf5-messagelib-16.04.3/debian/patches/fix-CVE-2017-9604.patch kf5-messagelib-16.04.3/debian/patches/fix-CVE-2017-9604.patch
--- kf5-messagelib-16.04.3/debian/patches/fix-CVE-2017-9604.patch 1970-01-01 01:00:00.0 +0100
+++ kf5-messagelib-16.04.3/debian/patches/fix-CVE-2017-9604.patch 2017-06-17 09:08:12.0 +0200
@@ -0,0 +1,26 @@
+From c54706e990bbd6498e7b1597ec7900bc809e8197 Mon Sep 17 00:00:00 2001
+From: Montel Laurent <mon...@kde.org>
+Date: Fri, 2 Jun 2017 13:56:41 +0200
+Subject: Make sure to sign/encrypt message when we send later
+
+(cherry picked from commit 4048f5e46d0a7d62d93d74fd2861dd70fb2ad660)
+---
+ messagecomposer/src/composer/composerviewbase.cpp | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/messagecomposer/src/composer/composerviewbase.cpp b/messagecomposer/src/composer/composerviewbase.cpp
+index d44b8b2..672ea1e 100644
+--- a/messagecomposer/src/composer/composerviewbase.cpp
b/messagecomposer/src/composer/composerviewbase.cpp
+@@ -468,7 +468,7 @@ void MessageComposer::ComposerViewBase::slotEmailAddressResolved(KJob *job)
+ // if so, we create a composer per format
+ // if we aren't signing or encrypting, this just returns a single empty message
+ bool wasCanceled = false;
+-if (m_neverEncrypt && mSaveIn != MessageComposer::MessageSender::SaveInNone) {
++if (m_neverEncrypt && mSaveIn != MessageComposer::MessageSender::SaveInNone && !mSendLaterInfo) {
+ MessageComposer::Composer *composer = new MessageComposer::Composer;
+ composer->setNoCrypto(true);
+ m_composers.append(composer);
+--
+cgit v0.11.2
+
diff -Nru kf5-messagelib-16.04.3/debian/patches/series kf5-messagelib-16.04.3/debian/patches/series
--- kf5-messagelib-16.04.3/debian/patches/series 2016-08-02 14:07:27.0 +0200
+++ kf5-messagelib-16.04.3/debian/patches/series 2017-06-17 09:08:12.0 +0200
@@ -1,2 +1,3 @@
upstream_add_copying_files.patch
make-it-impossible-to-override-css-settings-from-a-h.patch
+fix-CVE-2017-9604.patch
signature.asc
Description: This is a digitally signed message part.
Bug#869573: jessie-pu: package kdepim/4:4.14.1-1+deb8u1
Hey, > I'm confused. You already followed up to the mail you're quoting with a > debdiff and removed the moreinfo tag. sorry, i overseen that I already answered at you mail. But still the question is, if this is ready for jessie-pu. Best regards, sandro signature.asc Description: This is a digitally signed message part.
Bug#869573: jessie-pu: package kdepim/4:4.14.1-1+deb8u1
Control: tags -1 - moreinfo > We'll need to see a debdiff of the proposed package, built and tested on > jessie, before going any further, please. Mmh this comment I don't understand for this request. As pointed out this debdiff that was also proposed for security upload for jessie. It was built and tested already for the security upload and jessie was already a stable release. So I see not what I should built/test more for pu. Best Regards, sandro signature.asc Description: This is a digitally signed message part.
Bug#869574: stretch-pu: package kdepim/4:16.04.3-4
Hey, > currently in stretch is 4:16.04.3-3. Thus the version which should > preferably be used would be 4:16.04.3-3+deb9u1. just to understand the process better: * Do I need to send another debdiff with the corrected versionnumber first before uploading? * Do I need to close this bug within the changelog entry? * Are there any further issues with my debdiff? Best Regards, sandro signature.asc Description: This is a digitally signed message part.
Bug#869577: Bug#869574: stretch-pu: package kdepim/4:16.04.3-4
Hey, > It *will* need to be adjusted. You can't re-upload with a version number that's already been used. I didn't found the rule for the versionnumbers for pu, that's why I havn't touched them yet [0]. > Is this actually, as requested, a debdiff of the proposed package, or > simply the result of comparing the current unstable/testing package > against stable? As the version in testing and stable only differ in exactly the fix for this CVE, the proposed packages for stretch and the packages in testing are in this case the same. As you look at the debdiffs, it only adds one patch from upstream to fix this issue and adds a new entry in debian/changelog. Nothing that could be stripped out from the debdiff to fix the CVE. Sorry for not making it clear enough in first mail, but it is the first time I request a pu. Regards, sandro [0] https://www.debian.org/doc/manuals/developers-reference/ch05.html#upload-stable signature.asc Description: This is a digitally signed message part.
Bug#869573: jessie-pu: package kdepim/4:4.14.1-1+deb8u1
Control: tags -1 - moreinfo
> We'll need to see a debdiff of the proposed package, built and tested on
> jessie, before going any further, please.
As it was already proposed as security update, I already built and tested it
on jessie.
Best Regards,
sandro
diff -Nru kdepim-4.14.1/debian/changelog kdepim-4.14.1/debian/changelog
--- kdepim-4.14.1/debian/changelog 2014-09-20 11:40:58.0 +0200
+++ kdepim-4.14.1/debian/changelog 2017-06-17 09:37:20.0 +0200
@@ -1,3 +1,14 @@
+kdepim (4:4.14.1-1+deb8u1) jessie-security; urgency=high
+
+ * Team upload.
+ * Fix CVE-2017-9604: Send Later with Delay bypasses OpenPGP (Closes: #864804)
+- Added upstream patch 78c5552be2f00a4ac25bd77ca39386522fca70a8 in file
+ fix-CVE-2017-9604.patch
+- Added upstream patch c54706e990bbd6498e7b1597ec7900bc809e8197 in file
+ fix-CVE-2017-9604.p2.patch (nowadays messagelib)
+
+ -- Sandro Knauß <he...@debian.org> Sat, 17 Jun 2017 09:37:20 +0200
+
kdepim (4:4.14.1-1) unstable; urgency=medium
* Remove old Breaks/Replaces (for versions older than oldstable).
diff -Nru kdepim-4.14.1/debian/patches/fix-CVE-2017-9604.p2.patch kdepim-4.14.1/debian/patches/fix-CVE-2017-9604.p2.patch
--- kdepim-4.14.1/debian/patches/fix-CVE-2017-9604.p2.patch 1970-01-01 01:00:00.0 +0100
+++ kdepim-4.14.1/debian/patches/fix-CVE-2017-9604.p2.patch 2017-06-17 09:37:20.0 +0200
@@ -0,0 +1,21 @@
+From c54706e990bbd6498e7b1597ec7900bc809e8197 Mon Sep 17 00:00:00 2001
+From: Montel Laurent <mon...@kde.org>
+Date: Fri, 2 Jun 2017 13:56:41 +0200
+Subject: Make sure to sign/encrypt message when we send later
+
+(cherry picked from commit 4048f5e46d0a7d62d93d74fd2861dd70fb2ad660)
+---
+ messagecomposer/composer/composerviewbase.cpp | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+--- a/messagecomposer/composer/composerviewbase.cpp
b/messagecomposer/composer/composerviewbase.cpp
+@@ -288,7 +288,7 @@ void MessageComposer::ComposerViewBase::
+ }
+ }
+
+-if ( m_neverEncrypt && saveIn != MessageComposer::MessageSender::SaveInNone ) {
++if ( m_neverEncrypt && saveIn != MessageComposer::MessageSender::SaveInNone && !mSendLaterInfo) {
+ // we can't use the state of the mail itself, to remember the
+ // signing and encryption state, so let's add a header instead
+ m_msg->setHeader( new KMime::Headers::Generic( "X-KMail-SignatureActionEnabled", m_msg.get(),
diff -Nru kdepim-4.14.1/debian/patches/fix-CVE-2017-9604.patch kdepim-4.14.1/debian/patches/fix-CVE-2017-9604.patch
--- kdepim-4.14.1/debian/patches/fix-CVE-2017-9604.patch 1970-01-01 01:00:00.0 +0100
+++ kdepim-4.14.1/debian/patches/fix-CVE-2017-9604.patch 2017-06-17 09:37:20.0 +0200
@@ -0,0 +1,62 @@
+From 78c5552be2f00a4ac25bd77ca39386522fca70a8 Mon Sep 17 00:00:00 2001
+From: Montel Laurent <mon...@kde.org>
+Date: Fri, 2 Jun 2017 13:59:02 +0200
+Subject: Make sure that we use plugin when we use sendlater feature
+
+---
+ kmail/editor/kmcomposewin.cpp | 9 +
+ kmail/editor/kmcomposewin.h | 3 ++-
+ 2 files changed, 7 insertions(+), 5 deletions(-)
+
+--- a/kmail/editor/kmcomposewin.cpp
b/kmail/editor/kmcomposewin.cpp
+@@ -2671,7 +2671,7 @@ void KMComposeWin::printComposeResult( K
+
+ //
+ void KMComposeWin::doSend( MessageComposer::MessageSender::SendMethod method,
+- MessageComposer::MessageSender::SaveIn saveIn )
++ MessageComposer::MessageSender::SaveIn saveIn, bool willSendItWithoutReediting)
+ {
+ if ( mStorageService->numProgressUpdateFile() > 0) {
+ KMessageBox::sorry( this, i18np( "There is %1 file upload in progress.",
+@@ -2687,7 +2687,7 @@ void KMComposeWin::doSend( MessageCompos
+ }
+
+
+-if ( saveIn == MessageComposer::MessageSender::SaveInNone ) { // don't save as draft or template, send immediately
++if ( saveIn == MessageComposer::MessageSender::SaveInNone || willSendItWithoutReediting) { // don't save as draft or template, send immediately
+ if ( KPIMUtils::firstEmailAddress( from() ).isEmpty() ) {
+ if ( !( mShowHeaders & HDR_FROM ) ) {
+ mShowHeaders |= HDR_FROM;
+@@ -2854,6 +2854,7 @@ void KMComposeWin::slotSendLater()
+ return;
+ if ( !checkRecipientNumber() )
+ return;
++mComposerBase->setSendLaterInfo(0);
+ if ( mComposerBase->editor()->checkExternalEditorFinished() ) {
+ const bool wasRegistered = (SendLater::SendLaterUtil::sentLaterAgentWasRegistered() && SendLater::SendLaterUtil::sentLaterAgentEnabled());
+ if (wasRegistered) {
+@@ -2877,9 +2878,9 @@ void KMComposeWin::slotSendLater()
+ {
+ mComposerBase->setSendLaterInfo(info);
+ if (info->isRecurrence()) {
+-
Bug#869577: stretch-pu: package kf5-messagelib/4:16.04.3-3
Control: tags -1 - moreinfo
> We'll need to see a debdiff of the proposed package, built and tested on
> stretch, before going any further, please.
The debdiff is the version, that is currently in testing. The diff was created
when testing was in deep freeze, so actually the version state, that is now in
stretch. The versionnumber may need to be adjusted.
Best Regards,
sandro
diff -Nru kf5-messagelib-16.04.3/debian/changelog kf5-messagelib-16.04.3/debian/changelog
--- kf5-messagelib-16.04.3/debian/changelog 2016-08-02 14:07:27.0 +0200
+++ kf5-messagelib-16.04.3/debian/changelog 2017-06-17 09:08:12.0 +0200
@@ -1,3 +1,13 @@
+kf5-messagelib (4:16.04.3-3) unstable; urgency=high
+
+ * Team upload.
+
+ [ Sandro Knauß ]
+ * Fix CVE-2017-9604: Send Later with Delay bypasses OpenPGP (Closes: #864803)
+- Added upstream patch fix-CVE-2017-9604.patch
+
+ -- Sandro Knauß <he...@debian.org> Sat, 17 Jun 2017 09:08:12 +0200
+
kf5-messagelib (4:16.04.3-2) unstable; urgency=high
[ Automatic packaging ]
diff -Nru kf5-messagelib-16.04.3/debian/patches/fix-CVE-2017-9604.patch kf5-messagelib-16.04.3/debian/patches/fix-CVE-2017-9604.patch
--- kf5-messagelib-16.04.3/debian/patches/fix-CVE-2017-9604.patch 1970-01-01 01:00:00.0 +0100
+++ kf5-messagelib-16.04.3/debian/patches/fix-CVE-2017-9604.patch 2017-06-17 08:35:48.0 +0200
@@ -0,0 +1,26 @@
+From c54706e990bbd6498e7b1597ec7900bc809e8197 Mon Sep 17 00:00:00 2001
+From: Montel Laurent <mon...@kde.org>
+Date: Fri, 2 Jun 2017 13:56:41 +0200
+Subject: Make sure to sign/encrypt message when we send later
+
+(cherry picked from commit 4048f5e46d0a7d62d93d74fd2861dd70fb2ad660)
+---
+ messagecomposer/src/composer/composerviewbase.cpp | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/messagecomposer/src/composer/composerviewbase.cpp b/messagecomposer/src/composer/composerviewbase.cpp
+index d44b8b2..672ea1e 100644
+--- a/messagecomposer/src/composer/composerviewbase.cpp
b/messagecomposer/src/composer/composerviewbase.cpp
+@@ -468,7 +468,7 @@ void MessageComposer::ComposerViewBase::slotEmailAddressResolved(KJob *job)
+ // if so, we create a composer per format
+ // if we aren't signing or encrypting, this just returns a single empty message
+ bool wasCanceled = false;
+-if (m_neverEncrypt && mSaveIn != MessageComposer::MessageSender::SaveInNone) {
++if (m_neverEncrypt && mSaveIn != MessageComposer::MessageSender::SaveInNone && !mSendLaterInfo) {
+ MessageComposer::Composer *composer = new MessageComposer::Composer;
+ composer->setNoCrypto(true);
+ m_composers.append(composer);
+--
+cgit v0.11.2
+
diff -Nru kf5-messagelib-16.04.3/debian/patches/series kf5-messagelib-16.04.3/debian/patches/series
--- kf5-messagelib-16.04.3/debian/patches/series 2016-08-02 14:07:27.0 +0200
+++ kf5-messagelib-16.04.3/debian/patches/series 2017-06-17 09:02:09.0 +0200
@@ -1,2 +1,3 @@
upstream_add_copying_files.patch
make-it-impossible-to-override-css-settings-from-a-h.patch
+fix-CVE-2017-9604.patch
signature.asc
Description: This is a digitally signed message part.
Bug#869574: stretch-pu: package kdepim/4:16.04.3-4
Control: tags -1 - moreinfo
> We'll need to see a debdiff of the proposed package, built and tested on
> stretch, before going any further, please.
The debdiff is the version, that is currently in testing. The diff was created
when testing was in deep freeze, so actually the version state, that is now in
stretch. The versionnumber may need to be adjusted.
Best Regards,
sandrodiff -Nru kdepim-16.04.3/debian/changelog kdepim-16.04.3/debian/changelog
--- kdepim-16.04.3/debian/changelog 2016-11-23 14:38:49.0 +0100
+++ kdepim-16.04.3/debian/changelog 2017-06-17 12:12:03.0 +0200
@@ -1,3 +1,13 @@
+kdepim (4:16.04.3-4) unstable; urgency=high
+
+ * Team upload.
+
+ [ Sandro Knauß ]
+ * Fix CVE-2017-9604: Send Later with Delay bypasses OpenPGP (Closes: #864804)
+- Added upstream patch fix-CVE-2017-9604.patch
+
+ -- Sandro Knauß <he...@debian.org> Sat, 17 Jun 2017 12:12:03 +0200
+
kdepim (4:16.04.3-3) unstable; urgency=medium
* Team upload.
diff -Nru kdepim-16.04.3/debian/patches/fix-CVE-2017-9604.patch kdepim-16.04.3/debian/patches/fix-CVE-2017-9604.patch
--- kdepim-16.04.3/debian/patches/fix-CVE-2017-9604.patch 1970-01-01 01:00:00.0 +0100
+++ kdepim-16.04.3/debian/patches/fix-CVE-2017-9604.patch 2017-06-17 11:29:50.0 +0200
@@ -0,0 +1,62 @@
+From 78c5552be2f00a4ac25bd77ca39386522fca70a8 Mon Sep 17 00:00:00 2001
+From: Montel Laurent <mon...@kde.org>
+Date: Fri, 2 Jun 2017 13:59:02 +0200
+Subject: Make sure that we use plugin when we use sendlater feature
+
+---
+ kmail/editor/kmcomposerwin.cpp | 9 +
+ kmail/editor/kmcomposerwin.h | 3 ++-
+ 2 files changed, 7 insertions(+), 5 deletions(-)
+
+--- a/kmail/editor/kmcomposerwin.cpp
b/kmail/editor/kmcomposerwin.cpp
+@@ -2376,7 +2376,7 @@ void KMComposerWin::printComposeResult(K
+ }
+
+ void KMComposerWin::doSend(MessageComposer::MessageSender::SendMethod method,
+- MessageComposer::MessageSender::SaveIn saveIn)
++ MessageComposer::MessageSender::SaveIn saveIn, bool willSendItWithoutReediting)
+ {
+ if (mStorageService->numProgressUpdateFile() > 0) {
+ KMessageBox::sorry(this, i18np("There is %1 file upload in progress.",
+@@ -2391,7 +2391,7 @@ void KMComposerWin::doSend(MessageCompos
+ }
+ }
+
+-if (saveIn == MessageComposer::MessageSender::SaveInNone) { // don't save as draft or template, send immediately
++if (saveIn == MessageComposer::MessageSender::SaveInNone || willSendItWithoutReediting) { // don't save as draft or template, send immediately
+ if (KEmailAddress::firstEmailAddress(from()).isEmpty()) {
+ if (!(mShowHeaders & HDR_FROM)) {
+ mShowHeaders |= HDR_FROM;
+@@ -2558,6 +2558,7 @@ void KMComposerWin::slotSendLater()
+ if (!checkRecipientNumber()) {
+ return;
+ }
++mComposerBase->setSendLaterInfo(nullptr);
+ if (mComposerBase->editor()->checkExternalEditorFinished()) {
+ const bool wasRegistered = (SendLater::SendLaterUtil::sentLaterAgentWasRegistered() && SendLater::SendLaterUtil::sentLaterAgentEnabled());
+ if (wasRegistered) {
+@@ -2580,9 +2581,9 @@ void KMComposerWin::slotSendLater()
+ case SendLater::SendLaterDialog::SendDeliveryAtTime: {
+ mComposerBase->setSendLaterInfo(info);
+ if (info->isRecurrence()) {
+-doSend(MessageComposer::MessageSender::SendLater, MessageComposer::MessageSender::SaveInTemplates);
++doSend(MessageComposer::MessageSender::SendLater, MessageComposer::MessageSender::SaveInTemplates, true);
+ } else {
+-doSend(MessageComposer::MessageSender::SendLater, MessageComposer::MessageSender::SaveInDrafts);
++doSend(MessageComposer::MessageSender::SendLater, MessageComposer::MessageSender::SaveInDrafts, true);
+ }
+ break;
+ }
+--- a/kmail/editor/kmcomposerwin.h
b/kmail/editor/kmcomposerwin.h
+@@ -510,7 +510,8 @@ private:
+ * Send the message.
+ */
+ void doSend(MessageComposer::MessageSender::SendMethod method = MessageComposer::MessageSender::SendDefault,
+-MessageComposer::MessageSender::SaveIn saveIn = MessageComposer::MessageSender::SaveInNone);
++MessageComposer::MessageSender::SaveIn saveIn = MessageComposer::MessageSender::SaveInNone,
++bool willSendItWithoutReediting = false);
+
+ void doDelayedSend(MessageComposer::MessageSender::SendMethod method, MessageComposer::MessageSender::SaveIn saveIn);
+
diff -Nru kdepim-16.04.3/debian/patches/series kdepim-16.04.3/debian/patches/series
--- kdepim-16.04.3/debian/patches/series 2016-11-23 13:27:45.0 +0100
+++ kdepim-16.04.3/debian/patches/series 2017-06-17 11:2
Bug#869577: stretch-pu: package kf5-messagelib/4:16.04.3-3
Package: release.debian.org Severity: normal Tags: stretch User: release.debian@packages.debian.org Usertags: pu Hey, in order to fix CVE-2017-9604: "Send Later with Delay bypasses OpenPGP" (Closes: #864803), I want to request a point update for kdepim. As discussed in #864803, the security team don't want to warrent a DSA on it's own. And propose to do a pu for kf5-messagelib. Just for keeping the overview: * for jessie we need only kdepim updated (see #869573) * for stretch the kdepim package was splitted into kf5-messagelib and kdepim, and both needs to be updated in order to fix CVE-2017-9604. Both packages are fixed in testing with the version: kdepim 4:16.04.3-4 (see #869574) kf5-messagelib 4:16.04.3-3 Best Regards, sandro -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'oldstable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.11.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)
Bug#869574: stretch-pu: package kdepim/4:16.04.3-3
Package: release.debian.org Severity: normal Tags: stretch User: release.debian@packages.debian.org Usertags: pu Hey, in order to fix CVE-2017-9604: "Send Later with Delay bypasses OpenPGP" (Closes: #864803), I want to request a point update for kdepim. As discussed in #864803, the security team don't want to warrent a DSA on it's own. And propose to do a pu for kdepim. Just for keeping the overview: * for jessie we need only kdepim updated (see #869573) * for stretch the kdepim package was splitted into kf5-messagelib and kdepim, and both needs to be updated in order to fix CVE-2017-9604. Both packages are fixed in testing with the version: kdepim 4:16.04.3-4 kf5-messagelib 4:16.04.3-3 Best Regards, sandro -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'oldstable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.11.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)
Bug#869573: jessie-pu: package kdepim/4:4.14.1-1+deb8u1
Package: release.debian.org Severity: normal Tags: jessie User: release.debian@packages.debian.org Usertags: pu Hey, in order to fix CVE-2017-9604: "Send Later with Delay bypasses OpenPGP" (Closes: #864804), I want to request a point update for kdepim. As discussed in #864804, the security team don't want to warrent a DSA on it's own. But propose to do a pu for kdepim. Best Regards, sandro -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'oldstable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.11.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)
Bug#842277: transition: qtkeychain
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Hi dear release team, Now with liblibqt5keychain1 and libqtkeychain1 in the archive, we can start transtion the existing packages to the archive so that the new qtkeychain package can transition to testing. The following source packages need to be rebuilt: charmtimetracker owncloud-client No changes are needed for both packages to be build with qtkeychain 0.7.0. Please schedule binNMUs for the above mentioned packages on all architectures. Thank you. Sandro Knauß The automatic Ben file is correct: title = "auto-qtkeychain"; is_affected = .depends ~ /\b(libqt5keychain0|libqtkeychain0|libqt5keychain1|libqtkeychain1)\b/; is_good = .depends ~ /\b(libqt5keychain1|libqtkeychain1)\b/; is_bad = .depends ~ /\b(libqt5keychain0|libqtkeychain0)\b/; -- System Information: Debian Release: stretch/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#796744: jessie-pu: package owncloud-client/1.7.0~beta1+really1.6.4+dfsg-1
Package: release.debian.org Severity: normal Tags: jessie User: release.debian@packages.debian.org Usertags: pu Hey, the version 1.6.4+dfsg-1 of owncloud client can't interact with owncloud server 8.1 [#791721]. This versionnumber 1.7.0~beta1+really1.6.4+dfsg-1 is created by acident. It is simply the upstream version 1.6.4. The prefix is only needed, becuase one time 1.7.0~beta1 was push to unstable instead of experimental. The problem is so far that upstream server checks the version of the client and disallows the connection with an older client ( 1.7). Upstream says, that they do it, because the older client is very unstable und not reliable. It is so far possible to disable this feature on the server. As far as I see different solutions to improve: * Either we say, okay client+server from stable works together and do nothing. * Mention the needed change in the stable package. * Ship a new version via stable * Ship a version in backports, you only need the client when a new server is used. I think the best UX would be shipping the new client to stable, but I want to hear yout opition about this issue. So far as I looked at the code it is very hard to extract a subset to cherrypick, there were overall improvments were made. I didn't prepare anything for the request so far, because I want to wait, till I know what possibilities you see. For sure we have to rebuild owncloud-client another time with qt4 for stable. Because qt5 shipped in stable is not current enough. As diff of the upstream: git clone git://anonscm.debian.org/pkg-owncloud/owncloud-client.git cd owncloud-client git diff upstream/1.6.4+dfsg..upstream/1.7.1+dfsg --stat csync src 188 files changed, 8362 insertions(+), 5347 deletions(-) Please feel to ask anything, if you missing informations. Regards, sandro -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (450, 'unstable'), (110, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.1.0-rc5-siduction-amd64 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#775745: patch has accepted upstream
The patch for #775114 has gone accepted upstream: https://git.reviewboard.kde.org/r/120119/ Regads, sandro -- Sandro Knauß Software Developer Kolab Systems AG Zürich, Switzerland e: kna...@kolabsys.com t: +41 43 501 66 91 w: http://kolabsys.com pgp: CE81539E Sandro Knauß signature.asc Description: This is a digitally signed message part.
