Updating local branches from Launchpad

2.) And why it is showing revision → 128 in my cygwin console whereas it is showing 140 in launchpad.net/dhis2 site’s code tab ?

I think this has to do with you not having commit rights, and therefore checking out a branch, which means you probably have to do “bzr merge” instead of “bzr update” in order to get the latest fix from Lars (which was in 139).

A small annoyance about having to do it this way is that bzr then always reports being at revision 128, ie.e you cannot really see what revision you have on your machine.

You could check out a complete new branch at revision 140, but that would be even more annoying. Maybe someone has a better suggestion? In any case, we should have this (the intricacies of keeping code up to date depending on how it has been checked out) well documented on the wiki. Is that something you could do, Brajesh?

Knut

···

On Wed, Apr 1, 2009 at 9:44 AM, Knut Staring knutst@gmail.com wrote:

On Wed, Apr 1, 2009 at 9:21 AM, Brajesh brajesh2murari@gmail.com wrote:

Cheers,
Knut Staring

Hello again,

Just want to make sure everyone is up to date with this pretty vital information on how to work with the source code for those of us that are not core programmers. Thanks to Ola for correcting my statement below.

The correct procedure is:

  1. To get the code the first time, do “bzr branch lp:dhis2”

  2. To get latest update (always do this before “mvn install”), do “bzr pull lp:dhis2”

http://208.76.222.114/confluence/display/DOC/Downloading+the+source+code

Knut

···

On Wed, Apr 1, 2009 at 9:46 AM, Knut Staring knutst@gmail.com wrote:

On Wed, Apr 1, 2009 at 9:44 AM, Knut Staring knutst@gmail.com wrote:

On Wed, Apr 1, 2009 at 9:21 AM, Brajesh brajesh2murari@gmail.com wrote:

2.) And why it is showing revision → 128 in my cygwin console whereas it is showing 140 in launchpad.net/dhis2 site’s code tab ?

I think this has to do with you not having commit rights, and therefore checking out a branch, which means you probably have to do “bzr merge” instead of “bzr update” in order to get the latest fix from Lars (which was in 139).

A small annoyance about having to do it this way is that bzr then always reports being at revision 128, ie.e you cannot really see what revision you have on your machine.

You could check out a complete new branch at revision 140, but that would be even more annoying. Maybe someone has a better suggestion? In any case, we should have this (the intricacies of keeping code up to date depending on how it has been checked out) well documented on the wiki. Is that something you could do, Brajesh?

Knut


Cheers,
Knut Staring


Cheers,
Knut Staring

“bzr pull” is enough here.

···

On Wed, Apr 1, 2009 at 10:59 AM, Knut Staring knutst@gmail.com wrote:

Hello again,

Just want to make sure everyone is up to date with this pretty vital information on how to work with the source code for those of us that are not core programmers. Thanks to Ola for correcting my statement below.

The correct procedure is:

  1. To get the code the first time, do “bzr branch lp:dhis2”
  1. To get latest update (always do this before “mvn install”), do “bzr pull lp:dhis2”

Are you sure? I got a nasty error message when trying that.

k

···

2009/4/1 Lars Helge Øverland larshelge@gmail.com

On Wed, Apr 1, 2009 at 10:59 AM, Knut Staring knutst@gmail.com wrote:

Hello again,

Just want to make sure everyone is up to date with this pretty vital information on how to work with the source code for those of us that are not core programmers. Thanks to Ola for correcting my statement below.

The correct procedure is:

  1. To get the code the first time, do “bzr branch lp:dhis2”
  1. To get latest update (always do this before “mvn install”), do “bzr pull lp:dhis2”

“bzr pull” is enough here.

Cheers,
Knut Staring

Hello again,

Just want to make sure everyone is up to date with this pretty vital information on how to work with the source code for those of us that are not core programmers. Thanks to Ola for correcting my statement below.

The correct procedure is:

  1. To get the code the first time, do “bzr branch lp:dhis2”
  1. To get latest update (always do this before “mvn install”), do “bzr pull lp:dhis2”

“bzr pull” is enough here.

Are you sure? I got a nasty error message when trying that.

I probably got the error since I had a checkout and not a branch. But then it worked fine when I supplied lp:dhis2 at the end.

k

···

2009/4/1 Knut Staring knutst@gmail.com

2009/4/1 Lars Helge Øverland larshelge@gmail.com

On Wed, Apr 1, 2009 at 10:59 AM, Knut Staring knutst@gmail.com wrote:

k

Cheers,
Knut Staring


Cheers,
Knut Staring