[DRE-commits] [ruby-rspec] 14/15: update README.source

Cédric Boutillier boutil at moszumanska.debian.org
Mon Jun 15 07:48:15 UTC 2015


This is an automated email from the git hooks/post-receive script.

boutil pushed a commit to branch master
in repository ruby-rspec.

commit cf5b54794e2dbc0305455506d28d12bae96a981d
Author: Cédric Boutillier <boutil at debian.org>
Date:   Mon Jun 15 09:38:34 2015 +0200

    update README.source
---
 debian/README.source | 16 ++++++----------
 1 file changed, 6 insertions(+), 10 deletions(-)

diff --git a/debian/README.source b/debian/README.source
index 9b8cc0a..224f445 100644
--- a/debian/README.source
+++ b/debian/README.source
@@ -1,8 +1,6 @@
 This package is maintained in a Git repository on Alioth.
 
-It uses the Debian 3.0 (quilt) source format, with multiple upstream tarballs.
-As such, it cannot follow the typical workflow with git-buildpackage as
-git-buildpackage doesn't support (yet?) multiple tarballs.
+It uses the Debian 3.0 (quilt) source format, with a single tarball.
 
 The upstream version has the following form: x.y.0c1e2m3s4-z
 x.y corresponds to the major/minor version of rspec.
@@ -30,9 +28,12 @@ update to a new upstream version
 use the following targets from debian/rules:
 
 - debian/rules get-orig-sources: 
-    download and create the multiple upstream tarballs
+    download the several upstream tarballs
 - debian/rules unpack-sources:
     unpack the sources, to be committed in the upstream branch
+    first, the content of the upstream branch needs to be removed, otherwise
+    files deleted in the newer version may persist, and be shipped inadvertedly
+    in the new source package.
     (awkward, because debian/rules is not present in the upstream branch...)
 - debian/rules gen-gemspecs:
     interpret upstream 'source' gemspec to real ones, with shell commands
@@ -41,9 +42,4 @@ use the following targets from debian/rules:
     update then debian/patches/gemspecs.patch with the diff between upstream
     source gemspecs and the generated ones.
 
-dpkg-source automatically creates an empty upstream main tarball for the source
-package, and will use the several components tarball.
-
-The tarballs are stored in the pristine-tar branch.
-
- -- Cédric Boutillier <boutil at debian.org> 2015-04-01
+ -- Cédric Boutillier <boutil at debian.org> 2015-06-15

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-ruby-extras/ruby-rspec.git



More information about the Pkg-ruby-extras-commits mailing list