Installing f-spot on armel installs a load of Win32 PE executables (.exe, .dll) and seems to rely on executing these to work.
dpkg prints out a load of "illegal instruction" errors when trying to configure the package, but the package is erroneously marked as successfully configured after installation.
It looks like f-spot and related packages (*mono* etc.) should not be packaged for armel at all, or ARM-targeted binaries need to be built (if this is supported by the source packages; apparently, mono can support ARM but I don't have much experience of these packages).
Binary package hint: f-spot
Installing f-spot on armel installs a load of Win32 PE executables (.exe, .dll) and seems to rely on executing these to work.
dpkg prints out a load of "illegal instruction" errors when trying to configure the package, but the package is erroneously marked as successfully configured after installation.
It looks like f-spot and related packages (*mono* etc.) should not be packaged for armel at all, or ARM-targeted binaries need to be built (if this is supported by the source packages; apparently, mono can support ARM but I don't have much experience of these packages).
The affected binary packages seem to be: 1.5-cil keyring1. 0-cil vfs2.24- cil addins0. 2-cil addins- gui0.2- cil cairo2. 0-cil corlib2. 0-cil data-tds2. 0-cil getoptions2. 0-cil posix2. 0-cil security2. 0-cil sharpzip2. 84-cil sqlite2. 0-cil system2. 0-cil system- data2.0- cil system- web2.0- cil dbus1.0- cil dbus-glib1. 0-cil
f-spot
libart2.24-cil
libflickrnet2.
libgconf2.24-cil
libglade2.0-cil
libglib2.0-cil
libgnome2.24-cil
libgnome-
libgnome-
libgtk2.0-cil
libmono2.0-cil
libmono-
libmono-
libmono-
libmono-
libmono-data2.0-cil
libmono-
libmono-
libmono-i18n2.0-cil
libmono-
libmono-
libmono-
libmono-
libmono-
libmono-
libmono-
libndesk-
libndesk-
mono-2.0-gac