Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 72819 - emerge-webrsync bugs
Summary: emerge-webrsync bugs
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High major (vote)
Assignee: Portage team
URL:
Whiteboard:
Keywords: InVCS
Depends on:
Blocks:
 
Reported: 2004-11-29 07:53 UTC by Evgeny Stambulchik
Modified: 2005-07-14 07:04 UTC (History)
0 users

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 Evgeny Stambulchik 2004-11-29 07:53:45 UTC
After emerge-webrsync,

# emerge gentoolkit
Calculating dependencies   
emerge: there are no ebuilds to satisfy "gentoolkit".

There is no /usr/portage/app-portage dir at all.

Reproducible: Always
Steps to Reproduce:
Comment 1 Mr. Bones. (RETIRED) gentoo-dev 2004-11-29 12:04:15 UTC
looks like a bad sync to me.  app-portage/gentoolkit is still in the tree.
Comment 2 Evgeny Stambulchik 2004-11-29 13:18:17 UTC
Changed title.
The culprit appears to be the "emerge-webrsync" script.

1. When opening the snapshot's tarball, it doesn't check for the exit status of `tar' command. In my case, on (a ~1GB ext3) /var partition, it ran out of inodes, so the /usr/portage tree was damaged as a result. A check for "$?" should be added after these lines:

sync_local() {
        echo Syncing local tree...
        tar jxf $FILE

2. It doesn't honour PORTAGE_TMPDIR set in /etc/make.conf. Instead of 

DISTDIR="/var/tmp/emerge-webrsync"

there should be

DISTDIR="$(/usr/lib/portage/bin/portageq envvar PORTAGE_TMPDIR)/emerge-webrsync"
Comment 3 Nicholas Jones (RETIRED) gentoo-dev 2004-12-17 11:39:46 UTC
Included fixes for 51-r9
Comment 4 Jason Stubbs (RETIRED) gentoo-dev 2005-07-14 05:47:35 UTC
Fixed on or before 2.0.51.22-r1 
Comment 5 Jason Stubbs (RETIRED) gentoo-dev 2005-07-14 06:58:24 UTC
Looking through the batch of bugs, I'm not sure that some of these are 
actually fixed in stable. Others, the requirements have possibly changed after 
the initial fix was committed. 
 
If you think this bug has been closed incorrectly, please reopen or ask that 
it be reopened. 
Comment 6 Evgeny Stambulchik 2005-07-14 07:04:26 UTC
I believe the two issues I reported on are indeed fixed now. Thanks!