It seems that some spins have their own bookmarks and their spec files
Before each release someone needs to verify that these conflicts are
properly set and that a particular spin is not missing a Conflicts
which others have entailed into their spec files.
However the best solution should be keeping the bookmarks (in this
case) of the spin dependencies. But this needs a further
Is there already a wiki page which defines such critical paths between spins ?
Any thoughts which can lead to some constructive guidelines (that can
be validated by FESCo) ?