| Summary: | gvfs-fuse needs to depend on fuse3, not fuse (no mounts in /run/user/1000/gvfs) | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Christian Lohmaier <lohmaier+mageia> |
| Component: | RPM Packages | Assignee: | QA Team <qa-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | andrewsfarm, jani.valimaa, olav, ouaurelien, sysadmin-bugs |
| Version: | 8 | Keywords: | advisory, validated_update |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | MGA8-64-OK | ||
| Source RPM: | gvfs-1.46.2-1.mga8.src.rpm | CVE: | |
| Status comment: | |||
|
Description
Christian Lohmaier
2021-03-26 18:41:39 CET
Can we kill fuse? To avoid making such a mistake. CC:
(none) =>
olav (In reply to Olav Vitters from comment #1) > Can we kill fuse? To avoid making such a mistake. I'd say not yet. $ urpmq --whatrequires lib64fuse2 | wc -l 46 CC:
(none) =>
jani.valimaa I switched fuse requires in gvfs-fuse to fuse3. Please test with gvfs-1.46.2-1.1.mga8 from core/updates_testing. Assignee:
bugsquad =>
qa-bugs What's interesting is that gvfs meson does check for fuse3, including the version. It shouldn't have accepted only "fuse". Is there some packaging problem in there? (In reply to Olav Vitters from comment #4) > What's interesting is that gvfs meson does check for fuse3, including the > version. It shouldn't have accepted only "fuse". Is there some packaging > problem in there? At some point fuse3 [1] was added as BR. Probably because of build failure. Fuse requires weren't updated to fuse3 when BR was added. [1] https://svnweb.mageia.org/packages/cauldron/gvfs/current/SPECS/gvfs.spec?revision=1427477&view=markup Tested (sort of) in a 64-bit MGA8 Gnome guest. "Sort of" because I know little of using Gnome, and even less of using gvfs. But, pressing on anyway... Checked for installed packages, and found that gvfs-fuse was installed, as was fuse, but fuse3 was not. Since there is no package list here, I used the list at http://madb.mageia.org/tools/listRpmsForQaBug/bugnum/28655/application/0 in qarepo to download the rpms to be updated: gvfs-1.46.2-1.1.mga8.x86_64.rpm gvfs-archive-1.46.2-1.1.mga8.x86_64.rpm gvfs-devel-1.46.2-1.1.mga8.x86_64.rpm gvfs-fuse-1.46.2-1.1.mga8.x86_64.rpm gvfs-goa-1.46.2-1.1.mga8.x86_64.rpm gvfs-google-1.46.2-1.1.mga8.x86_64.rpm gvfs-gphoto2-1.46.2-1.1.mga8.x86_64.rpm gvfs-iphone-1.46.2-1.1.mga8.x86_64.rpm gvfs-mtp-1.46.2-1.1.mga8.x86_64.rpm gvfs-smb-1.46.2-1.1.mga8.x86_64.rpm ----------------------------------------- The following 10 packages are going to be installed: - fuse3-3.10.1-1.mga8.x86_64 - gvfs-1.46.2-1.1.mga8.x86_64 - gvfs-archive-1.46.2-1.1.mga8.x86_64 - gvfs-fuse-1.46.2-1.1.mga8.x86_64 - gvfs-goa-1.46.2-1.1.mga8.x86_64 - gvfs-google-1.46.2-1.1.mga8.x86_64 - gvfs-gphoto2-1.46.2-1.1.mga8.x86_64 - gvfs-iphone-1.46.2-1.1.mga8.x86_64 - gvfs-mtp-1.46.2-1.1.mga8.x86_64 - gvfs-smb-1.46.2-1.1.mga8.x86_64 Note that fuse3 is being pulled in, indicating that it is a new dependency. No installation issues. Ran Nautilus afterward, as it is dependent on gvfs, and was able to mount and access an Android phone, but I don't know enough about gvfs to know if it was being used. That's as far as I can go. Giving it an OK anyway, as I did verify the new dependency, and at least Nautilus still seems to work. Validating. Still needs an advisory. Keywords:
(none) =>
validated_update Advisory: ======================== Updated gvfs-fuse packages add fuse3 dependency: The updated gvfs-fuse packages now depend on fuse3. References: https://bugs.mageia.org/show_bug.cgi?id=28655 ======================== Updated packages in 8/core/updates_testing: ======================== gvfs-1.46.2-1.1.mga8 gvfs-archive-1.46.2-1.1.mga8 gvfs-devel-1.46.2-1.1.mga8 gvfs-fuse-1.46.2-1.1.mga8 gvfs-goa-1.46.2-1.1.mga8 gvfs-google-1.46.2-1.1.mga8 gvfs-gphoto2-1.46.2-1.1.mga8 gvfs-iphone-1.46.2-1.1.mga8 gvfs-mtp-1.46.2-1.1.mga8 gvfs-smb-1.46.2-1.1.mga8 SRPMs from ======================== gvfs-1.46.2-1.1.mga8.src.rpm CC:
(none) =>
ouaurelien An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2021-0072.html Status:
NEW =>
RESOLVED |