Package: kwayland-integration
Version: 5.13.4-1
Severity: normal
Dear Maintainer,
kwayland-integration depends on qtwayland5. This package depends on both Qt's
client and compositor API. It absolutely makes no sense that a Wayland *client*
integration plugin depends on a compositor API. In fact
Package: qtwayland5
Version: 5.11.2-3
Severity: normal
Dear Maintainer,
QtWayland consists of a client part (providing the qpa platform plugin) and a
compositor part (providing an API to implement a Wayland server).
In Debian it's not possible to just install the client part. Thus the Plasma
se
Package: kwin-wayland
Version: 4:5.13.5-1+b1
Severity: normal
Dear Maintainer,
kwin-wayland incorrectly depends on kwayland-integration. KWin neither at build
nor at run time uses anyting from kwayland-integration.
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT po
Package: kwin
Severity: normal
Dear Maintainer,
upstream maintainer speaking here!
I installed Debian/testing on a new system this week and noticed that KWin
defaulted to Plastik decoration. This only happens if KWin got compiled without
the Breeze dependency.
Please rebuild KWin with Breeze de
Package: kwin-wayland
Severity: normal
Dear Maintainer,
upstream maintainer speaking here!
In Debian testing kwin-wayland depends on qtwayaland5, but the upstream version
does not
have any dependency on qtwayland at all. Neither at compile nor at runtime.
I suggest to remove this needless depe
Source: kwin
Severity: important
Dear Maintainer,
I got reports that KWin defaults to Plastik window decoration in Testing.
This means that KWin was built without the optional breeze dependency.
It is important to build kwin with the breeze dependency as otherwise the
default Plasma installation
> The permissions set by cmake are later tweaked in the package build process.
> I don't see any "gain" gaining the nogroup group as suggests the previous
> snippet. Is this to be able to write to global directory? If so, we would
> need to create a specific group.
I don't know why the nogroup is
Package: kde-cli-tools
Version: 4:5.4.3-1
Severity: normal
Dear Maintainer,
kdesu which is provided by kde-cli-tools needs to interact with kdesud,
which is provided by libkf5su-bin. But there is no direct dependency from
kde-cli-tools to said package defined. There is only a recommends from
libk
Package: libkf5su-bin
Version: 5.16.0-1
Severity: important
Dear Maintainer,
I noticed that the file
/usr/lib/x86_64-linux-gnu/libexec/kf5/kdesud
is group owned by "root" and not group suid.
Given the CMake snippet from the source package:
install(TARGETS kdesud DESTINATION ${KDE_INSTALL_LIBEXE
On Tuesday, August 18, 2015 07:45:09 PM you wrote:
> The patch here puts the plugins in the -dev package which is definitely
> wrong. IIRC upstream (mgraesslin) had an opinion on how the plugins should
> be shipped. CC'ing him for his input.
In the case of KWindowSystem there is only the option to
Package: libxkbcommon0
Version: 0.4.0-1
Severity: wishlist
Dear Maintainer,
please update the package to the latest upstream release. This is needed to
build Qt 5.3 which requires 0.4.1, the currently provided 0.4.0 is not
sufficient to build Qt 5.3.
-- System Information:
Debian Release: jess
Package: kde-window-manager
Version: 4:4.8.4-6
Severity: normal
The README.Debian is written against 4.0. The information is in all aspects not
relevant any more, for example it says that compositing support is still
immature and disabled by default. The instructions on how to enable do not
reflec
Package: kde-window-manager
Version: 4:4.8.4-3
Severity: normal
Dear Maintainer,
the source package of kde-workspace has an incorrect build conflict against
libgles2-mesa-dev.
kde-workspace and especially KWin build just fine with this package around and
in fact parts of KWin do not get build wi
13 matches
Mail list logo
