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

Releasing 2.6 [Was: bzr-hookless-email doesn't work with bzr 2.6]

Andrew Starr-Bochicchio — 2013-05-23T05:15:47

Bazaar's development process has always made be comfortable using
snapshots. The extensive regression tests led to it being fairly
solid. The most recent releases of both Debian and Ubuntu shipped
snapshots of 2.6dev. Though there are obviously people that feel
uncomfortable about using software labeled beta (especially when the
future of the project doesn't look quite so bright). Maybe it's time
to tag a 2.6 release?

What would it take for us to get there? Is this something people would
be interested in seeing?

There see to be four bugs currently targeted at 2.6~b3. One of them
has a merge proposal with an "approve" vote that hasn't been landed.
[2]

[1] https://launchpad.net/bzr/+milestone/2.6b3
[2] https://code.launchpad.net/~rosslagerwall/bzr/cmdline-empty-quotes/+merge/138995

Thanks!

share repo branches backup and multi-push

Chris Hecker — 2013-05-22T19:48:11

1.  What's the right way to back up a shared repo with a few branches 
under it?  I've been just archiving the repo .bzr directory, but then I 
got worried there was information in the branches that wasn't 
recoverable without them, but then I found bzr head --tips, which seems 
to correspond to the branches exactly?  Hmm, no, wait, if I unarchive 
the .bzr into a directory that doesn't have the branches in it, then bzr 
heads --tips doesn't actually print anything.  So, can I recover the 
branches from just the .bzr directory of the shared repo?  Do I need to 
archive all the branch .bzr dirs too?

2.  I asked a while back about "multi-push" to complement multi-pull. 
There isn't one, and I could write one, but from searching it also seems 
like there are a few other old plugins, like repo-push, and mirror.  I 
have a directory that has a few shared repos below it, which each have 
some branches below them.  I'd like to push them all recursively. 
What's the best bet for this?

Thanks,
Chris

late versioning

Lucio Crusca — 2013-05-14T13:55:47

Hello *,

I'm new to bazaar and I've just decided to start using a VCS for my code. I'm 
a bit late... I already have two "versions" of a project, say branch A and 
branch B, that sooner or later will have to merge. Version A is where I 
develop new features, while version B is the stable one where I just backport 
important fixes (by hand, e.g. copy & paste from A). I call them "versions" and 
not "branches" because, as of today, they aren't under any VCS.

Now I need to implement a new feature, somewhat bigger than a simple fix, and 
the customer can't wait until the features already partially implemented in 
branch A become finished and stable: I need to implement that feature starting 
from the code of branch B and then, sometimes in the future, merge that 
feature into A when A will be stable.

What should I do to start doing things the right way? Should I "bzr init" both 
directories? And then?

Thanks in advance
Lucio.

bzr-hookless-email doesn't work with bzr 2.6

Glenn Morris — 2013-05-10T17:15:46

Hi,

savannah.gnu.org uses bzr-hookless-email for commit notifications.
Recently, the system was updated to bzr 2.6 (somehow, this
never-to-be-finished beta version is the version in Debian stable).

Now bzr-hookless-email fails, because bzr 2.6 removed the
"revision_history" that it uses.

We found this bug report:
https://bugs.launchpad.net/bzr-hookless-email/+bug/988195

Applying the patch from there made it work again, for a while.

Now it is failing for the Emacs repository, with this error:

    Traceback (most recent call last):
      File "/usr/src/bzr-hookless-email/bzr_hookless_email.py", line 347, in <module>
        main()
      File "/usr/src/bzr-hookless-email/bzr_hookless_email.py", line 79, in main
        branch.update()
      File "/usr/src/bzr-hookless-email/bzr_hookless_email.py", line 147, in update
        msg = self._compose_email(revision)
      File "/usr/src/bzr-hookless-email/bzr_hookless_email.py", line 210, in _compose_email
        rev1 = rev2 = self._branch.revision_id_to_revn

"bzr branch" downloads 10x the whole repo size through "dumb" http server (format 2a)?

Marcin Wojdyr — 2013-05-03T13:56:15

Hi all,
I see that bzr is not developed anymore, but maybe some developers are
still around.
That's the same question I asked on LP a week ago:
https://answers.launchpad.net/bzr/+question/227479

We have a few bzr repositories with anonymous "dumb" http access and
we observe that branching repository 150MB repository transfers 1.5GB
of data. After the download the size of new repository is the same as
the old one, 150MB. By the size of repository I mean the size of .bzr.
Similar thing was observed with other repos and on other computers.

Is this a known issue?

I googled and the only relevant discussion I found is this:
http://osdir.com/ml/bazaar/2010-01/msg00660.html

So it's clear that the overhead is necessary for "pull", but is it the
same for "branch"?

Clients: bzr 2.5 on Linux and OSX, server: Apache.

Marcin

Website issues continued

Denys Duchier — 2013-04-20T20:06:32

I am still unable to access the wiki:

   http://wiki.bazaar.canonical.com/

As a result: the "Download", "Extras" and "Help" tabs of the website
don't work

Cheers,
--Denys

Bazaar book from Packt

Alexander Belchenko — 2013-04-20T07:05:29



Hi,
I'd like to mention there is book about Bazaar to be published this
spring:
http://www.packtpub.com/bazaar-version-control/book
Author of the book is Janos Gyerik https://launchpad.net/~janos-gyerik
I've been asked to review several chapters of the book, mostly about
advanced features, like using shelve, aliases, light checkouts and so on,
interacting with other VCSes, and programming bzr (plugins/hooks).I think
for chapter about bzr-svn and bzr-git Jelmer would be better reviewer ;-)
I think the author did a very good work to create such book. Even though
it appears only now.
Alexander

Website issues

Martin Packman — 2013-04-12T04:01:02

As several people reported yesterday, the Bazaar docs website is
having some issues. There's an internal ticket filed for resolving
this, though I'm travelling today so won't be able to chase it up. As
a workaround, rather than visiting the root and getting stuck in a
redirect loop, go to the language you want directly, so
<http://doc.bazaar.canonical.com/en/> and so on.

Martin

Is there a command to check if a revision is later than another (ie is a parent or ancestor of another).

Nicholas Allen — 2013-03-22T07:45:32

Hi,

Our software has an auto bug reporting feature and we know the revision 
id when the software crashes. If we fix the crash we mark the report as 
fixed and with the revision it is fixed in. If the report comes in again 
I would like the auto reporter to check if the version it crashed in is 
later than the version it was fixed in and if so reopen the issue. Also 
when I annotate a file it would be nice to be able to ask Bazaar on the 
command line "Is revision x later than revision y". That way I can also 
manually check stuff based on the line that was fixed and the revision 
that annotate shows me.

Is this possible or is there a simple plugin for this?

Cheers,

Nick

keywords: a problem and a question

M Busche — 2013-03-04T17:33:34

I've recently downloaded and installed this:


    bzr branch lp:bzr-keywords

Here's my bzr version info:

matt< at >meteor:cpp$ bzr --version
Bazaar (bzr) 2.5.1
  Python interpreter: /usr/bin/python 2.6.5
  Python standard library: /usr/lib/python2.6
  Platform: Linux-2.6.32-45-generic-i686-with-Ubuntu-10.04-lucid
  bzrlib: /usr/lib/pymodules/python2.6/bzrlib
  Bazaar configuration: /home/matt/.bazaar
  Bazaar log file: /home/matt/.bzr.log



THE PROBLEM:

Some keywords seem to work, and others do not.  Can anyone explain this result for my initial  commit-and-update cycle (where I was just trying out all the documented keywords)?  The first four tags are failing for some reason.


# $Date: (evaluation error) $
# $Committer: (evaluation error) $
# $Authors: (evaluation error) $
# $Revision-Id$
# $Path: cpp/SConstruct $
# $Filename: SConstruct $
# $Directory: cpp $
# $File-Id: sconstruct-20130130234613-01rcjondtjg69hz1-1 $
# $Now: Sat 2013-03-02 10:53:46 +0700 $
# $User: Matthew Busche <matt< at >meteor.m

BzrTools odd version mismatch message.

David Ingamells — 2013-03-04T07:28:50

Hi all, (especially Aaron)
Just encountered a confusing message from BzrTools:

$ bzr shell
Plugin "Bzrtools" is not up to date with installed Bazaar version 2.4.2.
There should be a newer version of Bzrtools available, e.g. 2.4.
bzr bzr:31/>

According to the BzrTools home page 
(http://doc.bazaar.canonical.com/plugins/en/bzrtools-plugin.html) 
version 2.3.0 is the latest!

I have installed from source:
BZR_VERSION=bzr-2.4.2
BZR_GTK_VERSION=bzr-gtk-0.100.0
BZRTOOLS_VERSION=bzrtools-2.3.0

Bazaar workflow question...

2013-02-20T21:28:29


Hello all,

   I have a question for the Bazaar community. We transitioned from VSS to
Bazaar about 18 months ago, with fairly good success, but we're having some
workflow issues, and I was hoping someone might have some suggestions.

Basically we have the following workflow:
1) A single master branch exists which contains all of our common code.
This branch only acts as a container; development and releases are handled
elsewhere.
2) For each planned product/release, the common code is branched, and
development for the product/release is done in the new branch.
3) At various points during the product/release branch's life cycle, merges
between the common code and product/release branches take place, and
revisions need to occasionally be shared between product/release branches
themselves.
4) When a product releases, the final state of the product/release branch
is merged into the common code, and the product/release branch is archived.

We haven't figured out the best way to keep branches synchronized. Both

Anyone have a plugin for sharing revisions between Bzr and DropBox?

Doug Lee — 2013-02-20T21:24:27

This may seem like an odd request, but I wonder if anyone has written
a Bazaar plugin that interfaces with the DropBox API to allow Bazaar
direct access to DropBox folder revisions. I don't know if
bidirectional linkage is practical, but I think it would be possible
to make Bazaar capable of following DropBox revisions, even
incrementally.

Thanks much for any info.

startup

Tim Cummings — 2013-02-08T20:51:05

Hello, I am looking for a Bazaar project manager for a short term opportunity in the Flint Michigan  area. Must have strong knowledge of Bazaar. Hoping someone can help me. My phone number is: 517-918-7015. e-mail: tcummings< at >centurytool.com<mailto:tcummings< at >centurytool.com>

We use Component Software CS-RCS Basic. We have to be able to check in and out Binary files. We only want to save the most recent 5 revisions. We want 2 shared repositories. We are hoping we can migrate all our files from CS-RCS Basic to Bazaar. We need at least 35 users(clients). Users should have access to both repositories.     Thanks

bzr lessons

Martin Pool — 2013-02-05T08:23:40

I gave a talk last week at linux.conf.au about things that I learned from
working on Bazaar and Launchpad, good and bad, and that covered most of
what I have to say.  The slides and notes are in <http://goo.gl/FPley>.
 There will be a video at some point when they're done editing them.

AUTO: Chris Kalisiak is out of the office. (returning 02/05/2013)

2013-02-02T15:01:30

I am out of the office until 02/05/2013.

I will respond to your message when I return.


Note: This is an automated response to your message  "bazaar Digest, Vol
96, Issue 1" sent on 2/2/2013 7:00:03 AM.

This is the only notification you will receive while this person is away.

bzrlib.errors.MalformedTransform: Tree transform is malformed

Guy Gascoigne-Piggford — 2013-02-01T22:29:17

I've been trying to merge between two branches, where in the parent branch
a series of directory trees have been deleted. This results in a
MalformedTransform error.

I logged a bug with more details
https://bugs.launchpad.net/bzr/+bug/1105358a few days ago.

Now I sort of know how I can work around it by explicitly generating the
diff, editing out the missing revisions and then just doing checkins in the
other branch but that will leave the branch as not knowing that a merge has
occurred, but I'm concerned that from this point onwards the error will
continue to occur and we'll be stuck doing manual merges between these
branches in the future.

Can anyone suggest a better way around the problem.

Thanks - Guy

bzr bd -S, get-orig-source, and quilt patches

Barry Warsaw — 2013-01-22T22:55:30

I'm working on a extending the existing python-whoosh packaging to include
Python 3 support.  The current released upstream tarball isn't Python 3.3
compatible, but its Mercurial repository is.  I've written a
get-{packaged-}orig-source target in my d/rules that does the right thing and
with some very inconvenient testing[1], am fairly certain my new rules work.

Now I've pushed my branch to lp:~barry/ubuntu/raring/python-whoosh/py3 but
`bzr bd -S` doesn't work, because I've modified d/patches/*.patch to fix a
problem in the hg trunk, and this doesn't apply to the unpacked source tree in
the raring branch.

Maybe what I'm trying to do is too stupid to succeed, but I thought I'd at
least ask to see if anybody has suggestions.  Is it possible to modify an
existing source branch with a new tarball containing a quilt patch that
doesn't apply to the source branch?

Cheers,
-Barry


[1] Involving unpacking the hg tarball and `cp -a`ing the debian directory
into there.  No, symlinking didn't work because of:

$ deb

Bazaar doc and sphinx: how customizations are done?

Dedeco — 2013-01-10T15:50:45

Hello,

I started to play with Sphinx-doc a little while ago, and today I was 
trying to understand how some customizations of Bazaar documentation are 
done.

Namely:
- how you got rid of some blank pages for latex output, making the PDF 
more concise
- how you got rid of header and footer

I think the "culprit" is this line in conf.py:

from bzrlib.doc_generate.conf import *

Now... how do I find the files it is importing, so I can check them out? 
Unfortunately, Bazaar documentation isn't compilable with this line 
commented.

Thanks,

Dedeco

Bazaar doc and sphinx: how customizations are done?

Dedeco — 2013-01-10T17:17:54

Hello,

I started to play with Sphinx-doc a little while ago, and today I was 
trying to understand how some customizations of Bazaar documentation are 
done.

Namely:
- how you got rid of some blank pages for latex output, making the PDF 
more concise
- how you got rid of header and footer

I think the "culprit" is this line in conf.py:

from bzrlib.doc_generate.conf import *

Now... how do I find the files it is importing, so I can check them out? 
Unfortunately, Bazaar documentation isn't compilable with this line 
commented.

Thanks,

Dedeco

revision id format stability?

Chris Hecker — 2013-01-10T06:31:15

How stable is the revision id format?  I'd like to include it in a 
version resource, but I don't want my email in there, so I want to stomp 
the domain name part in a script, but if the email or domain has dashes 
in it...etc.

Chris