Bug#905697: kdepimlibs: don't depend on libical

2019-04-02 Thread Sandro Knauß
Hi, thanks a lot for the patch. I already pushed a new version, with your patch added. hefee -- On Sonntag, 31. März 2019 22:35:05 CEST Giovanni Mascellani wrote: > user debian-rele...@lists.debian.org > > usertags 905697 + bsp-2019-03-fr-paris > thank you > > Hi, > > On Thu, 14 Feb 2019

Bug#905697: kdepimlibs: don't depend on libical

2019-03-31 Thread Giovanni Mascellani
user debian-rele...@lists.debian.org usertags 905697 + bsp-2019-03-fr-paris thank you Hi, On Thu, 14 Feb 2019 10:07:42 +0100 Emilio Pozuelo Monfort wrote: > kde-runtime has dozens of rdeps, so unless its dep on kdepimlibs can be broken > somehow, this would be much harder to solve for buster.

Bug#905697: kdepimlibs: don't depend on libical

2019-02-14 Thread Emilio Pozuelo Monfort
On 14/02/2019 09:50, Simon McVittie wrote: > On Fri, 08 Feb 2019 at 22:46:21 +0100, Sandro Knauß wrote: >> Keep in mind, that kdepimlibs is an old grufted lib set that we also would >> like to kill. > > Perhaps you could ask the ftp team to override its Section to oldlibs > to indicate this? >

Bug#905697: kdepimlibs: don't depend on libical

2019-02-14 Thread Simon McVittie
On Fri, 08 Feb 2019 at 22:46:21 +0100, Sandro Knauß wrote: > Keep in mind, that kdepimlibs is an old grufted lib set that we also would > like to kill. Perhaps you could ask the ftp team to override its Section to oldlibs to indicate this? > But we also have other packages depending on it like:

Bug#905697: Info received (Bug#905697: kdepimlibs: don't depend on libical)

2019-02-09 Thread Scott Kitterman
I think the only API change that's relevant might be: is_utc to icaltime_is_utc() in icaltimetype For anyonne with a non-trivial C++ knowledge (i.e. not me), I suspect this wouldn't be too hard. Scott K

Bug#905697: kdepimlibs: don't depend on libical

2019-02-08 Thread Scott Kitterman
What about porting it to libical3? That might be easier. I tried to build it and it does need some changes, but I don't think keeping libical2 is feasible. See the attached for the error. Scott K On Friday, February 08, 2019 10:46:21 PM Sandro Knauß wrote: > Hey, > > for me it looks like

Bug#905697: kdepimlibs: don't depend on libical

2019-02-08 Thread Sandro Knauß
Hey, for me it looks like we won't be able to get kdepimlibs without libical 2 for buster. Keep in mind, that kdepimlibs is an old grufted lib set that we also would like to kill. But we also have other packages depending on it like: * basket * kopete (it has a QT5 version in experimental, but

Bug#905697: kdepimlibs: don't depend on libical

2019-01-17 Thread Emilio Pozuelo Monfort
On 11/01/2019 13:37, Emilio Pozuelo Monfort wrote: > On 08/08/2018 10:38, Emilio Pozuelo Monfort wrote: >> Source: kdepimlibs >> Version: 4:4.14.10-10 >> Severity: serious >> Control: block 884128 with -1 >> >> Hi, >> >> libical2 from src:libical is superseded by libical3 (src:libical3). >> >>

Bug#905697: kdepimlibs: don't depend on libical

2019-01-11 Thread Emilio Pozuelo Monfort
On 08/08/2018 10:38, Emilio Pozuelo Monfort wrote: > Source: kdepimlibs > Version: 4:4.14.10-10 > Severity: serious > Control: block 884128 with -1 > > Hi, > > libical2 from src:libical is superseded by libical3 (src:libical3). > > Please either port kdepimlibs to libical3 or try to disable the

Bug#905697: kdepimlibs: don't depend on libical

2018-08-08 Thread Emilio Pozuelo Monfort
Source: kdepimlibs Version: 4:4.14.10-10 Severity: serious Control: block 884128 with -1 Hi, libical2 from src:libical is superseded by libical3 (src:libical3). Please either port kdepimlibs to libical3 or try to disable the libical support, so that we can only ship src:libical3 in buster.