The package contains conflicting -devel packages for multilib arches. libgsf-devel-1.14.1-2.i386.rpm Preparing... ################################################## file /usr/share/gtk-doc/html/gsf/GsfClipData.html from install of libgsf -devel-1.14.1-2 conflicts with file from package libgsf-devel-1.14.1-2 file /usr/share/gtk-doc/html/gsf/gsf-Bononbo.html from install of libgsf -devel-1.14.1-2 conflicts with file from package libgsf-devel-1.14.1-2 file /usr/share/gtk-doc/html/gsf/gsf-Compression.html from install of li bgsf-devel-1.14.1-2 conflicts with file from package libgsf-devel-1.14.1-2 file /usr/share/gtk-doc/html/gsf/gsf-GIOChannel.html from install of lib gsf-devel-1.14.1-2 conflicts with file from package libgsf-devel-1.14.1-2 file /usr/share/gtk-doc/html/gsf/gsf-GnomeVFS.html from install of libgs f-devel-1.14.1-2 conflicts with file from package libgsf-devel-1.14.1-2 file /usr/share/gtk-doc/html/gsf/gsf-Infile-reading-structed-files.html from install of libgsf-devel-1.14.1-2 conflicts with file from package libgsf-de vel-1.14.1-2 (etc for all gtk-doc)
Is there a fix design-pattern for this, i.e. is it something that afflicts all gtk-doc using stuff like gtk itself and should be fixed in gtk-doc, or something specific to libgsf ?
The best practice for gtk-doc using stuff (according to mclasen) is that the generated gtk-doc should be shipped within the upstream tarball. The root of the problem is that gtk-doc uses jade to generate the html and jade doesn't generate consistent anchors in the html. And fixing that is ... non-trivial.
doh, spec actually configures with --enable-gtk-doc, easyfix methinks.