tigercron script fails on Linux 3.0

[Ole Wolf]

Starting /usr/sbin/tigercron on a 3.0 kernel produces the following output:

$ sudo /usr/sbin/tigercron
Configuring...

Will try to check using config for 'x86_64' running Linux 3.0.0-12-generic...
--CONFIG-- [con007c] No configuration files for Linux. Using default
           configuration files. Not all checks may be performed.
--ERROR-- [init001e] Don't have required command DIFF.

It appears to be a result of the kernel version bump to 3.0, because the following workarounds make it work:

1. sudo ln -s /usr/lib/tiger/systems/Linux/2 /usr/lib/tiger/systems/Linux/3

or

2. sudo cp -a /usr/lib/tiger/systems/Linux/2 /usr/lib/tiger/systems/Linux/3

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: tiger 1:3.2.3-7
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu3
Architecture: amd64
Date: Sun Oct 16 22:23:23 2011
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcEnviron:
 LANGUAGE=da_DK:en_US:en
 PATH=(custom, user)
 LANG=da_DK.UTF-8
 LC_MESSAGES=da_DK.UTF-8
 SHELL=/bin/bash
SourcePackage: tiger
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Loïc (opensource-loic)]

Hi,

In addition to this report, and for the same reason, tiger can't find a configuration file named "config" on a 3.x kernel :
/usr/lib/tiger/config: line 360: /config: No such file or directory

This issue can be answered by the same quick fix Ole Wolf suggested, but there's also a coding typo in the /usr/lib/tiger/config script, line 351, where the closing } is including the definition of the default CONFIG_DIR in the quiet check. Patch to fix this part of the bug is attached.

[Ubuntu Foundations Team Bug Bot (crichton)]

The attachment "partial fix" of this bug report has been identified as being a patch. The ubuntu-reviewers team has been subscribed to the bug report so that they can review the patch. In the event that this is in fact not a patch you can resolve this situation by removing the tag 'patch' from the bug report and editing the attachment so that it is not flagged as a patch. Additionally, if you are member of the ubuntu-reviewers team please also unsubscribe the team from this bug report.

[This is an automated message performed by a Launchpad user owned by Brian Murray. Please contact him regarding any issues with the action taken in this bug report.]

[François Marier (fmarier)]

This got fixed in version 1:3.2.3-8 of the package.

A new bug has been filed for Linux 4: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785589