Activity log for bug #64371

Date Who What changed Old value New value Message
2006-10-06 15:41:59 digger vermont bug added bug
2006-11-24 08:38:01 Sebastian Dröge mono: status Unconfirmed Rejected
2006-11-24 08:38:01 Sebastian Dröge mono: statusexplanation Please install libmono-cairo2.0-cil to fix this build failure
2006-11-24 09:04:38 Sebastian Dröge mono: status Rejected Confirmed
2006-11-24 09:04:38 Sebastian Dröge mono: importance Undecided Medium
2006-11-24 09:04:38 Sebastian Dröge mono: statusexplanation Please install libmono-cairo2.0-cil to fix this build failure Ok, this is more a bug in gtk# and mono. gtk#'s pkgconfig file should just include the mono-cairo one. And mono should ship two pkg-config files for Mono.Cairo, one 1.0 and one 2.0 which specify the complete path to the assembly instead of just doing -r:Mono.Cairo When you do -r:something it will only look in /usr/lib/mono/[12].0, depending on with which compiler you build
2006-11-24 09:06:43 Sebastian Dröge mono: statusexplanation Ok, this is more a bug in gtk# and mono. gtk#'s pkgconfig file should just include the mono-cairo one. And mono should ship two pkg-config files for Mono.Cairo, one 1.0 and one 2.0 which specify the complete path to the assembly instead of just doing -r:Mono.Cairo When you do -r:something it will only look in /usr/lib/mono/[12].0, depending on with which compiler you build Please see bug #65238 for the mono part of this
2006-11-24 09:20:41 Sebastian Dröge bug assigned to mono (upstream)
2006-11-24 09:25:39 Sebastian Dröge gtk-sharp2: statusexplanation Please see bug #65238 for the mono part of this Ok, so this is a bug in f-spot instead. It should use Mono.Cairo's pkg-config file instead of using -r:Mono.Cairo. I'll file this bug upstream (same happens for banshee btw).
2006-11-24 09:25:52 Sebastian Dröge bug assigned to banshee (Ubuntu)
2006-11-24 09:26:15 Sebastian Dröge mono: status Unconfirmed Rejected
2006-11-24 09:26:24 Sebastian Dröge banshee: status Unconfirmed Confirmed
2006-11-24 09:26:24 Sebastian Dröge banshee: statusexplanation
2006-11-24 09:30:58 Sebastian Dröge bug assigned to banshee (upstream)
2006-11-24 09:31:20 Sebastian Dröge bug assigned to f-spot (upstream)
2006-11-24 14:26:23 Bug Watch Updater banshee: status Unknown Unconfirmed
2006-11-24 14:26:23 Bug Watch Updater f-spot: status Unknown Unconfirmed
2006-11-26 15:52:49 Bug Watch Updater banshee: status Unconfirmed Needs Info
2006-11-26 23:59:30 Sebastian Dröge banshee: status Confirmed Rejected
2006-11-26 23:59:30 Sebastian Dröge banshee: statusexplanation Ok, the banshee part of this was invalid... the f-spot part is still valid
2006-11-27 00:40:14 Sebastian Dröge mono: status Rejected Unknown
2006-11-27 12:14:42 Bug Watch Updater mono: status Unknown Confirmed
2006-11-28 11:39:37 Bug Watch Updater banshee: status Needs Info Rejected
2006-11-28 11:39:37 Bug Watch Updater f-spot: status Unconfirmed Rejected
2007-01-01 11:18:59 Bug Watch Updater mono: status Confirmed Rejected
2007-02-22 04:39:41 Andrew Mitchell f-spot: status Confirmed Rejected
2007-02-22 04:39:41 Andrew Mitchell f-spot: statusexplanation Ok, so this is a bug in f-spot instead. It should use Mono.Cairo's pkg-config file instead of using -r:Mono.Cairo. I'll file this bug upstream (same happens for banshee btw). No longer relevant with recent f-spot releases.
2007-05-20 07:16:32 Bug Watch Updater mono: status Rejected Confirmed
2007-06-09 10:13:37 Sebastian Dröge f-spot: status Rejected Confirmed
2007-06-09 10:13:37 Sebastian Dröge f-spot: statusexplanation No longer relevant with recent f-spot releases.
2007-06-09 10:14:41 Sebastian Dröge bug assigned to mono (Debian)
2007-06-18 07:38:51 Bug Watch Updater mono: status Unknown Confirmed
2008-09-15 05:59:12 Daniel T Chen mono: status Confirmed Incomplete
2008-09-15 05:59:12 Daniel T Chen mono: statusexplanation Is this symptom still reproducible in 8.10 alpha?
2008-09-15 23:02:56 Jo Shields mono: status Incomplete Fix Released
2008-09-15 23:02:56 Jo Shields mono: statusexplanation Is this symptom still reproducible in 8.10 alpha? No, not remotely. This is a problem with the runtime lib remapper in antique Mono releases. It's never been an issue in Intrepid.
2010-09-15 18:45:40 Bug Watch Updater f-spot: status Invalid Unknown
2010-09-15 18:45:40 Bug Watch Updater f-spot: importance Unknown High
2010-09-16 00:50:28 Bug Watch Updater banshee: importance Unknown High