package ninja 0.1.3-1 failed to install/upgrade: die: error: `/var/log/ninja.log' is not a regular file

[Nathan Williams]

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

[glen (kojocuz)]

Even though ninja is not fully installed it is running and functioning.

[glen (kojocuz)]

Yes this as been happening for some time and a solution is need, because every time synaptic runs there is a report about this and every time I try to remove Ninja it starts a new process and just use more system resource.

[keharitomenos (parmenides)]

My solution was to find every single file related with ninja and delete them...it worked.
Mi solución fue buscar todos los archivos relacionados con Ninja y borrarlos. Funcionó.

[faortiz (fortiz-usa)]

I think the error message happens because using "ninja start" is misleading: start is supposed to be the name of the config file and there is no start config file: it has to be created.

[Jean-Baptiste Lallement (jibel)]

Thanks for your report.

This is fixed in the current development release:
ninja (0.1.3-2) unstable; urgency=low

  * Fixed logrotate file typo. (Closes: #563328).
  * Added a default logcheck ignore file. (Closes: #563329).
  * Fixed incorrect init script dependencies. (Closes: #567443).
  * Changed and fixed initscript. (Closes: #563989).
  * Added a preinst script to create a logfile. (Closes: #568780).

 -- William Vera <email address hidden> Sun, 10 Jan 2010 18:44:45 -0600

This is a significant bug in Ubuntu. If you need a fix for the bug in previous versions of Ubuntu, please do steps 1 and 2 of the SRU Procedure [1] to bring the need to a developer's attention.

[1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure

[Jean-Baptiste Lallement (jibel)]

For those facing difficulties to remove the package, follow the steps below:
- open a terminal and enter the command
$ sudo gedit /var/lib/dpkg/info/ninja.prerm
- Add the following line just below "#!/bin/sh"
exit 0
- Save and close the file
- run the command:
$ sudo apt-get remove --purge ninja

[Jean-Baptiste Lallement (jibel)]

Nominating for SRU Lucid:
- Impact: Package is not installable in Lucid and once a user tried to install it, it is not removable.

- This is not a minimal patch that address only the logfile creation. But because the package is not installable and there is no risk of regression, I backported all the fixes from upstream that addresses the init process. A default logcheck ignore file was also added. I can remove it if you think it's too much.
- I verified that the package can be installed and removed in Lucid, and that the daemon can be started and stopped.

- regression: None,package cannot be installed and there is no dependency on this package.

[Martin Pitt (pitti)]

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?

[Jason Alva Herndon (jason2023)]

bug (605752)

[faortiz (fortiz-usa)]

 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 <email address hidden>
To: <email address hidden>
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

...

[faortiz (fortiz-usa)]

 You're welcome. :) I look forward to using the new release, thank you. :)

-----Original Message-----
From: Jean-Baptiste Lallement <email address hidden>
To: <email address hidden>
Sent: Thu, Jul 15, 2010 8:27 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

Thanks for your report.

This is fixed in the current development release:

ninja (0.1.3-2) unstable; urgency=low

  * Fixed logrotate file typo. (Closes: #563328).

  * Added a default logcheck ignore file. (Closes: #563329).

  * Fixed incorrect init script dependencies. (Closes: #567443).

  * Changed and fixed initscript. (Closes: #563989).

  * Added a preinst script to create a logfile. (Closes: #568780).

 -- William Vera <email address hidden> Sun, 10 Jan 2010 18:44:45 -0600

This is a significant bug in Ubuntu. If you need a fix for the bug in

previous versions of Ubuntu, please do steps 1 and 2 of the SRU

Procedure [1] to bring the need to a developer's attention.

[1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure

** Summary changed:

- package ninja 0.1.3-1 failed to install/upgrade

+ package ninja 0.1.3-1 failed to install/upgrade: die: error:

`/var/log/ninja.log' is not a regular file

** Changed in: ninja (Ubuntu)

       Status: New => Fix Released

--

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

Bug description:

Binary package hint: ninja

failed to install through synaptic in lucid

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

[faortiz (fortiz-usa)]

 You're welcome. :)

-----Original Message-----
From: Jason Alva Herndon <email address hidden>
To: <email address hidden>
Sent: Sat, Jul 17, 2010 4:08 am
Subject: [Bug 560336] Thank You

bug (605752)

--

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

[Rolf Leggewie (r0lf)]

lucid has seen the end of its life and is no longer receiving any updates. Marking the lucid task for this ticket as "Won't Fix".