* Steve Langasek
| On Thu, Oct 05, 2006 at 09:11:04AM -0600, Steve Langasek wrote:
| > So it's my recommendation to downgrade and "wontfix" this bug, since there's
| > no way to fix apache2-common's postrm script after the fact without
| > introducing a dummy package that re-breaks our dependency
On Tue, Oct 03, 2006 at 11:09:06AM +0200, Pierre Habouzit wrote:
> it should have been made an empty package, without maintainer scripts,
> so that it could be purged, as it's superseeded with apache2.2-common.
Totally not an option. The entire justification for renaming apache2-common
to apach
On Thu, Oct 05, 2006 at 09:11:04AM -0600, Steve Langasek wrote:
> So it's my recommendation to downgrade and "wontfix" this bug, since there's
> no way to fix apache2-common's postrm script after the fact without
> introducing a dummy package that re-breaks our dependency logic.
Oh, alternatively,
Package: apache2-common
Version: 2.0.55-4.2
Severity: serious
it should have been made an empty package, without maintainer scripts,
so that it could be purged, as it's superseeded with apache2.2-common.
[madcoder mad] LC_ALL=C sudo dpkg --purge apache2-common
(Reading database ... 142646 fi
4 matches
Mail list logo