This package should probably require initscripts-service instead of the full initscripts package. Is there any specific reason this can not be made to work with systemd? The commit doesn't have any details: https://src.fedoraproject.org/rpms/zfs-fuse/c/8972bd8b18fc3aaf6420e58cdf4ffbb78322c15f?branch=rawhide Reproducible: Always
This actually needs the initscripts package, as the zfs-fuse-helper script that allows it to work with systemd sources /etc/rc.d/init.d/functions. It's been using systemd in this way since 2012.
Let's reopen this. The problem right now is that I am forced to have zfs-fuse installed if I want to use virtualization. This makes me sad because we (initscripts maintainers) spent a lot of time getting it out from the most used installations. Can't we just rewrite the starting script? I would be to help with that, although I know nothing about zfs, so I probably would not be able to verify that the changes are not breaking anything.
If you're interested, it's here: https://src.fedoraproject.org/rpms/zfs-fuse/blob/rawhide/f/zfs-fuse-helper
(In reply to Gwyn Ciesla from comment #3) > If you're interested, it's here: > https://src.fedoraproject.org/rpms/zfs-fuse/blob/rawhide/f/zfs-fuse-helper It seems like this could be re-written just as a stand-alone bash script, but -- probably better to actually properly make a systemd unit file. I'm not a ZFS user either, though, so this also isn't something I should touch.
It's already a bash script called by a unit file... I'm not a ZFS expert either, I just kept it working and ported it, albeit in an ugly way, to systemd.
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21. Fedora Linux 38 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.
We still have a dependency on initscripts in Rawhide: https://src.fedoraproject.org/rpms/zfs-fuse/blob/rawhide/f/zfs-fuse.spec#_33
This bug appears to have been reported against 'rawhide' during the Fedora Linux 42 development cycle. Changing version to 42.
(I couldn't care less about ZFS. I only noticed this issue because zfs-fuse is the only package requiring initscripts on my mostly default install. I'll keep it short.) - zfs-fuse is unmaintained for a decade now - A decade ago it apparently didn't fully cover all zfs functionality - zfs is in (pretty) active development Why do we care about an unmaintained, outdated and partial user userspace implementation of a filesystem that has very little chance of ever being properly supported by Fedora? TL;DR: please orphan this package.
Are libguestfs-zfs and libvirt-daemon-driver-storage also ready to be orphaned?
(In reply to Gwyn Ciesla from comment #10) > Are libguestfs-zfs and libvirt-daemon-driver-storage also ready to be > orphaned? Yes, my request means libguestfs-zfs needs to be orphaned too (as it seems to be a wrapper around zfs-fuse). libvirt-daemon-driver-storage "only" needs to drop one of its dependencies. What is the procedure to draw the maintainers of those packages into this discussion?
File bugs against those components, have them block this bug, and in them, ask their opinion.
See bug #2363143 (libvirt covers both components).
If zfs-fuse is going away then we can drop the libguestfs-zfs subpackage.
(Richard, thanks for commenting. Not sure why I thought libguestfs was covered by libvirt.) Perhaps I should have asked to retire this package, as that is the procedure for packages no longer useful for Fedora. Anyhow, both the maintainers of libvirt and libguestfs reported - within hours! - that they'll accept any decision made by about zfs-fuse. If it would be considered helpful for a decision to retire, I'm happy to back up my assertions on the state of zfs-fuse: unmaintained, partial and outdated.
I have queued up a commit to remove the libguestfs-zfs subpackage entirely, which will remove the zfs-fuse dependency. It's waiting on a libguestfs upstream release.
Ok. Let me know when you're ready, and I'll retire zfs-fuse for f43+.
There seems no reason to delay, so this build should remove the zfs-fuse dependency: https://koji.fedoraproject.org/koji/taskinfo?taskID=132438524
Retired. Thanks all!
Note that libvirt has a storage backend for zfs which is broken by this, which caused rawhide compose to fail. ;( See: https://pagure.io/releng/failed-composes/issue/8177
(Please note I'm not familiar with the infrastructure behind rawhide nor with handling packages. I just commented on this bug.) Note that libvirt is OK with zfs-fuse being retired: https://bugzilla.redhat.com/show_bug.cgi?id=2363143#c1 But apparently this could have been coordinated somewhat better. Would the quickest resolution be to get libvirt drop their zfs storage backend? If so, who should do that?