[gentoo-user] output of emerge -v emacs-vcs (not the masking something else)

[gentoo-user] output of emerge -v emacs-vcs (not the masking something else)

[Harry Putnam]

I'm getting output from emerge -v emacs-vcs like this:


 * ERROR: app-editors/emacs-vcs-24.0.9999-r1 failed (unpack phase):
 *   bzr.eclass: can't pull from bzr://bzr.savannah.gnu.org/emacs/trunk/

I tried 
  bzr branch bzr://bzr.savannah.gnu.org/emacs/trunk/ 
by hand and had no problems with it.

Let me add that I started an emerge -v emacs-vcs an hour or two ago
but decided against it and ^C'ed out of it kind of late in the game.

On that occasion it was working and the ^C was done during the `make'
phase I think.

But ever since that run I get the error shown above. So errors out
early in the process.

I deleted the leavings in /var/tmp/portage/app-editors with r
  rm -rf /var/tmp/portage/app-editors
thinking that might be the source of the problem but it did not help. 

Still, I'm pretty sure its something about that earlier kill that is
causing this.

ps-I have /etc/portage/package.unmask with these contents:

  ~app-editors/emacs-vcs-23.1.9999
  ~app-editors/emacs-vcs-24.0.9999
  ~virtual/emacs-24

[gentoo-user] Re: output of emerge -v emacs-vcs (not the masking something else)

[walt]

On 07/03/2011 03:07 PM, Harry Putnam wrote:
> I'm getting output from emerge -v emacs-vcs like this:
> 
> 
>  * ERROR: app-editors/emacs-vcs-24.0.9999-r1 failed (unpack phase):
>  *   bzr.eclass: can't pull from bzr://bzr.savannah.gnu.org/emacs/trunk/
> 
> I tried 
>   bzr branch bzr://bzr.savannah.gnu.org/emacs/trunk/ 
> by hand and had no problems with it.

I've never used a 9999 version that pulls from bzr, but I have used
some that pull from git and (yuk) svn.  The cloned repos were stored
(I think) in /usr/portage/disfiles/git (or svn) -- or something similar.

If you can find a bzr repo in your /usr/portage/distfiles, try deleting
it.  My memory is a bit fuzzy here, but you get the general idea, I hope.

[gentoo-user] Re: output of emerge -v emacs-vcs (not the masking something else)

[Harry Putnam]

walt <w41ter@gmail.com> writes:

> On 07/03/2011 03:07 PM, Harry Putnam wrote:
>> I'm getting output from emerge -v emacs-vcs like this:
>> 
>> 
>>  * ERROR: app-editors/emacs-vcs-24.0.9999-r1 failed (unpack phase):
>>  *   bzr.eclass: can't pull from bzr://bzr.savannah.gnu.org/emacs/trunk/
>> 
>> I tried 
>>   bzr branch bzr://bzr.savannah.gnu.org/emacs/trunk/ 
>> by hand and had no problems with it.
>
> I've never used a 9999 version that pulls from bzr, but I have used
> some that pull from git and (yuk) svn.  The cloned repos were stored
> (I think) in /usr/portage/disfiles/git (or svn) -- or something similar.
>
> If you can find a bzr repo in your /usr/portage/distfiles, try deleting
> it.  My memory is a bit fuzzy here, but you get the general idea, I hope.

Haaa... yep, that worked .. (deleting bzr-src)

I was suprized to learn the repo was created in /usr/portage/distfiles

I thought it would happen in /var/tmp.  Well, now I know... thanks.

If you happen to do an `emerge emacs-vcs' be prepared for a really
looonnnnggg wait on bzr.  It is the absolute slowest thing going to
check a module out from.

Re: [gentoo-user] Re: output of emerge -v emacs-vcs (not the masking something else)

[Alan McKinnon]

On Wednesday 06 July 2011 22:54:56 Harry Putnam did opine thusly:
> walt <w41ter@gmail.com> writes:
> > On 07/03/2011 03:07 PM, Harry Putnam wrote:
> >> I'm getting output from emerge -v emacs-vcs like this:
> >>  * ERROR: app-editors/emacs-vcs-24.0.9999-r1 failed (unpack
> >>  phase): *   bzr.eclass: can't pull from
> >>  bzr://bzr.savannah.gnu.org/emacs/trunk/
> >> 
> >> I tried
> >> 
> >>   bzr branch bzr://bzr.savannah.gnu.org/emacs/trunk/
> >> 
> >> by hand and had no problems with it.
> > 
> > I've never used a 9999 version that pulls from bzr, but I have
> > used some that pull from git and (yuk) svn.  The cloned repos
> > were stored (I think) in /usr/portage/disfiles/git (or svn) --
> > or something similar.
> > 
> > If you can find a bzr repo in your /usr/portage/distfiles, try
> > deleting it.  My memory is a bit fuzzy here, but you get the
> > general idea, I hope.
> 
> Haaa... yep, that worked .. (deleting bzr-src)
> 
> I was suprized to learn the repo was created in
> /usr/portage/distfiles
> 
> I thought it would happen in /var/tmp.  Well, now I know... thanks.

Repo checkouts can be very very big, so you don't want to re-download 
everything every time you build a -9999 package, hence the use of 
persistent storage.

Using svn as an example, the first time you emerge the package portage 
will do a checkout. On subsequent times it will do an update, saving 
huge amounts of bandwidth.


> 
> If you happen to do an `emerge emacs-vcs' be prepared for a really
> looonnnnggg wait on bzr.  It is the absolute slowest thing going to
> check a module out from.
-- 
alan dot mckinnon at gmail dot com