Summary: | dev-ruby/globalid-0.4.2: missing test dependencies | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Rolf Eike Beer <eike> |
Component: | Current packages | Assignee: | Gentoo Ruby Team <ruby> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | ago |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Rolf Eike Beer
![]() After manually merging dev-ruby/thread_safe, then there are new failures: Error: RailtieTest#test_GlobalID.app_for_Blog::Application_defaults_to_blog: LoadError: cannot load such file -- crass test/cases/railtie_test.rb:21:in `block in <class:RailtieTest>' rails test test/cases/railtie_test.rb:20 E And the latter error does not go away even with this one merged: chroot ~ # equery l dev-ruby/crass * Searching for crass in dev-ruby ... [IP-] [ ] dev-ruby/crass-1.0.4:0 The thread_safe issue was resolved in bug 720290 *** Bug 720408 has been marked as a duplicate of this bug. *** I can't reproduce this. crass should already be installed as a dependency (via railties -> actionpack -> rails-html-sanitizer -> loofah). If crass is installed and this error remains then it would be useful to know what this returns: ruby -r crass -e "puts Crass.inspect" It just outputs "Crass". (In reply to Rolf Eike Beer from comment #6) > It just outputs "Crass". That was my expectation. So we now know it installed correctly and can be required. This also means I don't understand why this failure happens. (In reply to Rolf Eike Beer from comment #6) > It just outputs "Crass". Same here. The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=903f9ceadd8dc1d4a36e5d73e6547fb77560b31f commit 903f9ceadd8dc1d4a36e5d73e6547fb77560b31f Author: Hans de Graaff <graaff@gentoo.org> AuthorDate: 2020-05-16 04:20:40 +0000 Commit: Hans de Graaff <graaff@gentoo.org> CommitDate: 2020-05-16 04:20:40 +0000 dev-ruby/loofah: add proper gemspec Closes: https://bugs.gentoo.org/719254 Package-Manager: Portage-2.3.99, Repoman-2.3.22 Signed-off-by: Hans de Graaff <graaff@gentoo.org> dev-ruby/loofah/{loofah-2.5.0.ebuild => loofah-2.5.0-r1.ebuild} | 2 ++ 1 file changed, 2 insertions(+) Nope, this did only change the error: [IP-] [ ] dev-ruby/loofah-2.5.0-r1:0 Error: RailtieTest#test_GlobalID.app_can_be_set_with_config.global_id.app_=: LoadError: cannot load such file -- loofah test/cases/railtie_test.rb:27:in `block in <class:RailtieTest>' rails test test/cases/railtie_test.rb:25 (In reply to Rolf Eike Beer from comment #10) > Nope, this did only change the error: This upstream does very weird things with version numbers, it turns out. The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f295d004b21e35134e6a9afc5f904ad2a788bf68 commit f295d004b21e35134e6a9afc5f904ad2a788bf68 Author: Hans de Graaff <graaff@gentoo.org> AuthorDate: 2020-05-19 13:21:40 +0000 Commit: Hans de Graaff <graaff@gentoo.org> CommitDate: 2020-05-19 13:21:54 +0000 dev-ruby/loofah: fix version in gemspec Closes: https://bugs.gentoo.org/719254 Package-Manager: Portage-2.3.99, Repoman-2.3.22 Signed-off-by: Hans de Graaff <graaff@gentoo.org> dev-ruby/loofah/{loofah-2.5.0-r1.ebuild => loofah-2.5.0-r2.ebuild} | 3 +++ 1 file changed, 3 insertions(+) |