Your message dated Thu, 23 May 2013 11:04:38 +0200
with message-id <[email protected]>
and subject line Re: Bug#709267: cron-apt: Syntax error: "in" unexpected
has caused the Debian Bug report #709267,
regarding cron-apt: Syntax error: "in" unexpected
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
709267: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709267
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: cron-apt
Version: 0.9.1
Severity: important
Dear Maintainer,
Since a couple of days I receive an email message from Cron Daemon
with the following content:
/usr/sbin/cron-apt: 381: /usr/sbin/cron-apt: Syntax error: "in" unexpected
Line 381 of /usr/sbin/cron-apt contains the mentioned "in" instead
of "if".
Please fix.
Best regards,
Angel Ortega
-- System Information:
Debian Release: 7.0
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-4-486
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages cron-apt depends on:
ii apt 0.9.7.8
Versions of packages cron-apt recommends:
ii cron 3.0pl1-124
ii heirloom-mailx [mailx] 12.5-2
ii liblockfile1 1.09-5
cron-apt suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi
Thanks for the file. It is clearly a "random error" that have
occured on your system. My guess is that you have some kind of
bit errors on your disk.
Please see the attached diff file. There you can see quite a few
random changes in a few places.
I'll close this bug report and I think you should check your
disk using the "badblocks" command. :-)
Cheers,
// Ola
On Thu, May 23, 2013 at 07:12:28AM +0200, Angel Ortega wrote:
> 2013/5/22 Ola Lundqvist <[email protected]>:
>
> > I can not find any "in" in the source I have. Could you please
> > send me the file so I can have a look.
>
> Of course. Please find it attached to this message.
>
> > And you are sure there is no chance that this file may have
> > been modified by anyone on your system?
>
> No. I'm the only user on this system.
>
> I've replaced the "in" by an "if", but today I had received another
> error. I think the file went corrupted somehow in the wheezy
> transition.
>
> I've --reinstall'ed the package and the "in" is no longer an "if", so
> you may file this in the "unexplainable" folder and move on.
>
> Thanks for your help and keep the good work,
> Angel Ortega
--
--- Inguza Technology AB --- MSc in Information Technology ----
/ [email protected] Annebergsslingan 37 \
| [email protected] 654 65 KARLSTAD |
| http://inguza.com/ Mobile: +46 (0)70-332 1551 |
\ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 /
---------------------------------------------------------------
--- End Message ---
