Your message dated Wed, 21 Aug 2019 13:34:13 +0000
with message-id <[email protected]>
and subject line Bug#923935: fixed in android-sdk-meta 25.0.0+11
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
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: Thu, 27 Jun 2019 22:16:12 +0200
Source: android-sdk-meta
Architecture: source
Version: 25.0.0+11
Distribution: unstable
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) unstable; 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:
048114116ab3cd98c076301c0b171a08a0e2fb76 2076 android-sdk-meta_25.0.0+11.dsc
d24e482af5b06548ed74d1c859766375aa2a70e7 10380
android-sdk-meta_25.0.0+11.tar.xz
ed0f14fb380b9fe74e7e0158887c1978df99e5aa 5097
android-sdk-meta_25.0.0+11_source.buildinfo
Checksums-Sha256:
1277655e19d2a8cba395753c063c068015f7a3e31e3bab6598eb6a7cb447c621 2076
android-sdk-meta_25.0.0+11.dsc
6b7e59c0271ed95b13f772e3fc5047680a4835d19e8c0d1c8f2f3406573915cb 10380
android-sdk-meta_25.0.0+11.tar.xz
11c57068d1a9b0dbf383386ce3c93c29f9e77d90156b53cc11daa22e2347c736 5097
android-sdk-meta_25.0.0+11_source.buildinfo
Files:
b24592decd1227b221620b2b95ce434e 2076 metapackages optional
android-sdk-meta_25.0.0+11.dsc
d9802ae8eef6590147cb9d3af948fb19 10380 metapackages optional
android-sdk-meta_25.0.0+11.tar.xz
3165fe67d8d0bccc1934a3efadd88e5b 5097 metapackages optional
android-sdk-meta_25.0.0+11_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCAAdFiEElyI52+aGmfUmwGoFPhd4F7obm/oFAl1dQ+YACgkQPhd4F7ob
m/oYtQf/V+LEw9o98OC5hUeaHrzH4jL/TR/qp8qYza4+2LUBO1XxKHzCVZAdnxbS
GL0GVaSehwY3WhaRrkVNbgIQQHklCeFwDQSEcWsnUtOvNkYpq5XpveHAp6I4xpOH
sg/j/mHIFVuYI4/F55LQm9+y2aZ4sZKveiuJDyI/TSmqLNfi6i4A76SQ/oHOJVHe
apbVkufjwHkriuV8EjeLwbx4D2qFFPVqml/D3gcGR0/7FYVzGwBI/2WmnAL+WpGw
vMGyugZyMqUM5eWGehao90XEPkAusTdphrDybFPxBaE0/JO0T8rXQt8MnLnU+hTS
LqqnetePkBc1ao/sNL2qhzy3xTujrg==
=bjCM
-----END PGP SIGNATURE-----
--- End Message ---
