Comment 8 for bug 347983

The proposed karmic branch doesn't include the latest version of the karmic package (1.0.29.1-0ubuntu0.9.04.1).

Could you prepare a new version that is based on the latest version in karmic (there is a bzr branch available at lp:ubuntu/karmic/landscape-client)? Could you also update the changelog to only have one entry for the upload, similar to:

landscape-client (1.3.2.2-0ubuntu0.9.10.0) karmic; urgency=low

  * New upstream release:
    - Include the README file in landscape-client (LP: #396260)
    - Fix client capturing stderr from run_command when constructing
      hash-id-databases url (LP: #397480)
    - Use substvars to conditionally depend on update-motd (LP: #393454)
    - Fix reporting wrong version to the server (LP: #391225)
    - The init script does not wait for the network to be available
      before checking for EC2 user data (LP: #383336)
    - When the broker is restarted by the watchdog, the state of the client
      is inconsistent (LP: #380633)
    - Package stays unknown forever in the client with hash-id-databases
      support (LP: #381356)
    - Standard error not captured when calling smart-update (LP: #387441)
    - Changer calls reporter without switching groups, just user (LP: #388092)
    - Run smart update in the package-reporter instead of having a cronjob (LP: #362355)
    - Package changer does not inherit proxy settings (LP: #381241)
    - The ./test script doesn't work in landscape-client (LP: #381613)
    - The source package should build on all supported releases (LP: #385098)
    - Strip smart update's output (LP: #387331)
    - The fetch() timeout isn't based on activity (#389224)
    - Client can use a UUID of "None" when fetching the hash-id-database (LP: #381291)
    - Registration should use the fqdn rather than just the hostname (LP: #385730)

 -- Free Ekanayaka <email address hidden> Tue, 09 Jun 2009 09:27:43 +0200

landscape-client (1.0.29.1-0ubuntu0.9.04.1) karmic; urgency=low

  * debian/control: depend on libpam-modules, rather than update-motd

 -- Dustin Kirkland <email address hidden> Thu, 16 Jul 2009 11:36:27 -0500

In this use case I've just merge all of the 1.3.2{,1,2} entries?

The lp:ubuntu/karmic/landscape-client/ and lp:~landscape-client/ branch have no common ancestor but you should be able to figure out which revision to merge from lp:~landscape-client/ into lp:ubuntu/karmic/landscape-client/.