-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replace exfat-utils with exfatprogs #1214
Comments
https://build.opensuse.org/request/show/883333 by user favogt + RBrownSUSE - Switch from exfat-utils to exfatprogs, see also gh#yast/yast-storage-ng#1214 (forwarded request 883332 from favogt)
As far as I can see in a quick check:
So switching to exfatprogs looks like a safe bet. Having said so, do you have any pointer to the explanation about why exfat-utils was dropped in 15.3? |
The explanation is that SP3 already had exfatprogs. So there's not much substance behind that reasoning... |
According to https://lore.kernel.org/lkml/[email protected]/, they're both the same project, but looking at git, exfat-utils is something different. At least I'm even more confused now. |
Both packages provide binaries in But there is an important difference. The package exfat-utils also provides symlinks at So before changing this in yast2-storage-ng, we should adapt libstorage-ng to use the binaries at @aschnell Am I right? |
Yes, using /usr/sbin should work for both packages. But users setting mkfs option might face compatibility problems since the tools have different options. |
Now tracked at https://bugzilla.suse.com/show_bug.cgi?id=1184489 and (for the YaST team) at https://trello.com/c/N7gz5WP0/ |
@ancorgs, considering that https://bugzilla.suse.com/show_bug.cgi?id=1184489 is |
I will check. |
This is only fixed in the libstorage-ng side (which was the critical part). But YaST would still try to add |
exfat-utils was apparently replaced by exfatprogs, and SLE doesn't even have the former.
yast-storage-ng/src/lib/y2storage/storage_feature.rb
Line 78 in e505276
The text was updated successfully, but these errors were encountered: