| Summary: | dev-ruby/activesupport-2.3.14-r1 fails to patch | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Patrick Lauer <patrick> |
| Component: | New packages | Assignee: | Gentoo Ruby Team <ruby> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | normal | CC: | orzel |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Patrick Lauer
2012-10-20 01:56:43 UTC
I can't reproduce this. Please include the failed output file. I can reproduce. I suppose the latest ~arch patch is to blame. * 38:--- a/../metadata * 39:+++ b/../metadata what does it mean? maybe patch file seems to be corrupted. I've met the same situation as the first claim. (In reply to comment #3) > * 38:--- a/../metadata > * 39:+++ b/../metadata > > what does it mean? It means that we patch the metadata file directly, but due to the structure with multiple ruby targets that file is outside the normal source directory, hence .. in the path. I think the proper fix here is to remove Rails 2.3.x from the tree. It is no longer supported upstream. i'm hit by this too... the 2.3.14 works, and the 2.3.14-r1 seems broken since at least end of october... why dont you just remove the -r1 from portage ? or at least mask it.. ??? Here, it's locally masked, work well.. Rails 2.3 has now been masked for removal, so I'm closing this bug. |