Assaph, Instead of repeatedly slandering the Debian packagers, it would be more constructive to actually study the problem and understand what's going on.
http://bugs.debian.org/330400 This bug is resolved in Debian's rails since September of last year. Unfortunately, the instiki tarball forces you to use the rails packaged with it, so that if you have ruby >= 1.8.3, Instiki breaks. This is not Debian's fault. It's a consequence of Instiki not keeping up with current versions of ruby and rails. See: http://dev.rubyonrails.org/ticket/2245 So there you have it, plain and simple. The Debian packagers aren't incompetent, as you suppose. Finally, if you read the fine print, http://instiki.org/show/Debian (or at least the cached copy at Google, since the site seems to be down right now) even mentions this problem and suggests a workaround, though I can understand if you've missed it, as it is scanty on details: From what I understand ruby1.8.3+ breaks things. I had to specifically install ruby1.8.2 (ruby1.8=1.8.2-7sarge2) —Timcad I'd love to take my rough pre-packaging work on instiki and tidy it up into a proper package for Debian, but I'm a bit reluctant to make a go of it on my own with upstream development in a shambles. However, if there were others interested in making it happen, I'd certainly be happy to help collaboratively maintain it. Ben (aka. synrg at debian dot org -- not a Ruby maintainer, though) _______________________________________________ Instiki-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/instiki-users
