fix(parallels-tools): handle libfuse2->libfuse2t64 time64 rename#7
Open
DAEMON-404 wants to merge 1 commit into
Open
fix(parallels-tools): handle libfuse2->libfuse2t64 time64 rename#7DAEMON-404 wants to merge 1 commit into
DAEMON-404 wants to merge 1 commit into
Conversation
…stly Parallels Tools' installer hardcodes `apt-get install libfuse2`. On time64 Debian/Kali the FUSE 2 runtime was renamed libfuse2t64, so the literal name has no candidate and the installer dies "failed to install mandatory packages". parallels-tools.sh: replace the equivs + version-pinned .deb approach with three helpers - have_real_libfuse2 (real-runtime probe via libfuse2t64/libfuse2 package and ldconfig libfuse.so.2), fetch_kali_pool_deb (dynamic newest-version discovery from the Kali pool, multi-mirror, no version pin), and build_libfuse2_shim (dpkg-deb name-shim, no equivs dependency; Depends on the real runtime when present, else dependency-free). Ordered resolution: libfuse2 -> libfuse2t64 -> pool .deb -> honest runtime check (loud warning, never silent) -> name-shim -> abort before the doomed build if unsatisfiable. penv.py: prefer the bundled helper when it is newer than the deployed ~/.local/bin/pt-install, so a stale deployment can't re-run the old bugs. UPSTREAM_README.md: note the libfuse2/libfuse2t64 handling. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Fix Parallels Tools install failure on current Kali/Debian guests caused by the time64
libfuse2->libfuse2t64package rename.Why
Parallels' installer runs a hardcoded
apt-get install libfuse2. On time64 Debian/Kali that name has no candidate (the FUSE 2 runtime now ships aslibfuse2t64), so the installer dies at "failed to install mandatory packages". The previous helper relied onequivs(extra tooling) and a version-pinned.debURL (libfuse2t64_2.9.9-9+b1) that rots as Kali moves.Changes
parallels-tools.sh— three helpers + ordered, honest resolution:have_real_libfuse2— probeslibfuse2t64pkg /libfuse2pkg /ldconfiglibfuse.so.2fetch_kali_pool_deb— scrapes the Kali pool index,sort -Vpicks the newest matching${ARCH}/all, multi-mirror, no version pinbuild_libfuse2_shim—dpkg-debpackage literally namedlibfuse2(no equivs);Dependson the real runtime when present, else dependency-freelibfuse2->libfuse2t64-> pool.deb-> real-runtime check (loud warning, never silent) -> name-shim ->diebefore the doomed installer if unsatisfiablepenv.py— prefer the bundled helper when it is newer than the deployed~/.local/bin/pt-install, so a stale deployment can't re-run the old bugs.UPSTREAM_README.md— document the rename handling.Verification
bash -n parallels-tools.sh— passpython3 -m py_compile penv.py— passsort -Vnewest-pick, wrong-arch (arm64) exclusion,have_real_libfuse2returns non-zero cleanly underset -eu(no abort), shimDependspresent with runtime / omitted without — all pass🤖 Generated with Claude Code