Bug#895037: fixed in blueman 2.1.3-2

To: Christopher Schramm <debian@cschramm.eu>
Cc: 895037@bugs.debian.org
Subject: Bug#895037: fixed in blueman 2.1.3-2
From: Matteo Vescovi <ing.vescovi@gmail.com>
Date: Wed, 3 Jun 2020 15:21:03 +0200
Message-id: <[🔎] 7e9e7f45-10d7-df93-87b5-fca49b629ef5@gmail.com>
Reply-to: Matteo Vescovi <ing.vescovi@gmail.com>, 895037@bugs.debian.org
In-reply-to: <E1jgOxX-000HsZ-AN@fasolo.debian.org>
References: <E1jgOxX-000HsZ-AN@fasolo.debian.org> <E1jgOxX-000HsZ-AN@fasolo.debian.org> <20180406130739.Horde.nps0pNbMGvvgaBchWpoRfTJ@mail.das-netzwerkteam.de>

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 theentire meta-bug for libappindicator migration.


Thus, reopening and fixing accordingly.

Cheers.


--
ing. Matteo Vescovi

Reply to:

Prev by Date: Processed: tagging 960422
Next by Date: Processed: Re: Bug#895037: fixed in blueman 2.1.3-2
Previous by thread: Processed: tagging 960422
Next by thread: Processed: Re: Bug#895037: fixed in blueman 2.1.3-2
Index(es):
- Date
- Thread