On 27/12/13 14:30, Kurt Roeckx wrote:
I'm not sure what ruby is trying to do with it, it probably shouldn't be trying to do whatever it's doing.
You're most likely right; I just wanted to ensure this wasn't an issue for other upstream sources out there. I didn't expect builds to break while using the same version/different debian revision of a library.
Anyway, I'll trust your judgement: feel free to close this bug with a WONTFIX or a DONTDOTHATTHEN or something :)
-- M -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
