| 1 |
walt <w41ter@×××××.com> writes: |
| 2 |
|
| 3 |
> On 07/03/2011 03:07 PM, Harry Putnam wrote: |
| 4 |
>> I'm getting output from emerge -v emacs-vcs like this: |
| 5 |
>> |
| 6 |
>> |
| 7 |
>> * ERROR: app-editors/emacs-vcs-24.0.9999-r1 failed (unpack phase): |
| 8 |
>> * bzr.eclass: can't pull from bzr://bzr.savannah.gnu.org/emacs/trunk/ |
| 9 |
>> |
| 10 |
>> I tried |
| 11 |
>> bzr branch bzr://bzr.savannah.gnu.org/emacs/trunk/ |
| 12 |
>> by hand and had no problems with it. |
| 13 |
> |
| 14 |
> I've never used a 9999 version that pulls from bzr, but I have used |
| 15 |
> some that pull from git and (yuk) svn. The cloned repos were stored |
| 16 |
> (I think) in /usr/portage/disfiles/git (or svn) -- or something similar. |
| 17 |
> |
| 18 |
> If you can find a bzr repo in your /usr/portage/distfiles, try deleting |
| 19 |
> it. My memory is a bit fuzzy here, but you get the general idea, I hope. |
| 20 |
|
| 21 |
Haaa... yep, that worked .. (deleting bzr-src) |
| 22 |
|
| 23 |
I was suprized to learn the repo was created in /usr/portage/distfiles |
| 24 |
|
| 25 |
I thought it would happen in /var/tmp. Well, now I know... thanks. |
| 26 |
|
| 27 |
If you happen to do an `emerge emacs-vcs' be prepared for a really |
| 28 |
looonnnnggg wait on bzr. It is the absolute slowest thing going to |
| 29 |
check a module out from. |
Archives