Bug#123393: marked as forwarded (tetex-bin: when /var/lib/texmf/ls-R is 0 bytes long cron job gives error and can't fix)
Your message dated Wed, 9 Jul 2003 10:22:08 +0200
with message-id <20030709082208.GA32674@preusse-16223.user.cis.dfn.de>
has caused the Debian Bug report #123393,
regarding tetex-bin: when /var/lib/texmf/ls-R is 0 bytes long cron job gives error and can't fix
to be marked as having been forwarded to the upstream software
author(s) Thomas Esser <te@informatik.uni-hannover.de>.
(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 123393-forwarded) by bugs.debian.org; 9 Jul 2003 08:24:45 +0000
>From hille42@web.de Wed Jul 09 03:24:34 2003
Return-path: <hille42@web.de>
Received: from smtp03.web.de (smtp.web.de) [217.72.192.158]
by master.debian.org with esmtp (Exim 3.35 1 (Debian))
id 19aAFe-0007G5-00; Wed, 09 Jul 2003 03:24:34 -0500
Received: from [213.7.208.72] (helo=preusse-16223.user.cis.dfn.de)
by smtp.web.de with asmtp (WEB.DE 4.98 #232)
id 19aAFc-0002na-00; Wed, 09 Jul 2003 10:24:33 +0200
Received: by preusse-16223.user.cis.dfn.de (Postfix, from userid 1000)
id 7BED74752; Wed, 9 Jul 2003 10:22:08 +0200 (CEST)
Date: Wed, 9 Jul 2003 10:22:08 +0200
From: Hilmar Preusse <hille42@web.de>
To: Thomas Esser <te@informatik.uni-hannover.de>
Cc: 123393-forwarded@bugs.debian.org
Subject: (fwd) tetex-bin: when /var/lib/texmf/ls-R is 0 bytes long cron job gives error and can't fix
Message-ID: <20030709082208.GA32674@preusse-16223.user.cis.dfn.de>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="BXVAT5kNtrzKuDFl"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
User-Agent: Mutt/1.3.28i
Organization: Hilmar Preusse Inc.
X-Uptime: 10:12:46 up 21 days, 10:38, 3 users, load average: 1.01, 1.02, 1.00
X-Operating-System: Linux 2.4.21 i686
X-www.distributed.net: OGR: 92 packets (4412.47 stats units) [2.35 Mnodes/s]
X-Confirmation-Request: yes
X-Confirm-Reading-To: "Hilmar Preusse" <hille42@web.de>
Sender: hille42@web.de
Delivered-To: 123393-forwarded@bugs.debian.org
X-Spam-Status: No, hits=-13.1 required=4.0
tests=BAYES_01,FROM_ENDS_IN_NUMS,HAS_PACKAGE,PATCH_UNIFIED_DIFF,
USER_AGENT_MUTT
autolearn=ham version=2.53-bugs.debian.org_2003_06_27
X-Spam-Level:
X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debian.org_2003_06_27 (1.174.2.15-2003-03-30-exp)
--BXVAT5kNtrzKuDFl
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
Hi Thomas,
This bug has been sitting in the DBTS now for a while and is
collecting SPAM. IMHO that the bug(?) should be fixed in mktexlsr.
I've included a small patch. I don't know, if you like it and if this
is generally a good idea.
Should fit to mktexlsr 1.32 2002/10/22.
Just my 0.002 ¢,
Hilmar
----- Forwarded message from russell@coker.com.au -----
From: russell@coker.com.au
To: submit@bugs.debian.org
Subject: tetex-bin: when /var/lib/texmf/ls-R is 0 bytes long cron job gives error and can't fix
Date: Tue, 11 Dec 2001 10:53:06 +0100 (CET)
Message-Id: <20011211095306.EF6215CB3@lyta.coker.com.au>
X-Mailer: bug 3.3.10
Package: tetex-bin
Version: 1.0.7+20011202-1
Severity: normal
Cron gives the following error:
/etc/cron.daily/tetex-bin:
mktexlsr: /var/lib/texmf/ls-R lacks magic string. Skipping...
I think that the /etc/cron.daily/tetex-bin script should check for a
0 byte file (caused by disk getting full at the wrong time) and
remove it before running /usr/bin/mktexlsr to avoid this problem.
----- End forwarded message -----
--
sigmentation fault
--BXVAT5kNtrzKuDFl
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="mktexlsr.diff"
--- mktexlsr Sat Jun 21 00:00:00 2003
+++ mktexlsr.new Wed Jul 9 10:09:37 2003
@@ -86,6 +86,7 @@
cp /dev/null "$db_file"
# Use same permissions as parent directory, minus x,s, or t bits.
chmod `kpsestat -xst "$db_dir"` "$db_file"
+ elif test ! -s "$db_file"; then true
elif test "x`sed '1s/
$//;1q' \"$db_file\"`" != "x$ls_R_magic" \
&& test "x`sed '1s/
$//;1q' \"$db_file\"`" != "x$old_ls_R_magic"; then
echo "$progname: $db_file lacks magic string. Skipping..." >&2
--BXVAT5kNtrzKuDFl--
Reply to: