Comment # 35 on bug 1013047 from Imobach Gonzalez Sosa

The problem with yast2-schema is that we need to rebuild it everytime a YaST2
package changes. I've tried to rebuild the package today and I got the
following list of errors:

90:49: error: element "partition_alignment" not allowed here; expected the
element end-tag or element "btrfs_set_default_subvolume_name" or
"start_multipath"
632:31: error: element "peers" not allowed here; expected the element end-tag
or element "ntp_servers" or "ntp_sync"
720:35: error: element "restricts" not allowed here; expected the element
end-tag or element "ntp_servers" or "ntp_sync"
802:42: error: element "start_at_boot" not allowed here; expected the element
end-tag or element "ntp_servers" or "ntp_sync"
803:44: error: element "start_in_chroot" not allowed here; expected the element
end-tag or element "ntp_servers" or "ntp_sync"
804:42: error: element "sync_interval" not allowed here; expected the element
end-tag or element "ntp_servers" or "ntp_sync"
805:45: error: element "synchronize_time" not allowed here; expected the
element end-tag or element "ntp_servers" or "ntp_sync"

The partition_alignment element is not used anymore. And about the rest of
errors, they are related to the ntp-client configuration, that has changed.

Perhaps we should bump the yast2-schema version to make sure that it gets
properly rebuild.