Hi, I recently ran into a strange issue. I tried to package ruby-jekyll-feed 0.13.0, a plugin for Jekyll. This new upstream releases introduces a new feature, which allows to exclude some content in the resulting feed. It also comes with a test to test this feature. Trying to build the package fails, because some of the new feature tests fail [1]. The reason is that tests use the already packaged version of ruby-jekyll- feed, which is installed on the build system because jekyll depends on it and jekyll is a necessary build-dependency. I already opened #945334 [2] and requested to downgrade jekyll's dependencies on its plugins to suggestions. So a clean build environment would not contain ruby-jekyll-feed. But I'm still thinking that one should be able to force ruby (rake, rspec) to put the packaged plugin (0.13.0) before the installed one (0.12.1). The command called is: > RUBYLIB=/builds/ruby-team/ruby-jekyll-feed/debian/output/ruby-jekyll-feed- > 0.13.0/debian/ruby-jekyll-feed/usr/lib/ruby/vendor_ruby:. > GEM_PATH=debian/ruby-jekyll-feed/usr/share/rubygems- > integration/all:/var/lib/gems/2.5.0:/usr/lib/ruby/gems/2.5.0:/usr/share/rubyg > ems-integration/2.5.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64- > linux-gnu/rubygems-integration/2.5.0 ruby2.5 -S rake -f debian/ruby- > tests.rake So in both the RUBYLIB and the GEM_PATH variables the build location is put on top. Why is the installed plugin version used instead? [1] https://salsa.debian.org/ruby-team/ruby-jekyll-feed/-/jobs/420659 [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945334 Regards, Daniel
Attachment:
signature.asc
Description: This is a digitally signed message part