| Summary: | dev-ruby/racc-1.7.0 - ERROR: dev-ruby/racc-1.7.0::gentoo failed (prepare phase): | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
| Component: | Current packages | Assignee: | Gentoo Ruby Team <ruby> |
| Status: | RESOLVED FIXED | ||
| Severity: | critical | CC: | pacho, sam, strogdon |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
emerge-info.txt
dev-ruby:racc-1.7.0:20230616-030745.log emerge-history.txt environment etc.clang.tar.xz etc.portage.tar.xz |
||
|
Description
Toralf Förster
2023-06-16 08:55:19 UTC
Created attachment 863955 [details]
emerge-info.txt
Created attachment 863956 [details]
dev-ruby:racc-1.7.0:20230616-030745.log
Created attachment 863957 [details]
emerge-history.txt
Created attachment 863958 [details]
environment
Created attachment 863959 [details]
etc.clang.tar.xz
Created attachment 863960 [details]
etc.portage.tar.xz
I'm going to check if this is a side-effect of changes from yesterday. Not tried to repro yet. I can't reproduce this yet.. (In reply to Sam James from comment #8) > I can't reproduce this yet.. Got it, had to purge all ruby binpkgs (clean racc build was not enough) On my machine the cause was an empty shebang in /usr/bin/rake (fakegems-generated). The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a32b5379f8d17f985765fa70fe012abdff07c4c1 commit a32b5379f8d17f985765fa70fe012abdff07c4c1 Author: Sam James <sam@gentoo.org> AuthorDate: 2023-06-16 17:39:36 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2023-06-16 17:42:12 +0000 ruby-fakegem.eclass: adapt to ruby-ng.eclass changes ruby-fakegem uses an internal function (which is technically allowed, I guess, maybe, but all of this should really be shifted into ruby-utils ultimately - funnily enough negil pointed out that general class of problem yesterday. diff of bad/good:: ``` --- good/rake-13.0.6-r1/image/usr/bin/rake +++ bad/rake-13.0.6-r1-1/image/usr/bin/rake @@ -1,4 +1,4 @@ -#!/usr/bin/env ruby +#! ``` Closes: https://bugs.gentoo.org/908598 Fixes: 390ad2effe1c83a7cb25a892ad988937b53c07fe Signed-off-by: Sam James <sam@gentoo.org> eclass/ruby-fakegem.eclass | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) Additionally, it has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=594d94f491be2eb7cd37295a93522cf18559337f commit 594d94f491be2eb7cd37295a93522cf18559337f Author: Sam James <sam@gentoo.org> AuthorDate: 2023-06-16 17:42:03 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2023-06-16 17:42:13 +0000 dev-ruby/rake: revbump to propagate ruby-fakegem fix Bug: https://bugs.gentoo.org/908598 Signed-off-by: Sam James <sam@gentoo.org> dev-ruby/rake/{rake-13.0.6-r1.ebuild => rake-13.0.6-r2.ebuild} | 0 1 file changed, 0 insertions(+), 0 deletions(-) (In reply to Andrey Bugaevskiy from comment #10) > On my machine the cause was an empty shebang in /usr/bin/rake > (fakegems-generated). Thanks! I'd figured it out by diffing a good/bad version with an old eclass checkout, but if I hadn't, this would've been quite helpful - much appreciated in any case. *** Bug 908607 has been marked as a duplicate of this bug. *** The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a3413c5f9babccf6e769b9ed6a80c5c4f152477b commit a3413c5f9babccf6e769b9ed6a80c5c4f152477b Author: Sam James <sam@gentoo.org> AuthorDate: 2023-06-16 20:39:01 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2023-06-16 20:40:30 +0000 dev-lang/ruby: depend on fixed dev-ruby/rake Bug: https://bugs.gentoo.org/908598 Signed-off-by: Sam James <sam@gentoo.org> dev-lang/ruby/{ruby-3.0.6-r2.ebuild => ruby-3.0.6-r3.ebuild} | 2 +- dev-lang/ruby/{ruby-3.1.4-r2.ebuild => ruby-3.1.4-r3.ebuild} | 2 +- dev-lang/ruby/{ruby-3.2.2-r2.ebuild => ruby-3.2.2-r3.ebuild} | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) *** Bug 908605 has been marked as a duplicate of this bug. *** *** Bug 908756 has been marked as a duplicate of this bug. *** |
