Update landscape-client to 1.0.28

I'm preparing an updated package.

Here's a debdiff.

The debdiff above is for Jaunty.

Here's another debdiff, from 1.0.26.1 to 1.0.28. For Jaunty.

Okay, here are the Feature Freeze Exception details for the jaunty package.

- A description of the proposed changes, with sufficient detail to estimate their potential impact on the distribution

 The description of the changes are in the ticket description. The potential impact isn't too high because most of the changes are either bug fixes or unrelated new features, and they're all thoroughly unit tested.

 34 files changed, 1608 insertions(+), 412 deletions(-)

only 497 of these changes are to non-test files: the other 1200 or so are all test changes.

- A rationale for the exception, explaining the benefit of the change

It would be very helpful for this release to go into Jaunty so that Jaunty users of Landscape will be able to get the new features like EC2 support and non-root mode.

An explanation of the testing which has been performed on the new version in Ubuntu, including verification that the new package:
 - builds
 - installs and upgrades,
 - does not break packages which depend on it, or that corresponding updates have been prepared.

I've done testing on a Jaunty KVM that it builds and upgrades from the previous package, and once installed that it works. No packages depend on landscape-client.

Since this was recently approved for SRU microrelease exceptions, and you did a similar QA, I approve this FFE.

sponsored.

This bug was fixed in the package landscape-client - 1.0.28-0ubuntu1

---------------
landscape-client (1.0.28-0ubuntu1) jaunty; urgency=low

  * New upstream release. (LP: #343954)

 -- Martin Pitt <email address hidden> Wed, 18 Mar 2009 20:42:05 +0100

Actually, there were some problems with that upload. For some reason, the debdiff which I crafted and attached wasn't used, and instead lp:landscape-client trunk was used.

- The changelog entry didn't have all of the details which I included
- The version number that I specified wasn't used, which was carefully crafted to allow Intrepid->Jaunty upgrades to work properly, getting the Jaunty package installed even if the upstream release hasn't changed
- The version number in the landscape code itself is wrong, because lp:landscape-client trunk was used instead of the debdiff based on my release 1.0.28 release branch. This is problematic because this version is actually sent over the wire in our messaging protocol.

I think we'll need another upload to fix these issues.

Christopher,

sorry; I asked about this on IRC yesterday, and therve said that trunk is basically okay, except that 1.0.28 wasn't tagged. The current ubuntu package is a proper branch of trunk, thus applying debdiffs instead of merging would destroy history and the whole point of revision control?

Is there another branch that we should merge from, instead of trunk? I didn't see a 1.0.28 one.

Can you please merge the 1.0.28 release into trunk and tag it appropriately, to fix the version number in the landscape code itself? Please also add the changelog entries you want to see, then I can do another upload which closes all of them.

I'm preparing a new package to fix these issues.

oops, sorry, was out of date when I posted that comment. I'll prepare a new branch based on the ubuntu-core-dev branch.

Okay, I've prepared the branch, it's lp:~radix/landscape-client/jaunty-1.0.28-fixed

It only changes landscape/__init__.py, landscape/setup.py, and the debian changelog.

- This is based on the new upstream release branch with 1.0.28 in its version numbers
- I put in all the changelog entries to explain what changed in 1.0.28 (please see if the changelog is satisfying)
- the version number is 0ubuntu1.9.04.0 to reflect the landscape-client package convention allowing upgrades from previous distros to get the new distro's package.

This bug was fixed in the package landscape-client - 1.0.28-0ubuntu1.9.04.0

---------------
landscape-client (1.0.28-0ubuntu1.9.04.0) jaunty; urgency=low

  * Fix minor packaging issues in last release (LP: #343954)
    - Version number in landscape.VERSION is now correct
    - Fixed package version number to maintain convention
  * The following changes are in the 1.0.28 release:
    - Invalidate package cache when server UUID changes (LP: #339948)
    - Improve the "cloud mode" introduced in 1.0.26 to send more
      disambiguation data (LP: #343942) and allow the EC2 user data to specify
      the exchange and ping URLs (LP: #343947)
    - Allow importing of initial configurations (along with public SSL
      certificates) when running landscape-config (LP: #341705)
    - Support a non-root mode which allows running the client without the
      management functionality (LP: #82159)
    - Automatic cloud registration when there's no user-data to specify an OTP
      now works (LP: #344323)

 -- Christopher Armstrong <email address hidden> Thu, 19 Mar 2009 09:52:03 -0400