Bug#969613: xdg-desktop-portal-kde: please transition to pipewire 0.3, initially in experimental
Control: tags -1 + patch On Sun, 06 Sep 2020 at 00:08:08 +0100, Simon McVittie wrote: > pipewire 0.3 has now hit experimental. As discussed in #966535 and > on #debian-kde, the first step for transition #966535 is to make sure > the few packages that currently B-D on pipewire 0.2 can be recompiled > with 0.3. It would be great if you could do this in experimental soon > (please close this bug with that upload), and either be ready to re-upload > to unstable when the transition starts, or accept a 0-day NMU with the > same change. > > My next upload of xdg-desktop-portal to experimental will enable the > pipewire 0.3 dependency. You might not be able to test this functionality > in x-d-p-kde until I've done that (I'm not completely clear on how the > screencasting/remote desktop portal works). xdg-desktop-portal is now on its way to experimental. > Because x-d-p-kde has different versions in unstable and experimental, > it would also be great if someone from the KDE team could test a rebuild > of the x-d-p-kde from unstable that has been rebuilt against pipewire > 0.3 and report back whether it works. Unfortunately you won't be able to > upload that to Debian immediately, because we only have one instance of > experimental, and for this particular source package it's already in use. If the version in experimental is ready for release to bullseye, it would probably be best to use that one for this transition. Making it build against PipeWire 0.3 is straightforward: https://salsa.debian.org/qt-kde-team/kde/xdg-desktop-portal-kde/-/merge_requests/6 Or if you would prefer to keep the version in unstable and apply minimal fixes, it needs at least the FindPipeWire.cmake patches from https://salsa.debian.org/qt-kde-team/kde/xdg-desktop-portal-kde/-/merge_requests/5 and maybe the fixes to the C++ code too (taken from upstream release v5.18.1). In both cases, as with krfb, I have built the package successfully in sbuild but not otherwise tested it. I don't know how the components of KDE fit together, so I don't know whether the PipeWire integration is practically useful without having a version of kwin that also has PipeWire integration. If PipeWire integration is not testable in Debian yet, then it will be necessary to either upload it untested, or disable it until enough of the stack is in place that it can be tested. Either is fine from the point of view of this transition. Thanks, smcv
Processed: Re: Bug#969613: xdg-desktop-portal-kde: please transition to pipewire 0.3, initially in experimental
Processing control commands: > tags -1 + patch Bug #969613 [xdg-desktop-portal-kde] xdg-desktop-portal-kde: please transition to pipewire 0.3, initially in experimental Added tag(s) patch. -- 969613: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969613 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#969612: krfb: please transition to pipewire 0.3, initially in experimental
Processing control commands: > tags -1 + patch Bug #969612 [krfb] krfb: please transition to pipewire 0.3, initially in experimental Added tag(s) patch. -- 969612: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969612 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#969612: krfb: please transition to pipewire 0.3, initially in experimental
Control: tags -1 + patch On Sun, 06 Sep 2020 at 00:02:46 +0100, Simon McVittie wrote: > pipewire 0.3 has now hit experimental. As discussed in #966535 and > on #debian-kde, the first step for transition #966535 is to make sure > the few packages that currently B-D on pipewire 0.2 can be recompiled > with 0.3. It would be great if you could do this in experimental soon > (please close this bug with that upload), and either be ready to re-upload > to unstable when the transition starts, or accept a 0-day NMU with the > same change. This builds successfully: https://salsa.debian.org/qt-kde-team/kde/krfb/-/merge_requests/2 I haven't tested it beyond sbuild succeeding: I don't use KDE myself, so I don't know how the pieces fit together. If it's anything like GNOME, then it might not be possible to actually *use* the functionality provided by this PipeWire dependency until a sufficiently new version of kwin has been built with PipeWire support enabled, in which case the only testing that is required would be to check that it doesn't cause regressions for things that already work - but perhaps the "shape" of the KDE stack is sufficiently different that it doesn't need PipeWire in the compositor like GNOME does. smcv
kdevelop_5.6.0-1_amd64.changes is NEW
binary:kdevelop56-libs is NEW. binary:kdevelop56-libs is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so please be patient. Packages are routinely processed through to the archive, and do feel free to browse the NEW queue[1]. If there is an issue with the upload, you will receive an email from a member of the ftpteam. If you have any questions, you may reply to this email. [1]: https://ftp-master.debian.org/new.html or https://ftp-master.debian.org/backports-new.html for *-backports
Processing of kdevelop_5.6.0-1_amd64.changes
kdevelop_5.6.0-1_amd64.changes uploaded successfully to localhost along with the files: kdevelop_5.6.0-1.dsc kdevelop_5.6.0.orig.tar.xz kdevelop_5.6.0.orig.tar.xz.asc kdevelop_5.6.0-1.debian.tar.xz kdevelop-data_5.6.0-1_all.deb kdevelop-dbgsym_5.6.0-1_amd64.deb kdevelop-dev_5.6.0-1_amd64.deb kdevelop-l10n_5.6.0-1_all.deb kdevelop56-libs-dbgsym_5.6.0-1_amd64.deb kdevelop56-libs_5.6.0-1_amd64.deb kdevelop_5.6.0-1_amd64.buildinfo kdevelop_5.6.0-1_amd64.deb kdevplatform-dev_5.6.0-1_all.deb kdevplatform-l10n_5.6.0-1_all.deb plasma-kdevelop-dbgsym_5.6.0-1_amd64.deb plasma-kdevelop_5.6.0-1_amd64.deb Greetings, Your Debian queue daemon (running on host usper.debian.org)
Bug#969898: kmail: error in kmail help related to local folders
Package: kmail Version: 4:20.04.1-2 Severity: minor Dear Maintainer, in the kmail help I found an error. Please recheck and correct this is in the help text. The error I found, is in the part, where you describe, what to do, when loacal folders are double and can not be deleted. I only have the German text available, so please allow me to insert the part, which I think I am wrong. I am sure, someone in the community may translate this to find it in the Englishpart. This is the original: snip Der schwierigste Teil ist die Einstellung für den Ordner Postausgang. Suchen Sie zuerst die Datei specialmailcollectionsrc in Ihrem KDE-Einrichtungsordner $HOME/.kde4/share/config. Die Datei enthält unter anderem folgende Einträge: [SpecialCollections] DefaultResourceId=akonadi_maildir_resource_0 Starten Sie jetzt das Programm akonadiconsole. Suchen Sie auf der Karteikarte Agents das lokale Konto mit Ihrem Ordner Postausgang, klicken Sie darauf und notieren Sie den Namen des Identifier unten im Dialog wie zum Beispiel akonadi_maildir_resource_XXX. Tragen Sie diesen Wert in der vorher erwähnten Datei specialmailcollectionsrc als Ersatz des vorhandenen Wertes ein. Danach starten Sie das Programm akonadi wieder neu, indem Sie in akonadiconsole Server → Restart Server wählen oder folgendes in einer Konsole auf der Befehlszeile eingeben: snap - Ok, the error is this: First of all, the named path is wrong. It is not $HOME/.kde4/share/config, this is not existent. If all, it would be $HOME/.kde/share/config. The *kde4* existed a long time ago, but today no more. But secondary, this path is also itself wrong. Althought the named file exists below the path exists, it is not the correct one. You find also the file specialmailcollectionsrc below $HOME/.config, and this is the one which is the responsible. However, I believe, it is important, to edit BOTH files, the one below $HOME/.kde/share/config and the one below $HOME/.config. At least, this procedure worked here. It would be nice, if you could recheck this and maybe correct the text in the help files. Thank you very much! Hans -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.7.0-3-amd64 (SMP w/2 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages kmail depends on: ii akonadi-server 4:20.04.1-2+b1 ii kdepim-runtime 4:20.04.1-2 ii kio 5.70.1-1 ii libc62.31-3 ii libgcc-s110.2.0-6 ii libgpgmepp6 1.14.0-1 ii libkf5akonadiagentbase5 [libkf5akonadiagentbase5-20.04] 4:20.04.1-2+b1 ii libkf5akonadicontact5 [libkf5akonadicontact5-20.04] 4:20.04.1-2 ii libkf5akonadicore5abi2 [libkf5akonadicore5-20.04]4:20.04.1-2+b1 ii libkf5akonadimime5 [libkf5akonadimime5-20.04]4:20.04.1-2 ii libkf5akonadisearch-bin 4:20.04.1-2 ii libkf5akonadisearch-plugins 4:20.04.1-2 ii libkf5akonadisearchdebug5 [libkf5akonadisearchdebug5-20.04] 4:20.04.1-2 ii libkf5akonadisearchpim5 [libkf5akonadisearchpim5-20.04] 4:20.04.1-2 ii libkf5akonadiwidgets5abi1 [libkf5akonadiwidgets5-20.04] 4:20.04.1-2+b1 ii libkf5bookmarks5 5.70.0-1 ii libkf5calendarcore5abi2 5:5.70.0-2 ii libkf5calendarutils5 [libkf5calendarutils5-20.04]4:20.04.1-2 ii libkf5codecs55.70.0-1 ii libkf5completion55.70.0-1 ii libkf5configcore55.70.0-1 ii libkf5configgui5 5.70.0-1 ii libkf5configwidgets5 5.70.0-2 ii libkf5contacts5 5:5.70.0-4 ii libkf5coreaddons55.70.0-2 ii libkf5crash5 5.70.0-1 ii libkf5dbusaddons55.70.0-1 ii libkf5followupreminder5 [libkf5followupreminder5-20.04] 4:20.04.1-2 ii libkf5grantleetheme-plugins 20.04.1-2 ii libkf5gravatar5abi2 [libkf5gravatar5-20.04] 4:20.04.1-2 ii libkf5guiaddons5
