Recently support for the NILFS2 file-system was introduced in libstorage-ng. As a result, a new value was introduced for the so-called "storage features". See https://github.com/openSUSE/libstorage-ng/pull/874
yast-storage-ng contains a unit test to detect that situation and stop building when a new unknown feature is introduced. As expected, the unit test is failing now.
Solution
Adapt yast-storage-ng to correctly handle the new support for NILFS2, requesting the corresponding package if NILFS2 is used in the system and the package is available.
Coverage remained the same at 97.821% when pulling 08bf6767cfd9ca53f262e48b9333e42f2b81e298 on ancorgs:nilfs2 into 76777706f6648459391309fc3ce38e7c595489d5 on yast:master.
Problem
Recently support for the NILFS2 file-system was introduced in libstorage-ng. As a result, a new value was introduced for the so-called "storage features". See https://github.com/openSUSE/libstorage-ng/pull/874
yast-storage-ng contains a unit test to detect that situation and stop building when a new unknown feature is introduced. As expected, the unit test is failing now.
Solution
Adapt yast-storage-ng to correctly handle the new support for NILFS2, requesting the corresponding package if NILFS2 is used in the system and the package is available.