Hi gregor,

thanks for the report. The two problems have different causes, so separately.

On the failing architectures: this is more than a test problem, so let me state
it plainly. ruby-sass was Architecture: all, so /usr/bin/sass existed on every
architecture; dart-sass is a prebuilt native binary and is built only on
amd64/arm64/armhf/riscv64. So Sass compilation through AssetPack now works on
four architectures where it used to work on all of them.

The immediate bug in the upload is separate from that: the test added there
declares "Depends: @, dart-sass" without a restriction, so on the other
architectures the dependencies cannot be satisfied and autopkgtest reports a
failure rather than a skip - which is why the four architectures that pass in
the excuses are exactly the four with dart-sass. It needs one line in
debian/tests/control:

  --- a/debian/tests/control
  +++ b/debian/tests/control
  @@ -1,3 +1,4 @@
   Test-Command: TEST_SASS=1 prove -Ilib t/sass-bin.t
   Depends: @, dart-sass
  +Architecture: amd64 arm64 armhf riscv64
   Features: test-name=sass

With that the test is skipped instead of failing wherever dart-sass does not
exist.

On openQA I do not think 2.15-2 is the cause. Its autopkgtest has been broken
since ruby-sass 3.7.4-7 (2026-09-28) dropped the command line tools: openQA
uses AssetPack to compile its SASS assets and still depends on ruby-sass,
which no longer ships any binary. #1149563, filed five days before 2.15-2,
already describes it:

  "This caused a regression in openqa, due to the missing command line tool,
   as its tests fail when compiling sass assets. I tried patching openqa to
   depend on dart-sass instead of ruby-sass, but it then failed anyway."

The "failed anyway" was the old command line: 2.15-1 passed Ruby Sass
arguments, and dart-sass reads -s as --style. With the current package both
syntaxes work, which I checked against dart-sass 1.108.1:

  $ dart-sass -s --trace --scss -t compressed < in.scss
  "--trace" is not an allowed value for option "-s".
  $ dart-sass --stdin --trace --style=compressed < in.scss
  a{color:red}
  $ dart-sass --stdin --trace --indented < in.sass
  a { color: red; }

So what is left for openQA is its own dependency: it needs dart-sass instead
of ruby-sass, and on the architectures without dart-sass its asset compilation
has to be skipped as well.

cheers,
Emfox

Reply via email to