[bts-link] source package apache2
# # 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_bug.cgi?id=50278 # * remote status changed: (?) - NEW usertags 418067 + status-NEW thanks -- To UNSUBSCRIBE, email to debian-apache-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101122163451.17869.48970.btsl...@busoni.debian.org
Re: apache module postinst/prerm scripts
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, perhaps reenabling the module anyway under specific conditions (new-version == old-version ?). Any suggestion? True, that's a problem. But I don't see an elegant solution right now. On remove, you would have to remember if the package was enabled and on reinstall, you would then need to restore the original state. It would probably make sense to create one script in the apache package to handle all this, which can then be used by all the module packages. But I definitely won't have time to implement that in the forseeable future. -- To UNSUBSCRIBE, email to debian-apache-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101119.33950...@sfritsch.de
Re: apache module postinst/prerm scripts
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 simple ASCII file would work well to handle the state of the modules, even in the improbable case all the modules available have been selected at least once sometime in the history of a system. I remember Debian Apache 1.x kept a module database in the form of a file listing the Load commands for the modules. If that approach was abandoned some good reason existed though Can you envision an approach to the problem? -- Massimo On Mon, 22 Nov 2010 22:19:33 +0100, Stefan Fritsch wrote True, that's a problem. But I don't see an elegant solution right now. On remove, you would have to remember if the package was enabled and on reinstall, you would then need to restore the original state. It would probably make sense to create one script in the apache package to handle all this, which can then be used by all the module packages. But I definitely won't have time to implement that in the forseeable future. -- To UNSUBSCRIBE, email to debian-apache-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101119.33950...@sfritsch.de -- -- To UNSUBSCRIBE, email to debian-apache-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101122215201.m14...@unipr.it
