Control: tags -1 moreinfo
On Mon, 11 Dec 2017 19:43:59 +0100 Emilio Pozuelo Monfort
wrote:
> Source: libical
> Version: 2.0.0-1
> Severity: serious
>
> Hi,
>
> We have src:libical3 now, so libical2 should be dropped before the
> freeze. We shouldn't need to release buster with both libical 2 an
On 08/08/18 09:33, Niels Thykier wrote:
> Control: tags -1 moreinfo
>
> On Mon, 11 Dec 2017 19:43:59 +0100 Emilio Pozuelo Monfort
> wrote:
>> Source: libical
>> Version: 2.0.0-1
>> Severity: serious
>>
>> Hi,
>>
>> We have src:libical3 now, so libical2 should be dropped before the
>> freeze. We s
Hello,
As currently we have (for most of the platforms)
$ apt-cache madison libical2
libical2 | 2.0.0-4+b2 | http://ftp.fr.debian.org/debian buster/main
amd64 Packages
libical |2.0.0-4 | http://ftp.fr.debian.org/debian buster/main
Sources
What do we do with that bug ?
Thanks
On Wed, 8
Hey,
> That's basically kdepimlibs, as cyrus-imapd is not in testing and kmymoney
is already fixed in experimental and just needs an upload to sid.
> kdepimlibs may not be easy though as disabling libical will probably disable
some libs that may be used by rdeps. Someone needs to look at that.
Source: libical
Version: 2.0.0-1
Severity: serious
Hi,
We have src:libical3 now, so libical2 should be dropped before the
freeze. We shouldn't need to release buster with both libical 2 and 3.
Filing this bug so we don't forget about that.
Emilio
-- System Information:
Debian Release: buster/si
5 matches
Mail list logo