Bug#930168: Confirming the bug on Debian
I can confim the same behaviour on current Debian sid and I found a working solution for me. In the end it was an issue outside discover. appstream data update was disabled, I proplery did that because the files are that big. I sill could search apps via appstream, so I thought that is not the root issue. $ appstreamcli search kate Identifier: org.kde.kate.desktop [desktop-application] [...] So appstream was already installed and working. Steps I needed to do to list apps within discover: rename /etc/apt/apt.conf.d/#50appstream to /etc/apt/apt.conf.d/50appstream apt update That was all. So for others it is a good idea to check: * can I search apps vis appstream ( appstreamcli search kate ) * does the update command is successfull ( appstreamcli refresh --source=os); or the command that is triggered by /etc/apt/apt.conf.d/50appstream) * is /var/cache/swcatalog populated and writeable that at least should clearify the issue even more. regards, hefee On Mittwoch, 12. Juni 2019 01:07:03 CEST Alexander Kernozhitsky wrote: > I also encounter this bug on Debian Buster. > > But I manually disabled all the AppStream and DEP-11 metadata from apt > configs, so this may be the reason. > > Can anyone reproduce this on a clean system? signature.asc Description: This is a digitally signed message part.
Bug#1060180: uid-wrapper: cmocka does not set CMOCKA_LIBRARY anymore.
Package: uid-wrapper
Version: 1.3.0-4
Severity: normal
Tags: patch
X-Debbugs-Cc: he...@debian.org
Hey,
cmocka does not set CMOCKA_LIBRARY anymore with 1.1.6+. You can easly
use cmoka as library name. I tested the attached patch locally and it
makes the autopkgtests pass again.
Additionally enables VERBOSE=1 for make, so it is easier to spot what
command is actually executed.
Regards,
hefee
diff --git a/debian/tests/tests b/debian/tests/tests
index b2b4504..a5adfa6 100755
--- a/debian/tests/tests
+++ b/debian/tests/tests
@@ -6,7 +6,7 @@ rm -rf obj debian
mkdir obj
cd obj
cmake .. -DUNIT_TESTING=1
-make -C tests/
+make VERBOSE=1 -C tests/
cd tests
sed -e 's#\(LD_PRELOAD=[^:]*\)[^;]*/\(libuid_wrapper.so\)#\1:\2#' -i
CTestTestfile.cmake
make test ARGS="--output-on-failure"
diff --git a/tests/CMakeLists.txt b/tests/CMakeLists.txt
index 635e86e..0398261 100644
--- a/tests/CMakeLists.txt
+++ b/tests/CMakeLists.txt
@@ -59,7 +59,7 @@ function(ADD_CMOCKA_TEST_ENVIRONMENT _TEST_NAME)
ENVIRONMENT "${TORTURE_ENVIRONMENT}")
endfunction()
-set(TESTSUITE_LIBRARIES ${UWRAP_REQUIRED_LIBRARIES} ${CMOCKA_LIBRARY})
+set(TESTSUITE_LIBRARIES ${UWRAP_REQUIRED_LIBRARIES} cmocka)
if (BSD)
add_definitions(-DBSD)
Bug#1060179: resolv-wrapper: cmocka does not set CMOCKA_LIBRARY anymore.
Package: resolv-wrapper
Version: 1.1.8-2
Severity: normal
Tags: patch
X-Debbugs-Cc: he...@debian.org
Hey,
cmocka does not set CMOCKA_LIBRARY anymore with 1.1.6+. You can easly
use cmoka as library name. I tested the attached patch locally and it
makes the autopkgtests pass again.
Additionally enables VERBOSE=1 for make, so it is easier to spot what
command is actually executed.
Regards,
hefee
diff --git a/debian/tests/tests b/debian/tests/tests
index b4a4900..1a31031 100755
--- a/debian/tests/tests
+++ b/debian/tests/tests
@@ -6,7 +6,7 @@ rm -rf obj debian
mkdir obj
cd obj
cmake -DUNIT_TESTING=1 ..
-make -C tests/
+make VERBOSE=1 -C tests/
cd tests
sed -e 's#\(LD_PRELOAD=\)[^;]*/\(libresolv_wrapper.so\)#\1\2#' -i
CTestTestfile.cmake
make test ARGS="--output-on-failure"
diff --git a/tests/CMakeLists.txt b/tests/CMakeLists.txt
index 1262bed..2614d78 100644
--- a/tests/CMakeLists.txt
+++ b/tests/CMakeLists.txt
@@ -11,7 +11,7 @@ target_link_libraries(dns_srv ${RWRAP_REQUIRED_LIBRARIES})
add_executable(test_real_res_query test_real_res_query.c)
target_compile_options(test_real_res_query PRIVATE ${DEFAULT_C_COMPILE_FLAGS})
target_include_directories(test_real_res_query PRIVATE ${CMAKE_BINARY_DIR}
${CMOCKA_INCLUDE_DIR})
-target_link_libraries(test_real_res_query ${RWRAP_REQUIRED_LIBRARIES}
${CMOCKA_LIBRARY})
+target_link_libraries(test_real_res_query ${RWRAP_REQUIRED_LIBRARIES} cmocka)
configure_file(fake_hosts.in ${CMAKE_CURRENT_BINARY_DIR}/fake_hosts @ONLY)
@@ -19,11 +19,11 @@ add_library(${TORTURE_LIBRARY} STATIC torture.c)
target_compile_options(${TORTURE_LIBRARY} PRIVATE ${DEFAULT_C_COMPILE_FLAGS})
target_include_directories(${TORTURE_LIBRARY} PRIVATE ${CMAKE_BINARY_DIR}
${CMOCKA_INCLUDE_DIR})
target_link_libraries(${TORTURE_LIBRARY}
-${CMOCKA_LIBRARY}
+cmocka
${SWRAP_REQUIRED_LIBRARIES})
-set(TESTSUITE_LIBRARIES ${RWRAP_REQUIRED_LIBRARIES} ${CMOCKA_LIBRARY})
+set(TESTSUITE_LIBRARIES ${RWRAP_REQUIRED_LIBRARIES} cmocka)
# Some tests require socket_wrapper as well.
find_package(socket_wrapper REQUIRED)
Bug#1060178: priv-wrapper: cmocka does not set CMOCKA_LIBRARY anymore.
Package: priv-wrapper
Version: 1.0.1-3
Severity: normal
Tags: patch
X-Debbugs-Cc: he...@debian.org
Hey,
cmocka does not set CMOCKA_LIBRARY anymore with 1.1.6+. You can easly
use cmoka as library name. I tested the attached patch locally and it
makes the autopkgtests pass again.
Additionally enables VERBOSE=1 for make, so it is easier to spot what
command is actually executed.
Regards,
hefee
diff --git a/debian/tests/tests b/debian/tests/tests
index 0c268ac..b85a7c0 100755
--- a/debian/tests/tests
+++ b/debian/tests/tests
@@ -4,7 +4,7 @@ rm -rf obj
mkdir obj
cd obj
cmake -DUNIT_TESTING=1 ..
-make -C tests/
+make VERBOSE=1 -C tests/
cd tests
sed -e 's#\(LD_PRELOAD=\)[^;]*/\(libpriv_wrapper.so\)#\1\2#' -i
CTestTestfile.cmake
make test ARGS="--output-on-failure"
diff --git a/tests/CMakeLists.txt b/tests/CMakeLists.txt
index d33cf15..11526be 100644
--- a/tests/CMakeLists.txt
+++ b/tests/CMakeLists.txt
@@ -66,6 +66,6 @@ foreach(_PWRAP_TEST ${PWRAP_TESTS})
add_cmocka_test(${_PWRAP_TEST}
SOURCES ${_PWRAP_TEST}.c
COMPILE_OPTIONS -D_GNU_SOURCE
-LINK_LIBRARIES ${CMOCKA_LIBRARY} PRIVATE defaults)
+LINK_LIBRARIES cmocka PRIVATE defaults)
add_cmocka_test_environment(${_PWRAP_TEST})
endforeach()
Bug#1060177: nss-wrapper: cmocka does not set CMOCKA_LIBRARY anymore.
Package: nss-wrapper
Version: 1.1.15-2
Severity: normal
Tags: patch
X-Debbugs-Cc: he...@debian.org
Hey,
cmocka does not set CMOCKA_LIBRARY anymore with 1.1.6+. You can easly use cmoka
as
library name. I tested the attached patch locally and it makes the
autopkgtests pass again.
Regards,
hefee
diff --git a/tests/CMakeLists.txt b/tests/CMakeLists.txt
index 3b94076..e5feaaa 100644
--- a/tests/CMakeLists.txt
+++ b/tests/CMakeLists.txt
@@ -1,6 +1,6 @@
project(tests C)
-set(TESTSUITE_LIBRARIES nss_utils ${NWRAP_REQUIRED_LIBRARIES}
${CMOCKA_LIBRARY})
+set(TESTSUITE_LIBRARIES nss_utils ${NWRAP_REQUIRED_LIBRARIES} cmocka)
string(TOLOWER "${CMAKE_BUILD_TYPE}" CMAKE_BUILD_TYPE_LOWER)
add_library(nss_nwrap SHARED nss_nwrap.c)
Bug#1015370: cmocka: ftbfs with LTO (link time optimization) enabled
Control: reassign -1 binutils 2.41.50.20231206-1 Control: affects -1 cmocka Control: forwarded -1 https://sourceware.org/bugzilla/show_bug.cgi?id=24415 Control: retitle ld.gold - -Wl,--wrap not supported with LTO and optimization Hey, this is not a bug in cmocka. It is actually an bug in ld.gold , that does not correctly handles - -Wl,--wrap with LTO together correctly: https://gitlab.com/cmocka/cmocka/-/issues/20 The workaround is to disable building examples, as it is the only place where this feature is used. Current state is that ld.bfd and ld.lld are fixed. But ld.gold fails :( https://sourceware.org/bugzilla/show_bug.cgi?id=24415 Regards, hefee signature.asc Description: This is a digitally signed message part.
Bug#1058458: bookworm-pu: package nextcloud-desktop/3.7.3-1+deb12u1
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: nextcloud-desk...@packages.debian.org, he...@debian.org
Control: affects -1 + src:nextcloud-desktop
[ Reason ]
This pu will fix two issues maarked as important:
#1051071: some files with special characters are not synced.
#1053922: Two-factor authentication notifications unusable.
[ Impact ]
#1051071: Some files are not synced because of ":" in its name without
any feedback.
#1053922: Keeps Two-factor authentification not usable.
[ Tests ]
3.10.0 with the fixes included seems to run fine.
[ Risks ]
The fixes are very small and clear what they do and what they fix, so
the risk of side effects is very 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 (old)stable
[x] the issue is verified as fixed in unstable
[ Changes ]
Added to backported patches for upstream and updated the debian-branch
in gbp.conf.
diff -Nru nextcloud-desktop-3.7.3/debian/changelog
nextcloud-desktop-3.7.3/debian/changelog
--- nextcloud-desktop-3.7.3/debian/changelog2023-02-15 15:00:39.0
+0100
+++ nextcloud-desktop-3.7.3/debian/changelog2023-12-12 13:06:40.0
+0100
@@ -1,3 +1,13 @@
+nextcloud-desktop (3.7.3-1+deb12u1) bookworm; urgency=medium
+
+ * Backport patch to fix "fails to sync files with special chars like ':'"
+(Closes: #1051071)
+ * Backport patch 'Two-factor authentication notifications unusable'
+(Closes: #1056327)
+ * Update debian-branch in gbp.conf to point to the stable branch.
+
+ -- Sandro Knauß Tue, 12 Dec 2023 13:06:40 +0100
+
nextcloud-desktop (3.7.3-1) unstable; urgency=medium
* New upstream release.
diff -Nru nextcloud-desktop-3.7.3/debian/gbp.conf
nextcloud-desktop-3.7.3/debian/gbp.conf
--- nextcloud-desktop-3.7.3/debian/gbp.conf 2023-02-15 15:00:39.0
+0100
+++ nextcloud-desktop-3.7.3/debian/gbp.conf 2023-12-12 13:06:35.0
+0100
@@ -1,5 +1,5 @@
[DEFAULT]
-debian-branch = master
+debian-branch = debian/bookworm
upstream-branch = upstream
pristine-tar = True
compression = gz
diff -Nru nextcloud-desktop-3.7.3/debian/.gitignore
nextcloud-desktop-3.7.3/debian/.gitignore
--- nextcloud-desktop-3.7.3/debian/.gitignore 2023-02-15 15:00:39.0
+0100
+++ nextcloud-desktop-3.7.3/debian/.gitignore 1970-01-01 01:00:00.0
+0100
@@ -1 +0,0 @@
-files
diff -Nru
nextcloud-desktop-3.7.3/debian/patches/0005-fixed-detection-of-server-version-in-cmd-client-simi.patch
nextcloud-desktop-3.7.3/debian/patches/0005-fixed-detection-of-server-version-in-cmd-client-simi.patch
---
nextcloud-desktop-3.7.3/debian/patches/0005-fixed-detection-of-server-version-in-cmd-client-simi.patch
1970-01-01 01:00:00.0 +0100
+++
nextcloud-desktop-3.7.3/debian/patches/0005-fixed-detection-of-server-version-in-cmd-client-simi.patch
2023-12-12 13:06:35.0 +0100
@@ -0,0 +1,60 @@
+From: Patrick Cernko
+Date: Tue, 5 Sep 2023 06:11:54 +0200
+Subject: fixed detection of server version in cmd client similar to gui
+ client:
+
+first check status.php for version and then capabilities, only use version
string if not empty
+
+this also fixes 'File names containing the character ":" are not supported on
this file system.' errors in nextcloudcmd (on Linux): The invalidFilenameRegex
was set to a static default in case the server version was not set correctly.
As newer versions of nextcloud do not return the version in capabilities but
status.php, the server version was empty.
+
+Signed-off-by: Patrick Cernko
+---
+ src/cmd/cmd.cpp | 30 +-
+ 1 file changed, 29 insertions(+), 1 deletion(-)
+
+diff --git a/src/cmd/cmd.cpp b/src/cmd/cmd.cpp
+index 37c456d..2764f72 100644
+--- a/src/cmd/cmd.cpp
b/src/cmd/cmd.cpp
+@@ -442,12 +442,40 @@ int main(int argc, char **argv)
+ account->setTrustCertificates(options.trustSSL);
+
+ QEventLoop loop;
++auto *csjob = new CheckServerJob(account);
++csjob->setIgnoreCredentialFailure(true);
++QObject::connect(csjob, ::instanceFound, [&](const QUrl &,
const QJsonObject ) {
++// see ConnectionValidator::slotCapabilitiesRecieved: only set server
version if not empty
++QString serverVersion = CheckServerJob::version(info);
++if (!serverVersion.isEmpty()) {
++account->setServerVersion(serverVersion);
++}
++loop.quit();
++});
++QObject::connect(csjob, ::instanceNotFound, [&]() {
++loop.quit();
++});
++QObject::connect(csjob, ::timeout, [&](const QUrl &) {
++loop.quit();
++});
++csjob->start();
++loop.exec();
++
++if (csjob->reply()->error() != QNetworkReply::NoError){
++std::cout<<"Error connecting to server for status\n";
++return EXIT_FAILURE;
++}
++
+ auto *job = new JsonApiJob(account,
Bug#1054172: nextcloud-desktop: Header of main window displays black zone without widgets (XFCE)
Control: tags -1 +upstream Hey, That is not a packaging issue on Debian side, this is an upstream one. Search for a corresponding this issue or report a new one: https://github.com/nextcloud/desktop/issues Please report back the url of the upstream bugreport, so we can link this issue to the upstream bug report. Regards, hefee On Sonntag, 10. Dezember 2023 17:22:37 CET you wrote: > Le Wed, Oct 18, 2023 at 05:52:42PM +0200, Olivier Berger a écrit : > > I'm running Nextcloud-Desktop on XFCE, and just noticed that a recent > > update of my testing system caused the main dialog to display weirdly. > > > > The zone which usually contains a dropbox allowing to switch the current > > account is display as a fully black zone (see attached screenshot). > > > > Ths makes it quite difficult to use. > > Responding to myself, I figured out that this may be related to the > configuration of the Nextcloud server, which displays its Web interface > with a dark theme. > > When configuring another Nextcloud server in the same Desktop instance, I > can switch to the view of the other server's sync, and then it is displayed > with a different color (as the new server's display theme is different. See > attached screenshot. > > Unfortunately I'm not able to configure the initial server's Web display > preferences. > > Hope this helps, signature.asc Description: This is a digitally signed message part.
Bug#964434: nextcloud-desktop: Please move the menu entry of nextcloud-dektop to internet
Hey, we don't get any new info if the issue is reported upstream. Close this bug report, as it is not helpful to keep it open without any resonance. If we had an upstream bug we could track the status. Regards, hefee -- On Donnerstag, 24. September 2020 20:59:40 CEST you wrote: > Control: tags -1 +upstream > > > in order to make the program more accessible for the common user I would > > suggest to move it to the menupoine Internet. This is the place where most > > other desktop clients for internet services reside. > > This is not a Debian specific issue, so please report upstream and report > back the issue id of upstream, so we can track the upstream issue: > https://github.com/nextcloud/desktop/issues > > hefee signature.asc Description: This is a digitally signed message part.
Bug#971920: nextcloud-desktop: Not showing tray icon on Xfce
Control: tags -1 moreinfo upstream Hey, Sorry, I did overseen the bugreport and didn't come back in time. if it still is valid under the new version? What protocol does XFCE is using for tray icons. At least am aware that GNOME appidicator has for some users issues displaying tray icons: https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/232 But there are more bugs on upstream about issues with tray icon. Please look there maybe a matching bug report is already there: https://github.com/nextcloud/desktop/issues If you found a corresponding upstream bug or create a new issue Please report back the url, than we can keep track of the upstream bug. @chris: About the empty window. Maybe: https://github.com/nextcloud/desktop/issues/5443 https://github.com/nextcloud/desktop/issues/4602 if you are using wayland is qtwayland5 installed? Regards, hefee On Freitag, 9. Oktober 2020 21:09:23 CEST Christopher Obbard wrote: > For me on XFCE the tray icon appears but clicking on it does nothing. One > has to right click and go to settings for it to open > > Thanks! > Chris signature.asc Description: This is a digitally signed message part.
Bug#1030341: nextcloud-desktop-cmd: nextcloudcmd contains em-dashes instead of double dashes
Control: Forwarded -1 https://github.com/nextcloud/desktop/pull/6122 Hey, thanks for your bugreport. I sad down to create a fix and hopefully upstream will accept it. regards, hefee -- On Freitag, 3. Februar 2023 10:52:01 CEST you wrote: > Package: nextcloud-desktop-cmd > Version: 3.1.1-2+deb11u1 > Severity: normal > X-Debbugs-Cc: nicolas.geo...@ens.fr > > Hi. `man nextcloudcmd` says: > >—user, -u [user] > Use user as the login name. > > But: > > $ nextcloudcmd —user george [snip] > nextcloudcmd - command line Nextcloud client tool > [snip usage info] > > $ nextcloudcmd -user george [snip] > nextcloudcmd - command line Nextcloud client tool > [snip usage info] > > $ nextcloudcmd --user george [snip] > Password for user george: > > The man page (including its source file) contains an em-dash character > U+2014 instead of a double dash. It is not limited to the --user option. > > > -- System Information: > Debian Release: 11.6 > APT prefers stable-updates > APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, > 'stable') Architecture: amd64 (x86_64) > > Kernel: Linux 6.0.0-0.deb11.6-amd64 (SMP w/12 CPU threads; PREEMPT) > Locale: LANG=C, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages nextcloud-desktop-cmd depends on: > ii libc6 2.31-13+deb11u5 > ii libgcc-s1 10.2.1-6 > ii libnextcloudsync0 3.1.1-2+deb11u1 > ii libqt5core5a 5.15.2+dfsg-9 > ii libqt5network55.15.2+dfsg-9 > ii libqt5sql5-sqlite 5.15.2+dfsg-9 > ii libstdc++610.2.1-6 > ii nextcloud-desktop-common 3.1.1-2+deb11u1 > ii nextcloud-desktop-l10n3.1.1-2+deb11u1 > > nextcloud-desktop-cmd recommends no packages. > > nextcloud-desktop-cmd suggests no packages. > > -- no debconf information signature.asc Description: This is a digitally signed message part.
Bug#1037957: nextcloud-desktop: XFCE sessions cause broken behavior after 11 -> 12 upgrade
Hey, Thanks fir your bugreport. This is an issuse of the Nextcloud itself and not about the packaging. So please look into the upstream bugtracker: https://github.com/nextcloud/desktop/issues and report your bug there, if you don't find any matching one. Or even provide a bugfix/merge request ;) If you found or open a bugreport that matches please send this url to this bugreport, so we can track the upstream status and may backport the fix, if there is any. Best regards, hefee -- > After upgrading to Debian Bookworm from Bullseye, nextcloud-desktop > erroneously opens it's main popup window in the dead center of the screen > when a user logs in to an XFCE session. > > Closing the window normally, by clicking outside of the window, does not > work. > > Instead the user must either input the Alt-F4 combination. Or click on the > tray icon once to move the window back under the tray icon, (Where it > should appear normally.) and again to close the window. This has to be done > on every login regardless of reboots. > > Also, if the user has configured items to be excluded from sync (such as > files that are too big for the destination, server files on external > storage, etc.) nextcloud-desktop will also start sending notifications > about them prompting the user to configure the app despite having already > made their configuration choice. This too happens on every login, but can > be disabled by disabling notifications from the app. > > As an additional note, when I upgraded from Bullseye, the nextcloud-desktop > package was uninstalled due to a package conflict. I reinstalled it after > the upgrade was complete without the conflict occuring again. signature.asc Description: This is a digitally signed message part.
Bug#980025: nextcloud-desktop: Nextcloud-desktop starts but window doesn't display properly and disappears in GNOME
Hey, Is libqt5waylandclient is installed? > I can reproduce it here under Gnome / wayland; (Under X, it works.) > I've got a nvidia GPU with nvidia-drivers from non-free, maybe that's > another nvidia issue? that is quite possible. NVIDIA and wayland are not the best friends ;) > > If I start using specifing some QT_OPA_PLATFROM value, eg > > QT_QPA_PLATFORM=wayland nextcloud --logfile - --logdebug Well I run wayland on a daily basis and I don't see the error for the KDE Plasma desktop with wayland . Is libqt5waylandclient is installed? Maybe you can install kde-standard in parallel to your GMOME desktop, to make sure it is not a missing dependency? regards, hefee signature.asc Description: This is a digitally signed message part.
Bug#1034184: [Pkg-owncloud-maintainers] Bug#1034184: Bug#1034184: nextcloud-desktop: CVE-2023-28999
control: fixed -1 3.9.0-1 We can at least mark sid/trixie as fixed. As those two have a version > 3.8.0 ;) Regards, hefee signature.asc Description: This is a digitally signed message part.
Bug#1041765: nextcloud-desktop: Tray icon no longer works with gnome + indicator extension
Control: reassign -1 gnome-shell-extension-appindicator Control: affects -1 nextcloud-desktop Control: forwarded -1 https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/232 The problem is inside the AppIdicator extension than in Nextcloud. I found several issues pointing to gnome shell extension. Regards, hefee -- On Sonntag, 23. Juli 2023 10:59:42 CEST you wrote: > Package: nextcloud-desktop > Version: 3.9.0-1 > Severity: normal > > Dear Maintainer, > > since installing nextcloud-desktop 3.9, the systray icon no longer works as > expected in Gnome (with the AppIndicator extension): it shows shows three > white dots instead of the nextcloud icon. > Nextcloud shows everything as fully synced, so I am fairly sure that these > are the three dots Gnome shows when it cannot find the icon. However, I am > not sure why the icon can no longer be found -- it used to work fine before > I did a big "apt upgrade" yesterday. > > Here's another report of the same problem, with a screenshot: > https://forum.manjaro.org/t/nextcloud-client-icon-is-not-showing-correctly/1 > 38545 > > Kind regards, > Ralf > > -- System Information: > Debian Release: trixie/sid > APT prefers testing > APT policy: (500, 'testing') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 6.3.0-1-amd64 (SMP w/20 CPU threads; PREEMPT) > Kernel taint flags: TAINT_DIE, TAINT_WARN > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), > LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages nextcloud-desktop depends on: > ii libc6 2.37-5 > ii libcloudproviders0 0.3.1-2 > ii libgcc-s1 13.1.0-6 > ii libglib2.0-0 2.74.6-2 > ii libkf5archive5 5.107.0-1 > ii libnextcloudsync0 3.9.0-1 > ii libqt5core5a 5.15.8+dfsg-12 > ii libqt5dbus55.15.8+dfsg-12 > ii libqt5gui5 5.15.8+dfsg-12 > ii libqt5keychain10.14.1-1 > ii libqt5network5 5.15.8+dfsg-12 > ii libqt5qml5 5.15.8+dfsg-3 > ii libqt5quick5 5.15.8+dfsg-3 > ii libqt5quickcontrols2-5 5.15.8+dfsg-2 > ii libqt5sql5-sqlite 5.15.8+dfsg-12 > ii libqt5svg5 5.15.8-3 > ii libqt5webenginecore5 5.15.13+dfsg-1~deb12u1 > ii libqt5webenginewidgets55.15.13+dfsg-1~deb12u1 > ii libqt5widgets5 5.15.8+dfsg-12 > ii libstdc++6 13.1.0-6 > ii nextcloud-desktop-common 3.9.0-1 > ii nextcloud-desktop-l10n 3.9.0-1 > ii qml-module-qt-labs-platform5.15.8+dfsg-2 > ii qml-module-qtgraphicaleffects 5.15.8-2 > ii qml-module-qtqml 5.15.8+dfsg-3 > ii qml-module-qtqml-models2 5.15.8+dfsg-3 > ii qml-module-qtquick-controls2 5.15.8+dfsg-2 > ii qml-module-qtquick-dialogs 5.15.8-2 > ii qml-module-qtquick-layouts 5.15.8+dfsg-3 > ii qml-module-qtquick-window2 5.15.8+dfsg-3 > ii qml-module-qtquick25.15.8+dfsg-3 > > Versions of packages nextcloud-desktop recommends: > ii nextcloud-desktop-doc 3.9.0-1 > > nextcloud-desktop suggests no packages. > > -- no debconf information signature.asc Description: This is a digitally signed message part.
Bug#982922: /usr/bin/nextcloud: Doesn't sync files, remains in "waiting to sync" since update
Control: tags -1 upstream moreinfo unreproducible
Hey,
sorry, it is quite long time that I respond. I couldn't reproduce this issue
and never sees that behaviour.
if it still is valid under the new version 3.7.3 (from bookworm), than please
get in contact with upstream: https://github.com/nextcloud/desktop/issues
As it is not an packaging bug on our side.
Please report back the url of the upstream bug number, so we can track the
status and do a backport, if upstream fixes the issue.
Regards,
hefee
--
On Dienstag, 16. Februar 2021 16:58:46 CEST rol...@mxchange.org wrote:
> Package: nextcloud-desktop
> Version: 3.1.1-1
> Severity: important
> File: /usr/bin/nextcloud
>
> Dear Maintainer,
>
> * What led up to the situation?
> I updated this package from a previous version (I don't remember the version
> correctly, but it did always sync) over the package manager apitutude as
> usual.
>
> * What exactly did you do (or not do) that was effective (or ineffective)?
> I added new files into the synchronized folder and they are not uploaded,
> instead tons of "Network job timeout QUrl("remote.php/webdav")" appear in
> logile.
>
> * What was the outcome of this action?
> New files are not uploaded and not downloaded ("synchronized").
>
> * What outcome did you expect instead?
> That the files I added are uploaded and others (you can only choose
> directories, I know) downloaded I marked for synchronization.
>
> I later attach the full logfile to this report (I have to check for
> sensitive informations, like login hashes and so).
>
> Best regards,
> Roland
signature.asc
Description: This is a digitally signed message part.
Bug#1051071: nextcloud-desktop-cmd: fails to sync files with special chars like ':'
Control: forwarded -1 https://github.com/nextcloud/desktop/pull/6016 Control: fixed -1 3.10.0-1 Hey, great your MR got accepted for 3.10.0. Now we need to wait till it reaches testing. Than we can look into backport it to stable. I already checked, your patch applies cleanly on the version on bookworm. The description you have given, what the patch does and why it fixes the issue is also enough for me to understand what you did. I started to prepare a stable update version: https://salsa.debian.org/owncloud-team/nextcloud-desktop/-/tree/debian/bookworm Regards, hefee signature.asc Description: This is a digitally signed message part.
Bug#974610: Acknowledgement (nextcloud-desktop: Unable to add, change or remove accounts)
tags -1 moreinfo Hi, > The package depends on qml-module-qtquick-controls2 but in reality it > requires qml-module-qtquick-controls (without the "2" at the end) to work. nextcloud-desktop does not use qml-module-qtquick-controls directly, so it must be a missing dependency of a dependency. Is it still an issue? regards, hefee signature.asc Description: This is a digitally signed message part.
Bug#1040180: bookworm-pu: package kf5-messagelib/22.12.3-2~deb12u1
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: kf5-message...@packages.debian.org, he...@debian.org
Control: affects -1 + src:kf5-messagelib
[ Reason ]
KMail does can't verify signatures if they are signed with subkeys.
[ Impact ]
Users will see an invalid signature instead of a valid one.
[ Tests ]
Same package is on unstable for some days without any issue.
I also run KMail on a daily basis.
[ Risks ]
The patch is quite small and is a direct patch from upstream. It is very
unlikly that this has side effects.
[ Checklist ]
[*] *all* changes are documented in the d/changelog
[*] I reviewed all changes and I approve them
[*] attach debdiff against the package in bookworm
[*] the issue is verified as fixed in unstable
diff -Nru kf5-messagelib-22.12.3/debian/changelog
kf5-messagelib-22.12.3/debian/changelog
--- kf5-messagelib-22.12.3/debian/changelog 2023-03-01 21:33:30.0
+0100
+++ kf5-messagelib-22.12.3/debian/changelog 2023-07-02 23:21:13.0
+0200
@@ -1,3 +1,15 @@
+kf5-messagelib (4:22.12.3-2~deb12u1) bookworm; urgency=medium
+
+ * Rebuilt for bookworm.
+
+ -- Sandro Knauß Sun, 02 Jul 2023 23:21:13 +0200
+
+kf5-messagelib (4:22.12.3-2) unstable; urgency=medium
+
+ * Add upstream patch to search also for subkeys (Closes: #1037363).
+
+ -- Sandro Knauß Tue, 27 Jun 2023 14:09:30 +0200
+
kf5-messagelib (4:22.12.3-1) unstable; urgency=medium
[ Patrick Franz ]
diff -Nru kf5-messagelib-22.12.3/debian/patches/series
kf5-messagelib-22.12.3/debian/patches/series
--- kf5-messagelib-22.12.3/debian/patches/series2022-12-20
01:37:29.0 +0100
+++ kf5-messagelib-22.12.3/debian/patches/series2023-06-27
13:33:50.0 +0200
@@ -1 +1,2 @@
enable_debianabimanager.diff
+upstream-Look-for-matching-subkey-if-no-key-was-found-for-fin.patch
diff -Nru
kf5-messagelib-22.12.3/debian/patches/upstream-Look-for-matching-subkey-if-no-key-was-found-for-fin.patch
kf5-messagelib-22.12.3/debian/patches/upstream-Look-for-matching-subkey-if-no-key-was-found-for-fin.patch
---
kf5-messagelib-22.12.3/debian/patches/upstream-Look-for-matching-subkey-if-no-key-was-found-for-fin.patch
1970-01-01 01:00:00.0 +0100
+++
kf5-messagelib-22.12.3/debian/patches/upstream-Look-for-matching-subkey-if-no-key-was-found-for-fin.patch
2023-06-27 13:34:36.0 +0200
@@ -0,0 +1,44 @@
+From 70f39256784280d2034aa7bf1c4765f606c22d56 Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Ingo=20Kl=C3=B6cker?=
+Date: Wed, 3 May 2023 14:51:18 +0200
+Subject: Look for matching subkey if no key was found for fingerprint
+
+If the message was signed with a signing subkey instead of with the
+primary key of an OpenPGP certificate, then we won't find a key with
+findByFingerprint(). To look for a matching subkey we need to use
+findSubkeysByKeyID().
+
+FIXED-IN: 5.23.1
+BUG: 469304
+(cherry picked from commit 606ea1478d2d5b5aacdc6ef3f050655fe0352d87)
+---
+ mimetreeparser/src/messagepart.cpp | 12 +++-
+ 1 file changed, 11 insertions(+), 1 deletion(-)
+
+diff --git a/mimetreeparser/src/messagepart.cpp
b/mimetreeparser/src/messagepart.cpp
+index f1489d5e0..3e99e71c8 100644
+--- a/mimetreeparser/src/messagepart.cpp
b/mimetreeparser/src/messagepart.cpp
+@@ -848,8 +848,18 @@ void SignedMessagePart::sigStatusToMetaData()
+ // Search for the key by its fingerprint so that we can check for
+ // trust etc.
+ key =
Kleo::KeyCache::instance()->findByFingerprint(signature.fingerprint());
++if (key.isNull() && signature.fingerprint()) {
++// try to find a subkey that was used for signing;
++// assumes that the key ID is the last 16 characters of the
fingerprint
++const auto fpr = std::string_view{signature.fingerprint()};
++const auto keyID = std::string{fpr, fpr.size() - 16, 16};
++const auto subkeys =
Kleo::KeyCache::instance()->findSubkeysByKeyID({keyID});
++if (subkeys.size() > 0) {
++key = subkeys[0].parent();
++}
++}
+ if (key.isNull()) {
+-qCDebug(MIMETREEPARSER_LOG) << "Found no Key for Fingerprint"
<< signature.fingerprint();
++qCDebug(MIMETREEPARSER_LOG) << "Found no key or subkey for
fingerprint" << signature.fingerprint();
+ }
+ }
+
+--
+2.40.1
+
Bug#1038140: bookworm-pu: package onionshare/2.6-5
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: onionsh...@packages.debian.org,
pkg-privacy-maintain...@alioth-lists.debian.net, he...@debian.org
Control: affects -1 + src:onionshare
[ Reason ]
The version 2.6-4 does not install icons, desktop file and appstream metadata
file at the
correct place (Closes: #1036691). So users can only run onionshare via
commandline.
[ Tests ]
Autopkgtests make sure, that the main parts of the package are still
functioning. Manual tests, that onionshare is listed in desktop menu and
that it has the correct icon. Same version is installed in sid.
[ Risks ]
No real risks, as it is only installing some files to correct places.
[ 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 (old)stable
[x] the issue is verified as fixed in unstable
Do I need to do update the version with a stable extension ~deb12u1 as there
won't be any diff?
diff -Nru onionshare-2.6/debian/changelog onionshare-2.6/debian/changelog
--- onionshare-2.6/debian/changelog 2023-05-05 14:41:35.0 +0200
+++ onionshare-2.6/debian/changelog 2023-06-13 12:23:22.0 +0200
@@ -1,3 +1,10 @@
+onionshare (2.6-5) unstable; urgency=medium
+
+ * Install desktp/appmetadata at expected places. (Closes: #1036691)
+ * Install icons under usr/share/icons.
+
+ -- Sandro Knauß Tue, 13 Jun 2023 12:23:22 +0200
+
onionshare (2.6-4) unstable; urgency=medium
* Mark chat-server test as flaky, as it fails on i386 also randomly.
diff -Nru onionshare-2.6/debian/rules onionshare-2.6/debian/rules
--- onionshare-2.6/debian/rules 2022-12-22 14:32:13.0 +0100
+++ onionshare-2.6/debian/rules 2023-06-06 21:21:03.0 +0200
@@ -4,6 +4,8 @@
%:
dh $@ --buildsystem=pybuild
+SIZES = 16 32 64 128 256 512
+
override_dh_auto_build:
PYBUILD_NAME=onionshare-cli dh_auto_build --buildsystem=pybuild
--sourcedirectory cli --\
--after-build "CURDIR=$(CURDIR) BUILD_DIR={build_dir}
$(CURDIR)/debian/missing-sources/uglifyjs.sh"
@@ -24,8 +26,22 @@
rm debian/onionshare/usr/bin/onionshare-cli
execute_after_dh_auto_install:
- mkdir -p debian/onionshare/usr/share
+ mkdir -p debian/onionshare/usr/share/metainfo
+ cp desktop/org.onionshare.OnionShare.appdata.xml
debian/onionshare/usr/share/metainfo/
+ mkdir -p debian/onionshare/usr/share/applications
+ cp desktop/org.onionshare.OnionShare.desktop
debian/onionshare/usr/share/applications/
+
mv
debian/onionshare/usr/lib/python3*/dist-packages/onionshare/resources
debian/onionshare/usr/share/onionshare
+
+ # Move icons to the places where they are searched
+ mkdir -p debian/onionshare/usr/share/icons/hicolor/scalable/apps
+ cp desktop/org.onionshare.OnionShare.svg
debian/onionshare/usr/share/icons/hicolor/scalable/apps/
+ $(foreach size,$(SIZES), \
+ mkdir debian/onionshare/usr/share/icons/hicolor/$(size)x$(size); \
+ mv debian/onionshare/usr/share/onionshare/onionshare-$(size).png
debian/onionshare/usr/share/icons/hicolor/$(size)x$(size)/org.onionshare.OnionShare.png;
\
+ ln -s
/usr/share/icons/hicolor/$(size)x$(size)/org.onionshare.OnionShare.png
debian/onionshare/usr/share/onionshare/onionshare-$(size).png; \
+ ) true
+
mkdir -p debian/onionshare-cli/usr/share
mv
debian/onionshare-cli/usr/lib/python3*/dist-packages/onionshare_cli/resources
debian/onionshare-cli/usr/share/onionshare-cli
Bug#1037364: nextcloud-desktop: TLS initilization failed
Control: tags -1 moreinfo Control: serverity -1 important Hey, I never had issues with using Nextcloud desktop to connect to my server, that's why I downgrade the serverity, as it has something to do with your specific setup. I expect that the issue is that your server only accepts TLS < 1.3. The last years a lot of ciphers are not trusted anymore by default. You can check your servers certificate with online tools e.g. https://www.ssllabs.com/ssltest/. regards, hefee signature.asc Description: This is a digitally signed message part.
Bug#1035593: unblock: kwin/4:5.27.2-2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: k...@packages.debian.org, he...@debian.org
Control: affects -1 + src:kwin
Please unblock package kwin
[ Reason ]
Fix 1033212. For limba phones kwin is not usable at all, with that fix
it is usable again.
[ Impact ]
Plasma mobile is not usable on limba phones.
[ Tests ]
Marco Mattiolo, the author of the patch for kwin, tested it on their
devices.
[ Risks ]
The patch is very simple and straightforward. For me it seems not very
likly that it has bad outcome for other users. On experimental there is
also kwin 5.27.3 with that patch included and that is also tested be a
bunch of people.
[ 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 ]
You do a great work and you are very fast responding ;)
unblock kwin/4:5.27.2-2
diff -Nru kwin-5.27.2/debian/changelog kwin-5.27.2/debian/changelog
--- kwin-5.27.2/debian/changelog2023-02-28 15:01:10.0 +0100
+++ kwin-5.27.2/debian/changelog2023-05-05 14:22:35.0 +0200
@@ -1,3 +1,12 @@
+kwin (4:5.27.2-2) unstable; urgency=medium
+
+ * Team upload.
+
+ [ Marco Mattiolo ]
+ * Backport patch to fix kwin for Lima (Pinephone) (Closes: #1033212)
+
+ -- Sandro Knauß Fri, 05 May 2023 14:22:35 +0200
+
kwin (4:5.27.2-1) unstable; urgency=medium
[ Aurélien COUDERC ]
diff -Nru kwin-5.27.2/debian/patches/fix-for-Lima-disabling-GLSL.patch
kwin-5.27.2/debian/patches/fix-for-Lima-disabling-GLSL.patch
--- kwin-5.27.2/debian/patches/fix-for-Lima-disabling-GLSL.patch
1970-01-01 01:00:00.0 +0100
+++ kwin-5.27.2/debian/patches/fix-for-Lima-disabling-GLSL.patch
2023-05-05 14:16:46.0 +0200
@@ -0,0 +1,47 @@
+From 64d682a646d111a0250bbe3bff77ef0cead91403 Mon Sep 17 00:00:00 2001
+From: Hannah Kiekens
+Date: Tue, 28 Feb 2023 21:04:37 +
+Subject: [PATCH] Enable GLSL for Mali (Lima) / PinePhone devices
+
+Commit 88cf8355 changed the behaviour of Mali (Lima) / PinePhone devices by
disabling GLSL
+88cf8355 got backported in 5.27.1 and broke PinePhone devices (White rectangle
on topright quarter of a black screen)
+
+This patch restores the behaviour of 5.27.0
+
+
+(cherry picked from commit 0543949df709c69c99c46c9abad483250b01c288)
+---
+ .../libkwineffects/data/glplatform/lima-mali400-desktop-3.0| 2 +-
+ src/libkwineffects/kwinglplatform.cpp | 3 +--
+ 2 files changed, 2 insertions(+), 3 deletions(-)
+
+diff --git a/autotests/libkwineffects/data/glplatform/lima-mali400-desktop-3.0
b/autotests/libkwineffects/data/glplatform/lima-mali400-desktop-3.0
+index 8e32a85af81..cf83810fd8b 100644
+--- a/autotests/libkwineffects/data/glplatform/lima-mali400-desktop-3.0
b/autotests/libkwineffects/data/glplatform/lima-mali400-desktop-3.0
+@@ -6,7 +6,7 @@ ShadingLanguageVersion=1.30
+
+ [Settings]
+ LooseBinding=true
+-GLSL=false
++GLSL=true
+ TextureNPOT=true
+ Mesa=true
+ Lima=true
+diff --git a/src/libkwineffects/kwinglplatform.cpp
b/src/libkwineffects/kwinglplatform.cpp
+index 82554ca755b..aa0f5b105a5 100644
+--- a/src/libkwineffects/kwinglplatform.cpp
b/src/libkwineffects/kwinglplatform.cpp
+@@ -1138,8 +1138,7 @@ void GLPlatform::detect(OpenGLPlatformInterface
platformInterface)
+
+ if (isLima()) {
+ m_recommendedCompositor = OpenGLCompositing;
+-// GLSL works but causes dramatic FPS drop on this GPU
+-m_supportsGLSL = false;
++m_supportsGLSL = true;
+ }
+
+ if (isVideoCore4()) {
+--
+GitLab
+
diff -Nru kwin-5.27.2/debian/patches/series kwin-5.27.2/debian/patches/series
--- kwin-5.27.2/debian/patches/series 2022-10-02 18:15:15.0 +0200
+++ kwin-5.27.2/debian/patches/series 2023-05-05 14:16:46.0 +0200
@@ -1 +1,2 @@
uninitialized-yuvformat.patch
+fix-for-Lima-disabling-GLSL.patch
Bug#1035513: unblock: onionshare/2.6-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: onionsh...@packages.debian.org, he...@debian.org Control: affects -1 + src:onionshare Please unblock package onionshare [ Reason ] The new version fixes #1014966. It is only a fix in autopkgtests to make them non flaky. [ Impact ] As the new version only fixes autopkgtests, nothing for the users changes. [ Tests ] Run together with people of debianci the tests around 30 times to make sure, that is not flaky. [ Risks ] The risks are very low,as it does not toches the code itself. [ 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 ] onionshare is marked as autoremoval on 20th, May. With the current aging of 20 days, the package would be kicked out of testing before the 20-days delay is over. unblock onionshare/2.6-3 diff -Nru onionshare-2.6/debian/changelog onionshare-2.6/debian/changelog --- onionshare-2.6/debian/changelog 2022-11-19 17:38:57.0 +0100 +++ onionshare-2.6/debian/changelog 2023-05-04 15:24:12.0 +0200 @@ -1,3 +1,15 @@ +onionshare (2.6-3) unstable; urgency=medium + + * source only upload. + + -- Sandro Knauß Thu, 04 May 2023 15:24:12 +0200 + +onionshare (2.6-2) unstable; urgency=medium + + * The verbose flag makes the chat test not flaky. (Closes: #1034688) + + -- Sandro Knauß Tue, 02 May 2023 22:27:57 +0200 + onionshare (2.6-1) unstable; urgency=medium * new upstream release diff -Nru onionshare-2.6/debian/tests/control onionshare-2.6/debian/tests/control --- onionshare-2.6/debian/tests/control 2022-11-19 17:38:57.0 +0100 +++ onionshare-2.6/debian/tests/control 2023-04-25 23:45:25.0 +0200 @@ -18,7 +18,7 @@ Restrictions: allow-stderr, Features: test-name=share_website -Test-Command: XDG_CONFIG_HOME="$AUTOPKGTEST_TMP" onionshare-cli --local-only --chat --auto-stop-timer 2 +Test-Command: XDG_CONFIG_HOME="$AUTOPKGTEST_TMP" onionshare-cli -v --local-only --chat --auto-stop-timer 2 Depends: onionshare-cli Restrictions: allow-stderr, Features: test-name=chat_server
Bug#998325: akonadi-server: akonadi_indexing_agent crashes when kmail is active
Control: tags -1 +moreinfo Hey, that is properly a email, that triggers the indexer to crash. To get more details please install libkf5akonadisearchpim5-dbgsym to get a propper backtrace. Additionally, run akonadi with debug logging enabled: QT_LOGGING_RULES="*.debug=true;qt.*=false" akonadictl restart that should points you to the mail, that triggers this crash. Regards, hefee -- On Dienstag, 2. November 2021 13:44:03 CEST Hans-J. Ullrich wrote: > Package: akonadi-server > Version: 4:20.08.3-3 > Severity: important > > Dear Maintainer, > > I hope, this is the right package. I have the following problem with akonadi > on debian/bullseye, amd64. > > Problem: When I start kmail, then akoandi is crashing with the message, > "akonadi_indexing_agent is crashed" > > This is the output of the error: > > snip - > > > Application: akonadi_indexing_agent (akonadi_indexing_agent), signal: > Aborted > > [KCrash Handler] > #4 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 > #5 0x7f5ad974f537 in __GI_abort () at abort.c:79 > #6 0x7f5ad99a57ec in () at /lib/x86_64-linux-gnu/libstdc++.so.6 > #7 0x7f5ad99b0966 in () at /lib/x86_64-linux-gnu/libstdc++.so.6 > #8 0x7f5ad99b09d1 in () at /lib/x86_64-linux-gnu/libstdc++.so.6 > #9 0x7f5ad99b0c65 in () at /lib/x86_64-linux-gnu/libstdc++.so.6 > #10 0x7f5adb19bd0f in () at /lib/x86_64-linux-gnu/libxapian.so.30 > #11 0x7f5adb2516be in () at /lib/x86_64-linux-gnu/libxapian.so.30 > #12 0x7f5adb2517e2 in () at /lib/x86_64-linux-gnu/libxapian.so.30 > #13 0x7f5adb252e0c in () at /lib/x86_64-linux-gnu/libxapian.so.30 > #14 0x7f5adb23d7c9 in () at /lib/x86_64-linux-gnu/libxapian.so.30 > #15 0x7f5adb1b2101 in () at /lib/x86_64-linux-gnu/libxapian.so.30 > #16 0x7f5adb2b1140 in () at /lib/x86_64-linux-gnu/libxapian.so.30 > #17 0x7f5adb1c2fd8 in Xapian::Enquire::Internal::get_mset(unsigned int, > unsigned int, unsigned int, Xapian::RSet const*, Xapian::MatchDecider > const*) const () at /lib/x86_64-linux-gnu/libxapian.so.30 #18 > 0x7f5adb1c3245 in Xapian::Enquire::get_mset(unsigned int, unsigned int, > unsigned int, Xapian::RSet const*, Xapian::MatchDecider const*) const () at > /lib/x86_64-linux-gnu/libxapian.so.30 #19 0x7f5adb3be231 in () at > /lib/x86_64-linux-gnu/libKF5AkonadiSearchPIM.so.5 #20 0x7f5adb3be611 in > () at /lib/x86_64-linux-gnu/libKF5AkonadiSearchPIM.so.5 #21 > 0x55ebc1bd976a in () > #22 0x7f5ad9dbc5a6 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 > #23 0x7f5ada7aed29 in KJob::finished(KJob*, KJob::QPrivateSignal) () at > /lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 #24 0x7f5ada7af97c in > KJob::finishJob(bool) () at /lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 #25 > 0x7f5ad9db1ff1 in QObject::event(QEvent*) () at > /lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x7f5ada96b15f in > QApplicationPrivate::notify_helper(QObject*, QEvent*) () at > /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #27 0x7f5ad9d85fca in > QCoreApplication::notifyInternal2(QObject*, QEvent*) () at > /lib/x86_64-linux-gnu/libQt5Core.so.5 #28 0x7f5ad9d88a01 in > QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () > at /lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x7f5ad9ddde93 in () at > /lib/x86_64-linux-gnu/libQt5Core.so.5 #30 0x7f5ad83f1e6b in > g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #31 > 0x7f5ad83f2118 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #32 > 0x7f5ad83f21cf in g_main_context_iteration () at > /lib/x86_64-linux-gnu/libglib-2.0.so.0 #33 0x7f5ad9ddd51f in > QEventDispatcherGlib::processEvents(QFlags) > () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #34 0x7f5ad9d8498b in > QEventLoop::exec(QFlags) () at > /lib/x86_64-linux-gnu/libQt5Core.so.5 #35 0x7f5ad9d8cc00 in > QCoreApplication::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #36 > 0x55ebc1bc8ca8 in () > #37 0x7f5ad9750d0a in __libc_start_main (main=0x55ebc1bc3090, argc=3, > argv=0x7ffccce092a8, init=, fini=, > rtld_fini=, stack_end=0x7ffccce09298) at > ../csu/libc-start.c:308 #38 0x55ebc1bc30ca in () > [Inferior 1 (process 12884) detached] > > > snap > > Restarting akonadi-server and mysql does not help. Dunno, if this has > something to do with it, but this appeared after the last upgrade of > openjdk (however, it is not clear for me, that openjdk should cause this > issue, maybe it is just a coincidence. > > Hope, this mails does help though. > > Best regards > > Hans > > > -- System Information: > Debian Release: 11.1 > APT prefers stable-updates > APT policy: (500, 'stable-u
Bug#1008885: loops endlessly about (failed?) mariadb start
Control: tags -1 moreinfo
Hi,
About the loop: I never seen that before - It normally just fails and than not
try again to start up again. It maybe related with systemd integration of
Plasma. Or do you have any special autostart scripts? And with the newer
versions the wayland support got better, so maybe the issue is solved in
meanwhile?
if you don't use any Akonadi feature and don't want to remove meta-packages. I
would suggest to use akonadi-backend-sqlite and remove the mysql one.
Unfortunatelly you really need to modify your akonadiserverrc config. That at
least should make it start more easily. See the blog entry:
https://euroquis.nl//freebsd/2023/04/24/akonadi.html
Regards,
hefee
On Sonntag, 3. April 2022 13:57:05 CEST Marc Haber wrote:
> Package: akonadi-server
> Version: 4:21.12.3-2
> Severity: normal
>
> Hi,
>
> to see whether KDE Wayland works better when started via gdm3 instead of
> sddm (spoiler: No, same way of broken as with sddm), I exchanged sddm
> with gdm3. After going back to KDE X11 Session, I found my log being
> spammed with the following pattern, repeated endlessly:
>
> Apr 3 13:33:47 fan /usr/libexec/gdm-x-session[723825]:
> org.kde.pim.akonadiserver: Starting up the Akonadi Server... Apr 3
> 13:33:47 fan /usr/libexec/gdm-x-session[723821]:
> org.kde.pim.akonadicontrol: Service org.freedesktop.Akonadi.Control.lock
> already registered, terminating now. Apr 3 13:33:52 fan
> /usr/libexec/gdm-x-session[723825]: org.kde.pim.akonadiserver: database
> server stopped unexpectedly Apr 3 13:33:52 fan
> /usr/libexec/gdm-x-session[723825]: org.kde.pim.akonadiserver: Database
> process exited unexpectedly during initial connection! Apr 3 13:33:52 fan
> /usr/libexec/gdm-x-session[723825]: org.kde.pim.akonadiserver: executable:
> "/usr/sbin/mysqld" Apr 3 13:33:52 fan /usr/libexec/gdm-x-session[723825]:
> org.kde.pim.akonadiserver: arguments:
> ("--defaults-file=/home/mh/.local/share/akonadi/mysql.conf",
> "--datadir=/home/mh/.local/share/akonadi/db_data/",
> "--socket=/run/user/1001/akonadi/mysql.socket",
> "--pid-file=/run/user/1001/akonadi/mysql.pid") Apr 3 13:33:52 fan
> /usr/libexec/gdm-x-session[723825]: org.kde.pim.akonadiserver: stdout: ""
> Apr 3 13:33:52 fan /usr/libexec/gdm-x-session[723825]:
> org.kde.pim.akonadiserver: stderr: "2022-04-03 13:33:47 0 [Note]
> /usr/sbin/mysqld (server 10.6.7-MariaDB-3) starting as process 723831
> ...\n" Apr 3 13:33:52 fan /usr/libexec/gdm-x-session[723825]:
> org.kde.pim.akonadiserver: exit code: 1 Apr 3 13:33:52 fan
> /usr/libexec/gdm-x-session[723825]: org.kde.pim.akonadiserver: process
> error: "Unknown error" Apr 3 13:33:52 fan
> /usr/libexec/gdm-x-session[723825]: org.kde.pim.akonadiserver: Shutting
> down AkonadiServer... Apr 3 13:33:52 fan
> /usr/libexec/gdm-x-session[723819]: org.kde.pim.akonadicontrol: Application
> '/usr/bin/akonadiserver' exited normally... Apr 3 13:33:52 fan
> /usr/libexec/gdm-x-session[716950]: qt.qpa.xcb: QXcbConnection: XCB error:
> 3 (BadWindow), sequence: 58290, resource id: 67108869, major code: 18
> (ChangeProperty), minor code: 0 Apr 3 13:33:52 fan
> /usr/libexec/gdm-x-session[723843]: Connecting to deprecated signal
> QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) Apr
> 3 13:33:52 fan /usr/libexec/gdm-x-session[723845]:
> org.kde.pim.akonadicontrol: Service org.freedesktop.Akonadi.Control.lock
> already registered, terminating now. Apr 3 13:33:52 fan
> /usr/libexec/gdm-x-session[723849]: org.kde.pim.akonadiserver: Starting up
> the Akonadi Server... Apr 3 13:33:57 fan
> /usr/libexec/gdm-x-session[723849]: org.kde.pim.akonadiserver: database
> server stopped unexpectedly Apr 3 13:33:57 fan
> /usr/libexec/gdm-x-session[723849]: org.kde.pim.akonadiserver: Database
> process exited unexpectedly during initial connection! Apr 3 13:33:57 fan
> /usr/libexec/gdm-x-session[723849]: org.kde.pim.akonadiserver: executable:
> "/usr/sbin/mysqld" Apr 3 13:33:57 fan /usr/libexec/gdm-x-session[723849]:
> org.kde.pim.akonadiserver: arguments:
> ("--defaults-file=/home/mh/.local/share/akonadi/mysql.conf",
> "--datadir=/home/mh/.local/share/akonadi/db_data/",
> "--socket=/run/user/1001/akonadi/mysql.socket",
> "--pid-file=/run/user/1001/akonadi/mysql.pid") Apr 3 13:33:57 fan
> /usr/libexec/gdm-x-session[723849]: org.kde.pim.akonadiserver: stdout: ""
> Apr 3 13:33:57 fan /usr/libexec/gdm-x-session[723849]:
> org.kde.pim.akonadiserver: stderr: "2022-04-03 13:33:52 0 [Note]
> /usr/sbin/mysqld (server 10.6.7-MariaDB-3) starting as process 723855
> ...\n" Apr 3 13:33:57 fan /usr/libexec/gdm-x-session[723849]:
> org.kde.pim.
Bug#906693: akonadi-server: Akonadi waits to short for password
Control: tags -1 +moreinfo unreproducible Hey, Sorry that I haven't found time to look to it further. Well times runs and we already have 20.8 version on current stable additionally upstream has moved from direct KWallet support to use QtKeychain so also support other key storages. So it is a good time to retest it again, if it is still an issue. Myself hasn't seen this issue for several years. Regards, hefee -- On Sonntag, 19. August 2018 20:57:07 CEST Valentin Petzel wrote: > Package: akonadi-server > Version: 4:17.12.3-3 > Severity: normal > > Dear Maintainer, > > When establishing a connection to an account, where the password is > stored in KWallet, Akonadi prompts the password apparently if it doesn't > respond for some time. This is set so short that on login one is often > prompted for the e-Mail accounts' passwords before one has the chance to > enter the password for KWallet's encryption. You might want to consider > increasing the time Akonadi waits for the passwords. > > -- System Information: > Debian Release: buster/sid > APT prefers oldstable-updates > APT policy: (500, 'oldstable-updates'), (500, > 'oldstable-proposed-updates'), (500, 'unstable'), (500, 'oldstable') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 4.9.11-towo.2-siduction-amd64 (SMP w/4 CPU cores; PREEMPT) > Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8), LANGUAGE=de > (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages akonadi-server depends on: > ii akonadi-backend-mysql 4:17.12.3-3 > ii akonadi-backend-sqlite 4:17.12.3-3 > ii libc6 2.27-5 > ii libgcc11:8.2.0-2 > ii libkf5akonadiprivate5abi1 4:17.12.3-3 > ii libkf5akonadiwidgets5abi1 4:17.12.3-3 > ii libkf5configcore5 5.47.0-1 > ii libkf5coreaddons5 5.47.0-1 > ii libkf5crash5 5.47.0-1 > ii libkf5i18n55.47.0-1 > ii libqt5core5a 5.11.1+dfsg-6 > ii libqt5dbus55.11.1+dfsg-6 > ii libqt5gui5 5.11.1+dfsg-6 > ii libqt5network5 5.11.1+dfsg-6 > ii libqt5sql5 5.11.1+dfsg-6 > ii libqt5widgets5 5.11.1+dfsg-6 > ii libqt5xml5 5.11.1+dfsg-6 > ii libstdc++6 8.2.0-2 > > akonadi-server recommends no packages. > > Versions of packages akonadi-server suggests: > ii akonadi-backend-mysql 4:17.12.3-3 > pn akonadi-backend-postgresql > ii akonadi-backend-sqlite 4:17.12.3-3 > > -- no debconf information signature.asc Description: This is a digitally signed message part.
Bug#1035056: [pre-approval] plasma-desktop 5.27.X
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: pu X-Debbugs-Cc: plasma-desk...@packages.debian.org, pkg-kde-talk%40alioth-lists.debian.net, he...@debian.org Control: affects -1 + src:plasma-desktop Hey, before invest time, to do the debdiff and all paperwork for Plasma 5.27.X LTS packages, there's need to be a idea, how to get it into stable. Currently 5.27.3 on experimental. Upstream is relasing with a fibbonacci time frame, when stable will be release, we would be at ~5.27.5. I wanted to ask, if we find a solution together to get the new version into bookworm. Upstream wants to give bugfix releases over 2 years. Plasma 5.27 is a LTS branch, that is stable and only bug fixes with be released with next minor versions. No transitions nor API changes. By the time the most bug fixes are around multi screen support. From my point of view users would definitly benefit from these updates with no negative effect. Alternatives: * Using backport is not an option, because upstream is switching to Plasma 6 (based on Qt6), that will enter in sid soon after bookworm has released. * extract all bugfixes from Plasma 5.27.X and apply them as patches on top and remove the version bump. In the end it is a lot more work on our plate, with no benefit for users. Upstream has much more problems to understand, that Debian has all bugfixes included. It is the first time we the KDE manatiner are in this lucky situation that we can use the LTS releases from upstream. I hope we will find a good solution together to make the user experince better and not put a lot of work on yours/ours plate. The NACK on #1033271 made part of the team quite unmotivated to try it for Plasma. See the mail thread [1] Regards, hefee Plasma is ~50 pacakges - see a list of packages: https://salsa.debian.org/qt-kde-team/pkg-kde-dev-scripts/-/blob/master/tierdata/plasma.5.25.0.tier.sh [1] https://alioth-lists.debian.net/pipermail/pkg-kde-talk/2023-April/003467.html
Bug#1034688: [Pkg-privacy-maintainers] Bug#1034688: onionshare: flaky autopkgtest
Hey, I have no real idea why we see only a problem in the chat_server test. It is a problem in the shutdown... I can mark it as superficial so the failing test does not block the CI. But is only a workaround. Can you enable the verbose flag by hand, so we can see what function triggers this segmentation fault? Test-Command: XDG_CONFIG_HOME="$AUTOPKGTEST_TMP" onionshare-cli -v --local- only --chat --auto-stop-timer 2 Or can you give me the the back trace of the segmentation fault? On my system, I don't see the segmentation fault, so hard to taggle down. Properly it is https://github.com/onionshare/onionshare/issues/1408#issuecomment-908150292 and it is harmless. But without verbose log I cannot be sure. > The autopkgtests from onionshare are flaky and have been failing roughly > half the time over the last couple of weeks. Does that mean, that it run successfully before? Regards, hefee -- On Freitag, 21. April 2023 20:53:03 CEST Sebastian Ramacher wrote: > Source: onionshare > Version: 2.6-1 > Severity: serious > > > https://ci.debian.net/data/autopkgtest/testing/amd64/o/onionshare/32901091/l > og.gz > > Give this address and private key to the recipient: > http://127.0.0.1:17632 > Private key: E2GOT5LTUTP3OAMRCRXO4GSH6VKJEUOXZQUC336SRKAHTTT5OVSA > > Press Ctrl+C to stop the server > Stopped because auto-stop timer ran out > Segmentation fault > autopkgtest [22:20:10]: test chat_server: ---] > autopkgtest [22:20:10]: test chat_server: - - - - - - - - - - results - - - > - - - - - - - chat_server FAIL non-zero exit status 139 signature.asc Description: This is a digitally signed message part.
Bug#924788: /usr/bin/akonadictl: aKonadi server with postgreSQL backend fails to start after buster upgrade
Control: tags -1 +moreinfo unreproducible Hey, Sorry that I haven't found time to look to it further. >From the file list it seems like you switched to from PostgresQL backend to Mysql backend by dist-upgrade and than started it. That removed all of the postgres cluster. Maybe the config that selected the PostgresQL was removed while the upgrade? I need more information in order to fix anything. > I expect that aKonadi should be using postgreSQL 11, not 9.6, but that it > will auto-migrate my data. I don't know when this support was added to Akonadi, but bookworm will support for sure automatic upgrades to new PostgresQL versions. Regards, hefee signature.asc Description: This is a digitally signed message part.
Bug#969171: Again, not even looked at the real problem.
Hey, On Sonntag, 11. April 2021 20:18:51 CEST Eric Valette wrote: > > I think it is not a bug of the package. But it is definitely not severity > > grave as Akonadi is perfectly usable here in exact the same version > > (usable to the extent Akonadi works reliable, but that is an upstream > > issue). So downgrading severity to normal. > > When only akonadi-backend-sqlite is installed as you can see in > installed packages I find normal that the default config file is changed > to use sqlite by default as I would expect that removing > akonadi-backend-mysql would remove the mysql backend if it was used with > a warning. > > But apparently, you are more interested in having the package without > bug than working to simplify your user's life. We see this as a bug, too. Otherwise we would close this bug as invalid ;) Debian can't easily distinguish, if you only installed one backend or differnt ones. Well we could add logic to detect this, but that would be very error prune. So the proper solution needs to be done upstream aka in Akonadi directly. Akonadi has no support to check what different backends are available but simply try to start mysql. And if you tried it once, than Akonadi has created a user config that selects the mysql database and it is outside our control to switch the backend. Because Debian packages are not allowed to touch any stuff in $HOME. Never the less in future for trixie the situation needs to be improved, as Akonadi switched its default backend over to SQLite (see #1034561). Detecting available backends is becoming a bigger issue. Any help from your side to fix the problem is highly welcome: merge request, upstream bug report, patch etc. Unfortunately the Debian maintainers team is a lot of work and not enough resources, to do all work. Regards, hefee #1034561: https://bugs.debian.org/1034561 signature.asc Description: This is a digitally signed message part.
Bug#1034561: akonadi-server: Switch default Akonadi backend to SQLite
Package: akonadi-server Version: 4:22.12.3-1 Severity: normal X-Debbugs-Cc: he...@debian.org Hey, Upstream has changed their support for akonadi backends. Nowadays they recommend to use SQLite, Postgres and MySQL/MariaDB is not really recommend anymore. So we should change the Depends line for akonadi-server, after bullseye has been released. -- Forwarded Message -- Subject: Re: Is SQLite3 still not recommended? Date: Tuesday, 4. April 2023, 09:25:31 CEST Link: https://mail.kde.org/pipermail/kde-pim/2023-April/049426.html Hi, I think SQLite is a good choice these days. SQLite has made huge progress in the past many years since its support has been introduced to Akonadi. The documentation on wiki is certainly not up-to-date. While I was a big advocate for pushing PostgreSQL as the default backend for Akonadi in the past, I think nowadays going for anything else than SQLite as the default backend is silly. Especially with today's fast SSD drives, I don't think a regular user will notice any difference, it might actually turn out to be the fastest solution overall. Coincidentally, I recently learned that the SQLite shared cache mode, which Akonadi uses, has been deprecated for a while and WAL mode is now recommended for most usecases, so that's something to look into. There might be more new features in SQLite that have been introduced in the past years that Akonadi could leverage for better performance.
Bug#1034184: [Pkg-owncloud-maintainers] Bug#1034184: nextcloud-desktop: CVE-2023-28999
control: tags -1 + moreinfo Hey, thanks for your intial work in this bug. I added some more digging work into it that ends up with a lot of question marks... Do you know for sure, that the merge request #5560 fixes the CVE-2023-28999? At least I looked at the merge request and it is a very big one that touches 34 files (660 lines added/483 lines removed) and the commits have white space changes and add a new metadata version (1.2). Do we need this new metadata version in order to fix the CVE? In total this does not looks like just a bugfix but as a feature branch. It does not looks like, we can simply ship this big patch to bookworm/bullseye :( The commit that adds a new metadata version: https://github.com/nextcloud/desktop/pull/5560/commits/ 1b0a93eabc8f1322ef299cba3c4db81944c7d2c6 At least there are other merge requests that touches E2EE in Nextcloud Desktop: https://github.com/nextcloud/desktop/pull/5534 and than there are these new issues with 3.8.0 and EE2E, that scares me to back port additionally: https://github.com/nextcloud/desktop/issues/5564 Additionally it does not apply clean on the v3.7.3 - so more work needs to put into getting this into Debian. regards, hefee > The following vulnerability was published for nextcloud-desktop. > > CVE-2023-28999[0]: > | Nextcloud is an open-source productivity platform. In Nextcloud > | Desktop client 3.0.0 until 3.8.0, Nextcloud Android app 3.13.0 until > | 3.25.0, and Nextcloud iOS app 3.0.5 until 4.8.0, a malicious server > | administrator can gain full access to an end-to-end encrypted folder. > | They can decrypt files, recover the folder structure and add new > | files.#8203; This issue is fixed in Nextcloud Desktop 3.8.0, > | Nextcloud Android 3.25.0, and Nextcloud iOS 4.8.0. No known > | workarounds are available. > > https://github.com/nextcloud/security-advisories/security/advisories/GHSA-88 > 75-wxww-3rr8 https://github.com/nextcloud/desktop/pull/5560 > > If you fix the vulnerability please also make sure to include the > CVE (Common Vulnerabilities & Exposures) id in your changelog entry. > > For further information see: > > [0] https://security-tracker.debian.org/tracker/CVE-2023-28999 > https://www.cve.org/CVERecord?id=CVE-2023-28999 > > Please adjust the affected versions in the BTS as needed. > > ___ > Pkg-owncloud-maintainers mailing list > pkg-owncloud-maintain...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-owncloud-mainta > iners signature.asc Description: This is a digitally signed message part.
Bug#1033383: unblock: itinerary/22.12.3-1
Forgotten to attach the debdiff. Sorry for that.
hefee
diff -Nru itinerary-22.12.2/autotests/timelinesectiondelegatecontrollertest.cpp itinerary-22.12.3/autotests/timelinesectiondelegatecontrollertest.cpp
--- itinerary-22.12.2/autotests/timelinesectiondelegatecontrollertest.cpp 2023-01-30 00:56:54.0 +0100
+++ itinerary-22.12.3/autotests/timelinesectiondelegatecontrollertest.cpp 2023-02-25 05:55:22.0 +0100
@@ -22,6 +22,7 @@
void initLocale()
{
+qputenv("LC_ALL", "en_US.utf-8");
qputenv("TZ", "UTC");
qputenv("LANG", "en_US");
}
diff -Nru itinerary-22.12.2/CMakeLists.txt itinerary-22.12.3/CMakeLists.txt
--- itinerary-22.12.2/CMakeLists.txt 2023-01-30 00:56:54.0 +0100
+++ itinerary-22.12.3/CMakeLists.txt 2023-02-25 05:55:22.0 +0100
@@ -6,7 +6,7 @@
# KDE Application Version, managed by release script
set (RELEASE_SERVICE_VERSION_MAJOR "22")
set (RELEASE_SERVICE_VERSION_MINOR "12")
-set (RELEASE_SERVICE_VERSION_MICRO "2")
+set (RELEASE_SERVICE_VERSION_MICRO "3")
set (RELEASE_SERVICE_VERSION "${RELEASE_SERVICE_VERSION_MAJOR}.${RELEASE_SERVICE_VERSION_MINOR}.${RELEASE_SERVICE_VERSION_MICRO}")
project(itinerary VERSION ${RELEASE_SERVICE_VERSION})
diff -Nru itinerary-22.12.2/debian/changelog itinerary-22.12.3/debian/changelog
--- itinerary-22.12.2/debian/changelog 2023-02-06 08:31:25.0 +0100
+++ itinerary-22.12.3/debian/changelog 2023-03-24 00:10:48.0 +0100
@@ -1,3 +1,11 @@
+itinerary (22.12.3-1) unstable; urgency=medium
+
+ [ Sandro Knauß ]
+ * New upstream bugfix.
+ * Add missing QML runtime dependencies (Closes: #1032889)
+
+ -- Sandro Knauß Fri, 24 Mar 2023 00:10:48 +0100
+
itinerary (22.12.2-1) unstable; urgency=medium
* Team upload.
diff -Nru itinerary-22.12.2/debian/control itinerary-22.12.3/debian/control
--- itinerary-22.12.2/debian/control 2023-02-05 12:23:29.0 +0100
+++ itinerary-22.12.3/debian/control 2023-03-24 00:08:56.0 +0100
@@ -48,16 +48,24 @@
Package: itinerary
Architecture: any
-Depends: qml-module-org-kde-kitemmodels,
+Depends: plasma-framework,
+ qml-module-org-kde-kitemmodels,
+ qml-module-org-kde-i18n-localedata,
+ qml-module-org-kde-kirigami2,
qml-module-org-kde-kopeninghours,
qml-module-org-kde-kosmindoormap,
qml-module-org-kde-kpublictransport,
qml-module-org-kde-prison,
qml-module-qt-labs-platform,
qml-module-qt-labs-qmlmodels,
+ qml-module-qtgraphicaleffects,
qml-module-qtlocation,
qml-module-qtmultimedia,
qml-module-qtpositioning,
+ qml-module-qtquick-controls2,
+ qml-module-qtquick-layouts,
+ qml-module-qtquick-window2,
+ qml-module-qtquick2,
${misc:Depends},
${shlibs:Depends}
Description: Digital travel assistant protecting your privacy
diff -Nru itinerary-22.12.2/po/ca/kde-itinerary.po itinerary-22.12.3/po/ca/kde-itinerary.po
--- itinerary-22.12.2/po/ca/kde-itinerary.po 2023-01-30 00:56:54.0 +0100
+++ itinerary-22.12.3/po/ca/kde-itinerary.po 2023-02-25 05:55:22.0 +0100
@@ -9,7 +9,7 @@
msgstr ""
"Project-Id-Version: itinerary\n"
"Report-Msgid-Bugs-To: https://bugs.kde.org\n;
-"POT-Creation-Date: 2023-01-07 03:38+\n"
+"POT-Creation-Date: 2023-02-13 02:41+\n"
"PO-Revision-Date: 2022-11-22 10:43+0100\n"
"Last-Translator: Josep M. Ferrer \n"
"Language-Team: Catalan \n"
@@ -1314,18 +1314,18 @@
msgid "Itinerary change"
msgstr "Canvi en l'itinerari"
-#: app/localizer.cpp:124
+#: app/localizer.cpp:126
#, kde-format
msgctxt "day-only date format"
msgid "dd "
msgstr "dd "
-#: app/localizer.cpp:169
+#: app/localizer.cpp:171
#, kde-format
msgid "%1m"
msgstr "%1 m"
-#: app/localizer.cpp:172 app/localizer.cpp:174
+#: app/localizer.cpp:174 app/localizer.cpp:176
#, kde-format
msgid "%1km"
msgstr "%1 km"
diff -Nru itinerary-22.12.2/po/ca@valencia/kde-itinerary.po itinerary-22.12.3/po/ca@valencia/kde-itinerary.po
--- itinerary-22.12.2/po/ca@valencia/kde-itinerary.po 2023-01-30 00:56:54.0 +0100
+++ itinerary-22.12.3/po/ca@valencia/kde-itinerary.po 2023-02-25 05:55:22.0 +0100
@@ -9,7 +9,7 @@
msgstr ""
"Project-Id-Version: itinerary\n"
"Report-Msgid-Bugs-To: https://bugs.kde.org\n;
-"POT-Creation-Date: 2023-01-07 03:38+\n"
+"POT-Creation-Date: 2023-02-13 02:41+\n"
"PO-Revision-Date: 2022-11-22 10:43+0100\n"
"Last-Translator: Josep M. Ferrer \n"
"Language-Team: Catalan \n"
@@ -1314,18 +1314,18 @@
msgid "Itinerary change"
msgstr "Canvi en l'itinerari"
-#: app/localizer.cpp:1
Bug#1032047: mariadb-server: Preinst fails if user has mariadb running while system service stopped.
Hey, can you explain, why this is now an issue and wasn't for several Debian versions? As I package Akonadi for a while now I never had issues with Mariadb upgrades. I know from Postgres that you need to have both version installed ( old+new) to make a successfully upgrade, wouldn't that be a possible solution for MariaDB too? So that you do not remove the old mariadb-server version when installing the new one? Than a user can re-login and everything is fine. > But I would expect that to end up as a severe policy violation; I don't have > a reference handy though. That is at least also in my head, that it is not allowed to start/stop user processes. Regards, hefee PS: sorry I'm not a lot on my PC the last weeks. signature.asc Description: This is a digitally signed message part.
Bug#1033383: unblock: itinerary/22.12.3-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: itiner...@packages.debian.org, debian-qt-...@lists.debian.org, he...@debian.org Control: affects -1 + src:itinerary Please unblock package itinerary [ Reason ] The new version is only a small bugfix of itinerary and several updates of supported translations. So the only relevant change in code are two lines in src/app/localizer.cpp to show timezone information, if we are currently not in UTC. and one line in src/app/JourneySectionStopDelegate.qml to shorten long stop names in journey section view. Additionally I updated the list of all runtime QML depedencies to fix #1032889, that is the most relevant change to request the unblock request. [ Tests ] as the code fixes are only cosmetic, there are no special autotests and nothing big can break. I use itinerary myself so I can tell the app is still running. [ Risks ] trival changes / only a leaf package. [ 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 itinerary/22.12.3-1
Bug#1028571: bullseye-pu: package akregator/20.08.3-1+deb11u1
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: akrega...@packages.debian.org, Jeff Sacksteder
, he...@debian.org
Control: affects -1 + src:akregator
Hey,
[ Reason ]
[#1027689] - Akregator is not able to delete feeds/folders. It can end
in request data from websites you don't want to.
[ Impact ]
Akregator seems broken for users.
[ Tests ]
Manual test were done to check the patch and tests are still ongoing.
[ Risks ]
The patch it self comes from upstream and is a simply backport (int
replacement with uint). I think the risk of sideeffects is quite 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 (old)stable
[x] the issue is verified as fixed in unstable
diff -Nru akregator-20.08.3/debian/changelog akregator-20.08.3/debian/changelog
--- akregator-20.08.3/debian/changelog 2023-01-13 00:49:15.0 +0100
+++ akregator-20.08.3/debian/changelog 2020-12-16 01:50:53.0 +0100
@@ -1,11 +1,3 @@
-akregator (4:20.08.3-1+deb11u1) bullseye; urgency=medium
-
- [ Sandro Knauß ]
- * Add backport patch 2f6d4e233ae8178535d74c1da0cf75a54762d165.diff
-(Closes: #1027689).
-
- -- Sandro Knauß Fri, 13 Jan 2023 00:49:15 +0100
-
akregator (4:20.08.3-1) unstable; urgency=medium
[ Sandro Knauß ]
diff -Nru
akregator-20.08.3/debian/patches/2f6d4e233ae8178535d74c1da0cf75a54762d165.diff
akregator-20.08.3/debian/patches/2f6d4e233ae8178535d74c1da0cf75a54762d165.diff
---
akregator-20.08.3/debian/patches/2f6d4e233ae8178535d74c1da0cf75a54762d165.diff
2023-01-08 23:44:59.0 +0100
+++
akregator-20.08.3/debian/patches/2f6d4e233ae8178535d74c1da0cf75a54762d165.diff
1970-01-01 01:00:00.0 +0100
@@ -1,317 +0,0 @@
a/src/command/deletesubscriptioncommand.cpp
-+++ b/src/command/deletesubscriptioncommand.cpp
-@@ -124,7 +124,7 @@ public:
- void jobFinished();
-
- QWeakPointer m_list;
--int m_subscriptionId = -1;
-+uint m_subscriptionId = 0;
- };
-
- DeleteSubscriptionCommand::Private::Private(DeleteSubscriptionCommand *qq) :
q(qq)
-@@ -146,13 +146,13 @@ DeleteSubscriptionCommand::~DeleteSubscr
- delete d;
- }
-
--void DeleteSubscriptionCommand::setSubscription(const QWeakPointer
, int subId)
-+void DeleteSubscriptionCommand::setSubscription(const QWeakPointer
, uint subId)
- {
- d->m_list = feedList;
- d->m_subscriptionId = subId;
- }
-
--int DeleteSubscriptionCommand::subscriptionId() const
-+uint DeleteSubscriptionCommand::subscriptionId() const
- {
- return d->m_subscriptionId;
- }
a/src/command/deletesubscriptioncommand.h
-+++ b/src/command/deletesubscriptioncommand.h
-@@ -39,9 +39,9 @@ public:
- explicit DeleteSubscriptionCommand(QObject *parent = nullptr);
- ~DeleteSubscriptionCommand() override;
-
--void setSubscription(const QWeakPointer , int subId);
-+void setSubscription(const QWeakPointer , uint subId);
-
--int subscriptionId() const;
-+uint subscriptionId() const;
- QWeakPointer feedList() const;
-
- private:
a/src/command/editsubscriptioncommand.cpp
-+++ b/src/command/editsubscriptioncommand.cpp
-@@ -83,13 +83,13 @@ public:
- void jobFinished();
-
- QSharedPointer m_list;
--int m_subscriptionId;
-+uint m_subscriptionId;
- SubscriptionListView *m_subscriptionListView = nullptr;
- };
-
- EditSubscriptionCommand::Private::Private(EditSubscriptionCommand *qq) : q(qq)
- , m_list()
--, m_subscriptionId(-1)
-+, m_subscriptionId(0)
- , m_subscriptionListView(nullptr)
- {
- }
-@@ -108,13 +108,13 @@ EditSubscriptionCommand::~EditSubscripti
- delete d;
- }
-
--void EditSubscriptionCommand::setSubscription(const QSharedPointer
, int subId)
-+void EditSubscriptionCommand::setSubscription(const QSharedPointer
, uint subId)
- {
- d->m_list = feedList;
- d->m_subscriptionId = subId;
- }
-
--int EditSubscriptionCommand::subscriptionId() const
-+uint EditSubscriptionCommand::subscriptionId() const
- {
- return d->m_subscriptionId;
- }
a/src/command/editsubscriptioncommand.h
-+++ b/src/command/editsubscriptioncommand.h
-@@ -40,8 +40,8 @@ public:
- explicit EditSubscriptionCommand(QObject *parent = nullptr);
- ~EditSubscriptionCommand() override;
-
--void setSubscription(const QSharedPointer , int subId);
--int subscriptionId() const;
-+void setSubscription(const QSharedPointer , uint
subId);
-+uint subscriptionId() const;
- QSharedPointer feedList() const;
-
- SubscriptionListView *subscriptionListView() const;
a/src/command/expireitemscommand.cpp
-+++ b/src/command/expireitemscommand.cpp
-@@ -50,7 +50,7 @@ public:
- void jobFinished(KJob *);
-
- QWeakPointer m_feedList;
--QVector m_feeds;
-+QVector m_feeds;
- QSet m_jobs;
- };
-
-@@ -94,7 +94,7 @@ void ExpireItemsCommand::Private::create
Bug#1027689: Akregator Update
Control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=429444 Control: fixed -1 4:22.08.3-1 Hey, We cannot bring akregator 22.08.3 to stable without backport all other pim packages (~70). In principal it is doable but the Debian mantainer team is too small for this. See the direct build dependency graph (https:// salsa.debian.org/qt-kde-team/pkg-kde-dev-scripts/-/blob/master/tierdata/ kdepim.22.08.0.tier.png) On the other side we can backport individual commits to 20.08, if the apply clearly. That is the case for the referenced commit. So we can ship a fixed version in stable. BUT someone needs to test the fixed application, as it may introduce other bugs, as we cherry-pick one single commit. And it is not a one-line fix. Are you able to test the package, if I send you a link for the fixed debs? After we are sure, that the cherry-picking was successful. there is only some paperwork to do to ship the fixed package with the next stable point release. Cheers, hefee -- On Montag, 2. Januar 2023 00:14:28 CET Jeff Sacksteder wrote: > Package: Akregator > Version: 4:20.08.3-1 > > As of 11.6, Stable continues to include Akregator 4:20.08.3-1, which > includes this bug: > > https://bugs.kde.org/show_bug.cgi?id=429444 > https://invent.kde.org/pim/akregator/-/commit/546db72108cba99a1881e97349ce55 > db5d1da88e > > Testing includes 4:22.08.3-1 and presumably fixes this. Can it be added to > Stable? signature.asc Description: This is a digitally signed message part.
Bug#1027547: onionshare: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.10 --dir cli returned exit code 13
Control: reassign -1 flask-socketio 5.0.1-1
Control: forcemerge -1 1023568
Hey,
the bug is not inside onionshare but in flask-socketio.
regards,
hefee
On Sonntag, 1. Januar 2023 15:16:09 CET Lucas Nussbaum wrote:
> Source: onionshare
> Version: 2.5-2
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20230101 ftbfs-bookworm
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
> Relevant part (hopefully):
> > make[1]: Entering directory '/<>'
> > PYBUILD_NAME=onionshare-cli HOME=/tmp dh_auto_test --buildsystem=pybuild
> > --sourcedirectory cli>
> > pybuild --test --test-pytest -i python{version} -p 3.10 --dir cli
> >
> > I: pybuild base:240: cd
> > /<>/.pybuild/cpython3_3.10_onionshare-cli/build; python3.10
> > -m pytest tests ImportError while loading conftest
> > '/<>/.pybuild/cpython3_3.10_onionshare-cli/build/tests/conft
> > est.py'. tests/conftest.py:8: in
> >
> > from onionshare_cli import common, web
> >
> > onionshare_cli/__init__.py:30: in
> >
> > from .web import Web
> >
> > onionshare_cli/web/__init__.py:21: in
> >
> > from .web import Web
> >
> > onionshare_cli/web/web.py:38: in
> >
> > from flask_socketio import SocketIO
> >
> > /usr/lib/python3/dist-packages/flask_socketio/__init__.py:24: in
> >
> > from werkzeug.serving import run_with_reloader
> >
> > E ImportError: cannot import name 'run_with_reloader' from
> > 'werkzeug.serving' (/usr/lib/python3/dist-packages/werkzeug/serving.py)
> > E: pybuild pybuild:388: test: plugin pyproject failed with: exit code=4:
> > cd /<>/.pybuild/cpython3_3.10_onionshare-cli/build;
> > python3.10 -m pytest tests>
> > rm -fr -- /tmp/dh-xdg-rundir-UYdeNRLC
> >
> > dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p
> > 3.10 --dir cli returned exit code 13
> The full build log is available from:
> http://qa-logs.debian.net/2023/01/01/onionshare_2.5-2_unstable.log
>
> All bugs filed during this archive rebuild are listed at:
> https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230101;users=lucas
> @debian.org or:
> https://udd.debian.org/bugs/?release=na=ign=7=7
> =only=ftbfs-20230101=lu...@debian.org
> ugs=1=1=1=1#results
>
> A list of current common problems and possible solutions is available at
> http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
>
> If you reassign this bug to another package, please mark it as 'affects'-ing
> this package. See https://www.debian.org/Bugs/server-control#affects
>
> If you fail to reproduce this, please provide a build log and diff it with
> mine so that we can identify if something relevant changed in the meantime.
signature.asc
Description: This is a digitally signed message part.
Bug#806717: Forwarding email with a long header causes longer than 998 byte lines
Hey, I think the fix will be published with KMime 22.12.0 (should reach unstable the next days), as there is a MR request that should fix that: https://invent.kde.org/pim/kmime/-/merge_requests/7 Regards, hefee -- On Dienstag, 13. Dezember 2022 20:14:28 CET Mikko Tuumanen wrote: > I received an email with a x-ms-exchange-antispam-messagedata-0: header > and I tried to forward it with kmail. > > That caused error message: > "The server said: maximum allowed line length is 998 octets, got 1702" > > In the original message, the header was split into multiple lines like > this: > > x-ms-exchange-antispam-messagedata-0: > =?iso-8859-1?Q?X9nvzr27qYcmEJpSHcp6K5gWYoBjPRlTmpppdR4VrmwY1cP0Mp4QNB9+kY?= > =?iso-8859-1?Q?ZWd5EsMdHUa4x0pKA1ObLVns8RuLFV3mCsHlMT31xBfLxra6jZ+p5hbSHx?= > > > But when the message was forwarded with kmail, the header > turned into one too long line: > > x-ms-exchange-antispam-messagedata-0: lwf7pdVSQS1T... > > > It seems that kmail has more than one header "fixing" problem. signature.asc Description: This is a digitally signed message part.
Bug#1025670: Bug#1025671: RM: marble [armel ppc64el s390x] -- RoQA; qtwebengine-opensource-src not available
Hey, you wrote those bugreports very fast. When I uploaded the new marble version I overseen, that QtWebEnigne is not built on all archs. But QtWebEngine is a optional build dependency, so it is easy to build marble without QtWebEngine. I uploaded marble 4:22.08.3-2 with QtWebEngine to be optional. Hefee -- On Mittwoch, 7. Dezember 2022 11:06:39 CET Bas Couwenberg wrote: > Package: ftp.debian.org > Severity: normal > User: ftp.debian@packages.debian.org > Usertags: remove > X-Debbugs-Cc: mar...@packages.debian.org > Control: affects -1 + src:marble > Control: block -1 by 1025670 > > Please remove marble from the architectures where qtwebengine5-dev is not > available to unblock testing migration. > > Kind Regards, > > Bas signature.asc Description: This is a digitally signed message part.
Bug#1025318: nextcloud-desktop: libGL error: failed to load driver: i915 (Segmentation fault)
Hey,
this seems like you have an issue with your graphic card driver and not an
issue with Nextcloud desktop. Do you have xserver-xorg-video-intel installed?
hefee
On Freitag, 2. Dezember 2022 14:55:19 CET you wrote:
> Package: nextcloud-desktop
> Version: 3.6.1-1
> Severity: normal
>
> Dear Maintainer,
>
> *** Reporter, please consider answering these questions, where appropriate
> ***
>
> When I open "nextcloud-desktop" on terminal, it cannot open and reture
> the error messages:
>
> libGL error: MESA-LOADER: failed to retrieve device information
> libGL error: MESA-LOADER: failed to open i915: /usr/lib/dri/i915_dri.so:
> cannot open shared object file: No such file or directory (search paths
> /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, su
> ffix _dri)
> libGL error: failed to load driver: i915
> libGL error: MESA-LOADER: failed to retrieve device information
> libGL error: MESA-LOADER: failed to open i915: /usr/lib/dri/i915_dri.so:
> cannot open shared object file: No such file or directory (search paths
> /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, su
> ffix _dri)
> libGL error: failed to load driver: i915
> Segmentation fault
>
> Please help, thank you.
>
> *** End of the template - remove these template lines ***
>
>
> -- System Information:
> Debian Release: bookworm/sid
> APT prefers unstable
> APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 6.0.0-5-amd64 (SMP w/8 CPU threads; PREEMPT)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
> LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages nextcloud-desktop depends on:
> ii libc6 2.36-6
> ii libcloudproviders0 0.3.1-2
> ii libgcc-s1 12.2.0-9
> ii libglib2.0-0 2.74.2-1
> ii libnextcloudsync0 3.6.1-1
> ii libqt5core5a 5.15.6+dfsg-4
> ii libqt5dbus55.15.6+dfsg-4
> ii libqt5gui5 5.15.6+dfsg-4
> ii libqt5keychain10.13.2-5
> ii libqt5network5 5.15.6+dfsg-4
> ii libqt5qml5 5.15.6+dfsg-2
> ii libqt5quick5 5.15.6+dfsg-2
> ii libqt5quickcontrols2-5 5.15.6+dfsg-2
> ii libqt5sql5-sqlite 5.15.6+dfsg-4
> ii libqt5svg5 5.15.6-2
> ii libqt5webenginecore5 5.15.10+dfsg-7+b1
> ii libqt5webenginewidgets55.15.10+dfsg-7+b1
> ii libqt5widgets5 5.15.6+dfsg-4
> ii libstdc++6 12.2.0-9
> ii nextcloud-desktop-common 3.6.1-1
> ii nextcloud-desktop-l10n 3.6.1-1
> ii qml-module-qt-labs-platform5.15.6+dfsg-2
> ii qml-module-qtgraphicaleffects 5.15.6-2
> ii qml-module-qtqml-models2 5.15.6+dfsg-2
> ii qml-module-qtquick-controls2 5.15.6+dfsg-2
> ii qml-module-qtquick-dialogs 5.15.6-2
> ii qml-module-qtquick-layouts 5.15.6+dfsg-2
> ii qml-module-qtquick-window2 5.15.6+dfsg-2
> ii qml-module-qtquick25.15.6+dfsg-2
>
> Versions of packages nextcloud-desktop recommends:
> pn nextcloud-desktop-doc
>
> nextcloud-desktop suggests no packages.
>
> -- no debconf information
signature.asc
Description: This is a digitally signed message part.
Bug#1025162: akonadi-server won't start if the home directory is not immediately under /home
Hey,
thanks for your bugreport. The problem is not akonadiserver, it is AppArmor,
that is securing your system. Akonadi has a AppArmor profile, so you need to
adjust that profile for your setup ( or disable AppArmor - NOT RECOMMENDED).
To make it permanently you have to modify and your home path to the HOMEDIRS
setting in. After modifying you need to reload AppArmor profiles:
/etc/apparmor.d/tunables/home.d/site.local
See current state of AppArmor (you may also need to install apparmor-utils):
$ aa-status
(see usr.bin.akonadiserver is in enforce mode)
Disable AppArmor (only for testing ;)
$ aa-disable usr.bin.akonadiserver
enable it again:
$ aa-enforce usr.bin.akonadiserver
Maybe we need to forward this bugreport to AppArmor to be able to read the
users' home via /etc/passwd...
Regards,
hefee
--
On Mittwoch, 30. November 2022 15:09:10 CET Josep Guerrero wrote:
> Package: akonadi-server
> Version: 4:20.08.3-3
> Severity: important
>
> Dear Maintainer,
>
>* What led up to the situation?
>
> I updated from debian buster to debian bullseye. When logging in, akonadi
> always produced and error ("exit code 253 (unknown error)") and couldn't
> start kmail at all as a consequence.
>
>* What exactly did you do (or not do) that was effective (or
> ineffective)?
>
> I discovered that newly created for users under /home akonadiserver would
> work. For newly created users under /home/directory wouldn't. I moved my
> home from /home/nodens/user to /home/user and linked /home/nodens to /home.
>
>* What was the outcome of this action?
>
> Akonadiserver started working againi for my user, but only when home was
> directly under /home. When it didn't work, dmesg showed some apparmor
> errors.
>
>* What outcome did you expect instead?
>
> I expected it to work wherever the home was.
>
>
> -- System Information:
> Debian Release: 11.5
> APT prefers stable-updates
> APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
> 'stable') Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 5.10.0-19-amd64 (SMP w/4 CPU threads)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
> LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages akonadi-server depends on:
> ii akonadi-backend-mysql4:20.08.3-3
> ii libaccounts-qt5-11.16-2
> ii libc62.31-13+deb11u5
> ii libgcc-s110.2.1-6 ii
> libkf5akonadiprivate5abi2 [libkf5akonadiprivate5-20.08] 4:20.08.3-3 ii
> libkf5akonadiwidgets5abi1 [libkf5akonadiwidgets5-20.08] 4:20.08.3-3 ii
> libkf5configcore55.78.0-4 ii
> libkf5coreaddons55.78.0-4 ii
> libkf5crash5 5.78.0-3 ii
> libkf5i18n5 5.78.0-2 ii
> libqt5core5a 5.15.2+dfsg-9 ii
> libqt5dbus5 5.15.2+dfsg-9 ii
> libqt5gui5 5.15.2+dfsg-9 ii
> libqt5network5 5.15.2+dfsg-9 ii
> libqt5sql5 5.15.2+dfsg-9 ii
> libqt5widgets5 5.15.2+dfsg-9 ii
> libqt5xml5 5.15.2+dfsg-9 ii
> libstdc++6 10.2.1-6
>
> akonadi-server recommends no packages.
>
> Versions of packages akonadi-server suggests:
> ii akonadi-backend-mysql 4:20.08.3-3
> pn akonadi-backend-postgresql
> pn akonadi-backend-sqlite
>
> -- no debconf information
signature.asc
Description: This is a digitally signed message part.
Bug#1024888: qt6-declarative-private-dev: Missing depdendency on qt6-base-private-dev
Package: qt6-declarative-private-dev Version: 6.3.1+dfsg-5 Severity: normal X-Debbugs-Cc: he...@debian.org When I try to build qcoro 0.7.0 I get the following CMake error. QCoro depends on Qt6::QmlPrivate and Qt6::QuickPrivate, both are shipped via qt6-declatiave-private-dev. But qt6-declativate-private-dev depends on qt6-base-private-dev (It searches /usr/include/x86_64-linux-gnu/qt6/QtCore/6.3.1). hefee CMake Error in qcoro/qml/CMakeLists.txt: Imported target "Qt::QmlPrivate" includes non-existent path "/usr/include/x86_64-linux-gnu/qt6/QtCore/6.3.1" in its INTERFACE_INCLUDE_DIRECTORIES. Possible reasons include: * The path was deleted, renamed, or moved to another location. * An install or uninstall procedure did not complete successfully. * The installation package was faulty and references files it does not provide. CMake Error in tests/CMakeLists.txt: Imported target "Qt6::QuickPrivate" includes non-existent path "/usr/include/x86_64-linux-gnu/qt6/QtCore/6.3.1" in its INTERFACE_INCLUDE_DIRECTORIES. Possible reasons include: * The path was deleted, renamed, or moved to another location. * An install or uninstall procedure did not complete successfully. * The installation package was faulty and references files it does not provide. CMake Error in qcoro/qml/CMakeLists.txt: Imported target "Qt::QmlPrivate" includes non-existent path "/usr/include/x86_64-linux-gnu/qt6/QtCore/6.3.1" in its INTERFACE_INCLUDE_DIRECTORIES. Possible reasons include: * The path was deleted, renamed, or moved to another location. * An install or uninstall procedure did not complete successfully. * The installation package was faulty and references files it does not provide. CMake Error in tests/CMakeLists.txt: Imported target "Qt6::QuickPrivate" includes non-existent path "/usr/include/x86_64-linux-gnu/qt6/QtCore/6.3.1" in its INTERFACE_INCLUDE_DIRECTORIES. Possible reasons include: * The path was deleted, renamed, or moved to another location. * An install or uninstall procedure did not complete successfully. * The installation package was faulty and references files it does not provide.
Bug#1024886: qt6-declarative-dev: Missing depdendency on libqt6opengl6-dev
Package: qt6-declarative-dev Version: 6.3.1+dfsg-5 Severity: normal X-Debbugs-Cc: he...@debian.org When I try to build the new qcoro version 0.7.0 I need Qt6Quick and install qt6-declativate-dev I get the following error in CMake. Please add libqt6opengl6-dev to the depdendency of qt6-declarative-dev. hefee -- Could NOT find Qt6OpenGL (missing: Qt6OpenGL_DIR) CMake Warning at /usr/lib/x86_64-linux-gnu/cmake/Qt6/Qt6Config.cmake:223 (find_package): Found package configuration file: /usr/lib/x86_64-linux-gnu/cmake/Qt6Quick/Qt6QuickConfig.cmake but it set Qt6Quick_FOUND to FALSE so package "Qt6Quick" is considered to be NOT FOUND. Reason given by package: Qt6Quick could not be found because dependency Qt6OpenGL could not be found. Call Stack (most recent call first): CMakeLists.txt:83 (find_package) CMake Error at CMakeLists.txt:83 (find_package): Found package configuration file: /usr/lib/x86_64-linux-gnu/cmake/Qt6/Qt6Config.cmake but it set Qt6_FOUND to FALSE so package "Qt6" is considered to be NOT FOUND. Reason given by package: Failed to find Qt component "Quick". Expected Config file at "/usr/lib/x86_64-linux-gnu/cmake/Qt6Quick/Qt6QuickConfig.cmake" exists
Bug#1024178: RM: pypy-stem/1.8.0-3.1
Hey, > Migration of python-step is currently blocked as removal of pypy-stem > would render vanguards uninstallable. So what's the plan regarding > vanguards? The pypy-stem was already a broken package and not functional it broke the autopkgtests see #1022111. Vanguards should be ported to python3 anyways and than we can create a pypy3-stem package. Just a remark - me is not the python- stem maintainer and the removal was done via a MNU by Bastian Germann (b...@debian.org)... regards, hefee -- On Dienstag, 15. November 2022 22:25:21 CET Sebastian Ramacher wrote: > Control: tags -1 moreinfo > > Hi Hefee > > On 2022-11-15 21:53:23 +0100, Hefee wrote: > > Package: release.debian.org > > Severity: normal > > User: release.debian@packages.debian.org > > Usertags: rm > > X-Debbugs-Cc: he...@debian.org, > > pkg-privacy-maintain...@alioth-lists.debian.net > > > > The pypy-stem package is broken, as pypy is a Python 2 interpreter and > > stem code is written for Pythno 3 only. Additionally Pypy is marked for > > removal #1011926. The new python-stem version 1.8.1-1.1 is not building > > pypy-stem anymore. So the removal of pypy-stem in testing would enable > > the > > migration of python-stem and would untangle it from pypy removal. > > > > And would finally help the new onionshare version to migrate to > > testing, as it depends on the new version of python3-stem. > > Migration of python-step is currently blocked as removal of pypy-stem > would render vanguards uninstallable. So what's the plan regarding > vanguards? > > Cheers signature.asc Description: This is a digitally signed message part.
Bug#1024184: transition: alkimia
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition X-Debbugs-Cc: he...@debian.org, pkg-kde-t...@lists.alioth.debian.org A easy transition as it has only one package depdens on alkimia: kmymoney (successfully builds with old and new version of alkimia). The new version of alkimia depends on serveral new libriaries, it is hard to say if the new version will compile on all archs as before. It seems like the last Qt transition is still challangeing some buildds. So we may loose some archs with this transtion. hefee Ben file: title = "alkimia"; is_affected = .depends ~ "libalkimia5-7" | .depends ~ "libalkimia5-8"; is_good = .depends ~ "libalkimia5-8"; is_bad = .depends ~ "libalkimia5-7";
Bug#1024178: RM: pypy-stem/1.8.0-3.1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm X-Debbugs-Cc: he...@debian.org, pkg-privacy-maintain...@alioth-lists.debian.net The pypy-stem package is broken, as pypy is a Python 2 interpreter and stem code is written for Pythno 3 only. Additionally Pypy is marked for removal #1011926. The new python-stem version 1.8.1-1.1 is not building pypy-stem anymore. So the removal of pypy-stem in testing would enable the migration of python-stem and would untangle it from pypy removal. And would finally help the new onionshare version to migrate to testing, as it depends on the new version of python3-stem. hefee
Bug#1023568: [Pkg-privacy-maintainers] Bug#1023568: flask-socketio is outdated, leading to broken autopkgtest in onionshare
Hey, > Looking a second time with a deeper view on it, there is something more > under the hood to tune and adjust. The cli.show_server_banner function from flask changed, that triggers the issue. But the "onionshare --help" tests fails because it cannot install onionshare correctly. From my point of view it is more an issue for your testbed and I cannot see the issue on onionshare side ( yet). Regards, hefee signature.asc Description: This is a digitally signed message part.
Bug#1023568: [Pkg-privacy-maintainers] Bug#1023568: flask-socketio is outdated, leading to broken autopkgtest in onionshare
Hey, can you give me a link to the complete output of the atopkgtests to check what is broken. Actually his test is the only one that tests the GUI application onionshare ( I don't know any good way to check GUI applications). In it self it only test does not check any feature of onionshare (that's why it is marked as superficial) - But segfaulting when you just want to view the help means properly that there is an issue with the application by itself. Regards, hefee signature.asc Description: This is a digitally signed message part.
Bug#1023568: [Pkg-privacy-maintainers] Bug#1023568: onionshare: autopkgtest regression with flask 2.2.2
Control: reassign -1 python3-flask-socketio 5.0.1-1 Control: affects -1 onionshare-cli Hey, >From my point of view it is an issue within flask-socketio and has nothing to >do with onionshare. The import flask_socketio from onionshare works. But than flask-socketio fails to import werkzeug, so the problem is either flask-socketio or werkzeug. As werkzeug and flask are updated in experimental, I expect flask.socketio to be the problem. It seems like flask-socketio 5.3.0 fixes this see Changes line 11: https://github.com/miguelgrinberg/Flask-SocketIO/blob/main/CHANGES.md Relevant autopkgtest test: autopkgtest [22:25:35]: test onionshare-cli_help: onionshare-cli --help Traceback (most recent call last): File "/usr/bin/onionshare-cli", line 5, in from onionshare_cli import main File "/usr/lib/python3/dist-packages/onionshare_cli/__init__.py", line 30, in from .web import Web File "/usr/lib/python3/dist-packages/onionshare_cli/web/__init__.py", line 21, in from .web import Web File "/usr/lib/python3/dist-packages/onionshare_cli/web/web.py", line 38, in from flask_socketio import SocketIO File "/usr/lib/python3/dist-packages/flask_socketio/__init__.py", line 24, in from werkzeug.serving import run_with_reloader ImportError: cannot import name 'run_with_reloader' from 'werkzeug.serving' (/usr/lib/python3/dist-packages/werkzeug/serving.py) The full log (amd64) is reachable under https://ci.debian.net/data/autopkgtest/unstable/amd64/o/onionshare/27759203/log.gz The full list of packages that fail with flask from experimental can be found here. https://qa.debian.org/excuses.php?experimental=1=flask hefee signature.asc Description: This is a digitally signed message part.
Bug#1022774: ITP: itinerary -- Digital travel assistant protecting your privacy
Package: wnpp Severity: wishlist Owner: Hefee X-Debbugs-Cc: debian-de...@lists.debian.org, he...@debian.org * Package name: itinerary Version : 22.08.2 Upstream Author : Volker Krause * URL : https://invent.kde.org/pim/itinerary * License : LGPL-2.0+ Programming Lang: C++ with Qt and QML Description : Digital travel assistant protecting your privacy Getting your itinerary presented in a unified, well structured and always up to date fashion rather than advertisement overloaded HTML email monstrosities or countless vendor-specific apps. It will be maintained under the Debian Qt/KDE Maintainers Team’s umbrella.
Bug#1022358: ITP: kopeninghours -- A library for parsing and evaluating OSM opening hours expressions.
Package: wnpp Severity: wishlist Owner: Hefee X-Debbugs-Cc: debian-de...@lists.debian.org, he...@debian.org * Package name: kopeninghours Version : 22.08.2 Upstream Author : Volker Krause * URL : https://invent.kde.org/libraries/kopeninghours * License : LGPL-2.0-or-later Programming Lang: C++ (Qt) Description : library for parsing and evaluating OSM opening hours expressions. It is a library, QML module and python3 binding to evulate OSM opening hours expressions. OSM opening hours expressions are used to describe when a feature is open/available or closed. This format is not only used in OpenStreetMap itself, but in various other data sources or APIs needing such a description as well. It will be maintained under the Debian Qt/KDE Maintainers Team’s umbrella.
Bug#1022272: ITP: kosmindoormap -- Open Street Map indoor map renderer of for example a (large) train station.
Package: wnpp Severity: wishlist Owner: Hefee X-Debbugs-Cc: debian-de...@lists.debian.org, he...@debian.org * Package name: kosmindoormap Version : 22.08.2 Upstream Author : Volker Krause * URL : https://invent.kde.org/libraries/kosmindoormap * License : LGPL-2.0-or-later Programming Lang: C++ (Qt) Description : Open Street Map indoor map renderer of for example a (large) train station. It is a library and QML module to show OSM indoor maps. It has floor-level separation of OSM data and inter-floor navigation using stairs, escalators or elevators. Information for details like a selected amenity. Identifying railway platforms or airport gates in the map data. It is integrated with KPublicTransport to show line icons for railway platforms, show availability of rental bikes and get realtime equipment (elevators/escalators/etc) status information. It will be maintained uder the Debian Qt/KDE Maintainers Team’s umbrella.
Bug#1022111: python-stem: pypy-stem ships a Python2 version
Source: python-stem Version: 1.8.1-1 Severity: important X-Debbugs-Cc: he...@debian.org Hey, the pypy-stem package runs the code as Python2. This breaks, as the code is Python3 only. So it needs to use pypy3. Btw. that is the reason why the autopkgtests are failing. The pypy-stem packaga installs tor-prompt and this is executed with pypy and in Python2 there is no collections.abc. Additionally, the pypy-stem package should handle tor-prompt via update-alternative (like python3-stem). To make it possible for the user to choose the default variant. Regards, hefee -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.0.0-1-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#959972: Obsolete binaries?
Hey, > On Bullseye (11.5), needrestart seems to think that nextcloud-desktop is > using (or trying to use) an obsolete binary. One solution would be to > provide a backport. > > With nextcloud-desktop running, needrestart reports that my user is > running an outdated binary. Shut it down, and needrestart no longer > reports the obsolete binary. this sounds like an bug of needrestart and not about the old version. As needrestart checks only if there is a binary that is using an outdated library. This is not about any newer version available for a binary. regards, hefee signature.asc Description: This is a digitally signed message part.
Bug#959972: nextcloud-desktop: Please provide a backport for buster
Hey, > It would be nice to let users of buster enjoy the improvements since 2.6 I won't do the backport. Others need to do the work. Normally backporting is not much work and a good starting point to learn packaging. If anyone needs help feel free to ask me! I will sponser and support it. regards, hefee signature.asc Description: This is a digitally signed message part.
Bug#1018198: modemmanager: FTBFS test failing with common_test_ccwa_response: assertion failed: (result)
Package: modemmanager Version: 1.18.10-1 Severity: serious Tags: upstream patch bookworm sid ftbfs Justification: FTBFS Forwarded: https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/870 X-Debbugs-Cc: he...@debian.org Hey, when I try a recompiliation of ModemManager, the tests are failing with: /test_ccwa_response: ** ERROR:test-modem-helpers.c:4204:common_test_ccwa_response: assertion failed: (result) FAIL GTester: last random seed: R02S1c9c8a2a8c689230b60594a14f54dc63 make[5]: *** [Makefile:889: test-nonrecursive] Terminated make[5]: Leaving directory '/<>/src/tests' make[4]: *** [Makefile:736: check-am] Error 2 make[4]: Leaving directory '/<>/src/tests' make[3]: *** [Makefile:1991: check-recursive] Error 1 make[3]: Leaving directory '/<>/src' make[2]: *** [Makefile:2142: check] Error 2 make[2]: Leaving directory '/<>/src' make[1]: *** [Makefile:540: check-recursive] Error 1 make[1]: Leaving directory '/<>' dh_auto_test: error: make -j4 check "TESTSUITEFLAGS=-j4 --verbose" VERBOSE=1 returned exit code 2 make: *** [debian/rules:12: binary] Error 25 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 This bug is also reported upstream https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/issues/601 It seems like the issue is that with new glibc >= 2.73.2 PCRE1 is replaced with PCRE2. There is also a first patch for it, but this does not fix this issue completly. I initally wanted to fix my breakage of my UMTS stick failing https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/issues/621 I will not open a second bug report as the bugfix is don with same MR. regards, hefee -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') merged-usr: no Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.0-4-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages modemmanager depends on: ii libc6 2.34-6 ii libglib2.0-0 2.73.3-2 ii libgudev-1.0-0 237-2 ii libmbim-glib4 1.26.4-1 ii libmbim-proxy 1.26.4-1 ii libmm-glib01.18.10-1 ii libpolkit-gobject-1-0 0.105-33 ii libqmi-glib5 1.30.8-1 ii libqmi-proxy 1.30.8-1 ii libqrtr-glib0 1.2.2-1 ii libsystemd0251.4-1 ii policykit-10.105-33 Versions of packages modemmanager recommends: ii usb-modeswitch 2.6.1-3+b1 modemmanager suggests no packages. -- no debconf information
Bug#1010576: akonadi cannot kill mysql due to apparmor rules
Hi, the fix is already in master, it is actually just a typo in the profile name: https://invent.kde.org/pim/akonadi/-/commit/ a6fb4c7de13eed9d90237388113425413bf4d733 that may be worth to backport. > If I set akonadi's profile to complain instead of enforce, akonadi can > kill mysql ok: > > sudo aa-complain /etc/apparmor.d/usr.bin.akonadiserver > sudo systemctl reload apparmor.service you don't need to restart apparmor after set akonadiserver to complain mode. > Somehow mysql should be running in the mysqld_akonadi profile but it is > running in fact unconstrained and therefore akonadiserver is not allowed > to send a signal to it. Don't know how to fix that, though. I see the same apparmor issue, but Akonadi is still not able to kill mariadb process. > I suspect the fact that mysql hangs after suspend/resume is a different > bug in mysql. yepp - But I have no idea how to debug this. regards, hefee signature.asc Description: This is a digitally signed message part.
Bug#1008829: pysrs-bin: envfrom2srs and srs2envtol fails with ModuleNotFoundError: No module named 'ConfigParser'
Control: forwarded -1 https://github.com/sdgathman/pysrs/issues/12 Hey, > Why do you insist on keeping broken packages in Debian? because pysrs is more than these two scripts - the core part is the python library supporting handle SRS. > Sorry. What's the less offensice way to describe broken and untested? Just telling it is broken is fine. But saying it is crap and ask directly for removal is offensive. > > It is only the two example scripts, that are not properly ported to Python > > 3. > You are installing known broken examples in $PATH? But why! > > Well, whatever. Thanks for not caring about quality I try not to ship broken packages on purpose, but I'm just a human make mistakes and don't have the time to test everything. I start asking upstream to create a new version in order to get a fixed package in Debian soon. regards hefee signature.asc Description: This is a digitally signed message part.
Bug#1008829: pysrs-bin: envfrom2srs and srs2envtol fails with ModuleNotFoundError: No module named 'ConfigParser'
Control: severity -1 normal Hey, > # envfrom2srs > Traceback (most recent call last): > File "/usr/bin/envfrom2srs", line 14, in > from ConfigParser import ConfigParser, DuplicateSectionError > ModuleNotFoundError: No module named 'ConfigParser' > > # srs2envtol > Traceback (most recent call last): > File "/usr/bin/srs2envtol", line 14, in > from ConfigParser import ConfigParser, DuplicateSectionError > ModuleNotFoundError: No module named 'ConfigParser' > > No need to clutter the archive with broken and untested packages. > Please remove can you please use a less offensive language. It is only the two example scripts, that are not properly ported to Python 3. With a big warning in the top of the file: # Use only if absolutely necessary. It is *very* inefficient and # a security risk. This was fixed upstream, but they not have released a new version. Regards, hefee signature.asc Description: This is a digitally signed message part.
Bug#1007743: kldap: BD-Uninstallable on s390x
Control: reassign -1 qtkeychain/0.13.2-4 Control: affects -1 kldap Control: tags -1 +patch That is more an issue of qtkeychain than of kldap ;) Qtkeychain does not build on s390x because of misssing Qt6 for s390x: https://tracker.debian.org/pkg/qtkeychain Ubuntu has already the needed patches to disable Qt6 for s390x: https://patches.ubuntu.com/q/qtkeychain/qtkeychain_0.13.2-4ubuntu1.patch So it should be easy to adopt it for Debian. hefee On Dienstag, 15. März 2022 23:20:32 CET Sebastian Ramacher wrote: > Source: kldap > Version: 21.08.1-1 > Severity: serious > Tags: ftbfs > Justification: fails to build from source (but built successfully in the > past) > > > kldap build-depends on missing: > - qt5keychain-dev:s390x > > Please get this fixed or request the removal of the s390x binaries of > kldap. > > Cheers signature.asc Description: This is a digitally signed message part.
Bug#1006230: qt6-base-dev: Undefined target Qt::CorePrivate.
In meanwhile we found a workaround: https://salsa.debian.org/owncloud-team/qtkeychain/-/merge_requests/3 aka: Add qtbase5-private-dev, qt6-tools-dev, qt6-tools-dev-tool, libgcrypt20- dev and qt6-l10n-tools to BDs. and no need to add qt6-base-private-dev. Fedora 34 has the same issue, when building qtkeychain: https://github.com/frankosterfeld/qtkeychain/issues/202 Regards, hefee signature.asc Description: This is a digitally signed message part.
Bug#1006230: qt6-base-dev: Undefined target Qt::CorePrivate.
Package: qt6-base-dev Version: 6.2.2+dfsg-5 Severity: important X-Debbugs-Cc: he...@debian.org If I just use in CMake "find_package(Qt6 COMPONENTS Core REQUIRED)" I end up with the bug: "Targets not yet defined: Qt::CorePrivate" Also if I add qt6-base-private-dev explicitly to the Build-Depends list, I still get the same error. That's why it seems like a bug inside qt6-base. See the build of qtkeychain: https://salsa.debian.org/owncloud-team/qtkeychain/-/jobs/2496539#L1939 https://salsa.debian.org/owncloud-team/qtkeychain/-/pipelines/351397 and the correspondig CMakeLists.txt: https://salsa.debian.org/owncloud-team/qtkeychain/-/blob/master/CMakeLists.txt and relevant Debian files: https://salsa.debian.org/owncloud-team/qtkeychain/-/blob/work/hefee/qt6/debian/control https://salsa.debian.org/owncloud-team/qtkeychain/-/blob/work/hefee/qt6/debian/control Regards, hefee -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.16.0-1-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages qt6-base-dev depends on: ii libqt6concurrent6 6.2.2+dfsg-5 ii libqt6core6 6.2.2+dfsg-5 ii libqt6dbus6 6.2.2+dfsg-5 ii libqt6gui66.2.2+dfsg-5 ii libqt6network66.2.2+dfsg-5 ii libqt6openglwidgets6 6.2.2+dfsg-5 ii libqt6printsupport6 6.2.2+dfsg-5 ii libqt6sql66.2.2+dfsg-5 ii libqt6test6 6.2.2+dfsg-5 ii libqt6widgets66.2.2+dfsg-5 ii libqt6xml66.2.2+dfsg-5 ii qmake66.2.2+dfsg-5 ii qt6-base-dev-tools6.2.2+dfsg-5 ii qt6-qpa-plugins 6.2.2+dfsg-5 Versions of packages qt6-base-dev recommends: ii libqt6opengl6-dev 6.2.2+dfsg-5 qt6-base-dev suggests no packages. -- no debconf information
Bug#1006210: ITP: qcoro -- C++20 coroutines for Qt
Package: wnpp Severity: wishlist Owner: Hefee X-Debbugs-Cc: debian-de...@lists.debian.org, he...@debian.org * Package name: qcoro Version : 0.4.0 Upstream Author : Daniel Vrátil * URL : https://qcoro.github.io * License : MIT Programming Lang: C++ Description : C++20 coroutines for Qt QCoro is a C++ library that provide set of tools to make use of C++20 coroutines in connection with certain asynchronous Qt actions. It is already Qt6 ready and Neochat(#989529) depends on it. I will package it under the Qt/KDE Maintainer team umbrella: https://salsa.debian.org/qt-kde-team/extras/qcoro Regards, hefee
Bug#996924: nextcloud-desktop: deletes dirs on the server although they're still here locally
Control: tags -1 +upstream Hey, It would be helpful, if you can try a newer version from Debian unstable, if you see the same behaviour or if is been fixed meanwhile. Anyways this is an upstream bug. So you should get in contact with nextcloud directly: https://github.com/nextcloud/desktop/issues If you find a corresponding bug or create a new one please leave a message here, so we can update the metadata for this bug. Regards, hefee -- > From time to time, whole directories get erased from the server for no > reason. I've seen it happen a few times already, but not early enough > to be able to catch logs. So far I've been lucky enough to be able to > restore from backups, but it's not something that I can afford to see > happen again. > > In my case, the client sent a DELETE request for a directory that > hadn't been deleted locally. The > ~/.local/share/Nextcloud/Documents_sync.log file shows it: > > 12:27:42||TEMP|INST_REMOVE|Up|1633813324|61620350e2e1d|0|06377550ocptyqgkbgt > 0|4||204|0|0 > > At the same time, the server log shows the corresponding request: > > [REDACTED] [17/Oct/2021:14:27:42 +0200] "DELETE > /remote.php/dav/files/DetR/Documents/TEMP HTTP/1.1" 204 609 "-" > "Mozilla/5.0 (Linux) mirall/3.1.1-2+deb11u1 (Nextcloud)" > > So obviously, on all other clients using that shared Documents > directory, the TEMP directory is deleted. It's still present locally, > but there's a discrepancy with the server, and that discrepancy is not > always resolved in the right direction: sometimes in the past the > directory was restored from the local version and eventually > re-uploaded then re-synced to other clients, but other times the local > version was deleted too, in which case the directory is completely > lost. > > This is really major, and the fact that it happens "rarely" (although > a couple of times a year for me) doesn't make it less grave. > > For reference the server runs 21.0.0, but I've seen this bug happen > with previous versions too, and I don't think the bug is server-side. > > I'm fully willing to help provide more info if instructed how, but > note that the bug is unpredictable to me. > > It may be relevant that my Documents share is about 500 GB in size, > with about 300k files. > > Please advise. signature.asc Description: This is a digitally signed message part.
Bug#995875: SSL error when trying to retrieve bug reports
Control: reassign -1 ca-certificates/20210119 Control: forcemerge 995432 -1 Control: affects -1 apt-listbugs Hey, I have the same problem with a sid system. The root issue is, that the root ceritficate of Let's encrypt has expired: https://letsencrypt.org/docs/dst-root-ca-x3-expiration-september-2021/ The workaround is to disable that certificate and run update-ca-certificates: sed -ie 's#^!\?mozilla/DST_Root_CA_X3\.crt#!mozilla/DST_Root_CA_X3.crt#g' /etc/ca-certificates.conf update-ca-certificates Regards, hefee signature.asc Description: This is a digitally signed message part.
