Please allow jedstate_0.5.4.transitional.1-1 and jed-extra_2.2.1-1.etch.1

[Rafael Laboissiere]

Request (short):

    Please, allow jedstate_0.5.4.transitional.1-1 and
    jed-extra_2.2.1-1.etch.1 in testing.

Rationale (long):

    Jedstate is a JED add-on which allows the recalling of the cursor
    position when a file is revisited in a future session of the JED editor.
    The functionalities of jedstate have been superseded by the gdbmrecent
    module in the jed-extra package.

    Moreover, there has been no sign of upstream activity in jedstate, its
    original maintainer orphaned the package half a year ago, and jedstate
    is severily broken as regards the current JED initialization system
    (Bug#406815).

    I decided then to make the Debian JED Group adopt the jedstate package
    and transform it into a transition package to allow users migrate their
    jedstate database into the new gdbmrecent database.  I uploaded
    jedstate_0.5.4.transitional.1-1 to unstable, which contains no
    "upstream" files (i.e. *.orig.tar.gz is empty).  It provides only a Perl
    script (jedstate-to-gdbmrecent) which does the migration above. This new
    version of the pacakge also Recommends: jed-extra.

    While testing my personal translated database with the gdbmrecent I
    discovered a bug in the jed-extra package.  I prepared the version of
    2.2.1-1.etch.1 of jed-extra for inclusion in etch.  The changes are
    minimal, essentially the inclusion of
    debian/patches/gdbmrecent-clean-stack.dpatch. The diffs between 2.2.1-1
    (the version currently in testing) and 2.2.1-1.etch.1 are attached
    below.

Thanks in advance,

-- 
Rafael
-------------- next part --------------
Index: debian/patches/gdbmrecent-clean-stack.dpatch
===================================================================
--- debian/patches/gdbmrecent-clean-stack.dpatch	(.../2.2.1-1)	(revision 0)
+++ debian/patches/gdbmrecent-clean-stack.dpatch	(.../2.2.1-1.etch.1)	(revision 544)
@@ -0,0 +1,19 @@
+#! /bin/sh /usr/share/dpatch/dpatch-run
+## gdbmrecent-clean-stack.dpatch by Rafael Laboissiere <rafael at debian.org>
+##
+## DP: Empty the stack in call to purge_not_so_recent() in function
+## DP: gdbm_delete().  The problem was confirmed by the upstream author.
+
+ at DPATCH@
+
+--- jed-extra-2.2.1.orig/gdbmrecent/gdbmrecent.sl
++++ jed-extra-2.2.1/gdbmrecent/gdbmrecent.sl
+@@ -226,7 +226,7 @@
+    foreach(keys)
+      {
+ 	key=();
+-	gdbm_delete(db, key);
++	() = gdbm_delete(db, key);
+      }
+ }
+ 

Property changes on: debian/patches/gdbmrecent-clean-stack.dpatch
___________________________________________________________________
Name: svn:executable
   + *

Index: debian/patches/00list
===================================================================
--- debian/patches/00list	(.../2.2.1-1)	(revision 544)
+++ debian/patches/00list	(.../2.2.1-1.etch.1)	(revision 544)
@@ -1,4 +1,5 @@
+gdbmrecent-clean-stack
 #missing_autoload
-
 #apsmode
 #ding
+
Index: debian/changelog
===================================================================
--- debian/changelog	(.../2.2.1-1)	(revision 544)
+++ debian/changelog	(.../2.2.1-1.etch.1)	(revision 544)
@@ -1,3 +1,12 @@
+jed-extra (2.2.1-1.etch.1) unstable; urgency=low
+
+  * debian/patches/01_gdbmrecent-clean-stack.dpatch: Added patch to fix a
+    bug in purge_not_so_recent(), which did not popped a value in the
+    stack after the call to gdbm_delete().  This patch is blessed by the
+    usptream author. [RL]
+
+ -- Rafael Laboissiere <rafael at debian.org>  Mon,  5 Feb 2007 22:33:54 +0100
+
 jed-extra (2.2.1-1) unstable; urgency=low
 
   New upstream release [GM]