[SCM] packaging of Crypt::Urandom in Debian branch, master, updated. upstream/0.31-14-g808a91c

[Alexandre Mestiashvili]

The following commit has been merged in the master branch:
commit 808a91c13a2f459b6eaf2305e07bf1c4c0c7a2de
Author: Alexandre Mestiashvili <alex at biotec.tu-dresden.de>
Date:   Mon Apr 29 15:52:29 2013 +0200

    TODO needs a review.
    
    Git-Dch: Ignore

diff --git a/debian/changelog b/debian/changelog
index f508930..171164d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -4,20 +4,34 @@ libcrypt-urandom-perl (0.34-1) UNRELEASED; urgency=low
   * since, 0.29-1 was never uploaded into the archive, you can merge the two
     changelog entries (keeping just "Initial Release"). And there's yet
     another new upstream version!
+
+  - Updated.
+
   * the build-dependency on "perl (>= 5.11.1) | libextutils-parsexs-perl (>=
     2.21)" seems to be bogus - where does that come from?
-  - it comes from the initial dh_make
+
+  - The build-dependency comes from the initial dh_make...
+     I've removed libextutils-parsexs-perl from the control file and the pckage
+     build fine without it.
+  - Do I also need a version for the perl package? 
+
   * this is an Architecture: all package, that is: no XS, nothing that needs to
     be compiled, no arch-dependent binary packages. So: no need to depend on a
     specific minor version of debhelper, and if you want to be nice to people
     backporting packages to squeeze, you can lower dh compatibility to 8 as
     there's no difference between 8 and 9 for non-XS packages; keep
     only debhelper in B-D, and move the other dependencies to B-D-I.
+
+  - I see, I've moved libtest-pod-perl,perl to B-D-I.
+     if I set debhelper to 8, than I get the following:
+     W: libcrypt-urandom-perl source: package-needs-versioned-debhelper-build-depends 9
+
   * the short description is meant to fit into the sentence "$package is a
     ...", in your case "libcrypt-urandom-perl is a module provides non
     blocking randomness". I'd suggest to change this to either "module THAT
     provides...", "module providing..." or "module to provide..."
-  - fixed
+
+  - Yes, doesn't sound nice :), fixed.
 
   * Initial Release. (Closes: #702567)
 

-- 
packaging of Crypt::Urandom in Debian