Re: KDE PIM 19.08.2 in experimental

2019-11-09 Thread Martin Steigerwald
Hi Sandro. Thank you very much for your packaging work. Sandro Knauß - 09.11.19, 19:34:35 CET: > to get akregator working again you need libkf5syndication5abi1 > 1:5.62.0-1 from experimental. KSydication has moved to Frameworks, > that's why the completly different version. The >

Re: KDE PIM 19.08.2 in experimental

2019-11-09 Thread Sandro Knauß
Hey, > At least kgpg has weird dependencies: > > libkf5akonadicontact5 (>= 4:18.08.3), libkf5akonadicontact5-18.08, > libkf5akonadicore5-18.08, libkf5akonadicore5abi2 (>= 4:18.08.3), [...] > libkf5contacts5 (>= 4:18.08.3), libkf5contacts5-18.08, > > which prevents its installation. Argh, the

Re: KDE PIM 19.08.2 in experimental

2019-11-09 Thread Sandro Knauß
Hey, to get akregator working again you need libkf5syndication5abi1 1:5.62.0-1 from experimental. KSydication has moved to Frameworks, that's why the completly different version. The libkf5syndication5abi1 shipps a wrong symbols files, that's why the dependencies are not correct. > apt

Re: KDE PIM 19.08.2 in experimental

2019-11-09 Thread Luigi Toscano
Sandro Knauß ha scritto: > Hey, > > I started to upload KDE PIM 19.08.2 to experimental. It should be functional, > if it is compiled. As I switched the way how KDEPIM is handled (I now use > virtual packages instead of symbolsfiles), it can't detect if "external > ap

Re: KDE PIM 19.08.2 in experimental

2019-11-09 Thread Martin Steigerwald
t;>> Sandro Knauß - 08.11.19, 11:05:44 CET: > >>>> I started to upload KDE PIM 19.08.2 to experimental. It should be > >>>> functional, if it is compiled. As I switched the way how KDEPIM > >>>> is > >>>> handled (I now use virtual packages i

Re: KDE PIM 19.08.2 in experimental

2019-11-09 Thread Martin Steigerwald
Am 09.11.19 um 11:03 schrieb Benjamin Eikel: Hi Martin, Am Samstag, 9. November 2019, 09:38:38 CET schrieb Martin Steigerwald: Am 08.11.19 um 16:08 schrieb Martin Steigerwald: Sandro Knauß - 08.11.19, 11:05:44 CET: I started to upload KDE PIM 19.08.2 to experimental. It should be functional

Re: KDE PIM 19.08.2 in experimental

2019-11-09 Thread Benjamin Eikel
Hi Martin, Am Samstag, 9. November 2019, 09:38:38 CET schrieb Martin Steigerwald: > Am 08.11.19 um 16:08 schrieb Martin Steigerwald: > > Sandro Knauß - 08.11.19, 11:05:44 CET: > >> I started to upload KDE PIM 19.08.2 to experimental. It should be > >> functional, if it

Re: KDE PIM 19.08.2 in experimental

2019-11-09 Thread Martin Steigerwald
Am 08.11.19 um 16:08 schrieb Martin Steigerwald: Sandro Knauß - 08.11.19, 11:05:44 CET: I started to upload KDE PIM 19.08.2 to experimental. It should be functional, if it is compiled. As I switched the way how KDEPIM is handled (I now use virtual packages instead of symbolsfiles), it can't

Re: KDE PIM 19.08.2 in experimental

2019-11-08 Thread Martin Steigerwald
Hey Sandro, Sandro Knauß - 08.11.19, 11:05:44 CET: > I started to upload KDE PIM 19.08.2 to experimental. It should be > functional, if it is compiled. As I switched the way how KDEPIM is > handled (I now use virtual packages instead of symbolsfiles), it > can't detect if "exte

KDE PIM 19.08.2 in experimental

2019-11-08 Thread Sandro Knauß
Hey, I started to upload KDE PIM 19.08.2 to experimental. It should be functional, if it is compiled. As I switched the way how KDEPIM is handled (I now use virtual packages instead of symbolsfiles), it can't detect if "external applications" are broken. This is fixed, if I get g