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

[Florian Schlichting]

The following commit has been merged in the master branch:
commit 5d56c711ec481b52f649b8f9f8913ca0be6d581e
Author: Florian Schlichting <fsfs at debian.org>
Date:   Sat Apr 27 23:54:20 2013 +0200

    back to UNRELEASED, TODO added to changelog

diff --git a/debian/changelog b/debian/changelog
index bdce273..9692db5 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,4 +1,21 @@
-libcrypt-urandom-perl (0.31-1) unstable; urgency=low
+libcrypt-urandom-perl (0.31-1) UNRELEASED; urgency=low
+
+  TODO:
+  * 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!
+  * the build-dependency on "perl (>= 5.11.1) | libextutils-parsexs-perl (>=
+    2.21)" seems to be bogus - where does that come from?
+  * 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.
+  * 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..."
 
   * Imported Upstream version 0.31
 

-- 
packaging of Crypt::Urandom in Debian