[Bug 272120] Re: Please sync bzr-builddeb 2.0.1 (universe) from Debian experimental (main)

James Westby jw+debian at jameswestby.net
Mon Sep 22 17:36:46 BST 2008


** Summary changed:

- [Freeze exception] Update to version 2.0.1
+ Please sync bzr-builddeb 2.0.1 (universe) from Debian experimental (main)

** Description changed:

+ Hi,
+ 
+ Please sync bzr-builddeb from experimental, as it has loads of
+ fixes we want for Intrepid.
+ 
+ Thanks,
+ 
+ James
+ 
+ =====
+ Freeze exception request:
+ 
+ 
  Binary package hint: bzr-builddeb
  
  Hi,
  
  I'd like permission to upload bzr-builddeb 2.0.1 (via Debian).
  
  This is a release specifically for Intrepid. It mainly fixes bugs, but there is one
  new feature that I considered essential, hence my request for a freeze exception.
  
  You can see the list of bugs fixed at
  
    https://edge.launchpad.net/bzr-builddeb/+milestone/2.0.1
  
  The new feature is to provide a "package:" revisionspec, which allows you to
  more easily do things like diff two versions of a package.
  
  The new feature comes in a 69 line file, plus tests. I'm fairly confident
  that it won't destabilise things.
  
  Thanks,
  
  James

** Changed in: bzr-builddeb (Ubuntu)
       Status: Confirmed => New

** Description changed:

  Hi,
  
  Please sync bzr-builddeb from experimental, as it has loads of
  fixes we want for Intrepid.
  
  Thanks,
  
  James
+ 
+ 
+ bzr-builddeb (2.0.1) experimental; urgency=low
+ 
+   * Fix retrieval of the upstream source from a watch file of the archive.
+     - It would download to the specified tarball directory, but then
+       report it as stored in the compatibility directory. (bug #262618)
+   * Don't move the result if the source and destination are the same location.
+     (bug #262621)
+   * Use --result-dir rather than --result for concistency with the other
+     options and the configuration key. --result is still accepted, but
+     deprecated. (bug #263643)
+   * Add a revisionspec that allows you to specify a revision by the
+     package version number, e.g. -r package:0.1-1.
+     https://blueprints.launchpad.net/bzr-builddeb/+spec/package-revisionspec
+   * Use the upstream part of the version number when repacking the tarball.
+     (bug #263373)
+   * Merge the upstream tags in to the packaging ones after importing a new
+     upstream. (bug #263373)
+   * Strip the changelog message as debcommit does. Thanks to Colin Watson.
+     (bug #265045)
+   * "Fix" fetching between two locked branches which share a repository.
+     (bug #264705)
+   * Handle remote files in repack check that checksums match when target
+     exists. (bug #263371)
+   * Fix the README to mention bzrtools is required.
+   * Depend on at least 0.1.11 of python-debian for strict=False support.
+   * Check that versions are in the ancestry of the current branch.
+     (bug #264701)
+   * Fix locking problems with merge_upstream in shared repository.
+   * Handle invalid version numbers in the changelog by ignoring them.
+     (bug #248447)
+   * During merge-upstream correctly check whether the new upstream is
+     already imported. (bug #272118)
+ 
+  -- James Westby <james.westby at canonical.com>  Mon, 22 Sep 2008 12:04:09
+ +0100
+ 
  
  =====
  Freeze exception request:
  
  
  Binary package hint: bzr-builddeb
  
  Hi,
  
  I'd like permission to upload bzr-builddeb 2.0.1 (via Debian).
  
  This is a release specifically for Intrepid. It mainly fixes bugs, but there is one
  new feature that I considered essential, hence my request for a freeze exception.
  
  You can see the list of bugs fixed at
  
    https://edge.launchpad.net/bzr-builddeb/+milestone/2.0.1
  
  The new feature is to provide a "package:" revisionspec, which allows you to
  more easily do things like diff two versions of a package.
  
  The new feature comes in a 69 line file, plus tests. I'm fairly confident
  that it won't destabilise things.
  
  Thanks,
  
  James

-- 
Please sync bzr-builddeb 2.0.1 (universe) from Debian experimental (main)
https://bugs.launchpad.net/bugs/272120
You received this bug notification because you are a member of Ubuntu
Sponsors for universe, which is a direct subscriber.



More information about the Ubuntu-universe-sponsors mailing list