Debian Patches
Status for ruby-mdl/0.18.1+ds-2
| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| 0001-no-bundler-in-tests.patch | Do not use Bundler when running the test suite Debian builds and tests against Debian-packaged gems (via Build-Depends), not against Gemfile.lock. Bundler.setup would fail in a clean build environment: no network access, Gemfile references a non-default gem source, and lists dev-only gems (pry, rubocop, ...) that are not packaged for Debian. |
Norwid Behrnd <nbehrnd@protonmail.com> | not-needed | |||
| 0002-no-bundle-exec-in-tests.patch | Do not invoke the `bundle` binary from the CLI test helper test/test_cli.rb's run_cmd helper shells out via `bundle exec` to run bin/mdl. Debian's build environment has no `bundle` executable and tests must exercise the package as installed from Debian-packaged gems, not through Bundler. |
Norwid Behrnd <nbehrnd@protonmail.com> | not-needed | |||
| 0003-require-mdl-via-rubygems.patch | Load mdl via rubygems instead of a hardcoded relative path test/setup_tests.rb uses require_relative '../lib/mdl', which assumes lib/ is physically present next to test/. gem2deb's autopkgtest mode temporarily renames lib/ away to verify the package as actually installed, which breaks this hardcoded path. require 'mdl' resolves correctly in both the build-time test run (RUBYLIB=. is set by gem2deb) and the autopkgtest run (resolves via the installed gem). |
Norwid Behrnd <nbehrnd@protonmail.com> | not-needed |
All known versions for source package 'ruby-mdl'
- 0.18.1+ds-2 (sid)
- 0.17.0-2 (forky)
- 0.17.0-2~bpo13+1 (trixie-backports)
- 0.13.0-4 (trixie)
- 0.13.0-4~bpo12+1 (bookworm-backports)
- 0.12.0-3 (bookworm)