Summary: | dev-vcs/rcs-5.10.1 - rm: cannot remove .../rcs: No such file or directory | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | Current packages | Assignee: | Aaron W. Swenson <titanofold> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | ago, sam |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 862612 | ||
Attachments: |
emerge-info.txt
dev-vcs:rcs-5.10.1:20220205-162533.log emerge-history.txt environment etc.portage.tar.bz2 logs.tar.bz2 temp.tar.bz2 |
Description
Toralf Förster
2022-02-05 16:30:16 UTC
Created attachment 764405 [details]
emerge-info.txt
Created attachment 764406 [details]
dev-vcs:rcs-5.10.1:20220205-162533.log
Created attachment 764407 [details]
emerge-history.txt
Created attachment 764408 [details]
environment
Created attachment 764409 [details]
etc.portage.tar.bz2
Created attachment 764410 [details]
logs.tar.bz2
Created attachment 764411 [details]
temp.tar.bz2
Why is 'rm -R "${ED}"/usr/share/doc/rcs || die' necessary? I just deleted the line from the ebuild, then it seems correctly work (AFAIK). (In reply to OKUMURA N. Shin-ya from comment #8) > Why is 'rm -R "${ED}"/usr/share/doc/rcs || die' necessary? > I just deleted the line from the ebuild, then it seems correctly work > (AFAIK). I imagine it was there because the build system previously didn't respect ${docdir}. The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=88c3f5c267c2fd85898bd21b23fe6d617c0273e8 commit 88c3f5c267c2fd85898bd21b23fe6d617c0273e8 Author: Sam James <sam@gentoo.org> AuthorDate: 2022-08-01 03:26:52 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2022-08-01 03:26:52 +0000 dev-vcs/rcs: fix USE=doc install Closes: https://bugs.gentoo.org/832759 Signed-off-by: Sam James <sam@gentoo.org> dev-vcs/rcs/rcs-5.10.1.ebuild | 1 - 1 file changed, 1 deletion(-) *** Bug 862654 has been marked as a duplicate of this bug. *** |