Multilib issue with hard-coded paths in mash script

Christian Krause chkr at
Sat Nov 6 23:43:42 UTC 2010


During the F14 release cycle gtk2 was updated from 2.20.x to 2.22.x.
During this change gdk-pixbuf2 was split off into a separate package and
the location of the gdk-pixbuf loaders has changed from:

F13: /usr/lib/gtk-2.0/2.10.0/loaders/
F14: /usr/lib/gdk-pixbuf-2.0/2.10.0/loaders

This caused now some strange effects due to the hard-coded paths in the
mash script for creating the x86_64 repository:

>From mash/mash/
            if fnmatch(dirname, '/usr/lib*/gtk-2.0/*/loaders'):
                return True

So in F13 the mash script picked up all i686 packages which provided
gdk-pixbuf loaders.

In F14 the script does not pick them up anymore (because of the changed
path) and so the i686 versions of some loaders are missing in the x86_64

This has now caused e.g. the following bug .

The whole issue raises now some questions:

1. Specifically with respect to the problem with gdk-pixbuf: Should the
gdk-pixbuf loaders be multilib or not? If yes, the mash script must be

2. Should the mash script be reviewed whether there are any other
hard-coded paths outdated? Should the script even be Fedora release

Best regards,

More information about the devel mailing list