Debian Patches
Status for ruby-librarian/0.6.4-5
| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| 0001-Add-patch-to-keep-VERSION-in-the-library-namespace.patch | Add patch to keep VERSION in the library namespace When installed as system package, the gem still looks for /usr/lib/ruby/VERSION to find its version. Have librarian look in /usr/lib/ruby/vendor_ruby/librarian instead. (The packaging needs to install VERSION there in another commit) |
Stig Sandbeck Mathisen <ssm@debian.org> | no | 2014-02-15 | ||
| 0002-Disable-tsort-based-unit-spec.patch | Disable failing spec tests using tsort | Sebastien Badia <sbadia@debian.org> | not-needed | 2018-03-18 | ||
| 0003-Relax-dependency-on-thor.patch | Relax dependency on thor | Lucas Nussbaum <lucas@debian.org> | no | 2021-01-21 | ||
| 0006-Rename-File.exists-to-.exist.patch | Rename File.exists? to .exist to support ruby-fakefs 2.x and ruby 3.2 |
=?utf-8?q?C=C3=A9dric_Boutillier?= <boutil@debian.org> | no | 2023-11-29 | ||
| fix-ruby3.0-FTBFS.patch | Backport upstream patch to fix ruby-3.0 FTBFS | Nilesh Patra <nilesh@debian.org> | not-needed | 2021-10-22 | ||
| search-for-Rakefile-relatively-to-pwd.patch | [PATCH] search for the Rakefile relatively to pwd This is a fix (workaround?) for https://bugs.debian.org/987113 In most cases, we run the spec tests from a full source checkout, testing the current state in the VCS. However, in Debian, we also want to test that the built package is actually working fine. To do so, we install the package and then re-use the spec tests from the source, but now running against the *installed* version of the code. Obviously, we don't install the Rakefile, as it contains nothing of use for the end-users of the package. But now, if we'd run the tests, they will try to find the Rakefile by looking at the path of cli_macro.rb (in /usr/share/rubygems-integration) and call .dirname on it, until path.join("Rakefile") exists, which will never be true (it will traverse until / and loop there). Instead, we can try to start from the place where we call the tests from (pwd) and should get a path where it can find the Rakefile and be happy. Now, after explaining all this, the only question for me is: why does it even look for a Rakefile? Because the source tree of librarian doesn't look like a librarian project anyways? |
Evgeni Golov <evgeni@golov.de> | no | 2021-04-24 |
Showing 1 to 6 of 6 entries