On 18/12/17 04:41, Andreas Beckmann wrote:
> Followup-For: Bug #883921
>
> experimental NMU for libical3:
>
> nmu libkolab_1.0.2-5 . ANY . experimental . -m "Rebuild against libical3."
>
> libkolab1 will pick up a new dependency on libical3, fixing an
> unresolved symbol it currently has (only i
Followup-For: Bug #883921
experimental NMU for libical3:
nmu libkolab_1.0.2-5 . ANY . experimental . -m "Rebuild against libical3."
libkolab1 will pick up a new dependency on libical3, fixing an
unresolved symbol it currently has (only in experimental).
Andreas
Control: tags -1 confirmed
On 09/12/17 12:33, Matthias Klose wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
>
> Please setup a libical transition tracker.
>
> title = "libical 3.0.0";
> is_affected = .depends ~ /libic
Processing control commands:
> tags -1 confirmed
Bug #883921 [release.debian.org] transition: libical
Added tag(s) confirmed.
--
883921: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883921
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
I have done uploads for evolution-data-server, evolution and
evolution-ews, since I've been planning for weeks to do those today
and I don't think they'll really hold up the transition. It's an
unusual transition and I didn't want evolution-data-server to
accidentally migrate to testing a couple da
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Please setup a libical transition tracker.
title = "libical 3.0.0";
is_affected = .depends ~ /libical2|libical3/;
is_good = .depends ~ /libical3/;
is_bad = .depends ~ /libical2/;
The ne
6 matches
Mail list logo
