Re: Re: QT target version for trixie

I appreciate the advice to target Qt 6 when possible. I'd like to switch Digikam from Qt5 to Qt6. Is there a guide to replacing package names? For example, Digikam builds with qtbase5-dev. I can't find qtbase6-dev in the archive. Am I overlooking something? Thanks, -Steve signature.asc

Re: akonadi database creating 300MB+ log message per day

On Saturday, July 1, 2023 1:17:56 P.M. CDT Steven Robbins wrote: > I'm seeing odd behaviour but not sure where the fault lies -- it is perhaps > some configuration issue on my part -- so asking here before filing a bug. > > The file ~/.local/share/akonadi/db_data/mysql.err is b

akonadi database creating 300MB+ log message per day

I'm seeing odd behaviour but not sure where the fault lies -- it is perhaps some configuration issue on my part -- so asking here before filing a bug. The file ~/.local/share/akonadi/db_data/mysql.err is being spammed by error logs many times per minute: 2023-07-01 13:06:27 256 [ERROR]

Bug#1031953: libkf5screen8: Second monitor issues with NVIDIA

On Saturday, February 25, 2023 3:57:45 P.M. CST you wrote: > Please don’t. I plan to upload the whole of Plasma 5.27.2 targeting > bookworm. Awesome, thanks! > 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

Re: qtav: FTBFS with ffmpeg 5.0

Heads up for those following this bug: qtav appears to be unmaintained upstream. My only interest in the package was to enable video playback in digikam. Digikam upstream has taken most of the qtav code, incorporated into digikam source tree and fixed it up. The next release of digikam

kdevelop cannot run lldb-mi

Hello, I'm trying to debug within KDevelop. When I select to debug a binary, KDevelop shows a big error message "Could not start debugger. Could not run 'lldb-mi'. Make sure that the path name is specified correctly". I can manually configure to use GDB instead of LLDB. But supposing I

qtpaths -- is it expected to work?

Hi, I'm maintaining digikam for Debian and -- due to ffmpeg issues -- trying to help out with upstream development. The digikam setup script uses the commands: QT_INSTALL_PREFIX=`qtpaths --install-prefix` QT_PLUGIN_INSTALL_DIR=`qtpaths --plugin-dir` Currently both fail (on

Handling symbols file

Hi, I've uploaded exiv2 to experimental and many builds failed due to changed symbols. Is this the up-to-date explanation for symbols files: https://qt-kde-team.pages.debian.net/symbolfiles.html ? I don't see explicit details on what to do with all the architecture-specific diff files.