Project

General

Profile

Actions

Bug #21774

closed

jammy/bookworm FUSE packages have incorrect FUSE dependency

Added by Brett Smith about 2 months ago. Updated about 1 month ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Category:
Deployment
Story points:
-

Description

test-provision-ubuntu2204: #1 /console

09:30:37   2024-05-15T13:30:28.174537954Z crunch-run Using FUSE mount: Traceback (most recent call last):
09:30:37   2024-05-15T13:30:28.174537954Z crunch-run   File "/usr/bin/arv-mount", line 6, in <module>
09:30:37   2024-05-15T13:30:28.174537954Z crunch-run     import arvados_fuse.command
09:30:37   2024-05-15T13:30:28.174537954Z crunch-run   File "/usr/lib/python3-arvados-fuse/lib/python3.10/site-packages/arvados_fuse/__init__.py", line 58, in <module>
09:30:37   2024-05-15T13:30:28.174537954Z crunch-run     import llfuse
09:30:37   2024-05-15T13:30:28.174537954Z crunch-run ImportError: libfuse.so.2: cannot open shared object file: No such file or directory

This happens because the package declares it depends on fuse but that now gets you libfuse.so.3. We need to specify libfuse2 instead.

We have code in the package testing scripts to catch this, but we only run it in debug mode. That seems weird. I feel like we should always run it.


Related issues

Blocks Arvados - Support #21664: Add test provision ubuntu 22.04 & make sure it passesResolvedBrett SmithActions
Blocks Arvados - Support #21663: Add test provision debian 12 & make sure it passesResolvedBrett SmithActions
Actions

Also available in: Atom PDF