Summary: | app-arch/tarsync-0.2.1 doesn't work with symlinked target directory | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Ivan Yarych <vanya> |
Component: | Binary packages support | Assignee: | Brian Harring (RETIRED) <ferringb> |
Status: | RESOLVED TEST-REQUEST | ||
Severity: | normal | CC: | andre_4you, mikopp |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Ivan Yarych
2007-12-07 07:59:25 UTC
Hmm. Just dug deeper and looks that's the tarsync fault. Looks like that's an easy fix in main.c of tarsync online 232. But not for me :) Can somebody help me with a patch? Instead of using a symlink, you can set PORTDIR in make.conf to be any directory that you want. (In reply to comment #2) > Looks like that's an easy fix in main.c of tarsync online 232. But not for me > :) > Can somebody help me with a patch? It may not be worth the trouble if you don't need to use a symlink anyway. Works with PORTDIR set. actualy I knew about that setting, but I always try to use thing in 'standard' way to avoid any troubles. Anyway I think the author could fix the problem with symlink in case he get some spare time. Thanks. I'm experiencing the same problem, but my /usr/portage isn't a symlink, its a mountpoint. I have the same problem, any news on this? (In reply to comment #5) > I'm experiencing the same problem, but my /usr/portage isn't a symlink, its a > mountpoint. Specifics please... this one I'm not able to replicate. Symlink is line 232 (suprised no one posted a one liner patch for this on a related note). Any news on this? Per comment #7 looks like maintainer cannot reproduce, is anybody still suffering this with 0.2.1-r1 and fully updated system? (In reply to comment #9) > Per comment #7 looks like maintainer cannot reproduce, is anybody still > suffering this with 0.2.1-r1 and fully updated system? |