Bug#895038: libappindicator: deprecated in Debian; AppIndicator based applications, please switch to Ayatana (App)Indicator(s)
Hi Mike,
This (obviously) wasn't done for buster, but it might be time to revisit it
for bullseye.
On Mon, Oct 22, 2018 at 10:13:32AM +0000, Mike Gabriel wrote:
> > On Fri, Apr 06, 2018 at 01:07:39PM +0000, Mike Gabriel wrote:
> > > Package: src:libappindicator
> > > Severity: serious
> > >
> > > The libappindicator package is currently QA team maintained in Debian and
> > > shall be phased out hopfully during the buster release cycle. The
> > > alternative (maintained upstream and Debian-downstream) is
> > > libayatana-appindicator.
> > >
> > > There is a lot of porting work to do (little patches are required for each
> > > application), to let all AppIndicator aware applications build against the
> > > new and supported AppIndicator shared lib fork "libayatana-appindicator".
> > >
> > > For details, please see [1]
> > >
> > > For a list of applications that require porting and the porting status, see
> > > [2]
> >
> > What's the status of this? Looking at testing, there are still quite a few
> > packages remaining that (build-)depend on libappindicator:
>
> I wish I could give more time to writing patches against the listed
> packages. Possibly, I should do a bug filing round first and then add
> patches, when I get to working on individual packages.
>
> > # Broken Depends:
[...]
> The above list is irrelevant, what counts are the build-deps.
Well, this was the output of dak rm. These dependencies need to be resolved
someway before the removal can be done. But I suspect your point is that these
will be solved when the build-depends (for the same packages) are solved, so
it's better to look at the build-depends.
[snip]
Note that the list of packages with broken build-depends shown by dak rm isn't
much shorter than it was a year ago.
> > To help the overview of what's still missing, it might be good to add
> > blocking
> > bugs for every package to this one.
It seems this wasn't done. Please add blocking bugs to this bug, so it's easy
to see what's missing.
Looking at the list of usertagged bugs you mentioned, it seems most of these
bugs are listed as fixed. So the remaining packages either don't have a bug,
or the bug wasn't usertagged.
If you want to get this done for bullseye, please upgrade these bugs to
serious. Autoremovals will take care of some of the packages. The rest will
need manual fixes.
Cheers,
Ivo
Reply to: