#1149752 openqa-server: FTBFS: ERROR: Could not find a valid gem 'sass' (>= 0), here is why:

#1149752#5
Date:
2026-10-02 19:09:39 UTC
From:
To:
Dear maintainer:

During a rebuild of all packages in unstable, this package failed to build.

Below you will find the last part of the build log (probably the most
relevant part, but not necessarily). If required, the full build log
is available here:

https://people.debian.org/~sanvila/build-logs/202610/

About the archive rebuild: The build was made on virtual machines from AWS,
using sbuild and a reduced chroot with only build-essential packages.

If you cannot reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

If this is really a bug in one of the build-depends, please use
reassign and add an affects on src:openqa-server, so that this is still
visible in the BTS web page for this package.

Thanks.
--------------------------------------------------------------------------------
[...]
 ($?=-1, $!=29, PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games) at /usr/share/perl5/Mojolicious/Plugin/AssetPack/Pipe.pm line 30.
<internal:/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb>:139:in `require': cannot load such file -- ubygems (LoadError)
Did you mean?  rubygems
	from <internal:/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb>:139:in `require'
[2026-10-02 16:32:58.21359] [229] [warn] Installing sass... Please wait. (gem install --user-install sass)
ERROR:  Could not find a valid gem 'sass' (>= 0), here is why:
          Unable to download data from https://rubygems.org/ - Socket::ResolutionError: Failed to open TCP connection to rubygems.org:443 (getaddrinfo: Temporary failure in name resolution) (https://rubygems.org/specs.4.8.gz)
run(/bin/sass) failed: No such file or directory at /usr/share/perl5/Mojolicious/Plugin/AssetPack/Pipe.pm line 27.
 ($?=-1, $!=29, PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games) at /usr/share/perl5/Mojolicious/Plugin/AssetPack/Pipe.pm line 30.
make[2]: *** [Makefile:113: generate-assets] Error 29
make[2]: Leaving directory '/<<PKGBUILDDIR>>'
dh_auto_install: error: make -j2 install DESTDIR=/<<PKGBUILDDIR>>/debian/tmp AM_UPDATE_INFO_DIR=no INSTALL="install --strip-program=true" SHELL=/bin/bash GENERATE_PACKED_ASSETS_FAILS_ON_MISSING_ASSETS=1 SKIP_GENERATE_PACKED_ASSETS= returned exit code 2
make[1]: *** [debian/rules:49: override_dh_auto_install] Error 25
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:7: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess failed with exit status 2
--------------------------------------------------------------------------------

#1149752#10
Date:
2026-10-05 16:46:10 UTC
From:
To:
tags 1149752 + patch
block 1149752 by 1149563
thanks

ruby-sass 3.7.4-7 dropped its sass command line tool, so no "sass" ends up in
the chroot and AssetPack falls back to "gem install --user-install sass",
which fails offline ("run(/bin/sass) failed: No such file or directory").
The attached patch builds against dart-sass instead.

Note this is only half of the fix. AssetPack itself also passes
Ruby-Sass-only options to sass, which is #1149563; with the patch from that
bug applied as well, the package builds again.

Emfox