[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#921005: marked as done (Missing manual dependency for package gcin on libappindicator3-1)



Your message dated Tue, 19 Jan 2021 09:33:47 +0000
with message-id <E1l1nOV-000GJy-Ci@fasolo.debian.org>
and subject line Bug#921005: fixed in gcin 2.9.0+dfsg1-2
has caused the Debian Bug report #921005,
regarding Missing manual dependency for package gcin on libappindicator3-1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
921005: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921005
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: gcin
Version: 2.8.8+dfsg1-1
Severity: important

Dear maintainers,

the gcin source has a build dependency on libappindicator3-dev, but the package
itself doesn't depend on libappindicator3-1. I guess the library is just
dynamically dlopen'ed, so the maintainer scripts can't detect it.

When I start gcin, I get a message window with a close button and the text:
"libappindicator3.so.1: cannot open shared object file: No such file or
directory". And clicking the close button results in a SIGSEGV.

Manually installing libappindicator3-1 fixes the problem, so I guess the gcin
package needs a manual libappindicator3-1 dependency.

Regards,
Jan-Marek Glogowski

--- End Message ---
--- Begin Message ---
Source: gcin
Source-Version: 2.9.0+dfsg1-2
Done: Yao Wei (魏銘廷) <mwei@debian.org>

We believe that the bug you reported is fixed in the latest version of
gcin, 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 921005@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Yao Wei (魏銘廷) <mwei@debian.org> (supplier of updated gcin 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: SHA512

Format: 1.8
Date: Tue, 19 Jan 2021 16:56:59 +0800
Source: gcin
Architecture: source
Version: 2.9.0+dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Input Method Team <debian-input-method@lists.debian.org>
Changed-By: Yao Wei (魏銘廷) <mwei@debian.org>
Closes: 921005 956766
Changes:
 gcin (2.9.0+dfsg1-2) unstable; urgency=medium
 .
   * Use libayatana-appindicator (Closes: #956766)
   * debian/control: Recommends libayatana-appindicator3-1 (Closes: #921005)
Checksums-Sha1:
 af00e4327559bac56cccac66ba4e2df520cf9662 2628 gcin_2.9.0+dfsg1-2.dsc
 cd1c8215b30a3f0a5966fd9b930e8147545760e2 23148 gcin_2.9.0+dfsg1-2.debian.tar.xz
 4def2d08be2fc64096f7e7aedf403de4a4828d31 19668 gcin_2.9.0+dfsg1-2_amd64.buildinfo
Checksums-Sha256:
 920249199ffa6de6e65f6ecbc29cef3c7cb3a21d6111b6aaf9b0af66511b64d7 2628 gcin_2.9.0+dfsg1-2.dsc
 d9d005f951272c5fba0a7854f24b3b72f1996b6088696fbc06a615100fcaff96 23148 gcin_2.9.0+dfsg1-2.debian.tar.xz
 d492bf36eebfe8e9ca97bdaefafd73c042d8a82198a843a2f75acb336083a79a 19668 gcin_2.9.0+dfsg1-2_amd64.buildinfo
Files:
 1ef6a4ae32446758cb2aece288cec6d9 2628 utils optional gcin_2.9.0+dfsg1-2.dsc
 8795cdc75683221bc8defd873c7009da 23148 utils optional gcin_2.9.0+dfsg1-2.debian.tar.xz
 b4768d90727888c41f64237d584b9bdb 19668 utils optional gcin_2.9.0+dfsg1-2_amd64.buildinfo

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

iQJEBAEBCgAuFiEE8htgli/cvAeDZWXRl1ewRNNETDMFAmAGo2gQHG13ZWlAZGVi
aWFuLm9yZwAKCRCXV7BE00RMM2ZMD/oDXAK6W8D/N8obaDbwLt8CmEr0x/DOePjT
PxCicoi+oZHTaHvZo2YxlPTYzkgIMXkOjhaTNeSbgmnQpqy5rDWSCve+pa863ulU
MYvf9MLgeZFdmkuPX5iVQ9Mk7duH0mykOvw9M+ECGaSgOtUwUOYWt7YRKvz4IaCg
dRKvxNmbGaiIZ8JGnbwLDU6U3bo0cJvUKEZJNys/yQ7RXbit4PufaVZifbNB59Rz
fD5p4vx+I3+kLxSJ6AbF9g7zTwd6U9YfG+GKMrR92eyFipD21+wa2ZSdPulamrIg
oV21FuiD20/7mkFiLDkQ1vyofBC5TIfXkwK6wIz27VC8X13LaXjMC8kqjb0QylhZ
i99pWF/pQ2Ul0cPJ+vpQaWy7aoqrwpYKb69Nkdyb1+M3Fc72Qm+I0mR4OYWlYwyz
o7asNcoYHawjGqGcEdopXCZbHJiiJVTvFLZbgk6woiufwMk6tEcCW4MF7O7nb2Vh
6nR8sPY8c2WDVkFdrqrm2BIZGn0X5dGAcbzUoJajjNHkE5hmiW/gQMIIRVQU+uYg
sP5FJvPblA1pa0vS2MoBiBIEB7SnbxwGIflvI57drrZHvx68pK/9h73MUd7274rT
Tiyx6Sf/TPcCTK4IkCVj3gJggx6XCb12IckMkxC/c731wmuiH15+KvoGITqLDsYj
jQVjmsS+3Q==
=7W0P
-----END PGP SIGNATURE-----

--- End Message ---

Reply to: