Package: quota
Version: 3.16-7
Severity: grave
Get the following error
apt-get install quota
The following NEW packages will be installed:
quota
0 upgraded, 1 newly installed, 0 to remove and 7 not upgraded.
Need to get 0B/504kB of archives.
After this operation, 1389kB of additional disk
severity 510987 normal
thanks
On Tue, Jan 06, 2009 at 02:42:12PM +0100, Bastien ROUCARIES wrote:
insserv: Service quota has to be enabled to start service quotarpc
insserv: exiting now!
insserv? What exactly are you doing here? This error message does not come from
quota. It seems that insserv
severity 510987 grave
thanks
Restore grave severity because quota is not instalable. insserv is a
new init infrastructure I agree, but your package should not break.
Does not fix the problem.
host:/home/bastien# invoke-rc.d quota start
invoke-rc.d: unknown initscript, /etc/init.d/quota not
Hi Michael,
On Tue, Jan 06, 2009 at 04:20:50PM +0100, Michael Meskes wrote:
On Tue, Jan 06, 2009 at 02:42:12PM +0100, Bastien ROUCARIES wrote:
insserv: Service quota has to be enabled to start service quotarpc
insserv: exiting now!
insserv? What exactly are you doing here? This error
Tags 510987 + patch
thanks
Hi,
On Tue, Jan 06, 2009 at 05:10:35PM +0100, Patrick Schoenfeld wrote:
the package by manipulating the order manually. It however needs further
investigation for the package generation process (I'm not sure if this
can be handled with dh_installinit or if postinst
severity 510987 important
thanks
Restore grave severity because quota is not instalable. insserv is a
new init infrastructure I agree, but your package should not break.
This reasoning is getting it done. Let's see:
grave
makes the package in question unusable or mostly so, or causes data
insserv is the new system that should enable us to start service
parallel. To fix packages for is a release goal. I guess it would be
Right, but not release critical, unless I'm mistaken.
interesting to fix it for Lenny, but I'm not sure if this is still
possible with the current unblock
well, its easy as well. Attached patch (against the source package) fixes the
issue.
...
Does this mean insserv only checks the runlevel during link creation? That
explains why my workaround didn't work. I thought it was checking at runtime.
+quota (3.16-7.1) unstable; urgency=low
Will do
User initscripts-ng-de...@lists.alioth.debian.org
Usertags 510987 incorrect-dependency
thanks
Add user tags for traking purpose :)
So, quota is still usable for everyone who does not run insserv during first
installation, which is stil the majority of users. There neither is a security
Hi,
On Tue, Jan 06, 2009 at 06:19:44PM +0100, Michael Meskes wrote:
well, its easy as well. Attached patch (against the source package) fixes
the issue.
Does this mean insserv only checks the runlevel during link creation? That
explains why my workaround didn't work. I thought it was
On Tue, Jan 06, 2009 at 06:14:37PM +0100, Michael Meskes wrote:
insserv is the new system that should enable us to start service
parallel. To fix packages for is a release goal. I guess it would be
Right, but not release critical, unless I'm mistaken.
Thats my appraisal, too.
Thats not proof to further changes to the runlevel configuration of
quota, but it would do for Lenny.
But then there won't be any change to Lenny quota package either, so the
runlevel configuration cannot change in Lenny anymore. Given that the SID
package is already fixed, we should be fine.
12 matches
Mail list logo
