On Sun, 20 Apr 2014 12:56:30 Jonas Smedegaard wrote: > Bug arguably is at both packages (but I maintain both, so no need for > further BTS ping-pong):
Sorry, I didn't check who maintain those packages. My intention was merely to assign bug to the right package. My impression is that the problem is in "ruby-sass" package because updating it broke "ruby-compass" which (unlike "ruby-sass") was not updated recently. > I suspect this problem to be caused not by changes to ruby-sass code (it > was upgraded), but instead to change of default Ruby version. > > I guess this could be solved by a simple binNMU of ruby-compass. I re-built "ruby-compass" in "unstable" but it did not fix the problem. > Also there is a new major release of Compass that I want to > upgrade to - i.e. my plan is to do a source-full release instead and > expect that to magically solve this issue. I also hope that new upstream release of "ruby-compass" will fix the problem. Until then we're stuck with broken `compass` unfortunately... -- Regards, Dmitry Smirnov.
signature.asc
Description: This is a digitally signed message part.
