gmane.comp.version-control.bazaar-ng.general

Re: [ANN] bzr-2.5.1 has been frozen !

Gordon Tyler — 2012-05-26T03:33:18

Mac OS X installer uploaded. Includes the following packages (* updated
since 2.5.0):

paramiko 1.7.7.1
pycrypto 2.4.1
*bzr 2.5.1
sip 4.13
PyQt-mac-gpl 4.8.6
launchpadlib 1.9.12
*python-fastimport 0.9.2
*dulwich 0.8.5
subvertpy subvertpy-0.8.10
bzrtools release-2.5
bzr-colo 0.4.0
bzr-email r52
bzr-explorer release-1.2.2
*bzr-fastimport r356 (tip)
*bzr-git bzr-git-0.6.8
*bzr-loom bzr-loom-2.2.0
bzr-pipeline release-1.4
*qbzr release-0.22.3
*bzr-rewrite bzr-rewrite-0.6.3
bzr-upload bzr-upload-1.1.0
bzr-xmloutput r161
*bzr-svn bzr-svn-1.2.2
bzr-keychain r15

Re: [ANN] bzr-2.5.1 has been frozen !

Alexander Belchenko — 2012-05-23T14:36:25

Vincent Ladeuil пишет:

Please, use QBzr 0.22.3 for installers.

[ANN] bzr-2.5.1 has been frozen !

Vincent Ladeuil — 2012-05-22T15:28:05

Now is the time for our first minor release in the 2.5 series: 2.5.1

Packagers and installers builders, it's up to you again !

See the Changelog at https://launchpad.net/bzr/2.5/2.5.1 for more
details about what is included and for the tarball.

I'll make the official announcement next Tuesday morning UTC
(2011-05-29) with... whatever packages/installers are available at this
point.

Have fun !

    Vincent

Re: bzr commit e-mail fails with bzr 2.4.x and 2.5.x on Fedora Core 14

Gaiseric Vandal — 2012-05-18T16:42:55


Sorry- I stand corrected.

I forgot to add the post_commit_to back into branch.conf

With revision 54, bzr email notification hook works as long as I have
the following set

        post_commit_mailer=smtplib


With out smtplib, I still get an error


-> bzr commit --message "test" --unchanged
Committing to:
/home/myname/bzr/localrepo/localrepo1/                         
Committed revision
73.                                                        
From: myname< at >company.com : No such file or directory
: ERROR: Failed to send email: exit status 1

But I can manage with out that with "smtplib" does work.

Thanks for your help

Re: bzr commit e-mail fails with bzr 2.4.x and 2.5.x on Fedora Core 14

Gaiseric Vandal — 2012-05-18T16:22:26


r 55 has the same problems  as the current one (r 57).
r 54 and r50 don't give me any errors, but I don't get any mail.


Thanks

Re: bzr commit e-mail fails with bzr 2.4.x and 2.5.x on Fedora Core 14

Vincent Ladeuil — 2012-05-18T14:15:17

<snip/>

    > If I have "post_commit_mailer=smtplib" in my bazaar.conf set, then I get
    > the following error.

    -> pwd
    >         /home/myname/bzr/workspace/localrepo1
    -> bzr commit --unchanged -m "test"
    >         Committing to:
    > /home/myname/bzr/localrepo/localrepo1/                                                                

    >         Committed revision
    > 39.                                                                                               

    >         bzr: ERROR: exceptions.AttributeError: 'SMTPConnection' object
    > has no attribute 'send_text_email'

That's a recent regression in the email plugin :-(

Reverting to revno 55 should work around the issue.

  cd ~/.bazaar/plugins/email
  bzr pull -r55 --overwrite


          Vincent

Re: post_transform_hook syntax etc

Martin Packman — 2012-05-17T13:15:04

As John mentioned, it's just that the hook point in on MutableTree not
Branch. Try <lp:~gz/+junk/treetransform_hook_example> for starting
off.


Having looked again, this seems like it might be a little more
painful, as I'm not sure of how you get the changes just made from a
tree transform, so post_transform doesn't tell you which files were
changed. In pre_transform, you can get the changes due to happen with
iter_changes, see the docstring on InterTree.iter_changes in
bzrlib/tree.py for the format. Not sure the best way forward from
there, either stash the info and act on it in post_transform, or edit
the transform somehow. Jelmer or Vincent may have better ideas.

Martin

Re: post_transform_hook syntax etc

John Arbash Meinel — 2012-05-17T12:58:36

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 5/17/2012 2:39 PM, phil wigglesworth wrote:
is present in 2.5 of the bzr library (I'm using 2.5.0).

post_transform is not a branch hook, it is a mutable tree hook.

from bzrlib import mutabletree

def post_transform_hook(tree, transform):
  print 'post_transform_hook'

mutabletree.MutableTree.hooks.install_named_hook('post_transform', ...)

I don't know a lot about the details, but that should get you closer
to what you want.

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk+09fwACgkQJdeBCYSNAAP2EACguw3Y2vIPxo2qUY9/w50bXS82
aP4An35ztzAGiUDVTN6F08AX+GoFP0P9
=g8kf
-----END PGP SIGNATURE-----

post_transform_hook syntax etc

phil wigglesworth — 2012-05-17T12:39:46

I'm trying to work around a
problem<https://bugs.launchpad.net/bzr/+bug/997933>(997933) in Bazaar
(bzrlib 2.5.0). The defect causes Bazaar to trample on
inherited file permissions on files in Win7-64, so that when anyone in the
team changes anything, everyone else gets "file permission" errors on that
changed file. That defect report is not the subject of this post, the
work-around is.

My problem working around that defect is how to create a "post transform
hook", which as far as I can
see<https://code.launchpad.net/%7Ejelmer/bzr/transform-hooks/+merge/89007>is
present in 2.5 of the bzr library (I'm using 2.5.0).

Syntax-wise I have this in my hook file:

from bzrlib import branch

def post_transform_hook():
   print "post_transform_hook"

branch.Branch.hooks.install_named_hook('post_transform',
post_transform_hook, 'My post_transform hook')

Running that garners me the message: "The BranchHooks hook 'post_transform'
is unknown in this version of bzrlib."

Does anyone know what the problem is? I've no real

Re: What is the purpose of `rmbranch` command?

Stefan Monnier — 2012-05-17T02:19:35

Ha!  Just what I needed, thanks!


        Stefan

Re: What is the purpose of `rmbranch` command?

Aaron Bentley — 2012-05-16T17:11:36

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 12-05-16 11:44 AM, Stefan Monnier wrote:

There's always hitchhiker, and for some sites, an sftp client works too.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk+z38QACgkQ0F+nu1YWqI3Q9gCfXrmAYn3o8hnyIQlMRQW9zhGZ
ekIAn1m/Z2MRUBL3Wsmfp8YF72GNUVuT
=neEm
-----END PGP SIGNATURE-----

Re: bzr commit e-mail fails with bzr 2.4.x and 2.5.x on Fedora Core 14

Gaiseric Vandal — 2012-05-16T16:28:10

That helps somewhat

I thought the bzrtools would include the necessary email plugins.  I
thought (incorrectly) bzr might just have a  single e-mail plugin     I
wasy able to use the " bzr branch lp:bzr-email email" command to install
the plugins for myself.  (I was also able to use "python setup.py
install" to install the plugins system wide, rather than just for myself.

bzr plugins -v now shows

email
  Sending emails for commits and branch changes.
   /usr/lib/python2.7/site-packages/bzrlib/plugins/email

That directory containers emailer.py. 

Now when I "bzr commit" I do get error messages about mail delivery.  So
I at least know the plugin is being called.

If I have "post_commit_mailer=smtplib" in my bazaar.conf set, then I get
the following error.

        -> pwd
        /home/myname/bzr/workspace/localrepo1
        -> bzr commit --unchanged -m "test"
        Committing to:
/home/myname/bzr/localrepo/localrepo1/                                                                

        Committed revi

Re: What is the purpose of `rmbranch` command?

Stefan Monnier — 2012-05-16T15:44:08

There are plenty of remote Bzr servers that do not offer access via
a shell.  I really wish I could rename and delete branches (and the
corresponding directories) without needing access to a shell.


        Stefan

Re: What is the purpose of `rmbranch` command?

Alexander Belchenko — 2012-05-16T13:16:44

John Arbash Meinel пишет:

Yes, that was my intuitive expectation.

I'm OK with any behavior and don't claim current behavior as bug, but 
I'd like to understand the intent of `rmbranch` command.

I see why Jelmer said that it was only useful for colocated branches.

My question arose because I tried to remove branch from bzr server 
(bzr:// protocol + Trac) with that command, and I found that `rmbranch` 
left almost everything on the server. That was confusing. (of course I 
was able to inspect what's left on disk to understood what'd happened).

Now I better understand why other people confused, see
http://stackoverflow.com/questions/10474291/remove-a-parent-branch-in-bazaar/

I can only imagine a simple way to improve the current status-quo:
print something to the user when `bzr rmbranch URL:/to/branch` command 
finishes, something about

`URL:/to/branch` is no more valid bzr branch, but still present on the disk.

In general, beyond colocated usage, this command is almost useless.

And I should note

Re: What is the purpose of `rmbranch` command?

Vincent Ladeuil — 2012-05-16T12:49:41

    > On Wed, May 16, 2012 at 02:17:24PM +0200, Vincent Ladeuil wrote:
    >> >>>>> Jelmer Vernooij <jelmer< at >vernstok.nl> writes:
    >> 
    >> <snip/>
    >> 
    >> >> I don't think Alexander asked for a separate command. Instead, AIUI, his
    >> >> point is that it makes little sense to remove the branch and leave an
    >> >> otherwise *empty* control directory (not to mention other possible bugs
    >> >> when trying to interact with this empty directory).
    >> 
    >> > This isn't always the case though - there can be other colocated
    >> > branches, a repository or a working tree. We have no way to remove a
    >> > repository for example.
    >> 
    >> But in those cases, the control directory (we're all talking about
    >> '.bzr' not '.bzr/branch' right ?) is therefore not empty.
    > That makes the behaviour of "bzr rmbranch" fairly unpredictable
    > though.

Hmm, I don't fully agree but better understand your point.

    > I can see the argument for removing a control directory if it's

Re: What is the purpose of `rmbranch` command?

Jelmer Vernooij — 2012-05-16T12:24:01

That makes the behaviour of "bzr rmbranch" fairly unpredictable
though.

I can see the argument for removing a control directory if it's
completely empty, but I think we should be more consistent about that
- "bzr remove-tree" should do the same, and we should have a way to
remove a repository from a control directory.

Cheers,

Jelmer

Re: What is the purpose of `rmbranch` command?

Jelmer Vernooij — 2012-05-16T12:22:06

What Vincent and Alexander are arguing is that in that case the
target/ directory should be kept around - it still contains a
repository.

I don't like the idea of automatically removing the control directory
in the case when only .bzr/branch exists (and no .bzr/checkout or
.bzr/repository) since it makes the behaviour of "bzr rmbranch"
unpredictable.

Cheers,

Jelmer

Re: What is the purpose of `rmbranch` command?

Vincent Ladeuil — 2012-05-16T12:17:24

<snip/>

    >> I don't think Alexander asked for a separate command. Instead, AIUI, his
    >> point is that it makes little sense to remove the branch and leave an
    >> otherwise *empty* control directory (not to mention other possible bugs
    >> when trying to interact with this empty directory).

    > This isn't always the case though - there can be other colocated
    > branches, a repository or a working tree. We have no way to remove a
    > repository for example.

But in those cases, the control directory (we're all talking about
'.bzr' not '.bzr/branch' right ?) is therefore not empty.

I don't think bialix is arguing about those valid cases.

  Vincent

Re: What is the purpose of `rmbranch` command?

John Arbash Meinel — 2012-05-16T12:13:39

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

...


bzr branch --no-tree lp:bzr target
bzr rmbranch target

Arguably, there should be no 'target/' directory left. Certainly that
is what people expect.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk+zmfMACgkQJdeBCYSNAAOTjwCdGiLyQM9W9RAzNM7oRiFgBn67
UgYAoJUO/ewAsxyGuGpGj/VALDF0PrwN
=b4F6
-----END PGP SIGNATURE-----

Re: What is the purpose of `rmbranch` command?

Jelmer Vernooij — 2012-05-16T10:53:58

This isn't always the case though - there can be other colocated
branches, a repository or a working tree. We have no way to remove a
repository for example.

As far as I understand this would unversion the current directory, which
would seem a bit odd. Am I misunderstanding something?

Cheers,

Jelmer

Re: bzr commit e-mail fails with bzr 2.4.x and 2.5.x on Fedora Core 14

Vincent Ladeuil — 2012-05-16T09:49:46

    > I am running Fedora Core 14 (X64.) I have uninstalled bzr 2.2.x
    > packages. I have installed bzr 2.5.0 and bzr 2.5.0 from source I have
    > also tried with bzr 2.6.B1 and bzr 2.4.2 + bzr plugins 2.4.1 .

mail on commits didn't change for ages so all versions above should
work.

    > I want to enable commit e-mails. I have been trying to get this to work
    > over the network (bzr+ssh or sftp) but with out luck. I have therefore
    > created a local repository on my computer.

    >                    /home/myname/bzr/localrepo/localrepo1

    > which I have now checked out to

    >                    /home/myname/bzr/workspace/localrepo1

This is what I use:

in ~/.bazaar/bazaar.conf:

  [DEFAULT]
  smtp_server = localhost
  post_commit_mailer = smtplib

Note that 'smtp_server' reflects my local setup, use whatever is
appropriate for you (an smtp server replying on the default 25 port or
use stmp_server=host:port if you use a non-standard port).

in ~/.bazaar/locations.conf:

  [/home/vila/s