Control: block 895025 by 857260
Control: severity 857260 serious
On Mon, 02 Jul 2018 at 10:38:53 +0100, Simon McVittie wrote:
> On Fri, 06 Apr 2018 at 10:58:00 +0000, Mike Gabriel wrote:
> > So, in a nutshell, these packages need to be addressed: smuxi,
> > pidgin-libnotify and mopidy-mpris require changes to have libindicate
> > removed from Debian.
>
> If you do not intend to ship libindicate in buster, should the remaining
> bugs blocking #895025 (#895027 in smuxi and #895026 in pidgin-libnotify)
> inherit RC severity from this one?
dak says libappindicator also needs changes if you want to
remove libindicate from buster (I already opened #857260 some time
ago). libappindicator is RC-buggy already, so escalating #857260 to RC
severity doesn't seem harmful; but there are rather more packages that
depend on libappindicator, so it will probably take longer to remove than
libindicate, and it might be worthwhile for people with an interest in
indicators to do a QA upload to fix #857260.
smcv@coccia ~ % dak rm -R -n -s testing libindicate
...
# Broken Depends:
pidgin-libnotify: pidgin-libnotify
smuxi: smuxi-frontend-gnome
# Broken Build-Depends:
libappindicator: libindicate-dev (>= 0.2.0)
libindicate-gtk-dev (>= 0.2.0)
pidgin-libnotify: libindicate-dev (>= 0.6.90)
libindicate-gtk-dev (>= 0.6.90)
(I get the same report for removal from unstable.)
Regards,
smcv
