Bug#858195: compass-bootstrap-sass-plugin: Wrong install path, and code not registered with Compass

[Jonas Smedegaard]

Quoting Antonio Terceiro (2017-03-29 17:42:33)
> Control: severity -1 important
> 
> On Wed, Mar 29, 2017 at 03:51:50PM +0200, Jonas Smedegaard wrote:
> > Quoting Antonio Terceiro (2017-03-28 20:01:37)
> > > Control: severity -1 wishlist
> > [...]
> > > While I agree with you that it _could_ work transparently, there 
> > > is nothing broken in the package. And I don't think this is 
> > > something we should be doing different from upstream.
> > 
> > Do you still believe there was nothing broken in the package?
> 
> No. Actually, it was _you_ who said that the original invocation as 
> documented by upstream worked with the version in testing:
> 
> $ compass create --using bootstrap-sass --require bootstrap-sass
> 
> I tested that again, and it turns out it doesn't.

I do not recognize having said that.  It helps if you quote the exact 
text you are referring to.


>> Please consider acknowledging that the former path was buggy, so that 
>> there is a chance of getting a fix included with Stretch.
> 
> Sure. I was going to request an unblock either way.

Thanks.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Bug#858195: compass-bootstrap-sass-plugin: Wrong install path, and code not registered with Compass

[Antonio Terceiro]

Control: severity -1 important

On Wed, Mar 29, 2017 at 03:51:50PM +0200, Jonas Smedegaard wrote:
> Quoting Antonio Terceiro (2017-03-28 20:01:37)
> > Control: severity -1 wishlist
> [...]
> > While I agree with you that it _could_ work transparently, there is 
> > nothing broken in the package. And I don't think this is something we 
> > should be doing different from upstream.
> 
> Do you still believe there was nothing broken in the package?

No. Actually, it was _you_ who said that the original invocation as
documented by upstream worked with the version in testing:

$ compass create --using bootstrap-sass --require bootstrap-sass

I tested that again, and it turns out it doesn't.

> Please consider acknowledging that the former path was buggy, so that 
> there is a chance of getting a fix included with Stretch.

Sure. I was going to request an unblock either way.


signature.asc
Description: PGP signature

Bug#858195: compass-bootstrap-sass-plugin: Wrong install path, and code not registered with Compass

[Jonas Smedegaard]

Quoting Antonio Terceiro (2017-03-28 20:01:37)
> Control: severity -1 wishlist
[...]
> While I agree with you that it _could_ work transparently, there is 
> nothing broken in the package. And I don't think this is something we 
> should be doing different from upstream.

Do you still believe there was nothing broken in the package?

Please consider acknowledging that the former path was buggy, so that 
there is a chance of getting a fix included with Stretch.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Bug#858195: compass-bootstrap-sass-plugin: Wrong install path, and code not registered with Compass

[Antonio Terceiro]

On Wed, Mar 29, 2017 at 10:21:26AM +0200, Jonas Smedegaard wrote:
> Quoting Antonio Terceiro (2017-03-29 03:16:32)
> > That said, I am willing to support this, but I don't agree it's an RC 
> > issue.
> > 
> > I tried changing /usr/share/compass/frameworks/bootstrap-sass to 
> > /usr/share/compass/frameworks/bootstrap as you said, but that doesn't 
> > exactly make it work:
> [...]
> 
> > Any ideas?
> 
> Attached patch is what I use.  It might not apply as-is - I use it 
> together with a couple other patches to address the other issues 
> mentioned initially in this bugreport about the odd packaging into two 
> binary packages.

Ah, I see. this patch is needed to workaround the "old" Ruby
installation layout. Most Ruby packages nowadays, specially the ones
related to static assets, kind of assume the Rubygems layout, which is
supported by our tools, and could even be the default at some point.

If you need similar patches in all compass packages, you might be
interested in switching to the Rubygems layout. With that you just
symlink the Rubygems package location into the compass directory and
things just work. Something link this:

version = $(shell dpkg-parsechangelog -SVersion | cut -d - -f 1)

override_dh_auto_install:
dh_auto_install
dh_link -p compass-bootstrap-sass-plugin \

/usr/share/rubygems-integration/all/gems/bootstrap-sass-$(version) \
/usr/share/compass/frameworks/bootstrap-sass

That could even be modularized in a dh_compass_plugin or something like that.

I will upload a fixed version soon. Note however that the name of the package
is bootstrap-sass, and that -sass suffix is needed to make things just work.
Changing that would require renaming stuff under lib/, what would not be
sane. The correct usage is:

compass create myproject --using bootstrap-sass


> Would you perhaps be interested in moving this package to the Sass team,
> and maintain the package there?  That helps coordinate the interaction
> between the Sass/Compass libraries (Compass is dead upstream, so there
> will likely soon be some restructuring to relax dependencies).
>
> I can also offer to take over maintenance of this package, if you don't
> mind that move but are not interested in joining that other team.

It's used by other Ruby packages, so I would rather have it stay in the Ruby
team.


signature.asc
Description: PGP signature

Bug#858195: compass-bootstrap-sass-plugin: Wrong install path, and code not registered with Compass

[Jonas Smedegaard]

Quoting Antonio Terceiro (2017-03-29 03:16:32)
> On Tue, Mar 28, 2017 at 10:20:30PM +0200, Jonas Smedegaard wrote:
>> Debian use /usr/share/compass as _shared_ location for Compass 
>> libraries - upstream has no such default location.
>> 
>> Your reasoning is the equivalent of installing C libraries in 
>> /usr/lip and arguing that one should always explicitly feed the 
>> compiler the path (not rely on default path being /usr/lib on Debian 
>> systems).
>
> I disagree with your analogy. There is a set of well known places 
> where you can put libraries so that compilers find them automatically, 
> and those are known to _everyone_ that does or use libraries, not only 
> in Debian.
> 
> In this case, there is a convention that only exists in Debian, and 
> AFAICT forces every single package to be patched. Is there any 
> movement in the direction of having this adopted upstream?

Compass does not dictate which locations should be looked up by default 
but certainly provides the mechanism for default lookup paths - and that 
mechanism is used in the Debian packaging of Compass.

You may try argue that compass-bootstrap-sass-plugin provides a 
_private_ library, not intended for general use.  But that makes little 
sense to me.


> That said, I am willing to support this, but I don't agree it's an RC 
> issue.
> 
> I tried changing /usr/share/compass/frameworks/bootstrap-sass to 
> /usr/share/compass/frameworks/bootstrap as you said, but that doesn't 
> exactly make it work:
[...]

> Any ideas?

Attached patch is what I use.  It might not apply as-is - I use it 
together with a couple other patches to address the other issues 
mentioned initially in this bugreport about the odd packaging into two 
binary packages.

Would you perhaps be interested in moving this package to the Sass team, 
and maintain the package there?  That helps coordinate the interaction 
between the Sass/Compass libraries (Compass is dead upstream, so there 
will likely soon be some restructuring to relax dependencies).

I can also offer to take over maintenance of this package, if you don't 
mind that move but are not interested in joining that other team.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private
Description: Use shared assets path untied from Ruby library path.
Author: Antonio Terceiro 
Author: Jonas Smedegaard 
Origin: vendor
Forwarded: not-needed
Last-Update: 2017-03-19

--- a/lib/bootstrap-sass.rb
+++ b/lib/bootstrap-sass.rb
@@ -32,7 +32,7 @@
 end
 
 def assets_path
-  @assets_path ||= File.join gem_path, 'assets'
+  @assets_path ||= '/usr/share/compass/frameworks/bootstrap-sass'
 end
 
 # Environment detection helpers
@@ -63,9 +63,9 @@
   ::Compass::Frameworks.register(
   'bootstrap',
   :version   => Bootstrap::VERSION,
-  :path  => gem_path,
+  :path  => assets_path,
   :stylesheets_directory => stylesheets_path,
-  :templates_directory   => File.join(gem_path, 'templates')
+  :templates_directory   => File.join(assets_path, 'templates')
   )
 end
 
--- a/lib/bootstrap-sass/engine.rb
+++ b/lib/bootstrap-sass/engine.rb
@@ -3,7 +3,7 @@
 class Engine < ::Rails::Engine
   initializer 'bootstrap-sass.assets.precompile' do |app|
 %w(stylesheets javascripts fonts images).each do |sub|
-  app.config.assets.paths << root.join('assets', sub).to_s
+  app.config.assets.paths << root.join(sub).to_s
 end
 app.config.assets.precompile << %r(bootstrap/glyphicons-halflings-regular\.(?:eot|svg|ttf|woff2?)$)
   end
--- a/templates/project/manifest.rb
+++ b/templates/project/manifest.rb
@@ -8,7 +8,7 @@
 
 # Copy JS and fonts
 manifest = Pathname.new(File.dirname(__FILE__))
-assets   = File.expand_path('../../assets', manifest)
+assets   = File.expand_path('../..', manifest)
 {:javascript => 'javascripts',
  :font   => 'fonts'
 }.each do |method, dir|


signature.asc
Description: signature

Bug#858195: compass-bootstrap-sass-plugin: Wrong install path, and code not registered with Compass

[Antonio Terceiro]

On Tue, Mar 28, 2017 at 10:20:30PM +0200, Jonas Smedegaard wrote:
> Debian use /usr/share/compass as _shared_ location for Compass libraries 
> - upstream has no such default location.
> 
> Your reasoning is the equivalent of installing C libraries in /usr/lip 
> and arguing that one should always explicitly feed the compiler the path 
> (not rely on default path being /usr/lib on Debian systems).

I disagree with your analogy. There is a set of well known places where
you can put libraries so that compilers find them automatically, and
those are known to _everyone_ that does or use libraries, not only in
Debian.

In this case, there is a convention that only exists in Debian, and
AFAICT forces every single package to be patched. Is there any movement
in the direction of having this adopted upstream?

That said, I am willing to support this, but I don't agree it's an RC issue.

I tried changing /usr/share/compass/frameworks/bootstrap-sass to
/usr/share/compass/frameworks/bootstrap as you said, but that doesn't
exactly make it work:

| $ compass create myproject --using bootstrap
| directory myproject/ 
| directory myproject/fonts/bootstrap/ 
| directory myproject/javascripts/ 
| directory myproject/javascripts/bootstrap/ 
| directory myproject/sass/ 
| directory myproject/stylesheets/ 
|create myproject/config.rb 
|create myproject/sass/styles.scss 
|create myproject/sass/_bootstrap-variables.scss 
|create myproject/javascripts/bootstrap.min.js 
|create myproject/javascripts/bootstrap.js 
|create myproject/javascripts/bootstrap/dropdown.js 
|create myproject/javascripts/bootstrap/collapse.js 
|create myproject/javascripts/bootstrap/modal.js 
|create myproject/javascripts/bootstrap/tooltip.js 
|create myproject/javascripts/bootstrap/transition.js 
|create myproject/javascripts/bootstrap/alert.js 
|create myproject/javascripts/bootstrap/carousel.js 
|create myproject/javascripts/bootstrap/popover.js 
|create myproject/javascripts/bootstrap/button.js 
|create myproject/javascripts/bootstrap/scrollspy.js 
|create myproject/javascripts/bootstrap/affix.js 
|create myproject/javascripts/bootstrap/tab.js 
|create myproject/javascripts/bootstrap-sprockets.js 
|create myproject/fonts/bootstrap/glyphicons-halflings-regular.woff2 
|create myproject/fonts/bootstrap/glyphicons-halflings-regular.woff 
|create myproject/fonts/bootstrap/glyphicons-halflings-regular.eot 
|create myproject/fonts/bootstrap/glyphicons-halflings-regular.svg 
|create myproject/fonts/bootstrap/glyphicons-halflings-regular.ttf 
| error myproject/sass/styles.scss (Line 2: File to import not found or 
unreadable: bootstrap-compass.
| Load paths:
|   Compass::SpriteImporter
|   /tmp/test-compass/myproject/sass
|   /usr/share/compass/frameworks/compass/stylesheets
|   /usr/share/compass/frameworks/bootstrap/stylesheets)
| Compilation failed in 1 files.

^^
note this bit here

| 
| *
| Congratulations! Your compass project has been created.
| 
| You may now add and edit sass stylesheets in the sass subdirectory of your 
project.
| 
| Sass files beginning with an underscore are called partials and won't be
| compiled to CSS, but they can be imported into other sass stylesheets.
| 
| You can configure your project by editing the config.rb configuration file.
| 
| You must compile your sass stylesheets into CSS when they change.
| This can be done in one of the following ways:
|   1. To compile on demand:
|  compass compile [path/to/project]
|   2. To monitor your project for changes and automatically recompile:
|  compass watch [path/to/project]
| 
| More Resources:
|   * Website: http://compass-style.org/
|   * Sass: http://sass-lang.com
|   * Community: http://groups.google.com/group/compass-users/
| 
| 
| To import your new stylesheets add the following lines of HTML (or 
equivalent) to your webpage:
| 
|   
| 

Any ideas?


signature.asc
Description: PGP signature

Bug#858195: compass-bootstrap-sass-plugin: Wrong install path, and code not registered with Compass

[Jonas Smedegaard]

Quoting Antonio Terceiro (2017-03-28 20:01:37)
> Control: severity -1 wishlist
> 
> Hi,
> 
> On Sun, Mar 19, 2017 at 06:13:06PM +0100, Jonas Smedegaard wrote:
> > Package: compass-bootstrap-sass-plugin
> > Version: 3.3.5.1-3
> > Severity: grave
> > Justification: renders package unusable
> > 
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA256
> > 
> > The most basic way to initialize a Compass project using this library
> > should be using the following command:
> > 
> > $ compass create --using bootstrap
> > 
> > That fails, however:
> > 
> > No such framework: "bootstrap"
> > 
> > 
> > Inspecting package contents it turns out that Sass files are shipped
> > twice, none of them below /usr/share/doc/compass-bootstrap-sass-plugin
> > as explected:
> > 
> >   * compass-bootstrap-sass-plugin includes them below
> > /usr/share/compass/frameworks/bootstrap-sass
> >   * ruby-bootstrap-sass ships them below
> > /usr/share/ruby-bootstrap-sass/assets
> > 
> > The correct path would be /usr/share/compass/frameworks/bootstrap - i.e.
> > without the -sass suffix.
> > 
> > Adapting the simplest Compass command for the renamed project path gets
> > further but still fails:
> > 
> > directory fonts/bootstrap/ 
> > directory javascripts/ 
> > directory javascripts/bootstrap/ 
> > directory sass/ 
> > directory stylesheets/ 
> >create config.rb 
> >create sass/styles.scss 
> >create sass/_bootstrap-variables.scss 
> >create javascripts/bootstrap.js 
> >create javascripts/bootstrap.min.js 
> >create javascripts/bootstrap-sprockets.js 
> >create javascripts/bootstrap/carousel.js 
> >create javascripts/bootstrap/popover.js 
> >create javascripts/bootstrap/scrollspy.js 
> >create javascripts/bootstrap/modal.js 
> >create javascripts/bootstrap/transition.js 
> >create javascripts/bootstrap/button.js 
> >create javascripts/bootstrap/alert.js 
> >create javascripts/bootstrap/collapse.js 
> >create javascripts/bootstrap/tab.js 
> >create javascripts/bootstrap/tooltip.js 
> >create javascripts/bootstrap/dropdown.js 
> >create javascripts/bootstrap/affix.js 
> >create fonts/bootstrap/glyphicons-halflings-regular.svg 
> >create fonts/bootstrap/glyphicons-halflings-regular.eot 
> >create fonts/bootstrap/glyphicons-halflings-regular.woff 
> >create fonts/bootstrap/glyphicons-halflings-regular.woff2 
> >create fonts/bootstrap/glyphicons-halflings-regular.ttf 
> > error sass/styles.scss (Line 2: File to import not found or unreadable: 
> > bootstrap-compass.
> > Load paths:
> >   Compass::SpriteImporter
> >   /usr/local/src/COUCH/omni/styling./sass
> >   /usr/share/compass/frameworks/compass/stylesheets
> >   /usr/share/compass/frameworks/blend-modes/stylesheets
> >   /usr/share/compass/frameworks/blueprint/stylesheets
> >   /usr/share/compass/frameworks/bootstrap-sass/stylesheets
> >   /usr/share/compass/frameworks/breakpoint/stylesheets
> >   /usr/share/compass/frameworks/color-schemer/stylesheets
> >   /usr/share/compass/frameworks/fancy-buttons/stylesheets
> >   /usr/share/compass/frameworks/h5bp/stylesheets
> >   /usr/share/compass/frameworks/layoutgala/stylesheets
> >   /usr/share/compass/frameworks/normalize-scss/stylesheets
> >   /usr/share/compass/frameworks/sassy-maps/stylesheets
> >   /usr/share/compass/frameworks/singularitygs/stylesheets
> >   /usr/share/compass/frameworks/slickmap/stylesheets
> >   /usr/share/compass/frameworks/susy/stylesheets
> >   /usr/share/compass/frameworks/toolkit/stylesheets
> >   /usr/share/compass/frameworks/yui/stylesheets)
> > Compilation failed in 1 files.
> > 
> > 
> > This next failure is due to the ruby code is not registering the path
> > with Compass, requiring to do that explicitly:
> > 
> > $ compass create --using bootstrap-sass --require bootstrap-sass
> > 
> > That works.
> > 
> > In short, this Compass library is installed in the wrong path, and its
> > ruby code is not registered with Compass.
> 
> Quoting the bootstrap-sass README:
> 
> | If you are creating a new Compass project, you can generate it with 
> bootstrap-sass support:
> |
> | ```console
> | $ bundle exec compass create my-new-project -r bootstrap-sass --using 
> bootstrap
> | ```
> 
> Ignoring tthe `bundle exec` bit that is not needed with Debian packages,
> you are supposed to use `--require bootstap-sass` explicitly.
> 
> While I agree with you that it _could_ work transparently, there is
> nothing broken in the package. And I don't think this is something we
> should be doing different from upstream.

Debian use /usr/share/compass as _shared_ location for Compass libraries 
- upstream has no such default location.

Your reasoning is the equivalent of installing C libraries in /usr/lip 
and arguing that one should always explicitly feed the compiler the path 
(not rely on default path being /usr/lib on Debian systems).


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  

Bug#858195: compass-bootstrap-sass-plugin: Wrong install path, and code not registered with Compass

[Antonio Terceiro]

Control: severity -1 wishlist

Hi,

On Sun, Mar 19, 2017 at 06:13:06PM +0100, Jonas Smedegaard wrote:
> Package: compass-bootstrap-sass-plugin
> Version: 3.3.5.1-3
> Severity: grave
> Justification: renders package unusable
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> 
> The most basic way to initialize a Compass project using this library
> should be using the following command:
> 
> $ compass create --using bootstrap
> 
> That fails, however:
> 
> No such framework: "bootstrap"
> 
> 
> Inspecting package contents it turns out that Sass files are shipped
> twice, none of them below /usr/share/doc/compass-bootstrap-sass-plugin
> as explected:
> 
>   * compass-bootstrap-sass-plugin includes them below
> /usr/share/compass/frameworks/bootstrap-sass
>   * ruby-bootstrap-sass ships them below
> /usr/share/ruby-bootstrap-sass/assets
> 
> The correct path would be /usr/share/compass/frameworks/bootstrap - i.e.
> without the -sass suffix.
> 
> Adapting the simplest Compass command for the renamed project path gets
> further but still fails:
> 
> directory fonts/bootstrap/ 
> directory javascripts/ 
> directory javascripts/bootstrap/ 
> directory sass/ 
> directory stylesheets/ 
>create config.rb 
>create sass/styles.scss 
>create sass/_bootstrap-variables.scss 
>create javascripts/bootstrap.js 
>create javascripts/bootstrap.min.js 
>create javascripts/bootstrap-sprockets.js 
>create javascripts/bootstrap/carousel.js 
>create javascripts/bootstrap/popover.js 
>create javascripts/bootstrap/scrollspy.js 
>create javascripts/bootstrap/modal.js 
>create javascripts/bootstrap/transition.js 
>create javascripts/bootstrap/button.js 
>create javascripts/bootstrap/alert.js 
>create javascripts/bootstrap/collapse.js 
>create javascripts/bootstrap/tab.js 
>create javascripts/bootstrap/tooltip.js 
>create javascripts/bootstrap/dropdown.js 
>create javascripts/bootstrap/affix.js 
>create fonts/bootstrap/glyphicons-halflings-regular.svg 
>create fonts/bootstrap/glyphicons-halflings-regular.eot 
>create fonts/bootstrap/glyphicons-halflings-regular.woff 
>create fonts/bootstrap/glyphicons-halflings-regular.woff2 
>create fonts/bootstrap/glyphicons-halflings-regular.ttf 
> error sass/styles.scss (Line 2: File to import not found or unreadable: 
> bootstrap-compass.
> Load paths:
>   Compass::SpriteImporter
>   /usr/local/src/COUCH/omni/styling./sass
>   /usr/share/compass/frameworks/compass/stylesheets
>   /usr/share/compass/frameworks/blend-modes/stylesheets
>   /usr/share/compass/frameworks/blueprint/stylesheets
>   /usr/share/compass/frameworks/bootstrap-sass/stylesheets
>   /usr/share/compass/frameworks/breakpoint/stylesheets
>   /usr/share/compass/frameworks/color-schemer/stylesheets
>   /usr/share/compass/frameworks/fancy-buttons/stylesheets
>   /usr/share/compass/frameworks/h5bp/stylesheets
>   /usr/share/compass/frameworks/layoutgala/stylesheets
>   /usr/share/compass/frameworks/normalize-scss/stylesheets
>   /usr/share/compass/frameworks/sassy-maps/stylesheets
>   /usr/share/compass/frameworks/singularitygs/stylesheets
>   /usr/share/compass/frameworks/slickmap/stylesheets
>   /usr/share/compass/frameworks/susy/stylesheets
>   /usr/share/compass/frameworks/toolkit/stylesheets
>   /usr/share/compass/frameworks/yui/stylesheets)
> Compilation failed in 1 files.
> 
> 
> This next failure is due to the ruby code is not registering the path
> with Compass, requiring to do that explicitly:
> 
> $ compass create --using bootstrap-sass --require bootstrap-sass
> 
> That works.
> 
> In short, this Compass library is installed in the wrong path, and its
> ruby code is not registered with Compass.

Quoting the bootstrap-sass README:

| If you are creating a new Compass project, you can generate it with 
bootstrap-sass support:
|
| ```console
| $ bundle exec compass create my-new-project -r bootstrap-sass --using 
bootstrap
| ```

Ignoring tthe `bundle exec` bit that is not needed with Debian packages,
you are supposed to use `--require bootstap-sass` explicitly.

While I agree with you that it _could_ work transparently, there is
nothing broken in the package. And I don't think this is something we
should be doing different from upstream.


signature.asc
Description: PGP signature

Bug#858195: compass-bootstrap-sass-plugin: Wrong install path, and code not registered with Compass

[Jonas Smedegaard]

Package: compass-bootstrap-sass-plugin
Version: 3.3.5.1-3
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

The most basic way to initialize a Compass project using this library
should be using the following command:

$ compass create --using bootstrap

That fails, however:

No such framework: "bootstrap"


Inspecting package contents it turns out that Sass files are shipped
twice, none of them below /usr/share/doc/compass-bootstrap-sass-plugin
as explected:

  * compass-bootstrap-sass-plugin includes them below
/usr/share/compass/frameworks/bootstrap-sass
  * ruby-bootstrap-sass ships them below
/usr/share/ruby-bootstrap-sass/assets

The correct path would be /usr/share/compass/frameworks/bootstrap - i.e.
without the -sass suffix.

Adapting the simplest Compass command for the renamed project path gets
further but still fails:

directory fonts/bootstrap/ 
directory javascripts/ 
directory javascripts/bootstrap/ 
directory sass/ 
directory stylesheets/ 
   create config.rb 
   create sass/styles.scss 
   create sass/_bootstrap-variables.scss 
   create javascripts/bootstrap.js 
   create javascripts/bootstrap.min.js 
   create javascripts/bootstrap-sprockets.js 
   create javascripts/bootstrap/carousel.js 
   create javascripts/bootstrap/popover.js 
   create javascripts/bootstrap/scrollspy.js 
   create javascripts/bootstrap/modal.js 
   create javascripts/bootstrap/transition.js 
   create javascripts/bootstrap/button.js 
   create javascripts/bootstrap/alert.js 
   create javascripts/bootstrap/collapse.js 
   create javascripts/bootstrap/tab.js 
   create javascripts/bootstrap/tooltip.js 
   create javascripts/bootstrap/dropdown.js 
   create javascripts/bootstrap/affix.js 
   create fonts/bootstrap/glyphicons-halflings-regular.svg 
   create fonts/bootstrap/glyphicons-halflings-regular.eot 
   create fonts/bootstrap/glyphicons-halflings-regular.woff 
   create fonts/bootstrap/glyphicons-halflings-regular.woff2 
   create fonts/bootstrap/glyphicons-halflings-regular.ttf 
error sass/styles.scss (Line 2: File to import not found or unreadable: 
bootstrap-compass.
Load paths:
  Compass::SpriteImporter
  /usr/local/src/COUCH/omni/styling./sass
  /usr/share/compass/frameworks/compass/stylesheets
  /usr/share/compass/frameworks/blend-modes/stylesheets
  /usr/share/compass/frameworks/blueprint/stylesheets
  /usr/share/compass/frameworks/bootstrap-sass/stylesheets
  /usr/share/compass/frameworks/breakpoint/stylesheets
  /usr/share/compass/frameworks/color-schemer/stylesheets
  /usr/share/compass/frameworks/fancy-buttons/stylesheets
  /usr/share/compass/frameworks/h5bp/stylesheets
  /usr/share/compass/frameworks/layoutgala/stylesheets
  /usr/share/compass/frameworks/normalize-scss/stylesheets
  /usr/share/compass/frameworks/sassy-maps/stylesheets
  /usr/share/compass/frameworks/singularitygs/stylesheets
  /usr/share/compass/frameworks/slickmap/stylesheets
  /usr/share/compass/frameworks/susy/stylesheets
  /usr/share/compass/frameworks/toolkit/stylesheets
  /usr/share/compass/frameworks/yui/stylesheets)
Compilation failed in 1 files.


This next failure is due to the ruby code is not registering the path
with Compass, requiring to do that explicitly:

$ compass create --using bootstrap-sass --require bootstrap-sass

That works.


In short, this Compass library is installed in the wrong path, and its
ruby code is not registered with Compass.

 - Jonas


- -- System Information:
Debian Release: 9.0
  APT prefers buildd-unstable
  APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages compass-bootstrap-sass-plugin depends on:
ii  ruby 1:2.3.3
ii  ruby-bootstrap-sass  3.3.5.1-3
ii  ruby-compass 1.0.3~dfsg-4
ii  ruby-sass3.4.23-1

Versions of packages compass-bootstrap-sass-plugin recommends:
ii  ruby-compass  1.0.3~dfsg-4

compass-bootstrap-sass-plugin suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIyBAEBCAAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAljOvB8ACgkQLHwxRsGg
ASHPXg/4pCgZCtjXnF5SmdLYvPOhAQs11cx/tHiqtqgOHJakrALAQynPXI/BZ1n6
xFVJnHjQLaHRyO1AppdNOr5uGmxCmXssbypLqn4KmmrYernCRMgeNntuKNt2auY5
ztjLL9UTcguswzoC7xSkN/ZGzwD+XQiBLL4d0icPjL+45uqYu09WEDq2rmO4se7e
urM0FzUztPTUUu+zA+Vb6WScKuYUXHbM4SycBtCgQk51NPi7rgZW1nFDV2T0TJW1
YqvUCOJ/SOxS0vvMSLZIgeWHMqYSIqWq1LbAJYUMkkQ9UoBwNs+UWjdz3na8Pp/Y
9HXSkpqFpLDrEoWPlYMnzzzSLfzLAvkaJuiQ15oP8Uh0P+vmabh1HxF1HsKj3HYk
7l5xNihUcfk0OvZyOTLAtCH0uuW/8JhmqDqoB6O05uKhaG41DPzmcDKQmCYaJgTB
pFX+ek/iz4lBCbcxe8cw0bkN4sArIQ3utxiN50b10XqXqAKt7YipnHza/G9LQH+T
q4ie1Yfvs0JHKKmXr10UCdHt88zFoAleCbzWBD+AzGpzA5zEKBH7S5PNqj/haHVl
5pC3uhkt2q0mpGffX9oKYhqm0/olJeUi7ngAMn1jccbBqyVmUMKSkh4llpNNX/dD