Your message dated Tue, 27 Aug 2019 21:47:08 +0000
with message-id <[email protected]>
and subject line Bug#923935: fixed in android-sdk-meta 25.0.0+11~deb10u1
has caused the Debian Bug report #923935,
regarding android-sdk: broken symlinks: proguardgui, proguardgui.jar
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 [email protected]
immediately.)
--
923935: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923935
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: android-sdk
Version: 25.0.0+3
Severity: minor
File: /usr/lib/android-sdk/tools/proguard/bin/proguardgui
File: /usr/lib/android-sdk/tools/proguard/lib/proguardgui.jar
User: [email protected]
Usertags: adequate broken-symlink
Control: found -1 android-sdk/25.0.0+9
There are two broken symlinks in android-sdk since 25.0.0+3.
I believe this was caused by deliberately not depending on or
recommending proguard-gui due to a large number of dependencies.
I think it would be reasonable to recommend proguard-gui instead or
perhaps a more elaborate solution like android-sdk & android-sdk-gui.
The bug report that brought about that change also mentions that
libproguard-java should be in the dependencies instead of proguard-cli.
This bug report brought to you by adequate:
https://bonedaddy.net/pabs3/log/2013/02/23/inadequate-software/
$ adequate android-sdk
android-sdk: broken-symlink /usr/lib/android-sdk/tools/proguard/bin/proguardgui
-> ../../../../../bin/proguardgui
android-sdk: broken-symlink
/usr/lib/android-sdk/tools/proguard/lib/proguardgui.jar ->
../../../../../share/java/proguardgui.jar
$ chase /usr/lib/android-sdk/tools/proguard/bin/proguardgui
chase: /usr/bin/proguardgui: No such file or directory
$ chase /usr/lib/android-sdk/tools/proguard/lib/proguardgui.jar
chase: /usr/share/java/proguardgui.jar: No such file or directory
$ apt-file search proguardgui
android-sdk: /usr/lib/android-sdk/tools/proguard/bin/proguardgui
android-sdk: /usr/lib/android-sdk/tools/proguard/lib/proguardgui.jar
proguard-gui: /usr/bin/proguardgui
proguard-gui: /usr/share/java/proguardgui.jar
$ apt-get changelog android-sdk | grep proguard
* only Depend on proguard-cli (Closes: #856410)
$ w3m -dump https://bugs.debian.org/856410 | grep -C4 'broken symlink'
but you could add a
Suggests: proguard-gui
since the package now causes some broken symlinks in piuparts:
2m26.6s ERROR: FAIL: Broken symlinks:
/usr/lib/android-sdk/tools/proguard/lib/proguardgui.jar ->
../../../../../share/java/proguardgui.jar
/usr/lib/android-sdk/tools/proguard/bin/proguardgui ->
../../../../../bin/proguardgui
$ w3m -dump https://bugs.debian.org/856410 | grep -A1 libproguard-java
Depending on the libproguard-java package could be sufficient and really
right thing to do.
-- System Information:
Debian Release: buster/sid
APT prefers testing-debug
APT policy: (900, 'testing-debug'), (900, 'testing'), (800,
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700,
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-3-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8),
LANGUAGE=en_AU.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages android-sdk depends on:
ii android-sdk-build-tools 27.0.1+9
ii android-sdk-common 25.0.0+9
ii android-sdk-platform-tools 27.0.0+9
ii default-jdk 2:1.11-71
ii default-jdk-headless 2:1.11-71
ii proguard-cli 6.0.3-1
Versions of packages android-sdk recommends:
ii default-jdk-headless 2:1.11-71
ii gradle 4.4.1-4
Versions of packages android-sdk suggests:
ii android-sdk-platform-23 6.0.1+r72-5
pn maven <none>
-- no debconf information
--
bye,
pabs
https://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: android-sdk-meta
Source-Version: 25.0.0+11~deb10u1
We believe that the bug you reported is fixed in the latest version of
android-sdk-meta, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Hans-Christoph Steiner <[email protected]> (supplier of updated android-sdk-meta
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 [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Mon, 26 Aug 2019 12:39:48 +0200
Source: android-sdk-meta
Architecture: source
Version: 25.0.0+11~deb10u1
Distribution: buster
Urgency: medium
Maintainer: Android Tools Maintainers
<[email protected]>
Changed-By: Hans-Christoph Steiner <[email protected]>
Closes: 923935 924175 931215
Changes:
android-sdk-meta (25.0.0+11~deb10u1) buster; urgency=medium
.
[ Jeff Muizelaar ]
* Add some more Amazon devices
.
[ Hans-Christoph Steiner ]
* fix DEB_REVISION parsing to work with more than one digit
* remove broken screenshot2 symlink (Closes: #924175)
* Suggests: proguard-gui for symlinks (Closes: #923935)
* document udev rule for providing device access to the console user
* update udev rules to latest upstream version (Closes: #931215)
* sync new devices in 51-android.rules from upstream
* Standards-Version 4.3.0 no changes
* sync whitespace in 51-android.rules with upstream
* sync comments in 51-android.rules with upstream
* sync manufacturer order in 51-android.rules from upstream
Checksums-Sha1:
8652f2aff38469d39aa6b7fe30b1099ee479d73b 2108
android-sdk-meta_25.0.0+11~deb10u1.dsc
d6945cd9ca25d2c46c407661f68f00f96e803eec 10416
android-sdk-meta_25.0.0+11~deb10u1.tar.xz
c2ab667fb75edbf56d9dad318384601eac639039 5129
android-sdk-meta_25.0.0+11~deb10u1_source.buildinfo
Checksums-Sha256:
0f9a9a8500e3f72ce4ad6e7f588a469a19b6a7209edd0514f186b54d44b3634f 2108
android-sdk-meta_25.0.0+11~deb10u1.dsc
525394d90dae6d44f522f383fe4f6a90d99355e8913b6c3d10624daca8f0b0ba 10416
android-sdk-meta_25.0.0+11~deb10u1.tar.xz
ff2df55cb770cef2839ff5fa6d966c8db2019ab79e8b9e2eba3c0b0d0c0df9e8 5129
android-sdk-meta_25.0.0+11~deb10u1_source.buildinfo
Files:
818a7eb06a57c4872df33ebb1b177f9a 2108 metapackages optional
android-sdk-meta_25.0.0+11~deb10u1.dsc
4ff36b24660469bd981beea07189ab4f 10416 metapackages optional
android-sdk-meta_25.0.0+11~deb10u1.tar.xz
56ace04bfeb460795455c799787c5789 5129 metapackages optional
android-sdk-meta_25.0.0+11~deb10u1_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCAAdFiEElyI52+aGmfUmwGoFPhd4F7obm/oFAl1jt7gACgkQPhd4F7ob
m/opQQf6Aj1UOhCWnDhyWbKZJc9o8Qu/vgrQinBJ22rqtK18ky62JXB7SnJGAIVJ
D+66IWDkRZ4G/9UyqGZf7DOOY9rm4HuhhROY9jvvKAeIzMG+8IYC55lnJsxnRWnS
gegq3l/quV8gZ8zYCt0of/nyWs6sw5OJlIXgyQtvmbpaDle0RfEqSlhAyVS6G0KH
jhg4FfCNZ9VSsvVXSAFdmNIbtTPAafz55n4CMeVu6zacT4uSIOfCTzthmA6kh8Li
vl2K6kQMH9QBm8Wr8Jh2FMFoD4vAfZXxwOM4n3unYby5O9a2K6Z0D3cOhLv8cQOh
ptqYZCBcwPft+TIGXPS1YZRvudR+HA==
=D6Hl
-----END PGP SIGNATURE-----
--- End Message ---
