On Wed, May 06, 2015 at 11:39:38AM +0530, Pirate Praveen wrote: > On Monday 04 May 2015 10:59 PM, Antonio Terceiro wrote: > > what exacty did you put in vendor/gems? > > I put the Gemfile directly without extracting. > > > To be clear, you need (in Gemfile) > > > > gem "bootstrap-sass", path: 'vendor/gems/bootstrap-sass' > > That was not working, so I thought of just giving vendor/gems. Even > though bundler could find it sprockets could not. > > > then you need to have a copy of bootstrap-sass, at the version it > > expects, extracted into vendor/gems/bootstrap-sass/ > > After extracting the contents, it is working now. > > > the patch I was able to in the repository modifies the Gemfile but does > > not put anything else in place ... > > I will create a diaspora-gems-compat package to install the offending > gems. That way I don't have to fiddle with diaspora source much and it > makes things flexible. Adding packages to the Debian archive to then request them to be removed s short while later imposes an overhead on other people, why don't you just embed those on the diaspora package itself for now? In your place, I would just ship them under debian/ in the source package and install to the right location. When you are able to drop them, just remove them from debian/ and remove their installation bits ... -- Antonio Terceiro <terceiro@debian.org>
Attachment:
signature.asc
Description: Digital signature