[SCM] Debian branch, master, updated. debian/1.2.2-3-26-g9bf217d

[Xavier Guimard]

The following commit has been merged in the master branch:
commit 9bf217d2d2a6834cc46db4a4f0e4a2e7434ff14c
Author: Xavier Guimard <x.guimard at free.fr>
Date:   Sat Apr 13 08:21:04 2013 +0200

    Remove comments to propose it to unstable

diff --git a/debian/changelog b/debian/changelog
index 049c200..c3e2e62 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,40 +1,4 @@
-lemonldap-ng (1.2.3-1) UNRELEASED; urgency=low
-
-  TODO:
-  - I am not sure all package dependencies are complete and correct, but I got
-    confused and this may in part be an upstream problem. A thorough audit may
-    be useful?
-    Examples:
-      + lemonldap-ng-handler does not have a dependency on
-        libapache-session-perl, but it's META.yml mentions
-        Apache::Session::Generate::MD5
-        => Handler depends on lemonldap-ng-conf which depends on
-           libapache-session-perl
-      + lemonldap-ng-handler's META.yml states that the build requires
-        Cache::Memcached, but libcache-memcached-perl was removed from B-D
-        -I?
-        => upstream error, not needed in tests
-      + does B-D-I need a dependency on libconvert-pem-perl for
-        Lemonldap::NG::Manager (see warning in build log)?
-        => Not for tests, only for run
-
-  THINGS TO THINK ABOUT
-  (no need to fix for release, or at all - it's up to you / upstream)
-  - is it useful to ship omegat.files/* as part of the released tarball? Some
-    of them are very big, with lots of changes, and I wouldn't expect people
-    working on translations to use the tarball, but rather an SVN checkout
-    directly?
-    => will be done in next release (make dist will be ajusted to remove this)
-  - does there need to be an upstream debian directory in the tarball -
-    wouldn't it be enough to have it in the VCS, but not package it? The
-    problem in this case is that changes that are made upstream are merged
-    into the master branch, even without conflicts, and they are not accounted
-    for by commits on the master branch, thus may escape the maintainer's
-    attention. Case in point: the "Merge tag 'upstream/1.2.3'" commit doesn't
-    just change debian/control, it also changes README.Debian but this is
-    somehow invisible! See also
-    http://wiki.debian.org/DebianMentorsFaq#What.27s_wrong_with_upstream_shipping_a_debian.2F_directory.3F
-    => will be done in next release (make dist will be ajusted to remove this)
+lemonldap-ng (1.2.3-1) unstable; urgency=low
 
   [ Salvatore Bonaccorso ]
   * Change Vcs-Git to canonical URI (git://anonscm.debian.org)
@@ -49,7 +13,7 @@ lemonldap-ng (1.2.3-1) UNRELEASED; urgency=low
   * Fix permissions in debian/rules instead of in postinst scripts and add
     lintian-overrides files to hide lintian permissions warnings
 
- -- Xavier Guimard <x.guimard at free.fr>  Sun, 07 Apr 2013 13:46:05 +0200
+ -- Xavier Guimard <x.guimard at free.fr>  Sat, 13 Apr 2013 08:20:42 +0200
 
 lemonldap-ng (1.2.2-3) unstable; urgency=low
 

-- 
Debian