On Thu, 2010-03-04 at 09:13 +0000, Jo Shields wrote: > On Thu, 2010-03-04 at 10:01 +0100, Mathieu Malaterre wrote: > > On Wed, Mar 3, 2010 at 3:03 PM, Mathieu Malaterre > > <email@example.com> wrote: > > > > > > > > > On Tue, Mar 2, 2010 at 9:52 PM, Jo Shields <firstname.lastname@example.org> wrote: > > >> > > >> I notice you're pulling in MonoDevelop in its entireity as a > > >> build-depend, which is a little odd... does it really not build with > > >> xbuild? If not, can you file a bug with the Mono folks, because it > > >> ought to... > > > > > > Done: > > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=572337 > > > > Forwarded to: > > https://bugzilla.novell.com/show_bug.cgi?id=558739 > > -> Seems to have been fixed in mono svn trunk > > > > So upload is frozen until the next upload of mono-xbuild ? > > I'll try to find time this weekend to backport the fix Okay, I've spoken with the xbuild author, and there's an easy fix (which I've tested). On your (commented out) xbuild build line, stick MONO_IOMAP=all at the start of the line. This will cause mono to ignore all instances of incorrect casing (e.g. readme.txt being called ReadMe.txt in the build file, or similar) and instances of bad path separators (/ versus \). And it builds fine, without pulling in all of MonoDevelop and all related cruft. Update your mentor package to use this, and I'll upload it.
Description: This is a digitally signed message part