Summary: | app-editors/emacs-cvs-23.0.60-r2 fails because of dodoc of a file not longer in the repository | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Tassilo Horn <tsdh> |
Component: | New packages | Assignee: | Emacs project <emacs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | john_r_graham |
Priority: | High | ||
Version: | 2008.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Tassilo Horn
2008-02-21 08:51:52 UTC
(In reply to comment #0) > BTW: Is it really sensible to make a merge fail only because of some missing > doc file? IMO a simple message that it couldn't be found and installed would > suffice here. No, it completely sucks but the maintainer thinks otherwise... commented on this multiple times, last time on Bug 190762 (In reply to comment #1) > (In reply to comment #0) > > BTW: Is it really sensible to make a merge fail only because of some missing > > doc file? IMO a simple message that it couldn't be found and installed would > > suffice here. > No, it completely sucks but the maintainer thinks otherwise... commented on > this multiple times, last time on Bug 190762 The comment by ulm there is still valid. Fixed. Thanks for reporting I understand the purpose, but why would a simple warning message File foo moved at upstream. Please report that to emacs@gentoo.org. not suffice? The missing doc file doesn't make emacs unusable. At least for temporary files like README.{unicode,multy-tty} killing the merge makes no sense. Those files were only there until someone volunteered to merge the changes into the normal README. (In reply to comment #3) > I understand the purpose, but why would a simple warning message > File foo moved at upstream. Please report that to emacs@gentoo.org. > not suffice? The missing doc file doesn't make emacs unusable. Because no one would read it. :) > At least for temporary files like README.{unicode,multy-tty} killing the merge > makes no sense. Those files were only there until someone volunteered to merge > the changes into the normal README. The live ebuilds are experimental (thus masked) and we want all tiny bits to fail to notice them early. So moving it over once they go in pretest phase or even stable we already have a complete working ebuild without cruft. Anything to add, ulm? *** Bug 211264 has been marked as a duplicate of this bug. *** |