Well, yes. It's a project of it's own right. I still think it's not very clever to put a helper binary that is exclusively used by libstorage into parted and then even install it into $PATH. Esp when there is another project with the same name (even when this one came later). However, I do not have the bandwidth to pester all affected parties until they do the right thing right now.
Hmm, I could move the binary to /usr/bin so it doesn't conflict with our fatresize in /usr/sbin though :)
We do not know whether it is exclusively used by libstorage-ng. Just changing fatresize would break compatibility. It is not so easy to say what the right thing is.
also https://github.com/yast/yast-storage-ng/issues/1357
@WernerFink, @a_jaeger, @dirkmueller, @dmolkentin, @msmeissn, @oertel, @seife, @trenn: review reminder
@lnussel is this still relevant after sr#1114024 has been declined?
Well, yes. It's a project of it's own right. I still think it's not very clever to put a helper binary that is exclusively used by libstorage into parted and then even install it into $PATH. Esp when there is another project with the same name (even when this one came later). However, I do not have the bandwidth to pester all affected parties until they do the right thing right now. Hmm, I could move the binary to /usr/bin so it doesn't conflict with our fatresize in /usr/sbin though :)
We do not know whether it is exclusively used by libstorage-ng. Just changing fatresize would break compatibility. It is not so easy to say what the right thing is.