Release Jed 0.99.18-1

[Rafael Laboissiere]

* Rafael Laboissiere <rafael at debian.org> [2006-05-13 18:24]:

> I will try to build the package during this weekend.

I just tried it and fixed two minor problems in debian/changelog and
debian/rules, as well as the Lintian warnings related to debconf. Thanks
very much for pushing this, Jürgen, I really appreciate your efforts.

The package builds now correctly but there are some issues that must be
addressed before the upload to unstable.  

First, when I tried to upgrade the package in my unstable chroot, it
failed with the error message:

========================================================================
$ debi
(Reading database ... 89003 files and directories currently installed.)
Preparing to replace jed 0.99.18-1 (using jed_0.99.18-1_i386.deb) ...
Unpacking replacement jed ...
Preparing to replace xjed 0.99.18-1 (using xjed_0.99.18-1_i386.deb) ...
Unpacking replacement xjed ...
Preparing to replace jed-common 0.99.16-6 (using jed-common_0.99.18-1_all.deb) ...
Unpacking replacement jed-common ...
dpkg: error processing jed-common_0.99.18-1_all.deb (--install):
 trying to overwrite `/usr/share/man/man1/jed.1.gz', which is also in package jed
rmdir: /etc/jed-init.d: Directory not empty
[...]
debi: debpkg -i failed
========================================================================

This problem has nothing to do with version 0.99.18-1, but with the
postrm script in version 0.99.16-6.  Unfortunately, this script was
changed from version 0.99.16-5 to version 0.99.16-6 in a wrong way. It
contained in version 0.99.16-5:

    if [ -z "`/bin/ls /etc/jed-init.d/`" ]; then 
      rmdir /etc/jed-init.d
    fi

In version 0.99.16-6, it changed to:

    if [ -d /etc/jed-init.d/ ]; then 
      rmdir /etc/jed-init.d
    fi

This change was done by Guenter on 2005-11-08 with the following log
message:

    simplified test syntax as it failed on GNU bash, version
    3.00.16(1)-release (i386-pc-linux-gnu) (trying to remove nonexistent dir)

The code above obviously fails when the directory exists but is
non-empty.  The goal of the code in 0.99.16-5 was completely different:
remove the /etc/jed-init.d/ directory only when it is empty.  It is very
unfortunate that this slipped into a version in unstable.  

The problem can be circumvented if we revert the changes in version
0.99.18-1, because dpkg tries to use the new postrm script when the one
of the version currently installed fails.

My question to Guenter: could you revert or, if possible, write a code
that works correctly and is compatible GNU bash 3.00.16(1)?

After reverting the postrm code, I ran into the following problem:

========================================================================
# debi
(Reading database ... 89003 files and directories currently installed.)
Preparing to replace jed 0.99.18-1 (using jed_0.99.18-1_i386.deb) ...
Unpacking replacement jed ...
Preparing to replace xjed 0.99.18-1 (using xjed_0.99.18-1_i386.deb) ...
Unpacking replacement xjed ...
Preparing to replace jed-common 0.99.16-6 (using
jed-common_0.99.18-1_all.deb) ...
Unpacking replacement jed-common ...
dpkg: error processing jed-common_0.99.18-1_all.deb (--install):
 trying to overwrite `/usr/share/man/man1/jed.1.gz', which is also in
package jed
dpkg-deb: subprocess paste killed by signal (Broken pipe)
[...]
========================================================================

Indeed, jed.1.gz appears in both jed and jed-common packages.  This must
be fixed.
 
-- 
Rafael