Just because something is abandoned, doesn't mean it no longer works. And just because one person (until JUST NOW) has a problem, doesn't mean a packaged gets removed.
The proper solution is to get python-pylibzfs building so that the new cockpit-zfs program can be built. THEN we can turn around and delete this project as obsolete, or migrate it to the new one. I personally use this project myself. Mostly to just monitor. Cockpit as a whole can be a jank management platform. Should we remove all of cockpit just because I have some problems with it? No. Same here. On 6/19/26 5:13 PM, [email protected] wrote:
hyperreal64 [1] filed a deletion request for cockpit-zfs-manager [2]: If an upstream component is abandoned then I'd say it would be best to delete this package from the AUR. I recall having the same issue as user mao58912 in the comments when I was trying to install it on Debian a while back. Attempting to install this will irreparably bork your system. Not a good idea to keep it in the AUR at all, let alone as flagged out of date or orphaned. [1] https://aur.archlinux.org/account/hyperreal64/ [2] https://aur.archlinux.org/pkgbase/cockpit-zfs-manager/
