Debian Bug report logs - #895037
RM: libappindicator -- RoQA; deprecated, no longer used

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Mike Gabriel <sunweaver@debian.org>

To: submit@bugs.debian.org

Subject: libappindicator: deprecated in Debian; AppIndicator based applications, please switch to Ayatana (App)Indicator(s)

Date: Fri, 06 Apr 2018 13:07:39 +0000

[Message part 1 (text/plain, inline)]

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]

Greets,
Mike

[1] https://lists.debian.org/debian-devel/2018/03/msg00506.html
[2] https://wiki.debian.org/Ayatana/IndicatorsTransition
-- 

mike gabriel aka sunweaver (Debian Developer)
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: sunweaver@debian.org, http://sunweavers.net

[Message part 2 (application/pgp-signature, inline)]

Message #12 received at 895037@bugs.debian.org (full text, mbox, reply):

From: Ivo De Decker <ivodd@debian.org>

To: Mike Gabriel <sunweaver@debian.org>, 895037@bugs.debian.org

Cc: 895038@bugs.debian.org

Subject: Re: libappindicator: deprecated in Debian; AppIndicator based applications, please switch to Ayatana (App)Indicator(s)

Date: Wed, 17 Oct 2018 15:46:11 +0200

Control: block 895038 by 895037

Hi,

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:

# Broken Depends:
blueman: blueman
caffeine: caffeine
clipit: clipit
diodon: diodon
gmpc: gmpc
gromit-mpx: gromit-mpx
growl-for-linux: growl-for-linux
gtimelog: gtimelog
gxkb: gxkb
hime: hime
kylin-burner: libburner-media3-1
modem-manager-gui: modem-manager-gui
parcellite: parcellite
psensor: psensor
redshift: redshift-gtk
roger-router: roger-router
solaar: solaar-gnome3

# Broken Build-Depends:
clipit: libappindicator3-dev
diodon: libappindicator3-dev (>= 0.3.0)
gcin: libappindicator3-dev
gmpc: libappindicator-dev
gromit-mpx: libappindicator3-dev
growl-for-linux: libappindicator-dev
gxkb: libappindicator-dev
hime: libappindicator-dev
kylin-burner: libappindicator3-dev (>= 0.0.7)
modem-manager-gui: libappindicator3-dev
parcellite: libappindicator-dev
psensor: libappindicator3-dev
roger-router: libappindicator3-dev
zeal: libappindicator-dev


For libindicator, the list is:

# Broken Depends:
cairo-dock-plug-ins: cairo-dock-alsamixer-plug-in
                     cairo-dock-messaging-menu-plug-in
libappindicator: libappindicator1
                 libappindicator3-1
lightdm-gtk-greeter: lightdm-gtk-greeter
workrave: workrave

# Broken Build-Depends:
cairo-dock-plug-ins: libindicator3-dev
libappindicator: libindicator-dev (>= 0.3.90)
                 libindicator3-dev (>= 0.3.90)
lightdm-gtk-greeter: libindicator3-dev
workrave: libindicator3-dev (>= 0.3.19)



Do you still think it's realistic to get this done before the transition
freeze (2019-01-12)? If not, this should be postponed.

To help the overview of what's still missing, it might be good to add blocking
bugs for every package to this one.

Thanks,

Ivo

Message #19 received at 895037@bugs.debian.org (full text, mbox, reply):

From: Mike Gabriel <sunweaver@debian.org>

To: Ivo De Decker <ivodd@debian.org>

Cc: 895037@bugs.debian.org, 895038@bugs.debian.org

Subject: Re: libappindicator: deprecated in Debian; AppIndicator based applications, please switch to Ayatana (App)Indicator(s)

Date: Mon, 22 Oct 2018 10:13:32 +0000

[Message part 1 (text/plain, inline)]

Hi Ivo,

On  Mi 17 Okt 2018 15:46:11 CEST, Ivo De Decker wrote:

> Control: block 895038 by 895037
>
> Hi,
>
> 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:
> blueman: blueman
> caffeine: caffeine
> clipit: clipit
> diodon: diodon
> gmpc: gmpc
> gromit-mpx: gromit-mpx
> growl-for-linux: growl-for-linux
> gtimelog: gtimelog
> gxkb: gxkb
> hime: hime
> kylin-burner: libburner-media3-1
> modem-manager-gui: modem-manager-gui
> parcellite: parcellite
> psensor: psensor
> redshift: redshift-gtk
> roger-router: roger-router
> solaar: solaar-gnome3

The above list is irrelevant, what counts are the build-deps.

However, the following packages need to be considered regarding the  
Depends: field:

  * python-appindicator (Python2 bindings, GTK-2 version)
    -> porting required to python-ayatana-appindicator
  * gir1.2-appindicator-0.1 (GTK-2 version)
    -> gir1.2-ayatanaappindicator-0.1
  * gir1.2-appindicator3-0.1 (GTK-3 version)
    -> gir1.2-ayatanaappindicator3-0.1
  *

> # Broken Build-Depends:
> clipit: libappindicator3-dev
> diodon: libappindicator3-dev (>= 0.3.0)
> gcin: libappindicator3-dev
> gmpc: libappindicator-dev
> gromit-mpx: libappindicator3-dev
> growl-for-linux: libappindicator-dev
> gxkb: libappindicator-dev
> hime: libappindicator-dev
> kylin-burner: libappindicator3-dev (>= 0.0.7)
> modem-manager-gui: libappindicator3-dev
> parcellite: libappindicator-dev
> psensor: libappindicator3-dev
> roger-router: libappindicator3-dev
> zeal: libappindicator-dev

This list is incomplete.

Additionally, you need to check for build-deps against:

  * libappindicator-dev (GTK-2 version of appindicator)
    -> porting required to libappindicator-dev (low prio)
  * libappindicator3-0.1-cil-dev (Mono bindings, GTK-2 version)
    -> porting required to libayatana-appindicator0.1-cil-dev

> For libindicator, the list is:

The libindicator transition is nearly done.

> # Broken Depends:
> cairo-dock-plug-ins: cairo-dock-alsamixer-plug-in
>                      cairo-dock-messaging-menu-plug-in
> libappindicator: libappindicator1
>                  libappindicator3-1
> lightdm-gtk-greeter: lightdm-gtk-greeter
> workrave: workrave

Broken Depends: are irrelevant here.

> # Broken Build-Depends:
> cairo-dock-plug-ins: libindicator3-dev

Actually, the cairo-dock Indicator stack is completely broken in  
Debian. The maintainer added a half-baked and untested fix (simply  
switching Build-Depends to aytana-ido without patching the code itself.

> libappindicator: libindicator-dev (>= 0.3.90)
>                  libindicator3-dev (>= 0.3.90)

-> This needs finishing the appindicator transition.

> lightdm-gtk-greeter: libindicator3-dev

-> Patch submitted already.

> workrave: libindicator3-dev (>= 0.3.19)

Oh, this one is new to me. Adding it to the wiki. [...] Ah, it's  
already there, but I wasn't aware of it being a libindicator porting  
issue (I though it was appindicator). Will take a look.

> Do you still think it's realistic to get this done before the transition
> freeze (2019-01-12)? If not, this should be postponed.

I'll do my best, but without help from maintainers, this will become  
difficult. I should write an enrolling mail to debian-devel, probably,  
to get more people on board.

> To help the overview of what's still missing, it might be good to  
> add blocking
> bugs for every package to this one.

Yeah, I will do this.

The current status of all filed bugs with patches is this:

for libappindicator -> libayatana-appindicator:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ayatana-appindicator;users=pkg-ayatana-devel@lists.alioth.debian.org

for libindicator -> libayatana-indicator
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ayatanaindicators;users=pkg-ayatana-devel@lists.alioth.debian.org

Unfortunately, not all bugs submitted had usertags (and some of the  
second URL (#880193, #880169) actually belong to the first  
(ayatana-appindicator).

The full list of work, already done and to be done, is here:
https://wiki.debian.org/Ayatana/IndicatorsTransition

Mike
-- 

mike gabriel aka sunweaver (Debian Developer)
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: sunweaver@debian.org, http://sunweavers.net

[Message part 2 (application/pgp-signature, inline)]

Message #24 received at 895037@bugs.debian.org (full text, mbox, reply):

From: Ivo De Decker <ivodd@debian.org>

To: Mike Gabriel <sunweaver@debian.org>

Cc: Ivo De Decker <ivodd@debian.org>, 895037@bugs.debian.org, 895038@bugs.debian.org

Subject: Re: libappindicator: deprecated in Debian; AppIndicator based applications, please switch to Ayatana (App)Indicator(s)

Date: Sun, 13 Jan 2019 16:25:16 +0100

Control: tags -1 buster-ignore

Hi,

On Mon, Oct 22, 2018 at 10:13:32AM +0000, Mike Gabriel wrote:
> 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.

It doesn't look like this will be done for buster.

Cheers,

Ivo

Message #35 received at 895037@bugs.debian.org (full text, mbox, reply):

From: Ivo De Decker <ivodd@debian.org>

To: Mike Gabriel <sunweaver@debian.org>

Cc: Ivo De Decker <ivodd@debian.org>, 895037@bugs.debian.org, 895038@bugs.debian.org

Subject: Re: libappindicator: deprecated in Debian; AppIndicator based applications, please switch to Ayatana (App)Indicator(s)

Date: Thu, 2 Apr 2020 14:11:42 +0200

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

Message #86 received at 895037@bugs.debian.org (full text, mbox, reply):

From: Simon McVittie <smcv@debian.org>

To: Mike Gabriel <sunweaver@debian.org>, 895037@bugs.debian.org, 895038@bugs.debian.org

Cc: Ivo De Decker <ivodd@debian.org>

Subject: Re: Bug#895038: libappindicator: deprecated in Debian; AppIndicator based applications, please switch to Ayatana (App)Indicator(s)

Date: Wed, 15 Apr 2020 09:49:03 +0100

On Thu, 02 Apr 2020 at 14:11:42 +0200, Ivo De Decker wrote:
> On Mon, Oct 22, 2018 at 10:13:32AM +0000, Mike Gabriel wrote:
> > > # 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.

For packages like redshift that do not require binary packages built by
libappindicator at build-time but only at runtime (mostly Python code using
gir1.2-appindicator* via pygobject), there are no Build-Depends, but
the Depends do matter.

`dak rm` is the tool that the ftp team would use if they removed
lib(app)indicator from unstable, so if you want lib(app)indicator to be
removed, all the packages that `dak rm` is concerned about will need to be
either removed or fixed.

> > > 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.

I've done that for you.

> 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.

I haven't done that. I think the severity of these bugs is a decision
for the maintainer of the replacement to make.

    smcv

Message #91 received at 895037@bugs.debian.org (full text, mbox, reply):

From: Mike Gabriel <sunweaver@debian.org>

To: Simon McVittie <smcv@debian.org>

Cc: 895037@bugs.debian.org, 895038@bugs.debian.org, Ivo De Decker <ivodd@debian.org>

Subject: Re: Bug#895038: libappindicator: deprecated in Debian; AppIndicator based applications, please switch to Ayatana (App)Indicator(s)

Date: Wed, 15 Apr 2020 19:06:59 +0000

[Message part 1 (text/plain, inline)]

Hi Simon, hi Ivo,

I am currently drowned in customer requests. Sorry for the late reply.

On  Mi 15 Apr 2020 10:49:03 CEST, Simon McVittie wrote:

>> > > 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.
>
> I've done that for you.

Thanks for that. What is the exact BTS query to list those bugs?

>> 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.
>
> I haven't done that. I think the severity of these bugs is a decision
> for the maintainer of the replacement to make.

I think we should start with important and raise to serious after 8  
weeks or so.

Mike

-- 

mike gabriel aka sunweaver (Debian Developer)
mobile: +49 (1520) 1976 148
landline: +49 (4351) 486 14 27

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: sunweaver@debian.org, http://sunweavers.net

[Message part 2 (application/pgp-signature, inline)]

Message #96 received at 895037@bugs.debian.org (full text, mbox, reply):

From: Simon McVittie <smcv@debian.org>

To: Mike Gabriel <sunweaver@debian.org>

Cc: 895037@bugs.debian.org, 895038@bugs.debian.org, Ivo De Decker <ivodd@debian.org>

Subject: Re: Bug#895038: libappindicator: deprecated in Debian; AppIndicator based applications, please switch to Ayatana (App)Indicator(s)

Date: Wed, 15 Apr 2020 20:21:59 +0100

On Wed, 15 Apr 2020 at 19:06:59 +0000, Mike Gabriel wrote:
> On  Mi 15 Apr 2020 10:49:03 CEST, Simon McVittie wrote:
> > I've done that for you.
> 
> Thanks for that. What is the exact BTS query to list those bugs?

Sorry, I don't know the CLI for it, but I made them block 895037/895038
as appropriate, and applied the same usertags you mentioned earlier in
the bug(s). For pre-existing bugs I just added blocks, so some of them
might not be usertagged correctly.

libappindicator:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895037 (look at "Fix blocked by")
https://udd.debian.org/cgi-bin/bts-usertags.cgi?tag=ayatana-appindicator&user=pkg-ayatana-devel%40lists.alioth.debian.org

libindicator:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895038
https://udd.debian.org/cgi-bin/bts-usertags.cgi?tag=ayatanaindicators&user=pkg-ayatana-devel%40lists.alioth.debian.org

    smcv

Message #101 received at 895037-close@bugs.debian.org (full text, mbox, reply):

From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>

To: 895037-close@bugs.debian.org

Subject: Bug#895037: fixed in blueman 2.1.3-2

Date: Wed, 03 Jun 2020 08:41:15 +0000

Source: blueman
Source-Version: 2.1.3-2
Done: Christopher Schramm <debian@cschramm.eu>

We believe that the bug you reported is fixed in the latest version of
blueman, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 895037@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Christopher Schramm <debian@cschramm.eu> (supplier of updated blueman package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Tue, 2 Jun 2020 08:05:00 +0200
Source: blueman
Architecture: source
Version: 2.1.3-2
Distribution: unstable
Urgency: low
Maintainer: Christopher Schramm <debian@cschramm.eu>
Changed-By: Christopher Schramm <debian@cschramm.eu>
Closes: 895037 942916 961215
Changes:
 blueman (2.1.3-2) unstable; urgency=low
 .
   * Fix systemd unit dir (Closes: #961215)
   * Use cython3 (Closes: #942916)
   * Use libayatanaappindicator (Closes: #895037)
Checksums-Sha1:
 7268b57f5c472676968d5fdc5bf151489ed4249f 1850 blueman_2.1.3-2.dsc
 d6a6330f5f3a073f7702316bf51fb9984e6eb584 5444 blueman_2.1.3-2.debian.tar.xz
 8e89f2a20d18e58c0fdf891e9662d8fb4e4fca1e 7925 blueman_2.1.3-2_amd64.buildinfo
Checksums-Sha256:
 d260bb106a94639975845df74b4fe968f71d222f0b338d2163fbd25ba8e35752 1850 blueman_2.1.3-2.dsc
 b894585ae2a30b0a8e88d298a29903b8f042df254643749821f24d75e195cfcc 5444 blueman_2.1.3-2.debian.tar.xz
 8969ce321eefb28e65f90db41ab137d0a39e319270aa42bfe39cdc772a37366d 7925 blueman_2.1.3-2_amd64.buildinfo
Files:
 b1058bec5562d2d15acf09530c2f5a75 1850 x11 optional blueman_2.1.3-2.dsc
 051e76b9829b6b9659e8bccf1002a404 5444 x11 optional blueman_2.1.3-2.debian.tar.xz
 44fe71e63f8347bbc4fb4b4f14c435d5 7925 x11 optional blueman_2.1.3-2_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEXmKe5SMhlzV7hM9DMiR/u0CtH6YFAl7XV3YACgkQMiR/u0Ct
H6Z5oQ/9E7d0LjifmVrbwPi5oEMiTIJjOl5JyyPVaJg2AWSQ7MWW0J0/rbgVc8Oc
6l12A028NVRU0CrM/2khGJqYvYwjFOsgS3N3jGkaUYF6YSVWeLJeAmxIaE1ZEXSx
nD8T92V7Ulvxs6eWOJqAMRv8erIieVIwCAjw+C56Qjh/zTUhVXqPm2DNwSFRAU+9
XjM4OnfcC+cKPwRiOGDDbAnecA+AuuizeY1I6DITts15eZ0DvjuakH+fys5IMfe/
21ES9YaqazasIJCI+yn4putXH7RSzDILgu29qfpGkvIqWIOwhRmnn8A4ZNw0B3Zi
kRO4Y09T27Ttjf12iKSgsaC1ZgoI/JatJy7yk2WfM4yfBFywIttcIqO1TPdRi4kU
HofWtFRGBIhLycblxDNDcFyKYy3oHKIZQNKey7bGc15Po3w+asAf3xmeThWPFWWK
uluALvF4IwMMsUu5y1z0iYF66czDv3wZPsInj2985mA+dtzdODt8Og+BIrbSJPJh
4ZR2x3CHpmSS7rXuASGWZPbA5lSIORDrTn9pyNC2WZ7VfPgHH415+cIXGFi6VU6N
3SGuo7r1v59kenJcCTwM+KBpm/IgmhWMo0e/rrO0ZZS8AKRvsMWi4xQNzV4c9rZV
bAi2Bzy08/iGGJ3PJ4MIHqmHBswmrE30kCuq3kehW+lXBl62Hko=
=LC/W
-----END PGP SIGNATURE-----

Message #106 received at 895037@bugs.debian.org (full text, mbox, reply):

From: Matteo Vescovi <ing.vescovi@gmail.com>

To: Christopher Schramm <debian@cschramm.eu>

Cc: 895037@bugs.debian.org

Subject: Re: Bug#895037: fixed in blueman 2.1.3-2

Date: Wed, 3 Jun 2020 15:21:03 +0200

Control: reopen -1
Control: fixed 956761 blueman/2.1.3-2

Hi!

On Wed, 03 Jun 2020 08:41:15 +0000 Debian FTP Masters 
<ftpmaster@ftp-master.debian.org> wrote:
>  blueman (2.1.3-2) unstable; urgency=low
>  .
>    * Fix systemd unit dir (Closes: #961215)
>    * Use cython3 (Closes: #942916)
>    * Use libayatanaappindicator (Closes: #895037)

Actually, this upload fixes the issue on blueman itself, not on the 
entire meta-bug for libappindicator migration.

Thus, reopening and fixing accordingly.

Cheers.


-- 
ing. Matteo Vescovi

Message #117 received at 895037@bugs.debian.org (full text, mbox, reply):

From: Simon McVittie <smcv@debian.org>

To: 895037@bugs.debian.org, 956760@bugs.debian.org, 956762@bugs.debian.org, 956767@bugs.debian.org, 956779@bugs.debian.org, 956778@bugs.debian.org, 956776@bugs.debian.org, 956772@bugs.debian.org, 956782@bugs.debian.org, 956774@bugs.debian.org, 956769@bugs.debian.org, 921339@bugs.debian.org, 956766@bugs.debian.org

Cc: Mike Gabriel <sunweaver@debian.org>, Paul Gevers <elbrus@debian.org>, 895038@bugs.debian.org

Subject: Re: Bug#895038: libappindicator: deprecated in Debian; AppIndicator based applications, please switch to Ayatana (App)Indicator(s)

Date: Thu, 10 Dec 2020 15:08:00 +0000

Control: severity -1 serious

On Thu, 10 Dec 2020 at 14:37:21 +0000, Mike Gabriel wrote:
> On  Do 10 Dez 2020 15:35:19 CET, Paul Gevers wrote:
> > We're running into the freeze of bullseye soon. The first bug I checked
> > is still only severity important, so is it realistic to get this done
> > before bullseye release? [...]
> > If yes, action is needed, this isn't going to happen
> > magically. At the least raising the blocking bugs to severity serious.
> 
> I'd suggest to raise severity of the still open bugs and get libappindicator
> kicked out before the bullseye release.
> 
> The fixes are easy to be done. Maintainers can ping me if they have problems.

Raising the blocking bugs to RC as requested.

> I am not so experienced with effective mass manipulation of bugs, Simon,
> could you bump the severity of the respective bugs?

There's no magic to it, you just send mail to the affected bug address(es)
with appropriate Control commands.

    smcv

Message #124 received at 895037@bugs.debian.org (full text, mbox, reply):

From: Ivo De Decker <ivodd@debian.org>

To: Simon McVittie <smcv@debian.org>

Cc: 895037@bugs.debian.org, Mike Gabriel <sunweaver@debian.org>, Paul Gevers <elbrus@debian.org>, 895038@bugs.debian.org

Subject: Re: Bug#895038: libappindicator: deprecated in Debian; AppIndicator based applications, please switch to Ayatana (App)Indicator(s)

Date: Mon, 28 Dec 2020 16:41:12 +0100

Hi,

On Thu, Dec 10, 2020 at 03:08:00PM +0000, Simon McVittie wrote:
> On Thu, 10 Dec 2020 at 14:37:21 +0000, Mike Gabriel wrote:
> > On  Do 10 Dez 2020 15:35:19 CET, Paul Gevers wrote:
> > > We're running into the freeze of bullseye soon. The first bug I checked
> > > is still only severity important, so is it realistic to get this done
> > > before bullseye release? [...]
> > > If yes, action is needed, this isn't going to happen
> > > magically. At the least raising the blocking bugs to severity serious.
> > 
> > I'd suggest to raise severity of the still open bugs and get libappindicator
> > kicked out before the bullseye release.
> > 
> > The fixes are easy to be done. Maintainers can ping me if they have problems.
> 
> Raising the blocking bugs to RC as requested.

I added some hints to finish this, and now libindicator and libappindicator
are no longer in testing.

Thanks!

Ivo

Message #131 received at 895037@bugs.debian.org (full text, mbox, reply):

From: Stephen Kitt <skitt@debian.org>

To: 895037@bugs.debian.org

Cc: Ivo De Decker <ivodd@debian.org>, Simon McVittie <smcv@debian.org>, Mike Gabriel <sunweaver@debian.org>, Paul Gevers <elbrus@debian.org>

Subject: Re: Bug#895038: libappindicator: deprecated in Debian; AppIndicator based applications, please switch to Ayatana (App)Indicator(s)

Date: Sun, 25 Apr 2021 21:00:08 +0200

[Message part 1 (text/plain, inline)]

On Mon, 28 Dec 2020 16:41:12 +0100 Ivo De Decker <ivodd@debian.org> wrote:
> I added some hints to finish this, and now libindicator and libappindicator
> are no longer in testing.

I uploaded a fix for #956782 in unstable, which means libappindicator is no
longer needed there either:

skitt@coccia:~$ dak rm --no-action -R libappindicator
Will remove the following packages from unstable:

gir1.2-appindicator-0.1 |   0.4.92-8 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
gir1.2-appindicator3-0.1 |   0.4.92-8 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
libappindicator |   0.4.92-8 | source
libappindicator-dev |   0.4.92-8 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
libappindicator-doc |   0.4.92-8 | all
libappindicator1 |   0.4.92-8 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
libappindicator3-1 |   0.4.92-8 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
libappindicator3-dev |   0.4.92-8 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x

Maintainer: Debian QA Group <packages@qa.debian.org>

------------------- Reason -------------------

----------------------------------------------

Checking reverse dependencies...
No dependency problem found.


I’m guessing this should be converted to an RM, but I’ll leave that up to
Mike.

Regards,

Stephen

[Message part 2 (application/pgp-signature, inline)]

Message #142 received at 895037-close@bugs.debian.org (full text, mbox, reply):

From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>

To: 895037-close@bugs.debian.org

Cc: libappindicator@packages.debian.org

Subject: Bug#895037: Removed package(s) from unstable

Date: Tue, 14 Sep 2021 18:56:51 +0000

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

gir1.2-appindicator-0.1 |   0.4.92-8 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
gir1.2-appindicator3-0.1 |   0.4.92-8 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
libappindicator |   0.4.92-8 | source
libappindicator-dev |   0.4.92-8 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
libappindicator-doc |   0.4.92-8 | all
libappindicator1 |   0.4.92-8 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
libappindicator3-1 |   0.4.92-8 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
libappindicator3-dev |   0.4.92-8 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x

------------------- Reason -------------------
RoQA; deprecated, no longer used
----------------------------------------------

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 895037@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/895037

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Sean Whitton (the ftpmaster behind the curtain)

Send a report that this bug log contains spam.