Your message dated Tue, 07 Mar 2006 03:02:27 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#353861: fixed in ssed 3.62-1 has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)
--- Begin Message ---Package: ssed Version: 3.60-2.1 Severity: serious When I build ssed under pbuilder, the build succeeds. However, the resulting package then fails to install with: frobnitz:~# dpkg -i /tmp/ssed_3.60-2.1_i386.deb Selecting previously deselected package ssed. (Reading database ... 9312 files and directories currently installed.) Unpacking ssed (from /tmp/ssed_3.60-2.1_i386.deb) ... Setting up ssed (3.60-2.1) ... No `START-INFO-DIR-ENTRY' and no `This file documents'. install-info(/usr/share/info/ssed.info.gz): unable to determine description for `dir' entry - giving up dpkg: error processing ssed (--install): subprocess post-installation script returned error exit status 1 Errors were encountered while processing: ssed This is probably from the following in the build-log: ... # Adjust info files to say ssed instead of sed OLDWD=`pwd`; cd /tmp/buildd/ssed-3.60/debian/ssed/usr/share/info; \ for f in *; do \ sed 's/^\* sed: (sed)/\* ssed: (ssed)/; \ s/sed.info/ssed.info/' $f > s$f ; \ rm $f; \ done; cd $OLDWD sed: -e expression #1, char 85: unterminated address regex ... which results in empty files being output. (Also, you should be using set -e in that or setting SHELL=/bin/sh -e, so the sed failure within the for loop would result in a build failure instead of broken packages.) -- Daniel Schepler
--- End Message ---
--- Begin Message ---Source: ssed Source-Version: 3.62-1 We believe that the bug you reported is fixed in the latest version of ssed, which is due to be installed in the Debian FTP archive: ssed_3.62-1.diff.gz to pool/main/s/ssed/ssed_3.62-1.diff.gz ssed_3.62-1.dsc to pool/main/s/ssed/ssed_3.62-1.dsc ssed_3.62-1_i386.deb to pool/main/s/ssed/ssed_3.62-1_i386.deb ssed_3.62.orig.tar.gz to pool/main/s/ssed/ssed_3.62.orig.tar.gz A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ganesan Rajagopal <[EMAIL PROTECTED]> (supplier of updated ssed package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.7 Date: Tue, 7 Mar 2006 16:19:33 +0530 Source: ssed Binary: ssed Architecture: source i386 Version: 3.62-1 Distribution: unstable Urgency: low Maintainer: Ganesan Rajagopal <[EMAIL PROTECTED]> Changed-By: Ganesan Rajagopal <[EMAIL PROTECTED]> Description: ssed - The super sed stream editor Closes: 219988 219988 240217 262132 342430 353861 Changes: ssed (3.62-1) unstable; urgency=low . * New upstream release (Closes: #219988, #262132, #219988). * Acknowledge NMU (Closes: #240217). * Update standards version. * Copy updated config.{guess,sub} before building (Closes: #342430). * Update DH_COMPAT version to 4 to avoid lintian warning. * Fix build breakage with new make (Closes: #353861). Files: d776c6d8d803720ca184cb86f571b551 578 utils extra ssed_3.62-1.dsc 8f35882af95da4e5ddbf3de1add26f79 855644 utils extra ssed_3.62.orig.tar.gz 9128d34ad370776f95b21becd007eb72 41141 utils extra ssed_3.62-1.diff.gz 97716176864ee00ec087a668baa73e45 178602 utils extra ssed_3.62-1_i386.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFEDWZrFeACul2MEuoRAunXAJoDCUOPU0PeuAeoySFyg9OVJjoe2wCgwEjA TsQwoBLCF/sxzDgTllgQKrE= =DwpJ -----END PGP SIGNATURE-----
--- End Message ---
