Hi Stefan
thanks for the answer.
I was thinking of the problem and I could only see as a solution the
introduction of a small database of the installed modules where their state
transitions are recorded. I don't know what database format is recommended by
Debian Policy in these cases, but a si
On Sunday 21 November 2010, Massimo Manghi wrote:
> So, after a remove and subsequent install the package is disabled
> because the symlinks from mods-enabled to mods-available are
> missing. I'm not sure I if I got it right, but it seems to me the
> checks on the arguments have to be changed, per
#
# bts-link upstream status pull for source package apache2
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user bts-link-upstr...@lists.alioth.debian.org
# remote status report for #418067 (http://bugs.debian.org/418067)
# * http://issues.apache.org/bugzilla/show_bu
3 matches
Mail list logo