"action not yet supported by current app_suite" when trying Pull in Bazaar Explorer in Windows 7

Asked by Jon Loldrup

Why this?
"action not yet supported by current app_suite"
when trying Pull in Bazaar Explorer in Windows 7 (using the toolbar button).

Isn't pull an essential command? Without it, I can't get access to the content of the branch.. Is Bazaar explorer for Windows in Alpha stage?

I imported the branch fine using 'Open URL' and entering this URL:

sftp://<email address hidden>/home/bzr/repo/trunk

and supplying my password.

Jon
ps. the branch has no working tree. Could that make a difference?

Question information

Revision history for this message
Martin Pool (mbp) said :
#1

Pull does normally work. Did you get any other details in that error message?

Revision history for this message
Jon Loldrup (loldrup) said :
#2

It also happens on linux. see attachment.

Mvh. Jon Loldrup

On 9 January 2011 04:53, Martin Pool
<email address hidden>wrote:

> Your question #140711 on Bazaar Explorer changed:
> https://answers.launchpad.net/bzr-explorer/+question/140711
>
> Status: Open => Answered
>
> Martin Pool proposed the following answer:
> Pull does normally work. Did you get any other details in that error
> message?
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
>
> https://answers.launchpad.net/bzr-explorer/+question/140711/+confirm?answer_id=0
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https://answers.launchpad.net/bzr-explorer/+question/140711
>
> You received this question notification because you are a direct
> subscriber of the question.
>

Revision history for this message
Pablo Trabajos (pajarico) said :
#3

I'm getting the same in windows 7. The "Show details" button shows me this:

Profile names is: qbzr
Action identifier: pull

bazaar version 2.2.1-3, standalone installer.

Revision history for this message
Alexander Belchenko (bialix) said :
#4

Bazaar Explorer on Windows is *not* in Alpha stage. But I can't reproduce this bug.

Revision history for this message
Alexander Belchenko (bialix) said :
#5

Can you open a bug report and provide more information, including screenshots and relevant part of .bzr.log?

Revision history for this message
Alexander Belchenko (bialix) said :
#6

And I need output of `bzr info` from the location where you're trying to invoke pull.

Revision history for this message
Pablo Trabajos (pajarico) said :
#7

Is this what you need?

Run command: bzr info
Lightweight checkout (format: 2a)
Location:
  light checkout root: .
   checkout of branch: http://bazaar.launchpad.net/~inkscape-webadmin/inkscape-web/inkscape-web/

Revision history for this message
Alexander Belchenko (bialix) said :
#8

If you have lightweight checkout then you need "update" command, not pull, to update your working copy.

Is it what you need?

Revision history for this message
Pablo Trabajos (pajarico) said :
#9

I cannot reproduce it anymore. I was using Pull to get a first copy of the branch. Finally I used "branch" command to get it and works. Pull also works once once I got the branch, but I will use Update as you told me from now on. I don't have much experience and maybe was using the wrong commands.

Revision history for this message
Jon Loldrup (loldrup) said :
#10

Now i dont have the error anymore so I cant reproduce.

On 11 January 2011 10:28, Alexander Belchenko <
<email address hidden>> wrote:

> Your question #140711 on Bazaar Explorer changed:
> https://answers.launchpad.net/bzr-explorer/+question/140711
>
> Alexander Belchenko requested for more information:
> Can you open a bug report and provide more information, including
> screenshots and relevant part of .bzr.log?
>
> --
> To answer this request for more information, you can either reply to
> this email or enter your reply at the following page:
> https://answers.launchpad.net/bzr-explorer/+question/140711
>
> You received this question notification because you are a direct
> subscriber of the question.
>

Revision history for this message
Jon Loldrup (loldrup) said :
#11

Ah well the problem is still there. I didn't look the right place
yesterday. see attached screenshot.
also find 'bzr info' from the server and the bzr.log file from the Windows
computer.

bzr@happybox:~/repo/trunk$ bzr info
Repository tree (format: 2a)
Location:
  shared repository: /home/bzr/repo
  repository branch: .

Jon

On 12 January 2011 06:51, Jon Loldrup
<email address hidden>wrote:

> Your question #140711 on Bazaar Explorer changed:
> https://answers.launchpad.net/bzr-explorer/+question/140711
>
> Status: Answered => Open
>
> You are still having a problem:
> Now i dont have the error anymore so I cant reproduce.
>
>
> On 11 January 2011 10:28, Alexander Belchenko <
> <email address hidden>> wrote:
>
> > Your question #140711 on Bazaar Explorer changed:
> > https://answers.launchpad.net/bzr-explorer/+question/140711
> >
> > Alexander Belchenko requested for more information:
> > Can you open a bug report and provide more information, including
> > screenshots and relevant part of .bzr.log?
> >
> > --
> > To answer this request for more information, you can either reply to
> > this email or enter your reply at the following page:
> > https://answers.launchpad.net/bzr-explorer/+question/140711
> >
> > You received this question notification because you are a direct
> > subscriber of the question.
> >
>
> --
> You received this question notification because you are a direct
> subscriber of the question.
>

Revision history for this message
Alexander Belchenko (bialix) said :
#12

Jon, I don't see here any attachments and I'm sure questions don't allow you to attach anything to it. So again, please file a bug report and attach all files there.

Revision history for this message
Alexander Belchenko (bialix) said :
#13

It's definitely not implemented yet feature for remote branches. See linked bug report.

Can you help with this problem?

Provide an answer of your own, or ask Jon Loldrup for more information if necessary.

To post a message you must log in.