Your message dated Sat, 20 Aug 2005 15:47:04 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#323983: fixed in cron 3.0pl1-89
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)
--------------------------------------
Received: (at submit) by bugs.debian.org; 19 Aug 2005 16:37:10 +0000
>From [EMAIL PROTECTED] Fri Aug 19 09:37:10 2005
Return-path: <[EMAIL PROTECTED]>
Received: from blars.org (renig.nat.blars.org) [64.81.35.59]
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1E69rh-00085M-00; Fri, 19 Aug 2005 09:37:09 -0700
Received: from quaff (quaff.nat.blars.org [172.16.2.7])
by renig.nat.blars.org (8.13.4/8.13.4/Debian-3) with ESMTP id
j7JGb71p022767
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
Fri, 19 Aug 2005 09:37:08 -0700
Received: from quaff.nat.blars.org (quaff [127.0.0.1])
by quaff (8.13.4/8.13.4/Debian-3) with ESMTP id j7JGRuLN027684;
Fri, 19 Aug 2005 09:27:56 -0700
Received: (from [EMAIL PROTECTED])
by quaff.nat.blars.org (8.13.4/8.13.4/Submit) id j7JGRuQu027682;
Fri, 19 Aug 2005 09:27:56 -0700
Date: Fri, 19 Aug 2005 09:27:56 -0700
From: Blars Blarson <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: cron: bashism in /etc/cron.daily/standard
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Reportbug-Version: 3.15
User-Agent: Mutt/1.5.10i
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
Package: cron
Version: 3.0pl1-88
Severity: serious
Justification: Policy 10.4
== is not an operator in posix test, please use = .
/etc/cron.daily/standard:
[: 83: ==: unexpected operator
[: 83: ==: unexpected operator
[: 83: ==: unexpected operator
[: 83: ==: unexpected operator
[: 83: ==: unexpected operator
[: 83: ==: unexpected operator
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/dash
Kernel: Linux 2.4.27-2-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages cron depends on:
ii adduser 3.67 Add and remove users and groups
ii debianutils 2.14.2 Miscellaneous utilities specific t
ii libc6 2.3.5-3 GNU C Library: Shared libraries an
ii libpam0g 0.76-23 Pluggable Authentication Modules l
ii libselinux1 1.24-4 SELinux shared libraries
Versions of packages cron recommends:
ii sendmail-bin [mail-transport- 8.13.4-3 powerful, efficient, and scalable
-- debconf information:
* cron/checksecurity:
---------------------------------------
Received: (at 323983-close) by bugs.debian.org; 20 Aug 2005 22:51:24 +0000
>From [EMAIL PROTECTED] Sat Aug 20 15:51:24 2005
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 3.36 1 (Debian))
id 1E6c7E-0006uC-00; Sat, 20 Aug 2005 15:47:04 -0700
From: Javier Fernandez-Sanguino Pen~a <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.56 $
Subject: Bug#323983: fixed in cron 3.0pl1-89
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Sat, 20 Aug 2005 15:47:04 -0700
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
Source: cron
Source-Version: 3.0pl1-89
We believe that the bug you reported is fixed in the latest version of
cron, which is due to be installed in the Debian FTP archive:
cron_3.0pl1-89.diff.gz
to pool/main/c/cron/cron_3.0pl1-89.diff.gz
cron_3.0pl1-89.dsc
to pool/main/c/cron/cron_3.0pl1-89.dsc
cron_3.0pl1-89_i386.deb
to pool/main/c/cron/cron_3.0pl1-89_i386.deb
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.
Javier Fernandez-Sanguino Pen~a <[EMAIL PROTECTED]> (supplier of updated cron
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: Sun, 21 Aug 2005 00:12:26 +0200
Source: cron
Binary: cron
Architecture: source i386
Version: 3.0pl1-89
Distribution: unstable
Urgency: low
Maintainer: Javier Fernandez-Sanguino Pen~a <[EMAIL PROTECTED]>
Changed-By: Javier Fernandez-Sanguino Pen~a <[EMAIL PROTECTED]>
Description:
cron - management of regular background processing
Closes: 323983
Changes:
cron (3.0pl1-89) unstable; urgency=low
.
* Fix bashishm in cron.daily script (Closes: #323983)
Files:
921db0f8e6ab030af3eabd1b523fed4e 770 admin important cron_3.0pl1-89.dsc
ffb7b81e61d9b721c7909232b8f2d786 48497 admin important cron_3.0pl1-89.diff.gz
fd8e4a297d01b592d44129178fd4db13 59808 admin important cron_3.0pl1-89_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iQCVAwUBQwerXftEPvakNq0lAQJGzAP/W4oIDUHag7DtdsV5OHUEJMWkvzv5zCKE
TXN7u7EEXJ2hVRwejwSr1BNnpFrFhQS3GTcH7Pj8g8ZX4rnVfo/jPQe4GChAVJ/a
CZarcU/RknQnHdaOw70J7Hdi6SOAoJamp2A/tBVbX7r3dJ5UHN74n/GG1/gprALG
dPEdzFTXL38=
=DF32
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
