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 loss,
or introduces a security hole allowing access to the accounts of users who use
the package.
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
hole, nor a data loss. So why should it be grave?
Also you should note that insserv is priority optional and not the standard
boot tool. Finally even insserv's man page says:
This package should be used with care, as incorrect or missing dependencies
can lead to an unbootable system.
Don't get me wrong, this is not about me not willing to fix it, it's about
getting the priority straight especially given how deep we are in the release
cycle.
> Does not fix the problem.
Hmm, seems I did identify the problem correctly but the workaround didn't work.
Sigh.
Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [email protected]
Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL!
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
