| Summary: | ghostscript-7.05.3-r1.ebuild (cp -a breaks build) | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Brian Elliott <linuxdogg> |
| Component: | New packages | Assignee: | Grant Goodyear (RETIRED) <g2boojum> |
| Status: | RESOLVED INVALID | ||
| Severity: | minor | ||
| Priority: | High | ||
| Version: | 1.2 | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
Interesting. Can you tell me something about your system? Have you changed any of the Portage defaults? The ebuild works fine for me, so I need some help figuring out what's going wrong. If you would run the emerge with the --debug flag and post the output at the error, that would be really helpful, too. Thanks! I installed from stage1-ix86-1.2.tbz2. The only Portage default I've changed is PORTAGE_TMPDIR=/usr/src. After looking at this again, the problem seems to be with cp. Here's some background. <bdogg@pandora:~>cp --version cp (fileutils) 4.1.8acl <bdogg@pandora:~>cp -a .gnome /tmp cp: preserving permissions for `/tmp/.gnome/application-info': Invalid argument cp: preserving permissions for `/tmp/.gnome/gnome-vfs': Invalid argument cp: preserving permissions for `/tmp/.gnome/accels': Invalid argument cp: preserving permissions for `/tmp/.gnome': Invalid argument This is the same error I was reporting above. However, the cp seems to work just fine. /tmp/.gnome has the correct permissions and all the files/dirs copied over properly. Am I missing something here, or should this bug be filed with cp/fileutils? If there's any other info you need, let me know. Thanks! Ross, I think you're right as I am using sys-kernel/xfs-sources. I should have done more research on the problem before submitting the bug, my bad. Closing. Thanks, all! |
line 55 of ghostscript-7.05.3-r1.ebuild contains: cp -a fonts ${D}/usr/share/ghostscript || die This generates the error 'cp: preserving permissions for ....: Invalid argument' Changing it to cp -R solves the problem.