No subject

If you need I may look in some places for paramiko or run some tests.

Also I just reboot this PC and 0.15 crash DISAPPEAR. IMO it could be
something wrong with http://sshwindows.sourceforge.net/ installer.

sshd was uninstalled (PC rebooted a few times after sshwindows
uninstall) before installing 0.15. When I realized than accesss to old
location fro unbinding is mandatory I installed it (without PC rebooting
- sshwindows did not ask for).

Also just before running 0.15 installer I moved 0.14 folder from \bzr to
\bzr--0.14 and installed 0.15 into \bzr

If Python uses some kind of lib caching (i.e. unpacks zips into %TEMP%)
then it could be possible that 0.15 used 0.14 cache. Just a guess - I'm
not familiar with Python.

>
>> OK, I decided to bzr 0.14 unbind/bind to UNC patch in hope to forget
>> about SSH - no luck. 0.14 (and 0.15) still ask for SSH password. I
>> looked in <branch>\.bzr\branch\location and there is still sftp URL so
>> it just silently exited from bind call, without any notifications that
>> bind failed or is not possible at all.
>
> So you're trying to unbind from the ssh location and bind to a UNC
> location, and that fails because you can't reach the ssh server?

Just retested. Results are slightly different (no crashing) but the same
for 0.14 and 0.15.

Sequence of operations was as follows:
1) try to unbind - fail because it was uanble to access to sshd (it was
stopped).

Output was:
ssh: connect to host <host> port 22: Connection refusedbzr: ERROR:
Unable to connect to SSH host <host>; EOF during negotiation

2) started sshd, try unbind - connected to sshd, asked for password,
logged in and failed.

Output was:
bzr: ERROR: Local branch is not bound

<branch>\.bzr\branch\location has valid sftp url.

3) sshd working, try bind (whout unbind) - connected to sshd, asked for
password, logged in, no extra output.

<branch>\.bzr\branch\location remains unchanged - points to sftp
location instead to UNC.

4) manul <branch>\.bzr\branch\location editing (changed to UNC patch) -
works fine (ran bzr log to test).

>
>> Next, suggestion: why not to just allow rebind without connecting to
>> server? What if server is not (and won't) available anymore and mobile
>> user will have to use mirror? (checkout from server A to notebook;
>> server A crash; rebind to server B and use it. I agree that mobile user
>> won't use lightweight checkout, but anyway it would be useful)
>
> I agree that if you're trying to unbind from a server we shouldn't
> talk to it anymore.  Is that what you're seeing?  
Yes
> It's more
> contentious whether we should talk to the new master when you connect,
> or only when you first try to update or commit.
Agree.
>
>> And last, question: when do you expect to have 1.0? (I know - it is hard
>> to tell but could you try please?)
>
> I think after a few (2-3?) more monthly cycles from here.  I think the
> main things we need to do are to speed up network access, close some
> more bugs and improve documentation.  What do you think we should do
> for 1.0?
>
Well, I'm learning Bazaar though using it in real work so I'm not aware
of all aspects.

As for now my priorities would be:

1) stability - I'm earning developing something. It is critical to be
100% sure that I've access to my sources.
2) large binary files support - somewhat blocking/annoying, see
https://bugs.launchpad.net/bzr/+bug/90943 for details.
....
N) performance in case of large number of controlled files (i.e 10000
files in my case)

Nice to have:

a) Integration with support of 3rd party bug tracking/other systems (I
posted my idea but it does not seem to be posted on list according to
https://lists.ubuntu.com/archives/bazaar/2007q1/thread.html, so I'm
attaching this post).


Best regards,
Andrew Voznytsa



--------------030409050902020701040702
Content-Type: message/rfc822;
 name="Attached Message"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="Attached Message"

Message-ID: <460F074B.9020408 at gmail.com>
Date: Sun, 01 Apr 2007 04:13:47 +0300
From: Andrew Voznytsa <andrew.voznytsa at gmail.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: bazaar at lists.canonical.com
Subject: Launchpad Bugs feature
X-Enigmail-Version: 0.94.3.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Hi all,

just read this message about bug feature - nice, I'm actually thinking
of some integrated system.

My idea of bug tracking with bazaar was to have server side hook to
integrate bzr daemon and bug tracking (BT) system. On checkout request
hook had to connect to bt get list of bugs/feature requests/etc export
it in some file format and give it as file to user. On checkin it had to
analize this bug-list file and commit send changes to BT.

For example, on checkout it may give me something in format like

<bug>
<id>id</id>
<description>bug</description>
<state>not fixed</state>
</bug>

after bug fixing I may simply change state to fixed and just commit
changes. Why file - just because if I checkout I'm getting project state
on the disk in file and don't have to remember or look somewhere else to
get actual info. And it looks nice for me ;)

I guess it could be possible to allow this hook to write some HTML
application to allow users edit this file in browser; Hook could be done
as plugin; etc.

I heard that Mantis BT (I'm using it currently) support SOAP and it
could be possible to get/set bug state (hope this makes sense - I don't
know a lot about Web/XML technologies a log - I work in multimedia
field, and mainly with MPEG bits).

-- 
Best regards,
Andrew Voznytsa



--------------030409050902020701040702--