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: debian...@lists.debian.org 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
