On 02/13/2016 09:03 AM, Maximiliano Curia wrote:
kgpg
There is a new version in experimental that should be installable.
New one at 4:15.12 depends on:
libakonadi-kde4
libkabc4
both of which conflict with kdepimlibs-data
kgpg also depends on libakonadi-contact4, which depends on the offending
pkgs:
libakonadi-kde4
libkabc4
Right, kgpg hasn't been ported to frameworks yet. kleopatra is the one that
was ported, we should probably depend on kleopatra | kpgp, as they provide the
same features, but kleopatra developers seem to be more active.
kleopatra doesn't create keys yet I don't think. And there's the issue
of kwallet not using pinentry before trying to engage gpg. Ubuntu has
pinentry-kde. Is that necessary or should pinentry-qt suffice? Or do we
need pam-kwalletd or such? Ever since the weird broken blowfish
implementation...
Will there ever peace between gpg and ssh? Ok. Getting off track.
Installing packages manually makes it more difficult to track what
packages are needed or need to be upgraded.
Incidentally, there's many packages with mixed dependencies on specific
versions of libqt5core5a throughout kde5. Some pkgs want 5.6.0 others
want 5.5.1. And they depend on each other.
Yes, this seems to be due to a hiccup in the buildds experimental dependency
solver, in the past the dependency solver tried to use the version in unstable
unless the required versions were only available in experimental, the new
solver used qt 5.6 even though the qt 5.5 version from unstable was enough to
fullfil the requiremens (this might sound simple, but it's a hard problem, and
it's something that has always brought headaches to packagers working with
experimental).
\m/ CAN I PLAY WITH MADNESS? \m/
Thanks for reporting!
Happy hacking,
