Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 77941 - emerge-webrsync broken in 2.0.51-r10
Summary: emerge-webrsync broken in 2.0.51-r10
Status: RESOLVED FIXED
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Tools (show other bugs)
Hardware: All Linux
: High major (vote)
Assignee: Portage team
URL:
Whiteboard:
Keywords: InVCS
Depends on:
Blocks:
 
Reported: 2005-01-13 23:46 UTC by Dirk Heinrichs
Modified: 2005-07-14 06:58 UTC (History)
2 users (show)

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


Attachments
Patch to fix the emerge-webrsync (emerge-webrsync.patch,508 bytes, patch)
2005-01-17 00:56 UTC, Erol Zavidic
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Dirk Heinrichs 2005-01-13 23:46:42 UTC
In line 45, there is "if !tar ...", which should read "if ! tar ...", otherwise emerge-webrsync fails with "!tar: No such file or directory."

Reproducible: Always
Steps to Reproduce:
Comment 1 Dirk Heinrichs 2005-01-14 01:52:05 UTC
It's still there in -r12.

Hmm, I wonder why this can happen in a -rXY release. I thought -rXY was for ebuild changes only.
Comment 2 Erol Zavidic 2005-01-17 00:56:36 UTC
Created attachment 48733 [details, diff]
Patch to fix the emerge-webrsync

run as root, patch -p0 <emerge-webrsync.patch
Comment 3 Dirk Heinrichs 2005-01-17 01:10:11 UTC
What's wrong with just inserting a " " (blank) between "!" and "tar"?

BTW: Still present in -r13.
Comment 4 Erol Zavidic 2005-01-17 01:29:18 UTC
I guess just my coding style, like to have a bit more control. :-)
Comment 5 Erol Zavidic 2005-01-20 08:47:46 UTC
resolved in 2.0.51-r14
Comment 6 Jason Stubbs (RETIRED) gentoo-dev 2005-07-14 05:47:39 UTC
Fixed on or before 2.0.51.22-r1 
Comment 7 Jason Stubbs (RETIRED) gentoo-dev 2005-07-14 06:58:27 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.