Bug#1072857: Proposed fix for #1072857
Hi,
being hit by this too, I’ve sumbitted an MR at [1].
You’ll also find in attachment the same fix on top of the version of dput
currently in the archive which is slightly different from the one in the salsa
repo.
You can put it in /usr/share/dput/dput/dput.py as a short-term workaround.
[1] https://salsa.debian.org/debian/dput/-/merge_requests/13
Happy hacking,
--
Aurélien#! /usr/bin/python3
#
# dput/dput.py
# Part of ???dput???, a Debian package upload toolkit.
#
# This is free software, and you are welcome to redistribute it under
# certain conditions; see the end of this file for copyright
# information, grant of license, and disclaimer of warranty.
""" dput ??? Debian package upload tool. """
import configparser
import email.parser
from hashlib import (
md5,
sha1,
)
import importlib
import os
import os.path
import pkgutil
import re
import signal
import stat
import subprocess
import sys
import textwrap
import types
from . import configfile
from . import crypto
from .helper import dputhelper
app_library_path = os.path.dirname(__file__)
debug = 0
def import_upload_functions():
""" Import upload method modules and make them available. """
upload_methods = {}
package_name = "methods"
modules_path = os.path.join(app_library_path, package_name)
modules_found = [
name for (__, name, ispkg) in
pkgutil.iter_modules([modules_path])
if not ispkg]
if debug:
sys.stdout.write("D: modules_found: {!r}\n".format(modules_found))
for module_name in modules_found:
module = importlib.import_module("{package}.{module}".format(
package=".".join(["dput", package_name]),
module=module_name))
if debug:
sys.stdout.write("D: Module: {module_name} ({module!r})\n".format(
**vars()))
method_name = module_name
if debug:
sys.stdout.write("D: Method name: {}\n".format(method_name))
upload_methods[method_name] = module.upload
return upload_methods
def parse_changes(changes_file):
""" Parse the changes file. """
check = changes_file.read(5)
if check != "-":
changes_file.seek(0)
else:
# found a PGP header, gonna ditch the next 3 lines
# eat the rest of the line
changes_file.readline()
# Hash: SHA1
changes_file.readline()
# empty line
changes_file.readline()
if not changes_file.readline().find("Format") != -1:
changes_file.readline()
changes_text = changes_file.read()
changes = email.parser.HeaderParser().parsestr(changes_text)
if 'files' not in changes:
raise KeyError("No Files field in upload control file")
for file_spec in changes['files'].strip().split("\n"):
if len(file_spec.split()) != 5:
sys.stderr.write(textwrap.dedent("""\
Invalid Files line in .changes:
{}
""").format(file_spec))
sys.exit(1)
return changes
def read_configs(config_files, debug):
""" Read configuration settings from config files.
:param config_files: Sequence of configuration files, open for reading.
:param debug: If true, enable debugging output.
:return: The resulting `ConfigParser` instance.
The config parser will parse each file in `config_files`. Configuration
from later files overrides earlier files.
"""
config = configparser.ConfigParser()
config.set('DEFAULT', 'login', "username")
config.set('DEFAULT', 'method', "scp")
config.set('DEFAULT', 'hash', "md5")
config.set('DEFAULT', 'allow_unsigned_uploads', "0")
config.set('DEFAULT', 'allow_dcut', "0")
config.set('DEFAULT', 'distributions', "")
config.set('DEFAULT', 'allowed_distributions', "")
config.set('DEFAULT', 'run_lintian', "0")
config.set('DEFAULT', 'run_dinstall', "0")
config.set('DEFAULT', 'check_version', "0")
config.set('DEFAULT', 'scp_compress', "0")
config.set('DEFAULT', 'default_host_main', "")
config.set('DEFAULT', 'post_upload_command', "")
config.set('DEFAULT', 'pre_upload_command', "")
config.set('DEFAULT', 'ssh_config_options', "")
config.set('DEFAULT', 'passive_ftp', "1")
config.set('DEFAULT', 'progress_indicator', "0")
for config_file in config_files:
if debug:
sys.stdout.write(
"D: Parsing configuration file ???{path}???\n".format(
path=config_file.name))
try:
config.read_file(config_file)
except configparser.ParsingError as e:
sys.stderr.write(textwrap.dedent("""\
Error parsing configuration file:
{0}
""").format(str(e)))
sys.exit(1)
config_file.close()
# only check for fqdn and incoming dir, rest have reasonable defaults
Bug#1072713: ITP: plasma5support -- support components for porting from KF5/Qt5 to KF6/Qt6
Package: wnpp Severity: wishlist Owner: Aurélien COUDERC X-Debbugs-Cc: debian-de...@lists.debian.org, Debian Qt/KDE Maintainers * Package name: plasma5support Version : 6.0.5 Upstream Contact: Plasma Developers * URL : https://invent.kde.org/plasma/plasma5support * License : LGPL Programming Lang: C++, QML Description : support components for porting from KF5/Qt5 to KF6/Qt6 Plasma5Support Framework providing migration aids for KF5 -> KF6 migrations. The package will be maintained under the Qt/KDE Team’s umbrella.
Bug#1072656: ITP: kglobalacceld -- daemon for global keyboard shortcuts on the Plasma desktop
Package: wnpp Severity: wishlist Owner: Aurélien COUDERC X-Debbugs-Cc: debian-de...@lists.debian.org, Debian Qt/KDE Maintainers * Package name: kglobalacceld Version : 6.0.5 Upstream Contact: Plasma Developers * URL : https://invent.kde.org/plasma/ocean-sound-theme * License : LGPL Programming Lang: C++ Description : daemon for global keyboard shortcuts on the Plasma desktop Daemon providing Global Keyboard Shortcut (Accelerator) functionality for the Plasma desktop. The package will be maintained under the Qt/KDE Team’s umbrella.
Bug#1072649: ITP: ocean-sound-theme -- Ocean Sound Theme for the Plasma desktop
Package: wnpp Severity: wishlist Owner: Aurélien COUDERC X-Debbugs-Cc: debian-de...@lists.debian.org, Debian Qt/KDE Maintainers * Package name: ocean-sound-theme Version : 6.0.5 Upstream Contact: Plasma Developers * URL : https://invent.kde.org/plasma/ocean-sound-theme * License : CC-BY-SA-4.0 Description : Ocean Sound Theme for the Plasma desktop The Ocean Sound Theme for Plasma for the release of Plasma 6. This package contains the sounds that are used in the sound theme. It will be maintained under the Qt/KDE Team’s umbrella.
Bug#1070322: marked as pending in kio
So I’ve went ahead and backported the 2 additional commits mentioned as fixing #1069855 for bookworm (sid doesn’t need them). You’ll find the changes to the debian/bookworm branch for bookworm [1] and master for sid [2]. I’ve uploaded the sid package. I don’t really have the setup to reproduce or test the fixes so @all involved would you be OK with : - reviewing the changes again and building the package from the bookworm Salsa branch, - testing (testing (and retesting)), CIFS and general use cases. The patches look unintrusive and the 2 first ones are exact commits from later KIO releases, but if there’s something we don’t want to break in KDE that’s probably KIO… - submitting the bug to release.debian.org and get the sign-off from the release team ? I can handle the actual upload once that’s cleared. [1] https://salsa.debian.org/qt-kde-team/kde/kio/-/commits/debian%2Fbookworm [2] https://salsa.debian.org/qt-kde-team/kde/kio/-/commits/master/ Thanks ! -- Aurélien
Bug#1069546: ktorrent: FTBFS on armel: dh_install: error: missing files, aborting
Control: severity -1 wishlist
Bug#1069546: ktorrent: FTBFS on armel: dh_install: error: missing files, aborting
Control: retitle -1 ktorrent: FTBFS on arches without QtWebEngine Control: severity -1 whishlist Control: tags -1 + wontfix Le 20 avril 2024 15:23:30 GMT+02:00, Lucas Nussbaum a écrit : >Source: ktorrent >Version: 22.12.3-2 >Severity: serious >Justification: FTBFS >Tags: trixie sid ftbfs >User: lu...@debian.org >Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armel > >Hi, Dear Lucas, >During a rebuild of all packages in sid, your package failed to build >on armel. what happens is that on arches that don't have QtWebEngine, the ktorrent build succeeds but doesn't produce some of the files expected by dh_install for the arch:all ktorrent-data package. The issue doesn't happen on buildds where arch:all packages are built on amd64 and other arches run dh_install -a. There is no easy way to split the generation of the arch:all files for ktorrent in a separate build-indep target so I'm marking this bug as whishlist+wontfix. Happy hacking, -- Aurélien
Bug#1069408: kwin: FTBFS on arm64: present.h:20:10: fatal error: dri3.h: No such file or directory
Control: reassign -1 libxcb Control: found -1 1.17.0-1 Control: retitle -1 libxcb-present-dev 1.17 misses dependency on libxcb-dri3-dev Control: affects -1 + kwin Le samedi 20 avril 2024, 14:16:27 CEST Lucas Nussbaum a écrit : > Source: kwin > Version: 4:5.27.10-1 > Severity: serious > Justification: FTBFS > Tags: trixie sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-arm64 > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on arm64. Dear X Team, it seems to me that libxcb-present-dev 1.17 misses dependency on libxcb-dri3-dev which was added as a private dependency between 1.15 and 1.17. This is causing kwin to FTBFS. If that’s correct you’ll find an MR against the libxcb repo adding that dependency at [1]. [1] https://salsa.debian.org/xorg-team/lib/libxcb/-/merge_requests/3 Happy hacking, -- Aurélien
Bug#1036886: Text input fields very hard to identify in high contrast / dark mode
Hi Samuel, Le 23 octobre 2023 02:00:25 GMT+02:00, Samuel Thibault a écrit : >Hello, > >Aurélien COUDERC, le dim. 28 mai 2023 18:51:08 +0200, a ecrit: >> If we don’t want to reduce the contrast of either the static text or the >> input fields an option could be for text input fields to have a border >> with the same color as the text that would make them clearly >> identifiable. > >I had a hard time getting a border. The simplest might be to just have >a black background, as attached. Would that be fine enough? (we don't >actually lose any contrast since it's the same blue as before) Thanks for looking into this ! (I'm neither a designer nor visually impaired so take my feedback with some grains of salt.) It looks better to me, but I'm not sure how much better it would be for someone needing the high contrast. Would they identify the difference between the black and dark blue ? I'm copying devian-accessibility in case they have an opinion. As you said it's not making things worse so AFAIC feel free to go for any option you prefer. Happy hacking, -- Aurélien
Bug#1052039: okular: Okular cannot open PDF files: Solved !
Le 17 septembre 2023 09:35:27 GMT+02:00, "Frédéric Tronel" a écrit : >Dear maintainer, > > >I have found the reason why >/usr/lib/x86_64-linux-gnu/qt5/plugins/okular/generators/okularGenerator_poppler.so >was linked against libtiff.so.5 on my system. >This was due to a local recompilation of libpoppler on my bulleyes >installation (that I have just migrated to >bookworm). The faulty library (libpoppler.so) was still installed in >/usr/local/lib ... >Removing it solves the problem. Good to hear, thanks for the feedback. -- Aurélien
Bug#1035431: desktop-base: leaves alternatives after purge:
Dear Andreas, Le lundi 15 mai 2023, 18:31:46 CEST Andreas Beckmann a écrit : > Followup-For: Bug #1035431 > Control: tag -1 patch > > Please see the attached patch for fixing the prerm. > > The git repository is not up-to-date. (The last upload is missing.) applied to git and pushed all the changes. Thank you for the patch ! -- Aurélien
Bug#1040234: Acknowledgement (plasma-systemmonitor: graphical artefacts with nouveau kernel module)
control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=471979
Bug#1038660: desktop-base: please set a placeholder theme during development, different from any release
Dear Jonathan,
Le 23 juin 2023 16:33:43 GMT+02:00, Jonathan Carter a écrit :
>On 2023/06/19 20:50, Simon McVittie wrote:
>> Prior art: GNOME applications built from their alpha/beta branches often
>> have yellow and black stripes (resembling hazard tape) overlaying part
>> of their icon, and a gear-wheel motif in the titlebar, to distinguish
>> them from the stable version of the same application.
>
>I've been playing with the idea of "egg", a theme based on Juliet Taka's
>Homeworld theme, previously used on Debian 11.
>
>The egg represents something that hasn't hatched yet, screenshot attached. I
>can probably work on this a bit more after I've taken care of the live bugs
>for 12.1.
>
>Any thoughts?
I don't think I would have seen the « egg » look of it without the subtitle,
but I do like it.
Are you willing to work on the whole theme including login background,
wallpaper (and maybe lock screen) variants ? The dark version of the wallpaper
? (OK we don't even have that until now, but… why not !)
Also while at it I'd like to be able to ship each theme in their own
debian-artwork-${release} binary package (including that testing theme), but
still handle the theme n->theme testing->theme n+1 transition automagically for
users.
I've pondered over it a couple of times but couldn't come up with a nice way of
doing it.
Thoughts ?
--
Aurélien
Bug#1038660: desktop-base: please set a placeholder theme during development, different from any release
Dear Simon, Le lundi 19 juin 2023, 20:50:35 CEST Simon McVittie a écrit : > Package: desktop-base > Version: 12.0.6 > Severity: normal > Tags: trixie sid > > Now that Debian 12 has been released, the version of desktop-base in > testing should no longer include Debian 12 branding, so that the testing > installer will be visually distinct from the Debian 12 stable release. I think this makes sense. > The simplest possible implementation of this would be to remove the "12" > from all the art components, but I think it would be better to use artwork > that is obviously different. Yes, I can do that. > One simple "programmer-art" way to do that would be to desaturate the > Debian 12 artwork down to greyscale to make it obviously a placeholder, > or rotate the hue to make it a different colour. I probably won’t do that. > However, it might be nicer (and definitely more fun!) to have a theme > specifically for Debian in its alpha/beta state, with a sense of "this is > under construction", to be replaced by a proper Debian 13 theme closer > to the Debian 13 freeze. Some of the contributors who were helping with > debian-cd testing during the Debian 12 release process had a similar > thought a while ago, and got as far as preparing a background image for > this purpose - I'll ask them to follow up here. Well I was not convinced at all by the last proposal I saw. Obviously theming and art are very personal but I wouldn’t want to replace quality artwork we’ve been having for the last couple of releases with something I consider less attractive just for the sake of it. OK for the artwort to convey the idea of work-in-progress but the art itself cannot be work-in-progress… And yes I know people can change it if they like but defaults count, especially since it will be part first impressions for new users of testing. Happy hacking, -- Aurélien
Bug#1034951: ktexteditor: diff for NMU version 5.103.0-1.1
Le jeudi 18 mai 2023, 18:29:49 CEST Andreas Metzler a écrit : > Control: tags 1034951 + patch > Control: tags 1034951 + pending > > Dear maintainer, > > I've prepared an NMU for ktexteditor (versioned as 5.103.0-1.1) and > uploaded it to DELAYED/10. Please feel free to tell me if I > should delay it longer. Applied to git. Thanks for the fix ! -- Aurélien
Bug#1035056: [pre-approval] plasma-desktop 5.27.X
Control: tags -1 -moreinfo Hi, Le dimanche 28 mai 2023, 14:13:48 CEST Aurélien COUDERC a écrit : > Le dimanche 28 mai 2023, 08:26:16 CEST Paul Gevers a écrit : > > [0] https://deb.li/plasma All packages are now built in unstable, all puipart tests pass, we don’t have autopkgtests for this package set. For the record in the 100+ bugs fixed we have several shell desktop, screen management crashers and app crashers due to screen management that we would highly prefer having in for bookworm. I’ve included the fix for RC bug #1034215 where the KDE crash reporter drkonqi wouldn’t start on application crashes. The Plasma 5.27 branch is going to be maintained upstream for a foreseeable future so if I can convince the stable release managers to do the same, I plan to push future Plasma bugfix releases to stable after the bookworm release. > > Also please prepare the correct set of hints, they need to be in the > > form of: > > unblock package-name/version-in-unstable I confirm the list of unblock hints from my previous email below. Thanks, -- Aurélien unblock bluedevil/4:5.27.5-2 unblock breeze-grub/5.27.5-2 unblock breeze-plymouth/5.27.5-2 unblock drkonqi/5.27.5-2 unblock flatpak-kcm/5.27.5-2 unblock kactivitymanagerd/5.27.5-2 unblock kdecoration/4:5.27.5-2 unblock kgamma5/5.27.5-2 unblock kinfocenter/4:5.27.5-2 unblock kmenuedit/4:5.27.5-2 unblock kpipewire/5.27.5-3 unblock ksshaskpass/4:5.27.5-2 unblock kwallet-pam/5.27.5-2 unblock kwayland-integration/5.27.5-2 unblock kwrited/4:5.27.5-2 unblock layer-shell-qt/5.27.5-2 unblock libkscreen/4:5.27.5-2 unblock libksysguard/4:5.27.5-2 unblock milou/4:5.27.5-2 unblock oxygen-sounds/4:5.27.5-2 unblock plasma-discover/5.27.5-2 unblock plasma-disks/5.27.5-2 unblock plasma-firewall/5.27.5-2 unblock plasma-nano/5.27.5-2 unblock plasma-nm/4:5.27.5-2 unblock plasma-pa/4:5.27.5-2 unblock plasma-sdk/5.27.5-2 unblock plasma-thunderbolt/5.27.5-2 unblock plasma-welcome/5.27.5-2 unblock plasma-workspace-wallpapers/4:5.27.5-2 unblock plymouth-kcm/5.27.5-2 unblock polkit-kde-agent-1/4:5.27.5-2 unblock qqc2-breeze-style/5.27.5-2 unblock sddm-kcm/4:5.27.5-2 unblock xdg-desktop-portal-kde/5.27.5-2 unblock breeze/4:5.27.5-2 unblock kde-gtk-config/4:5.27.5-2 unblock kscreen/4:5.27.5-2 unblock kscreenlocker/5.27.5-2 unblock ksystemstats/5.27.5-2 unblock oxygen/4:5.27.5-2 unblock plasma-systemmonitor/5.27.5-2 unblock plasma-vault/5.27.5-2 unblock breeze-gtk/5.27.5-2 unblock kwin/4:5.27.5-3 unblock plasma-integration/5.27.5-2 unblock plasma-workspace/4:5.27.5-2 unblock kde-cli-tools/4:5.27.5.1-2 unblock kdeplasma-addons/4:5.27.5-2 unblock khotkeys/4:5.27.5-2 unblock plasma-bigscreen/5.27.5-2 unblock plasma-browser-integration/5.27.5-2 unblock plasma-desktop/4:5.27.5-2 unblock plasma-remotecontrollers/5.27.5-2 unblock powerdevil/4:5.27.5-2 unblock systemsettings/4:5.27.5-2
Bug#889635: Also interested in dh_installsystemd templates support
Package: debhelper Version: 13.11.4 Followup-For: Bug #889635 X-Debbugs-Cc: Debian Qt/KDE Maintainers Hi, I’m also interested in this feature, needed for the drkonqi KDE crash manager to be started when systemd-coredump starts. Drkonqi ships a drkonqi-coredump-processor@.service unit with a WantedBy=systemd-coredump@.service and I had to reimplement [0] part of what dh_installsystemd does in the maintainer scripts. Note that in this case we don’t have a DefaultInstance so unlike what Vinctor wrote above we *don’t want* to start / restart the unit on install / upgrade as this would make no sense in this situation. [0] https://salsa.debian.org/qt-kde-team/kde/drkonqi/-/tree/master/debian Happy hacking, -- Aurélien -- System Information: Debian Release: 12.0 APT prefers unstable APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500, 'testing-security'), (500, 'testing'), (100, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-9-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages debhelper depends on: ii autotools-dev20220109.1 ii dh-autoreconf20 ii dh-strip-nondeterminism 1.13.1-1 ii dpkg 1.21.22 ii dpkg-dev 1.21.22 ii dwz 0.15-1 ii file 1:5.44-3 ii libdebhelper-perl13.11.4 ii libdpkg-perl 1.21.22 ii man-db 2.11.2-2 ii perl 5.36.0-7 ii po-debconf 1.0.21+nmu1 debhelper recommends no packages. Versions of packages debhelper suggests: ii dh-make 2.202301 -- no debconf information
Bug#1036886: Text input fields very hard to identify in high contrast / dark mode
Source: rootskel-gtk Severity: normal Tags: a11y Dear Mantainer, running the installer in graphical dark / high contrast mode, it’s very hard to identify text input fields in the installer pages, making it very difficult to see where things need to be input. The default theme does a must better job at it whereas the high contrast theme uses (almost ?) the same color for the global page background and the text input fields background, and the input fields have no visible border. If we don’t want to reduce the contrast of either the static text or the input fields an option could be for text input fields to have a border with the same color as the text that would make them clearly identifiable. -- System Information: Debian Release: 12.0 APT prefers unstable APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500, 'testing-security'), (500, 'testing'), (100, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-9-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1035056: [pre-approval] plasma-desktop 5.27.X
Le dimanche 28 mai 2023, 08:26:16 CEST Paul Gevers a écrit : > Control: tags -1 confirmed moreinfo > > Hi all, > > [For those following at home, I had multiple live discussions with > Aurélien at the Debian Reunion Hamburg.] > > On 27-05-2023 22:44, Aurélien COUDERC wrote: > > I don’t have particular bugs in mind, I think the selection that upstream > > makes of bugs that deserve a fix in their stable 5.27 branch makes sense > > for us to follow. > > Ok, it's terribly late but let's go for this then. ❤❤❤ > You'll need to help a > bit more though. You want the full set to migrate together, so please > check the status of the upload you did yesterday and let me know when > everything is ready. That means that no package should be blocked on > anything except age and the freeze. Piuparts and autopkgtest runs must > have finished and when finished neither must block migration. Did you > mention you have a web page for that already, can you share the link? Yes, that is [0]. [0] https://deb.li/plasma The packages on the dashboard are sorted by layers of build dependencies then alphabetically in each layer. So you will find the packages further in the dependency tree at the bottom, and not all built yet. The same dashboard for bookworm incorrectly reports breeze-grub as sucessfully built for mips64el and s390x but this was not the case. We I don’t think we have the equivalent for autopkgtests / puiparts so I’ll check these manually. > Also please prepare the correct set of hints, they need to be in the > form of: > unblock package-name/version-in-unstable That would be the list at the bottom. We will confirm when all builds / tests have passed. Cheers -- Aurélien unblock bluedevil/4:5.27.5-2 unblock breeze-grub/5.27.5-2 unblock breeze-plymouth/5.27.5-2 unblock drkonqi/5.27.5-2 unblock flatpak-kcm/5.27.5-2 unblock kactivitymanagerd/5.27.5-2 unblock kdecoration/4:5.27.5-2 unblock kgamma5/5.27.5-2 unblock kinfocenter/4:5.27.5-2 unblock kmenuedit/4:5.27.5-2 unblock kpipewire/5.27.5-3 unblock ksshaskpass/4:5.27.5-2 unblock kwallet-pam/5.27.5-2 unblock kwayland-integration/5.27.5-2 unblock kwrited/4:5.27.5-2 unblock layer-shell-qt/5.27.5-2 unblock libkscreen/4:5.27.5-2 unblock libksysguard/4:5.27.5-2 unblock milou/4:5.27.5-2 unblock oxygen-sounds/4:5.27.5-2 unblock plasma-discover/5.27.5-2 unblock plasma-disks/5.27.5-2 unblock plasma-firewall/5.27.5-2 unblock plasma-nano/5.27.5-2 unblock plasma-nm/4:5.27.5-2 unblock plasma-pa/4:5.27.5-2 unblock plasma-sdk/5.27.5-2 unblock plasma-thunderbolt/5.27.5-2 unblock plasma-welcome/5.27.5-2 unblock plasma-workspace-wallpapers/4:5.27.5-2 unblock plymouth-kcm/5.27.5-2 unblock polkit-kde-agent-1/4:5.27.5-2 unblock qqc2-breeze-style/5.27.5-2 unblock sddm-kcm/4:5.27.5-2 unblock xdg-desktop-portal-kde/5.27.5-2 unblock breeze/4:5.27.5-2 unblock kde-gtk-config/4:5.27.5-2 unblock kscreen/4:5.27.5-2 unblock kscreenlocker/5.27.5-2 unblock ksystemstats/5.27.5-2 unblock oxygen/4:5.27.5-2 unblock plasma-systemmonitor/5.27.5-2 unblock plasma-vault/5.27.5-2 unblock breeze-gtk/5.27.5-2 unblock kwin/4:5.27.5-3 unblock plasma-integration/5.27.5-2 unblock plasma-workspace/4:5.27.5-2 unblock kde-cli-tools/4:5.27.5.1-2 unblock kdeplasma-addons/4:5.27.5-2 unblock khotkeys/4:5.27.5-2 unblock plasma-bigscreen/5.27.5-2 unblock plasma-browser-integration/5.27.5-2 unblock plasma-desktop/4:5.27.5-2 unblock plasma-remotecontrollers/5.27.5-2 unblock powerdevil/4:5.27.5-2 unblock systemsettings/4:5.27.5-2
Bug#1035056: [pre-approval] plasma-desktop 5.27.X
Dear Paul, Le mardi 16 mai 2023, 22:20:37 CEST Paul Gevers a écrit : > > We don’t have the personpower to backport all these fixes to 5.27.2 > > individually and even if we did it would be a questionable option. > > I think we are aligned on that. But having said that, are there bug you > have particularly on your radar? And would it be an option to not cherry > pick backport bug fixes, but cherry pick packages with their bug fixes? I don’t have particular bugs in mind, I think the selection that upstream makes of bugs that deserve a fix in their stable 5.27 branch makes sense for us to follow. You can get an idea of the kind of bugs fixed at [0]. There’s no « fixed in version » field in their bugzilla so I took the list of bugs reported against 5.27.2..5.27.4 marked as fixed as an approximation. [0] https://bugs.kde.org/buglist.cgi?query_format=advanced=FIXED=5.27.2=5.27.3=5.27.4 Also note that some package (build)depend on other packages in the Plasma set having the exact same upstream version. While not a good argument in itself that still means we would need to do some version-fu to make the package cherry-pick option work. I’ve made some statistics about the 56-package Plasma set and between 5.27.2 (in testing) and 5.27.5 (in experimental) we have : - 4 packages with no change besides the version bump - 20 packages with transaltion-only commits (upstream never mentions these in their release notes) - 32 remaining packages having code fixes and mentioned in the release note, including 5 not having an explicit bug id linked Please find the details in the table below. Best, -- Aurélien | package | has | has non-transl | mentioned in | bug fixed in | | | translations | commits| rel notes| rel notes| |---|--||--|--| |breeze-grub| || | | |breeze-plymouth| || | | |layer-shell-qt | || | | |oxygen-sounds | || | | |kactivitymanagerd | x || | | |kdecoration| x || | | |kgamma5| x || | | |khotkeys | x || | | |kmenuedit | x || | | |ksshaskpass| x || | | |ksystemstats | x || | | |milou | x || | | |oxygen | x || | | |plasma-bigscreen | x || | | |plasma-browser-integration | x || | | |kwrited| x || | | |plasma-disks | x || | | |plasma-firewall| x || | | |plasma-nano| x || | | |plasma-systemmonitor | x || | | |plasma-thunderbolt | x || | | |plasma-vault | x || | | |plasma-workspace-wallpapers| x || | | |plymouth-kcm | x || | | |qqc2-breeze-style | |x | x | | |drkonqi| x |x | x | | |kwallet-pam| x |x | x | | |libksysguard | x |x | x | | |sddm-kcm | x |x | x | | |breeze-gtk | |x | x | x | |bluedevil | x |x | x | x | |breeze | x |x | x | x | |flatpak-kcm| x |x | x | x | |kde-cli-tools
Bug#1034215: drkonqi: dh_installsystemd doesn't handle files in /usr/lib/systemd/system
Hi ! Le mercredi 12 avril 2023, 13:25:06 CEST Andreas Henriksson a écrit : > Hello again, > > On Wed, Apr 12, 2023 at 01:19:52PM +0200, Andreas Henriksson wrote: > > On Tue, Apr 11, 2023 at 09:37:27AM +0200, bi...@debian.org wrote: > > > > > It seems that your package drkonqi is shipping files (.service, .socket or > > > .timer) in /usr/lib/systemd/system. > > [...] > > > > ``` > > $ apt-file show drkonqi | grep systemd/system > > drkonqi: /usr/lib/systemd/system/drkonqi-coredump-processor@.service > > ``` > > I forgot to mention that since this is a template unit (@.service) > maybe the severity should not be RC. > As far as I know debhelper will not enable any instance of a template > unit by default anyway, so the consequences that bigon warned about > probably doesn't apply here? @Laurent would you mind commenting on this ? As per my understanding what we would miss (the service not being activated on installation) doesn’t apply here because the only service file we ship is a systemd template. With a simple tweak to your search command, drkonqi disappears from the list. :) apt-file search -x '^/usr/lib/systemd/system/.*[^@]\.(service|timer|socket)$'|cut -d: -f1|sort -u So may I simply close this bug ? Thanks, -- Aurélien
Bug#1035056: [pre-approval] plasma-desktop 5.27.X
Dear Paul, Le dimanche 14 mai 2023, 22:05:19 CEST Paul Gevers a écrit : > Control: tags -1 moreinfo > > Hi, > > On 28-04-2023 15:29, Hefee wrote: > > 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. > > Please read the freeze policy [2] and the FAQ [3] very carefully and > make sure your request meets the requirements of this phase of the > freeze and make sure you can answer every relevant question from the > FAQ. Please only pursue if you convinced the answer is yes. we know the freeze policy and we know our request doesn’t meet the freeze policy requirements to the letter. What we’re asking for is an exception because we think the current policy isn’t helping with release quality for a project the size and complexity of Plasma and with such a level of upstream activity. As Patrick wrote there are over a hundred bugs fixed in 5.27.3, .4 and .5 releases that we’re currently not shipping in bookworm. We don’t have the personpower to backport all these fixes to 5.27.2 individually and even if we did it would be a questionable option. We consider the risk of introducing new bugs by not shipping all upstream changes to be higher than shipping complete point releases. In addition we would be creating a Debian-specific version of Plasma unsupported by upstream, in parallel to their very own bugfix release branch that they maintain with a very close target to ours : only bugfixes to avoid regressions. So the remaining options we can think of are : - Ship bookworm with Plasma as it is : good for the release policy and our team’s workload, certainly bad for our users and the image of Plasma on Debian. - Remove Plasma from stable : not doable for bookworm as it is in the essential set like you wrote below, not a good move for Debian anyway I hope we would agree. - Ship the point releases to stable : won’t follow the freeze policy to the letter, manageable work on our side, certainly good for our users besides possible regressions introduced upstream, regressions will be looked at by upstream if they happen. > > Currently 5.27.3 on experimental. Upstream is relasing with a fibbonacci > > time frame, > > What does that mean (sorry, I don't have the energy to look this up, too > many unblock requests to process)? Each point release is made further away in time from the previous, as Plasma 5.27 LTS stabilizes. > > 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. > > So you consider bumping 5.27.2 to 5.27.5 a targeted fix? Would you > request the same in a stable point update (because that's about the same > level at this phase of the release)? We consider it a better option for bookworm, being overall a big collection of fixes. We don’t pretend it meets the targeted fix policy for each and every commit that goes in. And yes, we would like to be able to ship Plasma point releases to stable. This hasn’t been discussed with the relevant teams yet. > > 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. > > [From FAQ] can you point at an upstream document that explains their policy? You may find the Plasma release page at [1] which only says : This is the last Plasma 5 release and will receive bugfixes only, no new features. The bugfixes are intended to continue being integrated into 5.27 until a first version of Plasma 6 can be released (and might continue longer). [1] https://community.kde.org/Schedules/Plasma_5#LTS_releases So they commit on putting only bugfixes in their LTS releases, but not only targeted bugfixes like we do. > > Plasma is ~50 pacakges - see a list of packages: > > I think you know by now, this fits extremely bad with the way the Freeze > is handled as we review everything and need to watch that everything > migrates. We're not going to give a set of key packages a cart blanch > this late in the freeze especially when we've NACK-ed already easier > things. E.g. although we're convinced the MariaDB unblock [4] really had > all best intentions and we hate to deny unblocks, it contained a bunch > of changes not meeting the freeze policy. I don’t want to compare situations but would like to discuss the merits of pushing Plasma point releases in bookworm. > We're frozen to ensure > stability and no surprises. The freeze policy is not ment to manage > packages (that's up to the maintainers), it's meant to ensure we can > manage the release process. And we do value your work on the release process and share the goal of releasing a stabilized Debian. We are not convinced that the process is helping us reaching that goal for Plasma, however. > In this particular case, we also don't have > tools to
Bug#1035056: Disappointed
Dear x s, Le 16 mai 2023 09:37:32 GMT+02:00, x s a écrit : >It’s really disappointing that the only reason for blocking Plasma 5.27.5 and >Frameworks 5.104 is that there’s “too many packages”. we understand that users are eager to see Plasma updated, we (the KDE packaging team) are too, thanks for your feedback. I'd prefer that we discuss the way to make it happen between the KDE packaging team and the release team in a dispassionate way though. >I’d like to remind you that GNOME 43.4 was allowed to migrate recently; why >does GNOME get special treatment and KDE has to stay stuck on an older, >buggier version? Debian KDE users would strongly appreciate you changing your >stance and allowing the best versions to be included on release. These were 2 packages : gnome-shell and mutter. We're talking 50+ packages for Plasma so it's nothing comparable. Paul raised some valid concerns in that regard and we're preparing a response. >If you still are not convinced on allowing these to be unblocked, would you at >least consider allowing them to migrate for the Debian 12.1 point release? >Again, I’d like to remind you that these are long-term support releases, they >strictly fix bugs and contain no new features. There are absolutely no >downsides to allowing them to migrate so they can be in Debian 12. Yes, we (the KDE packaging team) would very much like to do that if it's not possible to get an unblock before the release. No guarantee that it can fit into our release and stable updates processes though, so no guarantees. Stay tuned and please let us think about the implications and manage the topic in a way that is appropriate for a stable Debian release. All the best, -- Aurélien
Bug#1035894: unblock: desktop-base/12.0.6
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: desktop-b...@packages.debian.org, debian-desk...@lists.debian.org
Control: affects -1 + src:desktop-base
Dear Release Team,
please unblock package desktop-base.
[ Reason ]
It fixes a bug where Pymouth messages and prompts don’t get displayed
for some screen size and ratio combinations.
[ Impact ]
- Users won’t see the password prompt for LUKS encrypted volumes on boot
in certain screen configurations. (#1032412)
- The « remove media press enter to reboot » message isn’t shown after
initial installation.
[ Tests ]
I tested that there are no regression on single screen use cases and
both the original reporter and a second person confirmed the fix on
their multi-screen / multi-ratio configurations.
[ Risks ]
No risk identified, the patch is small and localised the new code
underwent more tests in more configurations that the one currently in
testing.
[ 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 ]
Thanks for your work on the release !
unblock desktop-base/12.0.6
diff -Nru desktop-base-12.0.5/debian/changelog
desktop-base-12.0.6/debian/changelog
--- desktop-base-12.0.5/debian/changelog2023-03-01 23:22:32.0
+0100
+++ desktop-base-12.0.6/debian/changelog2023-04-13 21:58:23.0
+0200
@@ -1,3 +1,10 @@
+desktop-base (12.0.6) unstable; urgency=medium
+
+ * Fix LUKS password not being shown in multi-screen setup with mixed aspect
+ratios.
+
+ -- Aurélien COUDERC Thu, 13 Apr 2023 21:58:23 +0200
+
desktop-base (12.0.5) unstable; urgency=medium
* Make the GDM Debian footer slightly smaller.
diff -Nru desktop-base-12.0.5/emerald-theme/plymouth/emerald.script
desktop-base-12.0.6/emerald-theme/plymouth/emerald.script
--- desktop-base-12.0.5/emerald-theme/plymouth/emerald.script 2023-03-01
23:01:49.0 +0100
+++ desktop-base-12.0.6/emerald-theme/plymouth/emerald.script 2023-04-13
21:58:23.0 +0200
@@ -119,7 +119,8 @@
#Debug("y = " + y);
text_height = first_line_height * 7.5;
-min_height = window_max.height - 2 * first_line_height;
+# subtract Window.GetY() to show info also at smallest of dual srceens
+min_height = window_max.height - 2 * first_line_height - Window.GetY();
#Debug("text_height=" + text_height + "; min_height=" + min_height);
if (y + text_height > min_height)
@@ -131,8 +132,8 @@
#- Screen/window setup ---
# Compute screen/image ratio and scale the background accordingly
-window_max.width = Window.GetX() * 2 + Window.GetWidth();
-window_max.height = Window.GetY() * 2 + Window.GetHeight();
+window_max.width = Window.GetWidth();
+window_max.height = Window.GetHeight();
screen_ratio = window_max.width / window_max.height;
small_dimension = Math.Min(window_max.width, window_max.height);
#Debug("Window.GetX():" + Window.GetX() + ", Window.GetY():" + Window.GetY());
Bug#1033271: [pre-approval] unblock: KDE frameworks 5.104
Dear Paul, Le 23 mars 2023 13:10:55 GMT+01:00, Paul Gevers a écrit : >Hi Aurélien, > >On 16-03-2023 22:38, Aurélien COUDERC wrote: >> Thus I’m looking for a pre-approval to upload all 83 to unstable in >> order to get them accepted into bookworm. >> I will file the 83 unblock requests if I get your approval, but I need >> the guarantee that all of the 83 packages will be unblocked if you >> accept to go down that route so the whole set of packages land >> consistently into bookworm. > >That's not reviewable from our side and handling 83 unblocks is painful too. >Sorry, our workflow doesn't support your request so let's not do this. you're bartering ease-to-review on your side against ease-to-maintain on our side. We have the case for both Frameworks (83 source packages) and Plasma (56 source packages) where we have upstream doing bugfix releases that we won't have in bookworm due to $process. That's disappointing, I don't like that conclusion at all, and it's not going to make neither bookworm nor our relation with upstream better. Now we're back to tracking upstream commits on nearly 150 git repos and backport the ones that seem the most pressing, thank you very much. Anyway, nothing personal. Thank you for your work on release coordination and all the best. -- Disappointed Aurélien
Bug#1000955: libkf5globalaccel-bin: /usr/bin/kglobalaccel5 eats up huge amount of CPU after suspend
Le 13 mars 2023 21:04:33 GMT+01:00, James Addison a écrit : >Followup-For: Bug #1000955 >Control: severity -1 normal > >A summary of a side-discussion between Filippo and myself about this bug: > > * Although the bug doesn't appear reproducible today, the cause hasn't been >confirmed. > > * We both agreed that it makes sense for bugs to continue to stay open until >it's clear that the reported problem has been solved. Thank you for the follow up. >Based on that I think we should leave the bug open, but reduce the severity so >that it isn't considered release-critical for bookworm. Agreed. -- Aurélien
Bug#1028208: plasma-discover: Program terminated with signal SIGSEGV
control: reassign -1 libpackagekitqt5-1 1.1.0-1
Bug#1030854: kded5: It keeps on crashing everytime I boot into the system
control: reassign -1 libpackagekitqt5-1 1.1.0-1 Le 7 mars 2023 19:43:58 GMT+01:00, "Bernhard Übelacker" a écrit : >> Stack trace of thread 67345: >> #0 0x7f8daa6a9ccc n/a (libc.so.6 + 0x8accc) >> #1 0x7f8daa65aef2 raise (libc.so.6 + 0x3bef2) >> #2 0x7f8dabf4c83d _ZN6KCrash19defaultCrashHandlerEi >> (libKF5Crash.so.5 + 0x583d) >> #3 0x7f8daa65af90 n/a (libc.so.6 + 0x3bf90) >> #4 0x7f8d5553b740 _ZNK10PackageKit11Transaction3tidEv >> (libpackagekitqt5.so.1 + 0x1a740) >> #5 0x7f8d555f16f3 n/a (kded_apperd.so + 0xf6f3) >> #6 0x7f8d555f1df6 n/a (kded_apperd.so + 0xfdf6) >> #7 0x7f8daaae8f4f n/a (libQt5Core.so.5 + 0x2e8f4f) >> #8 0x7f8d5552f095 >> _ZN10PackageKit6Daemon22transactionListChangedERK11QStringList >> (libpackagekitqt5.so.1 + 0xe095) >> #9 0x7f8daaae8f7c n/a (libQt5Core.so.5 + 0x2e8f7c) >> #10 0x7f8d55547b38 n/a (libpackagekitqt5.so.1 + 0x26b38) >> #11 0x7f8d55548d73 n/a (libpackagekitqt5.so.1 + 0x27d73) >> #12 0x7f8dab6c861b n/a (libQt5DBus.so.5 + 0x2361b) >> #13 0x7f8daaadd6f0 _ZN7QObject5eventEP6QEvent >> (libQt5Core.so.5 + 0x2dd6f0) >> #14 0x7f8dab962fae >> _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent >> (libQt5Widgets.so.5 + 0x162fae) > > >Hello, >this seems similar to the backtrace in bug #1026062. > >Kind regards, >Bernhard > > >https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026062 >
Bug#1028083: plasma-discover: Discover tray app crashes kded5, causing other system tray icons to vanish
control: reassign -1 libpackagekitqt5-1 1.1.0-1
Bug#1027326: kde-plasma-desktop: Process 1465 (kded5) of user 1000 dumped core.
control: reassign -1 libpackagekitqt5-1 1.1.0-1
Bug#1026062: kded5: kded crashes with signal 11
Many thanks to all for tracking this bug, adding info, coordinating with upstream, following progress, testing the fix, and thanks to Matthias for uploading the fixed upstream version. @Matthias I think we really shouldn't release without the fix so an upgraded severity to >= serious would be appropriate for this bug. But I'll leave you judge on that. Happy hacking ! -- Aurélien
Bug#1030854: kded5: It keeps on crashing everytime I boot into the system
cobtrol: reassign -1 libpackagekitqt5-1 1.1.0-1
Bug#1032674: /usr/bin/plasmashell: when killing a window via the grouped task bar, the task bar disappears
control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=464186 Le 10 mars 2023 21:45:57 GMT+01:00, Paul Gevers a écrit : >Package: plasma-workspace >Version: 4:5.27.0-1 >Severity: normal >File: /usr/bin/plasmashell > >Dear maintainers, Dear Paul, >Thank you for maintaining KDE in Debian, it must be a hell of a job. Thank you for coordinating Debian releases, it must be a hell of a job. > I >want to share the following annoyance which is probably due to a crash >and auto restart (so an annoyance, but probably it really should be >fixed). When I have multiple windows of the same program (qgit in my >case) I have their entries grouped in the task bar. If I hover over >their entry in the task bar, multiple minified windows appear with a >close button. When I press the close button of the minified window I >want to close, the task bar dissapears for several seconds. When the >bar returns I can see that `plasmashell` got started in the same >minute as the disappearance. This is tracked upstream as bug 464186 (now linked). The fix is in KDE Frameworks 5.104 which is expected to be released tomorrow (March 11.). I've not seen the release note yet but KDE Frameworks is a tightly coupled set of 83 source packages, and I'd prefer avoiding having to backport individual fixes as much as possible. If I could trick the Release Team into accepting 5.104 into bookworm as a whole, it would fix this issue and probably several others in a safe way. Frameworks 5.x is now in maintenance mode and upstream is supposed to include only bugfixes there. This particular fix is a oneliner so not an issue to backport in itself, but it would mean I'm going down the long hard path of patching on top of the 83 frameworks packages version 5.103, hoping not to (cross-)break more things. So patching is definitely not my preferred option. Let's see what the complete Frameworks 5.104 release note brings us and I'll file a proper unblock pre-approval bug to discuss this. Happy hacking, -- Aurélien
Bug#1026062: kded crashes after turning off screen
Hi, Le 10 mars 2023 12:16:46 GMT+01:00, Jordi Bosveld a écrit : >Yesterday I upgraded both my workstation and my HTPC to bookworm, and now I >see kded crashes too. The aforementioned patch did not fix them, but >considering how I manage to trigger this crash, that is expected. Reproducing >is super easy for me. All I have to do is turn off the screen (or tv). The >same line is reported (repeatedly) as with the PackageKit bug that was >hopefully fixed: > >Mar 10 11:22:57 relativity kded5[63899]: QDBusAbstractAdaptor: Cannot relay >signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: >KDEDModule* > >Needless to say, this did not happen on bullseye. One system is NVIDIA using >DisplayPort, the other is AMD (RADV) through HDMI, both X11. A third system >running Wayland does not seem affected. This bug report was about an apper/packagekit-qt crash. Your issue is unrelated, please open a second bug report. Thanks ! -- Aurélien
Bug#961731: fixed
control: fixed -1 0.19.0-5
Bug#1031690: Regression in wayland mixed DPI setups
Dear Odyx, Le lundi 20 février 2023, 18:10:58 CET Didier 'OdyX' Raboud a écrit : > Package: plasma-workspace-wayland > Version: 4:5.27.0-1 > Severity: important > Tags: upstream > > Hello there, > > it looks like there's a regression in mixed DPI setups (one hiDPI screen > at "150%", a lower-DPI screen at "100%"), on Wayland, for some non-KDE > applications. In my case, flatpak firefox has too small tabs depending > on which screen it initially got launched. This has been marked as fixed upstream in 5.27.1. Could you retest on 5.27.2 that we have in unstable and close this bug if it is indeed fixed ? Thanks, -- Aurélien
Bug#1032252: baloo-kf5: baloo displays search results multiple times.
control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=401863 Dear olaf, Le jeudi 2 mars 2023, 12:44:24 CET olaf a écrit : > Package: baloo-kf5 > Version: 5.103.0-2 > Severity: normal > > Dear Maintainer, > > The problem should be well known, e.g. it has been reported here over the > years: > - https://bugs.kde.org/show_bug.cgi?id=419302 Indeed, and it’s most recent follow-up up upstream bug seems to be [1] so I’m linking your Debian bug report to it. Unfortunately it doesn’t look like upstream has worked fix for it yet. [1] https://bugs.kde.org/show_bug.cgi?id=401863 Happy hacking, -- Aurélien
Bug#1032301: The KDE Plasma Widget is showing the "lo" interface
control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=465655 control: fixed -1 4:5.27.2-1 Dear only4com, Le 3 mars 2023 10:12:19 GMT+01:00, only4com a écrit : >Package: plasma-nm >Version: 4:5.27.0-1 > >Dear Maintainer > >the Plasma Widget Networks has started to show also the "lo" interface, which >is confusing (with a button to disable it, which obviously is no possible). This is a known upstream bug and has been fixed in Plasma 5.27.1. We have 5.27.2 in Debian unstable with the fix, that will migrate to testing in a couple of days. Happy hacking, -- Aurélien
Bug#1032273: unblock: plasma-welcome/5.27.2-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: plasma-welc...@packages.debian.org, Debian Qt/KDE Maintainers Control: affects -1 + src:plasma-welcome Dear Release Team, could you please age package plasma-welcome 5.27.2 so it can migrate to testing quickly. [ Reason ] Previous version 5.27.0 recently migrated to testing and introduced #1032258 [1] where I left some test code pollute the package and it makes the Plasma welcome app produce an nonsensical welcome page. The bug was not seen before that in unstable because you see it only on first login to Plasma and people will usually install testing, login, then upgrade to unstable. [ Risks ] The risk is low, the unstable version is a bugfix release for the version in testing, cleared from the leftover test code. Thanks ! -- Aurélien unblock plasma-welcome/5.27.2-1
Bug#1032258: plasma-welcome: contains unintended patches providing a nonsensical welcome screen
Oops. Will fix that right away. Le 2 mars 2023 14:09:46 GMT+01:00, Simon McVittie a écrit : >Package: plasma-welcome >Version: 5.27.0-1 >Severity: serious >Justification: not suitable for inclusion in a stable release in this form >Control: fixed -1 5.27.2-1 >
Bug#1031953: libkf5screen8: Second monitor issues with NVIDIA
Dear Steve, Le samedi 25 février 2023, 22:39:41 CET Steve M. Robbins a écrit : > > This is to note that the upstream bug titled "On X11 with proprietary NVIDIA > GPU drivers, external monitor disabled after reboot or wake-from-sleep" > applies > to Debian package 4.27.0-1. > > See https://bugs.kde.org/show_bug.cgi?id=460341 > > Today a fix has finally been found. There are at least a few reports that it > solves the issue -- I've tested it myself and it does solve the symptom I've > been having since October 2022. > > The patch is: > https://invent.kde.org/plasma/libkscreen/-/commit/1d237c29655c7e3fb15fb9b71e5f167bd207593f > > I'd love to see it applied before the release. Happy to do an upload myself > if > that's preferred. Please don’t. I plan to upload the whole of Plasma 5.27.2 targeting bookworm. But please do follow-up on this and if the patch doesn’t make into the 5.27.2 upstream release you’re welcome to report it here so we can apply the fix on top of that release. Thanks ! -- Aurélien
Bug#1031900: kimageformats FTBFS on i386
Le vendredi 24 février 2023, 21:17:38 CET Adrian Bunk a écrit : > 1031900 Thanks for the patch ! Applied and uploaded. Happy hacking, -- Aurélien
Bug#1021816: Reassign to desktop-base
control: reassign -1 desktop-base 12.0.0 control: fixed -1 desktop-base/12.0.3
Bug#1031846: installation-reports: Same as bug #1031806 Install completes successfully after reboot no /home /Documents etc folders
control: reassign -1 desktop-base 12.0.2 control: fixed -1 desktop-base/12.0.3
Bug#1031846: installation-reports: Same as bug #1031806 Install completes successfully after reboot no /home /Documents etc folders
Dear Jason, could you please confirm which desktop environment you installed ? If it's KDE/Plasma I fixed the issue in the desktop-base package version 12.0.3, currently in testing and that should reach unstable in a couple of days. If you feel like testing the fix you could upgrade to unstable and try with a new user to check that it's fixed. On an existing user running : xdg-user-dirs-update should fix the issue. Haply hacking ! -- Aurélien
Bug#1030552: systemsettings: Display Configuration disregards list of "Screen Priorities" at every login on KDE Plasma
control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=465396
Bug#1030396: Fwd: Bug#1030396: kde-spectacle: Automatic clipboard copy does nothing
control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=465010 Le 4 février 2023 17:08:35 GMT+01:00, Jesse Rhodes a écrit : >Hello Aurélien, > >Yes, that's exactly it. I am using the rectangle selection as described >there. Sorry, I did check for an upstream report but I must have missed it >in the list. No worries. So I'm linking that upstream bug report.
Bug#1030396: kde-spectacle: Automatic clipboard copy does nothing
Dear Jesse, Le 4 février 2023 03:41:37 GMT+01:00, Jesse Rhodes a écrit : >Package: kde-spectacle >Version: 22.12.1-1 >Severity: normal >X-Debbugs-Cc: je...@sney.ca > >Dear Maintainer, > >I have kde-spectacle set up to automatically copy any screenshots to the >clipboard so I can easily paste them into a chat application or image share >site, etc. This has been my workflow for some time. > >Since the update to kde 5.26.90, the spectacle window shows a "The screenshot >has been copied to the clipboard." tooltip, but when I go to paste, the >expected image isn't there and I paste whatever else was the most recent thing >in my clipboard. This looks like the following bug report : https://bugs.kde.org/show_bug.cgi?id=465010 Can you confirm you're using the rectangle selection as described there ? Thanks, -- Aurélien
Bug#1029656: Unexpected transition: libkscreen
Le 1 février 2023 01:10:32 GMT+01:00, "Aurélien COUDERC" a écrit : > > >Le 31 janvier 2023 23:16:18 GMT+01:00, Sebastian Ramacher > a écrit : >>On 2023-01-26 22:14:25 +0100, Sebastian Ramacher wrote: >>> Control: tags -1 moreinfo >>> >>> On 2023-01-25 23:37:33 +0100, Aurélien COUDERC wrote: >>> > Package: release.debian.org >>> > Severity: normal >>> > User: release.debian@packages.debian.org >>> > Usertags: transition >>> > X-Debbugs-Cc: libkscr...@packages.debian.org, >>> > pkg-kde-t...@alioth-lists.debian.net >>> > Control: affects -1 + src:libkscreen >>> > >>> > Dear Release Team, >>> > >>> > it has been raised to my attention that the libkscreen soname bump I >>> > recently asked to accept has caused issues with packages outside the >>> > Plasma package set… :-( >>> > This was obviously not intentional and our team members with whom I >>> > discussed the topic before uploading weren’t aware either. >>> > And the timing to discover this is particularly bad. >>> > >>> > Of course I should have checked more thoroughly myself, but here we are. >>> > >>> > >>> > So moving forward, the following packages are affected : >>> > - kylin-display-switch (kylin team) => rebuilds OK >>> > - lxqt-config (lxqt team) => FTBFS due to new libkscreen >>> > (#1029611) >>> > - ukui-control-center (kylin team) => FTBFS due to new libkscreen >>> > (#1029612) >>> > - ukui-settings-daemon (kylin team) => FTBFS due to new libkscreen >>> > (#1029613) > >For the record I've prepared patches to fix the 2 ukui packages, that were >accepted and uploaded by the maintainer. > >>> I have added a block hint for libkscreen until the situation is resolved. >>> Please either revert libkscreen in unstable or help with fixing these >>> bugs. >> >>The issues were fixed and the transition is done. > >Many thanks, > >-- >Aurélien
Bug#1029521: plasma-nm: Unable to access the VPN network in double authentication mode (fix)
control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=448153
Bug#1029613: ukui-settings-daemon FTBFS: Unexpected libkscreen transition
With the help of Sune Vuorela I was able to patch some workarounds into
libkscreen 4:5.26.90-3 and the compilation made some more progress but still
fails:
https://people.debian.org/~coucouf/ukui-settings-daemon_3.1.1.1-1_amd64-2023-01-25T15:02:13Z.build
xrandr-manager.cpp: In member function ‘void XrandrManager::monitorsInit()’:
xrandr-manager.cpp:1200:50: error: ‘isPrimaryChanged’ is not a member of
‘KScreen::Output’
1200 | connect(output.data(), ::Output::isPrimaryChanged,
this, [this](){
| ^~~~
xrandr-manager.cpp:1292:47: error: ‘primaryOutputChanged’ is not a member of
‘KScreen::Config’
1292 | connect(mConfig.data(), ::Config::primaryOutputChanged,
| ^~~~
Bug#1029612: ukui-control-center: FTBFS: Unexpected libkscreen transition
With the help of Sune Vuorela I was able to patch some workarounds into libkscreen 4:5.26.90-3 and the compilation made some more progress but still fails: https://people.debian.org/~coucouf/ukui-control-center_3.0.5.1-1_amd64-2023-01-25T14:51:50Z.build widget.cpp: In member function ‘void Widget::setConfig(const KScreen::ConfigPtr&, bool)’: widget.cpp:222:47: error: ‘primaryOutputChanged’ is not a member of ‘KScreen::Config’ 222 | connect(mConfig.data(), ::Config::primaryOutputChanged, | ^~~~ widget.cpp: In member function ‘bool Widget::isBacklight()’: widget.cpp:767:18: warning: ‘void QProcess::start(const QString&, QIODevice::OpenMode)’ is deprecated: Use QProcess::start(const QString , const QStringList ,OpenMode mode = ReadWrite) instead [-Wdeprecated-declarations] 767 | process.start(cmd); | ~^ /usr/include/x86_64-linux-gnu/qt5/QtCore/qprocess.h:168:10: note: declared here 168 | void start(const QString , OpenMode mode = ReadWrite); | ^ mv -f libshortcut.so ../../libshortcut.so widget.cpp: In member function ‘void Widget::setActiveScreen(QString)’: widget.cpp:1221:21: warning: operation on ‘enableCount’ may be undefined [-Wsequence-point] 1221 | enableCount = (output->isEnabled() ? (++enableCount) : enableCount); | ^~~
Bug#1029656: Unexpected transition: libkscreen
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition X-Debbugs-Cc: libkscr...@packages.debian.org, pkg-kde-t...@alioth-lists.debian.net Control: affects -1 + src:libkscreen Dear Release Team, it has been raised to my attention that the libkscreen soname bump I recently asked to accept has caused issues with packages outside the Plasma package set… :-( This was obviously not intentional and our team members with whom I discussed the topic before uploading weren’t aware either. And the timing to discover this is particularly bad. Of course I should have checked more thoroughly myself, but here we are. So moving forward, the following packages are affected : - kylin-display-switch (kylin team) => rebuilds OK - lxqt-config (lxqt team) => FTBFS due to new libkscreen (#1029611) - ukui-control-center (kylin team) => FTBFS due to new libkscreen (#1029612) - ukui-settings-daemon (kylin team) => FTBFS due to new libkscreen (#1029613) 1. LXQt We’ve worked with the LXQt people and could fix #1029611 with workarounds in libkscreen 4:5.26.90-3. They will also have a new upstream release right away that would let us drop these workarounds. 2. Kylin I’ve not heard back from the Kylin maintainers yet. The same workarounds fixed an initial set of issues, but there are more code changes required to adapt to the new libkscreen API in order to fix #1029612 and #1029613. So again please accept my apologies and thanks in advance for your help. Ben file: title = "libkscreen"; is_affected = .depends ~ "libkf5screen7" | .depends ~ "libkf5screen8"; is_good = .depends ~ "libkf5screen8"; is_bad = .depends ~ "libkf5screen7"; -- Aurélien
Bug#1029612: ukui-control-center: FTBFS: Unexpected libkscreen transition
Source: ukui-control-center X-Debbugs-Cc: Debian Qt/KDE Maintainers Version: 3.0.5.1-1 Severity: serious Tags: ftbfs Dear Kylin packaging team, I has been raised to my attention that ukui-control-center depends on libkscreen, which I thought was used only by Plasma components. So it turns out I have started an unplanned transition with my recent upload of Plasma 5.26.90 (5.27 beta). I’ll discuss with the release team how to sort the issue in a separate bug report but in the meantime I’ve started rebuilding rdeps with the new libkscreen, and unfortunately ukui-control-center fail to build. You’ll find a amd64 sbuild log at [0]. I’d appreciate if you could investigate the matter quickly so we can find a fix. Please accept my apology for this, and we will handle future libkscreen and Plasma libs soname bumps as proper transitions obviously… [0] https://people.debian.org/~coucouf/ukui-control-center_3.0.5.1-1_amd64-2023-01-25T10:34:30Z.build Thanks for your help. -- Aurélien
Bug#1029613: ukui-settings-daemon FTBFS: Unexpected libkscreen transition
Source: ukui-settings-daemon X-Debbugs-Cc: Debian Qt/KDE Maintainers Version: 3.1.1.1-1 Severity: serious Tags: ftbfs Dear Kylin packaging team, I has been raised to my attention that ukui-settings-daemon depends on libkscreen, which I thought was used only by Plasma components. So it turns out I have started an unplanned transition with my recent upload of Plasma 5.26.90 (5.27 beta). I’ll discuss with the release team how to sort the issue in a separate bug report but in the meantime I’ve started rebuilding rdeps with the new libkscreen, and unfortunately ukui-settings-daemon fail to build. You’ll find a amd64 sbuild log at [0]. I’d appreciate if you could investigate the matter quickly so we can find a fix. Please accept my apology for this, and we will handle future libkscreen and Plasma libs soname bumps as proper transitions obviously… [0] https://people.debian.org/~coucouf/ukui-settings-daemon_3.1.1.1-1_amd64-2023-01-25T10:42:56Z.build Thanks for your help. -- Aurélien
Bug#1029611: lxqt-config: FTBFS: Unexpected libkscreen transition
Source: lxqt-config X-Debbugs-Cc: Debian Qt/KDE Maintainers Version: 1.2.0-1 Severity: serious Tags: ftbfs Dear LXQt packaging team, I has been raised to my attention that lxqt-config depends on libkscreen, which I thought was used only by Plasma components. So it turns out I have started an unplanned transition with my recent upload of Plasma 5.26.90 (5.27 beta). I’ll discuss with the release team how to sort the issue in a separate bug report but in the meantime I’ve started rebuilding rdeps with the new libkscreen and unfortunately lxqt-config fails to build. You’ll find a amd64 sbuild log at [0]. I’d appreciate if you could investigate the matter quickly so we can find a fix. Please accept my apology for this, and we will handle future libkscreen and Plasma libs soname bumps as proper transitions obviously… [0] https://people.debian.org/~coucouf/lxqt-config_1.2.0-1_amd64-2023-01-25T10:31:32Z.build Thanks for your help. -- Aurélien
Bug#1029532: ITP: plasma-welcome -- KDE Plasma welcome center
Package: wnpp Severity: wishlist Owner: Aurélien COUDERC X-Debbugs-Cc: debian-de...@lists.debian.org, debian-qt-...@lists.debian.org * Package name: plasma-welcome Version : 5.26.90 Upstream Contact: Plasma Developers * URL : https://invent.kde.org/plasma/plasma-welcome * License : GPL Programming Lang: QML, C++ Description : KDE Plasma welcome center Welcome Center is the perfect introduction to KDE Plasma. It can help you learn how to connect to the internet, install apps, customize the system, and more! This package will be maintained under the Debian Qt/KDE Maintain Team’s umbrella.
Bug#1029531: ITP: flatpak-kcm -- Flatpak permissions management KCM
Package: wnpp Severity: wishlist Owner: Aurélien COUDERC X-Debbugs-Cc: debian-de...@lists.debian.org, debian-qt-...@lists.debian.org * Package name: flatpak-kcm Version : 5.26.90 Upstream Contact: Plasma Developers * URL : https://invent.kde.org/plasma/flatpak-kcm * License : GPL Programming Lang: C++, QML Description : Flatpak permissions management KCM Plasma System Settings module for managinng Flatpak permissions. The System Settings module allows users to changing what permissions have been granted to installed Flatpak applications. This package will be maintained under the Debian Qt/KDE Maintainers Team’s umbrella.
Bug#1026307: Fixed in 4:22.12.1-1
control: fixed -1 4:22.12.1-1
Bug#1029171: RM: muon -- ROM; Abandoned upstream
Package: ftp.debian.org Severity: normal User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: m...@packages.debian.org, Debian Qt/KDE Maintainers Control: affects -1 + src:muon Dear FTP Masters, Muon, the KDE graphical frontend for apt-based distros has been abandoned upstream with no activity for some years and the source repository now being archived (= read-only) on their GitLab [0]. It’s been superseded by Plasma Discover, using packagekit as a backend, which is actively maintained. Also another project named muon has sprung up [1] as a reimplementation of the meson build system in pure C99, and the maintainer would like to reuse the /user/bin/muon path for bookworm+1 which makes sense for a command line tool. So I hereby request the removal of src:muon from unstable. [0] https://invent.kde.org/system/muon [1] https://sr.ht/~lattis/muon/ Thanks, -- Aurélien
Bug#1027937: gwenview: Under Bookworm, Gwenview no longer displays NEF images (RAW images)
control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=463132 Dear Cropper, Le 4 janvier 2023 22:28:53 GMT+01:00, Cropper a écrit : >Package: gwenview >Version: 4:22.12.0-1+b1 >Severity: important >X-Debbugs-Cc: crop...@acm.org Thank you for your bug report. This has been fixed upstream and will be part of version 22.12.2 planned to be released on Feb 2. Happy hacking, -- Aurélien
Bug#1028381: kwrite depends on kate, but shouldn't
control: severity -1 wishlist Le mardi 10 janvier 2023, 11:21:31 CET Hendrik Lehmbruch a écrit : > Package: kwrite > Version: 4:22.12.1-1 > Severity: normal > > Dear Maintainer, Dear Hendrik, > Is there a reason why kwrite depends on kate? Yes, if you look at the libraries required by the kwrite binary, you’ll see that it depends on libkateprivate provided by our kate package. $ ldd $(which kwrite) | grep kate libkateprivate.so.22.12.1 => /lib/x86_64-linux-gnu/libkateprivate.so.22.12.1 (0x7f3c279c2000) > While kate did not depends on > kwrite, both depends on ktexteditor-katepart, but ktexeditor-katepart did not > depend on both. > It should be possible to install kwrite without installing kate (or remove > kate > without removing kwrite), and if i understand this right -> https://kate- > editor.org/post/2022/2022-03-31-kate-ate-kwrite/ <- it should work. It would be possible to make it work the way you want by splitting the kate package and shipping libkateprivate as a separate binary package. It’s too late for the next bookworm release to do so, the library transition freeze is around the corner (tomorrow). You can try and ping the bug report after the bookworm release if that’s important to you. I personally don’t have a strong incentive working on this but if you or someone else feels like doing the split, patches are welcome. Happy hacking ! -- Aurélien
Bug#1027177: ITP: activity-aware-firefox -- wrapper to make Firefox aware of Plasma Desktop activities
Package: wnpp Severity: wishlist Owner: Aurélien COUDERC X-Debbugs-Cc: debian-de...@lists.debian.org, Debian KDE Extras Team * Package name: activity-aware-firefox Version : 0.4.1 Upstream Contact: Matija Šuklje * URL : https://gitlab.com/hook/activity-aware-firefox * License : CC0-1.0 Programming Lang: Bash Description : wrapper to make Firefox aware of Plasma Desktop activities Using activity-aware-firefox you can have Firefox windows in each Plasma Activity bound to that Activity. What activity-aware-firefox does is to create a Firefox Profile the first time it is run in an Activity, using its unique ID. Then every next time you run activity-aware-firefox in that Plasma Activity, it will start the Firefox Profile associated with it. The package will be maintained under the Debian KDE Extras Team’s umbrella.
Bug#1027036: O: libiodbc2 -- iODBC Driver Manager
Package: wnpp Severity: normal X-Debbugs-Cc: libiod...@packages.debian.org, Debian Qt/KDE Maintainers Control: affects -1 + src:libiodbc2 I intend to orphan the libiodbc2 package. The package used to be required by the KDE stack but it’s not the case anymore since a couple of releases and so the Qt/KDE Team hasn’t been updating it. The project is not dead upstream and has seen several new releases since the last upstream version we packaged in 2014. The package description is: The iODBC (intrinsic Open Database Connectivity) driver manager is compatible with the ODBC 2.x and 3.x specification and performs all the jobs of a ODBC driver manager (i.e. driver loading, parameters and function sequence checking, driver's function invoking, etc). Any ODBC driver working with ODBC 2.0 and 3.x driver manager will also work with iODBC driver manager and vice versa. . Applications (using ODBC function calls) linked with iODBC driver manager will be able to simultaneously access different types of data sources within one process through suitable iODBC drivers. . This package contains the library files. Look for the iodbc package, too!
Bug#1026465: filelight: defective after upgrade to 20.12.0-1
Dear olaf, Le 20 décembre 2022 17:52:16 GMT+01:00, olaf a écrit : >Package: filelight >Version: 4:22.12.0-2 >Severity: normal > >Dear Maintainer, > >after upgrading to the current version filelight works only rudimentary, that >is, mouse clicks with the left mouse button to navigate are no longer accepted >and the call of the context menu with the right mouse button is no longer >there. > >To be on the safe side, I deleted all filelight files from all directories and >user directories and reinstalled filelight. > >The version filelight_20.12.0-1_amd64.deb still works fine. That'd really very peculiar. Both versions are supposed to be exactly the same besides an error in the Debian changelog in my 20.12.0-1 upload. Would you mind retesting back and forth between 20.12.0-1 and 20.12.0-2 and report back ? Thank you, -- Aurélien
Bug#1021364: RFS: ghostwriter/2.2.0-1 [RC] -- Distraction-free, themeable Markdown editor
Le mercredi 12 octobre 2022, 11:41:50 CET Sebastien Chavaux a écrit :
> Absolutely, I'm so in my head that I don't see what is the simplest...
Dear Sebastien,
as Ghostwriter has been onboarded as a KDE Project, I’d like to offer to
integrate the package into the perimeter of the Qt/KDE Packaging Team.
We have an « extras » group [0] for packages that are related to KDE but not
part of the main KDE Frameworks / Plasma / Gear releases that I think would be
suitable.
How we would do this is :
- give me (couc...@debian.org) or one of the team members owner access to your
packaging repo so we can move it to the qt-kde-team/extras group
- change the Maintainer field to : Debian KDE Extras Team
- put yourself in the Uploaders field
What you would get :
- you keep your usual access to the repo and can work on the package as you
used to
- team members and myself would be considered welcome to contribute to that
repository too
- it would gives additional scrutiny to the package that would show on our DDPO
dashboard
- you’re welcome to help on other packages of the team :)
Whether you’re interested or not, you’re welcome to hang out on the
#debian-qt-kde on Debian’s IRC for help and feedback or upload sponsorship.
To follow up on the RFS discussion:
- MathJax3 is currently not packaged so it’s fine to keep it vendored
(3rdparty) for now. We can migrate to the Debian package once it’s available.
- The source-is-missing lintian tags are false positives to me (if lintian
still really emits them, I haven’t checked). The folders
3rdparty/{MathJax,react} contain valid, human modifiable source files. Please
add a comment in the lintian-overrides file to explain so.
- You should use the Files-Excluded directive in debian/copyright [1] to
describe which files should be removed from the upstream source. That should be
the debian/ folder + 3rd party libraries already available in Debian.
- I would prefer the +ds suffix instead of +dfsg, +dfsg is more appropriate for
cases where we remove upstream sources due to licensing concerns which is not
the case here IIUC.
- uscan --download-current-version fails, it should work from a clean clone of
the repo (the uupdate is not required unless I’m missing something), and…
- it would be preferable for debian/watch to target the invent.kde.org repo
which is now the reference repo, you have examples for GitLab tags here [2].
- In the git packaging repo you have the « source » folder next to the « debian
» folder, it should be *inside* it.
- source/options can be removed.
- Remove debian/compat and replace the debhelper (>= 11) build dependency by a
debhelper-compat (= 13) build dep.
- Remove debian/git-build-recipe.manifest ? I don’t know what it’s for so it’s
probably not useful. :)
Feel free to ping me or the team on IRC about any of the above.
[0] https://salsa.debian.org/qt-kde-team/extras
[1] https://wiki.debian.org/UscanEnhancements
[2] https://wiki.debian.org/debian/watch#Gitlab
Thanks for your response & cheers,
--
Aurélien, on behalf of the Qt/KDE Packaging Team
Bug#1026446: Static javascript resources for Policy and DevRef give 404 errors, breaking search
Package: www.debian.org Severity: normal Dear Web Team, the policy and developer reference pages have links to some static js files used at least for the search functionality, but the URL for these resources all give 404 errors. This can be seen in the network tab of a browser’s developers tool when browsing to the policy [0] or devref [1] homepages. The consequence is that search is broken. Example of js loaded from the policy homepage and giving 404 : - jquery.js [2] [0] https://www.debian.org/doc/debian-policy/index.html [1] https://www.debian.org/doc/manuals/developers-reference/index.en.html [2] https://www.debian.org/doc/debian-policy/_static/jquery.js Thanks, -- Aurélien
Bug#1026307: Kwrite no longer remembers what files it had open before logging out of KDE or rebooting the PC
control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=463139
Bug#1022149: Link to upstream bug
control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=460701
Bug#1025943: dolphin: copy/move files: only the first item is copied to the clipboard
Le lundi 12 décembre 2022 12:01:16 CET, vous avez écrit : > Control: severity -1 serious > > Le lundi 12 décembre 2022, 11:45:56 CET antonio a écrit : > > Dear Maintainer, > > Dear Antonio, > > > there is a kde bug that makes it problematic to copy/move files, see link > > https://bugs.kde.org/show_bug.cgi?id=462928 > > > > I went back to the previous version 4:22.08.1-1 > > thank you for your bug report. > > I’m keeping 22.12.0 in unstable, but raising the severity of this bug report > so the new version doesn’t migrate to testing. FYI I just uploaded 4:22.12.0-2 including the upstream-revert of the commit that broke this. Happy hacking, -- Aurélien
Bug#1026070: kde-plasma-desktop: Right click on desktop and taskbar has no effect
control: tags -1 + moreinfo Dear Max, Le 14 décembre 2022 10:09:44 GMT+01:00, "Max Görner" a écrit : >Package: kde-plasma-desktop >Version: 5:135 >Severity: important > >Dear Maintainer, > > >about the same time as bug #1022972 appeard, after an update about one >and half months ago, right clicks stopped to have an effect in certain >situations. > >Previously, when doing an right click on the desktop, a context menu >opened. One of the elements of that context menu was an element that >opened an appearance settings menu which allowed me to configure the >background image. This context menu does not appear anymore. > >Also, a right click on the taskbar, which holds Kickoff, the icons of >open windows, the clock and the tray bar, has no effect neither. Thus I >am able neither to change its position nor to add or remove any widgets. > >I experience the very same problem on two machines that run Debian >Bookworm. I do not experience it on a machine that runs Ubuntu 22.04, if >that is of any help. thank you for your bug report. There are many people running testing and/or unstable, me included, for whom this bug doesn't happen. So we'll need a bit more analysis if we want to get it fixed. Could you try creating a new user (without an existing $HOME directory) on one of the machines where you see the bug and report back if the new user still has the issue ? Also can you find anything meaningful in the system log at the time where you right click or during the load of the user session ? Lastly if you could have a look at the upstream bugs.kde.org platform and look for a similar bug report that would be useful. I'll have a look too when I can. Happy hacking ! -- Aurélien
Bug#1025947: kdegraphics-thumbnailers: missing Breaks+Replaces: kdegraphics-mobipocket (<< 4:22.12.0)
Dear Andreas, Le lundi 12 décembre 2022, 12:54:36 CET Andreas Beckmann a écrit : > Package: kdegraphics-thumbnailers > Version: 4:22.12.0-1 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > > Hi, > > during a test with piuparts I noticed your package fails to upgrade from > 'testing'. > It installed fine in 'testing', then the upgrade to 'sid' fails > because it tries to overwrite other packages files without declaring a > Breaks+Replaces relation. […] > The existing > Breaks+Replaces: kdegraphics-mobipocket (<< 4:21.12.3) > are insufficiently versioned. thank you for your bug report, I’ve uploaded the fix. Happy hacking, -- Aurélien
Bug#1025943: dolphin: copy/move files: only the first item is copied to the clipboard
Control: severity -1 serious Le lundi 12 décembre 2022, 11:45:56 CET antonio a écrit : > Dear Maintainer, Dear Antonio, > there is a kde bug that makes it problematic to copy/move files, see link > https://bugs.kde.org/show_bug.cgi?id=462928 > > I went back to the previous version 4:22.08.1-1 thank you for your bug report. I’m keeping 22.12.0 in unstable, but raising the severity of this bug report so the new version doesn’t migrate to testing. Happy hacking, -- Aurélien
Bug#1025943: dolphin: copy/move files: only the first item is copied to the clipboard
Control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=462928
Bug#1025878: libkeduvocdocument-data: missing Breaks+Replaces: libkeduvocdocument5 (<< 4:22.11.90-2)
Le dimanche 11 décembre 2022, 04:41:25 CET Andreas Beckmann a écrit : > There are already > Breaks+Replaces: libkeduvocdocument5 (<< 4:21.12.3) > but that versioning is insufficient to catch all package versions > predating the package split. Ah yes, thank you Andreas. Fix uploaded. Happy hacking, -- Aurélien
Bug#1025832: transition: libkeduvocdocument
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition X-Debbugs-Cc: libkeduvocdocum...@packages.debian.org, Debian Qt/KDE Maintainers Control: affects -1 + src:libkeduvocdocument Dear Release Team, I’d like to request a transition slot for libkeduvocdocument. It has 4 reverse dependencies: - kanagram - khangman - kwordquiz - parley All 4 rebuild successfully with the new version of the library. I’ve uploaded libktorrent 4:22.11.90-2 with the new ABI to experimental and it builds successfully on all release architectures. [0] Ben file: title = "libkeduvocdocument"; is_affected = .depends ~ "libkeduvocdocument5" | .depends ~ "libkeduvocdocument5abi1"; is_good = .depends ~ "libkeduvocdocument5abi1"; is_bad = .depends ~ "libkeduvocdocument5"; [0] https://buildd.debian.org/status/package.php?p=libkeduvocdocument=experimental
Bug#1025715: Qt/KDE Team release plans for bookworm
Package: release.debian.org Severity: normal X-Debbugs-Cc: Debian Qt/KDE Maintainers Dear Release Team, with the freeze approaching the Qt/KDE Team has put up a document [0] to share our release goals for the Qt and KDE stack for bookworm. We’d like to encourage you to have a look at it. As a quick summary, we target the following versions for bookworm : - Qt 5 : 5.15.7 - Qt 6 : 6.4.2 - KDE Frameworks (libs) : 5.101 - Plasma (desktop) : 5.27.2 - KDE Gear (apps) 22.12.2 These targets should be mostly uneventful for all but Plasma. For Plasma, version 5.27.0 will be released on Feb 14. so 2 days after the beginning of the soft freeze. What I would like to do is upload the 5.27 beta to unstable when it’s released on Jan 19. and then consider the official 5.27.0 as a « small update » on top of 5.27 beta that would be suitable for upload during the soft freeze period. It’s usually the case that between beta and .0 releases of Plasma the changes are fixes targetted at bugs raised during the beta period. So I think it’s not too far fetched of an interpretation. It’s particularly important that we get Plasma 5.27 into bookworm because this will be the last upstream release based on Qt 5 and we expect it to receive important fixes for a long time, unlike our current 5.26.x which is more of an interim release and won’t get upstream fixes after the last 5.26.5 point release on Jan 3. Feedback welcome. [0] https://wiki.debian.org/PkgQtKde/BookwormReleasePlans Cheers, -- Aurélien for the Qt/KDE Team
Bug#1025277: ITP: ksanecore -- library providing logic to interface scanners
Package: wnpp Severity: wishlist Owner: Aurélien COUDERC X-Debbugs-Cc: debian-de...@lists.debian.org, Debian Qt/KDE Maintainers * Package name: ksanecore Version : 22.11.90 Upstream Author : Kåre Särs * URL : https://invent.kde.org/libraries/ksanecore * License : LGPL Programming Lang: C++ Description : library providing logic to interface scanners KSaneCore is a library that provides a Qt interface for the SANE library for scanner hardware. This package will be maintained under the Debian Qt/KDE Maintainers Team’s umbrella.
Bug#1024417: kgpg FTBFS: Did not find GPGME
Le 26 novembre 2022 06:48:56 GMT+01:00, Andreas Metzler a écrit : >On 2022-11-25 Aurélien COUDERC wrote: >[...] >> I tried applying the patch on top of upstream 22.08.3 and the build still >> fails. [0] > >> Ideas welcome, I won't have the time to analyse the issue any further. > >Good morning, > >adding pkg-config to Build-Depends works for me. Obviously… Thank you.
Bug#1024417: kgpg FTBFS: Did not find GPGME
Le 25 novembre 2022 18:36:49 GMT+01:00, Andreas Metzler a écrit : >On 2022-11-23 Daniel Kahn Gillmor wrote: >> On Wed 2022-11-23 16:27:43 +0100, Andreas Metzler wrote: >>> Unless kgpg maintainers/upstream has a strong opinion against using >>> pkg-config the obvious choice would be to drop cmake/FindGpgme.cmake >>> and simply use FindPkgConfig. - Attached patch seems to work for me, >>> i.e. build including dh_auto_test works. > >> Thanks for this, Andreas. > >> I've proposed this change upstream as well at >> https://invent.kde.org/utilities/kgpg/-/merge_requests/18 > >Great, with a little bit of luck we should be able to work out a fix >that is acceptable for all/most cmake-cases. I tried applying the patch on top of upstream 22.08.3 and the build still fails. [0] Ideas welcome, I won't have the time to analyse the issue any further. [0] https://salsa.debian.org/qt-kde-team/kde/kgpg/-/jobs/3571722 Haply hacking, -- Aurélien
Bug#1024756: transition: libktorrent
Hi Sebastian, Le 24 novembre 2022 21:23:47 GMT+01:00, Sebastian Ramacher a écrit : >Control: tags -1 confirmed >On 2022-11-24 11:05:08 +0100, Aurélien COUDERC wrote: >> Package: release.debian.org >> Severity: normal >> User: release.debian@packages.debian.org >> Usertags: transition >> X-Debbugs-Cc: Debian Qt/KDE Maintainers >> >> Dear Release Team, >> >> I’d like to request a transition slot for libktorrent. >> >> It has 2 reverse dependencies: >> - kget >> - ktorrent >Please go ahead. libktorrent is uploaded to unstable and built on all relevant archs. Could you please binNMU kget and ktorrent ? Thanks, -- Aurélien
Bug#1024756: transition: libktorrent
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition X-Debbugs-Cc: Debian Qt/KDE Maintainers Dear Release Team, I’d like to request a transition slot for libktorrent. It has 2 reverse dependencies: - kget - ktorrent Both rebuild successfully with the new version of the library. I’ve uploaded libktorrent 22.08.3-3 with the new ABI to experimental and it builds successfully on the same architectures as previously. [0] Ben file: title = "libktorrent"; is_affected = .depends ~ "libkf5torrent6abi2" | .depends ~ "libkf5torrent6abi3"; is_good = .depends ~ "libkf5torrent6abi3"; is_bad = .depends ~ "libkf5torrent6abi2"; [0] https://buildd.debian.org/status/package.php?p=libktorrent=experimental Thanks, -- Aurélien
Bug#1024716: ITP: kio-admin -- manage files as administrator using the admin:// KIO protocol
Package: wnpp Severity: wishlist Owner: Aurélien COUDERC X-Debbugs-Cc: debian-de...@lists.debian.org, Debian Qt/KDE Maintainers * Package name: kio-admin Version : 1.0.0 Upstream Author : Harald Sitter * URL : https://invent.kde.org/system/kio-admin * License : GPL Programming Lang: C++ Description : manage files as administrator using the admin:// KIO protocol kio-admin implements a new protocol admin:// which gives administrative access to the entire system. This is achieved by talking, over dbus, with a root-level helper binary that in turn uses existing KIO infrastructure to run file:// operations in root-scope. Or simply put: admin:// is exactly like file:// but redirected over dbus to gain administrative privileges. This package will be maintained under the Debian Qt/KDE Team’s umbrella.
Bug#1008694: Recent upstream activity
There was recent upstream activity on the topic. Bug : https://bugs.kde.org/show_bug.cgi?id=438206 Merge Request : https://invent.kde.org/kdevelop/kdev-python/-/merge_requests/16 Hopefully we can get kdevelop-python back for version 22.12 and into bookworm. -- Aurélien
Bug#1023024: Session crashes when switching back to first display from a second one connected with HDMI when Wayland is used with KDE
control: tags -1 + wontfix Dear mYnDstrEAm, Le 29 octobre 2022 12:29:23 GMT+02:00, mYnDstrEAm a écrit : >Package: plasma-workspace >Version: 5.20.5-6 > >First of all I don't know which package is causing this but it has to do with >Wayland and KDE. Wayland on Debian 11 is provided as a technology preview and is not supported. You should either upgrade to Debian testing if you need to run Wayland, or stay on X11 if you need to run Debian stable. Happy hacking, -- Aurélien
Bug#1021938: reassign Bug#1021938: libical bug
control: reassign -1 libical3 3.0.15-1 control: fixed -1 libical3/3.0.16-1
Bug#1018909: Forwarded upstream
control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=458069
Bug#1021904: Forwarded upstream
control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=460089 .
Bug#1017136: ksirk: diff for NMU version 4:21.08.0-1.1
Dear Reiner, Le 15 octobre 2022 18:27:35 GMT+02:00, Reiner Herrmann a écrit : >Control: tags 1017136 + patch >Control: tags 1017136 + pending > >Dear maintainer, > >I've prepared an NMU for ksirk (versioned as 4:21.08.0-1.1) and >uploaded it to DELAYED/2. Please feel free to tell me if I >should delay it longer. thanks for that, appreciated. Would you go as far as posting the change as an MR against the salsa repo ? https://salsa.debian.org/qt-kde-team/kde/ksirk Also if you're interested in KDE apps/gear in general, help is welcome on their maintenance. Happy hacking, -- Aurélien
Bug#1021573: ITP: kpipewire -- KDE's Pipewire library
Package: wnpp Severity: wishlist Owner: Aurélien COUDERC X-Debbugs-Cc: debian-de...@lists.debian.org, Debian Qt/KDE Maintainers * Package name: kpipewire Version : 5.26.0 Upstream Author : plasma-de...@kde.org * URL : https://invent.kde.org/plasma/kpipewire * License : LGPL Programming Lang: C++ Description : KDE's Pipewire library This library provides components for rendering and recording PipeWire streams using Qt. It will be maintained uder the Debian Qt/KDE Maintainers Team’s umbrella.
Bug#1019446: kde-config-cron: Binary missing
Hi, Le samedi 24 septembre 2022, 10:31:26 CEST c.bu...@posteo.jp a écrit : > Dear Bernhard, > > thanks for the reply. > > On 2022-09-24 10:09 Bernhard Übelacker wrote: > > I guess the kcm_cron.so is really just like a module > > loaded by systemsettings5. > > "systemsettings" and "systemsettings5" does not exist on my system and > not in the repos (via "apt-cache search"). That’s incorrect : $ apt-file search bin/systemsettings systemsettings: /usr/bin/systemsettings systemsettings: /usr/bin/systemsettings5 > It seems to me that the package "kde-config-cron" has some missing > dependencies. Yes indeed, it’s missing a dependency on the systemsettings package, I’ll add it in the next upload. Happy hacking, -- Aurélien
Bug#1017825: no metadata in dolphin information panel
Le vendredi 9 septembre 2022, 14:34:26 CEST r087...@yahoo.it a écrit : > On 05/09/22 22:53, Aurélien COUDERC wrote: > > sadly I have no other idea. I’ve just uploaded 22.08.1 to unstable. I’m not holding my breath but you can still give it a try. :-) Happy hacking, -- Aurélien
Bug#1019475: Connecting a HDMI to an external display ends the KDE session and can cause plasmashell to crash and a new "Dynamic user" to get added
control: -1 tags + wontfix Le 10 septembre 2022 10:04:14 GMT+02:00, mYnDstrEAm a écrit : >Package: plasma-workspace >Version: 5.20.5-6 > >Running Debian11 with KDE with Wayland. > >This happens when connecting a second HDMI to the display no matter if that >monitor is switched on or off when doing so. Dear mYnDstrEAm, thanks for taking the time to report this bug. Plasma on Wayland is really only provided as a technology preview on Debian 11 and has many known bugs including stability issues, so I'm marking this bug as « wontfix ». If you really need Wayland you should upgrade to Debian testing, and if you really need Debian stable you should stick to the Plasma X11 session. Happy hacking ! -- Aurélien
Bug#1017825: no metadata in dolphin information panel
Le dimanche 4 septembre 2022, 12:01:11 CEST r087...@yahoo.it a écrit : > Otherwise, which config file should I delete in order to reset dophin to > a pristine state? I can find the following dot files and folders having "dolphin" in their name in my $HOME. (that’s the result of : 'find . -iname "*dolphin*"' with some excludes). You may want to backup / remove these and try again : ./.cache/dolphin ./.config/session/dolphin_x <- a bunch of these with different x ./.config/session/dolphin_dolphin_dolphin ./.config/kde.org/UserFeedback.org.kde.dolphin.conf ./.config/dolphinrc ./.local/share/kxmlgui5/dolphin/dolphinui.rc ./.local/share/dolphin/dolphinstaterc I’ve also tried to disable indexing and I still do get the extended metadata displayed in Dolphin so that would confirm it’s unrelated. Happy hacking, -- Aurélien
Bug#1017825: no metadata in dolphin information panel
control: tags -1 + moreinfo Hi, Le 21 août 2022 10:52:55 GMT+02:00, r087...@yahoo.it a écrit : >Package: dolphin >Version: 22.04.3 > >When I select, e.g., an image in dolphin, the information panel shows only: >file size, file type, creation/modification/access times. No metadata >information such as image size or exif data is reported. See also: >https://bugs.kde.org/show_bug.cgi?id=457903 I cannot reproduce this. The image size and EXIF metadata are correctly shown here. Can you try providing more information ? Did you install your system / KDE software in a particular way ? (without apt recommends, … ?) Can you find dolphin logs in .xsession-errors / wayland-session.logs that could tell us more ? Thanks, -- Aurélien
Bug#1017580: plasma-desktop: dpkg error when upgrading plasma-desktop and plasma-workspace-data from Debian Bullseye to Bookworm
Dear Julian, Le 18 août 2022 00:53:32 GMT+02:00, "Julian Groß" a écrit : >Package: plasma-desktop >Version: 4:5.25.4-1 >Severity: normal > >Dear Maintainer, > >trying to dist-upgrade fresh Debian Bullseye with KDE to Debian Bookworm fails >with a: >``` >Unpacking plasma-workspace-data (4:5.25.4-2) over (4:5.20.5-6) ... >dpkg: error processing archive >/tmp/apt-dpkg-install-tgSUlx/82-plasma-workspace-data_4%3a5.25.4-2_all.deb >(--unpack): > trying to overwrite '/usr/share/qlogging-categories5/kcmusers.categories', > which is also in package plasma-desktop 4:5.20.5-4 >``` >Please redirect me if this is the wrong place for reporting this issue. Yes this is the correct place, thank you for your bug report. Indeed there's a Breaks/Replace relation missing to ensure the upgrade succeeds. I'll address that in the next upload. Cheers, -- Aurélien
Bug#1017611: discover: Discover stucks because fwupd is not installed
control: reassign -1 plasma-discover control: tags -1 + moreinfo Dear Mando, I guess you're talking about Discover the software management tool for KDE/Plasma, not the hardware discovery tool, so I'm reassigning the bug to the plasma-discover package. Le 18 août 2022 13:39:30 GMT+02:00, mando a écrit : >Package: discover >Version: 2.1.2-10 >Severity: normal > >Dear Maintainer, > >I tried to update my Debian through Discover. >I've enabled the contrib and non-free repository as I require some firmware >and non-free drivers (wifi, video cards) for a long time. >Since recent updates of KDE, Discover stucks when updating the package list >and complains because fwupd is not installed. >Installing fwupd solves the problem: > > apt install fwupd-amd64-signed > >... but I guess that Discover should work even if this package is not >installed. Yes it definitely should work without it. Could you try and remove fwupd again but also ensure plasma-discover-backend-fwup is not installed ? Having a look at the dependency/recommends chain it looks possible to have the later installed without the former and maybe that could explain your issue. Thanks ! -- Aurélien
Bug#910782: Fixed in the yet-to-be-released 5.97 upstream version
https://invent.kde.org/frameworks/kwallet/-/ merge_requests/11[1] [1] https://invent.kde.org/frameworks/kwallet/-/ merge_requests/11
Bug#1012422: plasma-systemmonitor: plasma system monitor doesn't start anymore
Le 06/06/2022 à 21:44, Adrian Ban a écrit :> Dear Maintainer, Dear Adrian, After upgrading the plasma-systemmonitor to version 5.24.5-1 and then to 5.24.90-2, I can't start it anymore. straces shows that is exists with 0. Thank you for your bug report. Indeed I need to tighten some dependencies to try and avoid this kind of situations, but from your bug report : ii ksystemstats 5.24.5-1 you’re using an older version of ksystemstats, which is not supported. Upgrading it (and other Plasma packages) to 5.24.90 should fix your issue. Generally speaking upstream doesn’t support mixed versions of Plasma components. So if you’re going the experimental / 5.25 beta route then you should upgrade *all* Plasma packages to 5.25 beta = 5.24.90 together. Otherwise you will experience strange bugs that will be specific to your partial upgrade and won’t be of any interest to upstream. Happy hacking ! -- Aurélien
Bug#1012248: kate: Adds an empty line after saving a file
control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=401475 control: tags -1 + wontfix Dear Nicolas, that’s the intended upstream behaviour. There’s a config option to change that behaviour if you don’t like it in Settings -> Configure Editor... -> Open/Save -> General -> Automatic Cleanups on Save. See the linked upstream bug report if you want more background. Happy hacking ! -- Aurélien Le 02/06/2022 à 10:18, Nicolas Patrois a écrit : Package: kate Version: 4:21.12.3-1 Severity: minor Tags: upstream Dear Maintainer, When I save a file, if the file does not end with an empty line, kate adds an empty line in its end. It’s not a problem for a Python script but it is for a data file. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 5.16.0-6-686-pae (SMP w/3 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR:fr:en_GB:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages kate depends on: ii kate5-data 4:21.12.3-1 ii kio 5.94.0-1 ii ktexteditor-katepart 5.94.0-2 ii libc62.33-7 ii libkf5bookmarks5 5.94.0-1 ii libkf5completion55.94.0-1 ii libkf5configcore55.94.0-3 ii libkf5configgui5 5.94.0-3 ii libkf5configwidgets5 5.94.0-1 ii libkf5coreaddons55.94.0-1 ii libkf5crash5 5.94.0-1 ii libkf5dbusaddons55.94.0-1 ii libkf5guiaddons5 5.94.0-1 ii libkf5i18n5 5.94.0-1 ii libkf5iconthemes55.94.0-1 ii libkf5kiocore5 5.94.0-1 ii libkf5kiofilewidgets55.94.0-1 ii libkf5kiogui55.94.0-1 ii libkf5kiowidgets55.94.0-1 ii libkf5newstuff5 5.94.0-2 ii libkf5parts5 5.94.0-1 ii libkf5plasma55.94.0-1 ii libkf5service-bin5.94.0-1 ii libkf5service5 5.94.0-1 ii libkf5syntaxhighlighting55.94.0-1 ii libkf5texteditor55.94.0-2 ii libkf5textwidgets5 5.94.0-1 ii libkf5wallet-bin 5.94.0-1 ii libkf5wallet55.94.0-1 ii libkf5widgetsaddons5 5.94.0-2 ii libkf5windowsystem5 5.94.0-1 ii libkf5xmlgui55.94.0-1 ii libkuserfeedbackcore11.2.0-2 ii libkuserfeedbackwidgets1 1.2.0-2 ii libqt5concurrent55.15.2+dfsg-16+b2 ii libqt5core5a 5.15.2+dfsg-16+b2 ii libqt5dbus5 5.15.2+dfsg-16+b2 ii libqt5gui5 5.15.2+dfsg-16+b2 ii libqt5network5 5.15.2+dfsg-16+b2 ii libqt5sql5 5.15.2+dfsg-16+b2 ii libqt5widgets5 5.15.2+dfsg-16+b2 ii libqt5xml5 5.15.2+dfsg-16+b2 ii libstdc++6 12.1.0-2 ii plasma-framework 5.94.0-1 ii qml-module-org-kde-kquickcontrolsaddons 5.94.0-1 ii qml-module-qtquick-layouts 5.15.2+dfsg-10 ii qml-module-qtquick2 5.15.2+dfsg-10 Versions of packages kate recommends: ii sonnet-plugins 5.94.0-1 Versions of packages kate suggests: pn darcs ii exuberant-ctags 1:5.9~svn20110310-16 ii git 1:2.36.1-1 ii khelpcenter 4:21.12.3-1 ii konsole-kpart4:21.12.3-1 ii mercurial6.1.2-1 ii subversion 1.14.2-1 -- no debconf information
