On Tue, Apr 08, 2014 at 17:29 +0300, Jaakko Niemi wrote: > Any news on this? We have now nasty situation as leiningen is broken > in testing, and fix is in unstable, but that won't go in because of it's > depending on clojure-contrib, which depends on clojure1.2, which is > broken on building and won't go in because of clojure1.4 which has > the fix on dependencies. > > Is there help needed for 2.x ? > > > I'll correct myself. leiningen was removed from testing, but somehow I ended > up installing it on my testing os. > > Recent version of leiningen upstream depends on clojure 1.6, which is not > packaged yet. There's also major churn going on on dependencies: > > http://dev.clojure.org/display/community/Where+Did+Clojure.Contrib+Go
Yes, leiningen has been removed from testing and the new version has not been packaged as it requires the packaging of a plethora of additional libraries that weren't necessary for leiningen 1.7.* - I hope to package them soon, but until then I would recommend to use leiningen from upstream. -- Wolodja <deb...@babilen5.org> 4096R/CAF14EFC 081C B7CD FF04 2BA9 94EA 36B2 8B7F 7D30 CAF1 4EFC
signature.asc
Description: Digital signature
