Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 201563 - app-arch/tarsync-0.2.1 doesn't work with symlinked target directory
Summary: app-arch/tarsync-0.2.1 doesn't work with symlinked target directory
Status: RESOLVED TEST-REQUEST
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Binary packages support (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Brian Harring (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-12-07 07:59 UTC by Ivan Yarych
Modified: 2013-03-03 16:49 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ivan Yarych 2007-12-07 07:59:25 UTC
emerge-delta-webrsync doesn't work when /usr/portage is a symlink to different place

Reproducible: Always

Steps to Reproduce:
1. run emerge-delta-webrsync
Actual Results:  
ravlyk ~ # LC_ALL=C emerge-delta-webrsync 
Looking for available base versions for a delta
fetching patches
--09:53:54--  http://mirror.muntinternet.net/pub/gentoo///snapshots/deltas/snapshot-20071206-20071207.patch.bz2.md5sum
           => `/usr/portage/distfiles/snapshot-20071206-20071207.patch.bz2.md5sum'
Connecting to 192.168.1.1:3128... connected.
Proxy request sent, awaiting response... 404 Not Found
09:53:54 ERROR 404: Not Found.

--09:53:54--  ftp://mirror.muntinternet.net/pub/gentoo///snapshots/deltas/snapshot-20071206-20071207.patch.bz2.md5sum
           => `/usr/portage/distfiles/snapshot-20071206-20071207.patch.bz2.md5sum'
Connecting to 192.168.1.1:3128... connected.
Proxy request sent, awaiting response... 404 Not Found
09:53:56 ERROR 404: Not Found.

--09:53:56--  http://mirror.qubenet.net/mirror/gentoo///snapshots/deltas/snapshot-20071206-20071207.patch.bz2.md5sum
           => `/usr/portage/distfiles/snapshot-20071206-20071207.patch.bz2.md5sum'
Connecting to 192.168.1.1:3128... connected.
Proxy request sent, awaiting response... 404 Not Found
09:53:56 ERROR 404: Not Found.

failed fetching snapshot-20071206-20071207.patch.bz2.md5sum
verbosity level(1)
patch_type=8
disabling bufferless, patch_count(1) == 1 || forced_reorder(1)
size1=293335040, size2=293447680
reconstruction return=0, commands=10076
result was 10076 commands
versions size is 293447680
applied 1 patches
reordering commands? 1
reconstructing target file based off of dcbuff commands...
collapsing
processing src 0: 6193 commands.
processing src 1: 3883 commands.
reconstruction completed successfully
verifying uncompressed md5
recompressing. (backgrounding)
  /tmp/delta-webrsync-v2vc79/portage-20071206.tar: beginning update to the tree
Syncing local tree...
apparently you have tarsync installed.  using it.
scanning tarball...
cleansed 1 dups out of 154187
something is screwy with target dir /usr/portage
ok, tarsync failed.  that's teh suck :/


Expected Results:  
The tree should be synced with the diffs.

Please don't draw your attention to 404 errors in output - they are shown because those snapshots was already downloaded.
Is there any workaround for this or fix?
I'm trying to use autofs for /usr/portage mounting, so /usr/portage points to /mnt/auto/portage .

emerge itself works well I think.
Comment 1 Ivan Yarych 2007-12-07 08:05:48 UTC
Hmm. Just dug deeper and looks that's the tarsync fault.
Comment 2 Ivan Yarych 2007-12-07 08:13:27 UTC
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?
Comment 3 Zac Medico gentoo-dev 2007-12-07 08:18:44 UTC
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.
Comment 4 Ivan Yarych 2007-12-07 08:25:01 UTC
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.
Comment 5 Andre Coetzee 2009-07-25 09:09:05 UTC
I'm experiencing the same problem, but my /usr/portage isn't a symlink, its a mountpoint.
Comment 6 mikopp 2010-01-04 07:45:55 UTC
I have the same problem, any news on this?
Comment 7 Brian Harring (RETIRED) gentoo-dev 2010-08-11 08:28:39 UTC
(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).
Comment 8 Pacho Ramos gentoo-dev 2013-01-20 08:03:35 UTC
Any news on this?
Comment 9 Pacho Ramos gentoo-dev 2013-02-03 14:55:14 UTC
Per comment #7 looks like maintainer cannot reproduce, is anybody still suffering this with 0.2.1-r1 and fully updated system?
Comment 10 Pacho Ramos gentoo-dev 2013-03-03 16:49:38 UTC
(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?