I'm not certain it's about a missing logfile. I just notice that I stopped
getting error messages altogether when I entered manually: ninja
mydefaultconfig instead of ninja start. With that in mind, is it possible to
make a dummy configuration file named start in order to stop the error messages
when it's intially installed?
-----Original Message-----
From: Martin Pitt <martin.p...@ubuntu.com>
To: for...@usa.com
Sent: Fri, Jul 16, 2010 8:13 am
Subject: [Bug 560336] Re: package ninja 0.1.3-1 failed to install/upgrade: die:
error: `/var/log/ninja.log' is not a regular file
It seems to me that a more proper fix would be to make the daemon create
the log file itself if it's missing? You currently create it as owner
root, so permission-wise it makes no difference. But it will help in the
cases where people (or cron jobs) clean /var/log/*. Also, if at all this
should be in the postinst, otherwise you'd create a file if the package
fails to unpack for other reasons.
logcheck is stretching SRU criteria a bit, but it seems fine to me.
The init script changes are too much for SRU for my taste. Fixing the
wrong Required-Start:/Stop "$all" is okay, but rewriting the entire
thing could cause too much trouble. Note that the package is not
entirely uninstallable, it just fails to install for new lucid
installations. But upgraders from hardy, karmic, etc. are very likely to
already have a log file, aren't they?
** Also affects: ninja (Ubuntu Lucid)
Importance: Undecided
Status: New
--
package ninja 0.1.3-1 failed to install/upgrade: die: error:
`/var/log/ninja.log' is not a regular file
https://bugs.launchpad.net/bugs/560336
You received this bug notification because you are a direct subscriber
of the bug.
Status in “ninja” package in Ubuntu: Fix Released
Status in “ninja” source package in Lucid: New
Bug description:
Binary package hint: ninja
failed to install through synaptic in lucid
TEST CASE:
$ apt-get install ninja
VERIFICATION DONE:
- The package installs fine and the daemon is started:
$ LANG=C sudo dpkg -i ninja_0.1.3-1ubuntu0.1_i386.deb
Selecting previously deselected package ninja.
(Reading database ... 203325 files and directories currently installed.)
Unpacking ninja (from ninja_0.1.3-1ubuntu0.1_i386.deb) ...
Setting up ninja (0.1.3-1ubuntu0.1) ...
log: reading configuration file: /etc/ninja/ninja.conf
log: ninja version 0.1.3 initializing
log: magic group: gid=0 (root)
log: logfile: /var/log/ninja.log
log: whitelist mapped in memory at 0xb7729000
log: entering daemon mode
ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: ninja 0.1.3-1
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic x86_64
NonfreeKernelModules: wl fglrx
Architecture: amd64
Date: Sat Apr 10 15:21:45 2010
ErrorMessage: subprocess installed post-installation script returned
error exit
status 1
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
SourcePackage: ninja
Title: package ninja 0.1.3-1 failed to install/upgrade: subprocess
installed
post-installation script returned error exit status 1
To unsubscribe from this bug, go to:
https://bugs.launchpad.net/ubuntu/+source/ninja/+bug/560336/+subscribe
--
package ninja 0.1.3-1 failed to install/upgrade: die: error:
`/var/log/ninja.log' is not a regular file
https://bugs.launchpad.net/bugs/560336
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
