On 2013-07-25 13:51:13 +0200, Arno Töll wrote:
> On 25.07.2013 13:39, Vincent Lefevre wrote:
> > If users are allowed to disable these modules in compliance with the
> > policy, then you need to make sure that Apache still works in such a
> > case (e.g. for a personal website that doesn't need thes
On Thu, Jul 25, 2013 at 1:35 PM, Arno Töll wrote:
> On 25.07.2013 13:25, Ondřej Surý wrote:
> > Wouldn't
> >
> > Package: apache2
> > Replaces: apache2.2-common (<< 2.4.0)
> > Breaks: apache2.2-common (<< 2.4.0)
> >
> > Solve the problem?
>
> That's what we do already (minus breaks). That allows
On 25.07.2013 13:39, Vincent Lefevre wrote:
> If users are allowed to disable these modules in compliance with the
> policy, then you need to make sure that Apache still works in such a
> case (e.g. for a personal website that doesn't need these modules).
> The use of IfModule could be a solution.
On 2013-07-25 13:13:18 +0200, Arno Töll wrote:
> On 25.07.2013 13:02, Vincent Lefevre wrote:
> > Then wouldn't it be possible during an upgrade of some packages
> > (e.g. apache2, apache2-doc) to make sure that these modules are
> > enabled, and re-enable them if they aren't?
>
> As said, unless d
On 25.07.2013 13:25, Ondřej Surý wrote:
> Wouldn't
>
> Package: apache2
> Replaces: apache2.2-common (<< 2.4.0)
> Breaks: apache2.2-common (<< 2.4.0)
>
> Solve the problem?
That's what we do already (minus breaks). That allows us to overwrite
and take-over conffiles from apache2.2-common. This w
On Thu, Jul 25, 2013 at 1:19 PM, Arno Töll wrote:
> On 25.07.2013 13:16, Ondřej Surý wrote:
> > could you please rethink the idea of re-adding apache2.2-common with
> > version Breaks: on all reverse depends (with versions from wheezy, the
> > jessie can be handled by filling RC bugs case-by-case
On 25.07.2013 13:16, Ondřej Surý wrote:
> could you please rethink the idea of re-adding apache2.2-common with
> version Breaks: on all reverse depends (with versions from wheezy, the
> jessie can be handled by filling RC bugs case-by-case).
Yes, we did not definitely decide on that. It is, howeve
On Wed, Jul 24, 2013 at 11:16 PM, Arno Töll wrote:
> On 24.07.2013 22:47, Stefan Fritsch wrote:
> >> The bug in apache2 is that we still treat this situation as an
> >> upgrade in the postinst even if there is nothing left of the old
> >> install. If we can detect it, we should probably treat it
On 25.07.2013 13:02, Vincent Lefevre wrote:
> Then wouldn't it be possible during an upgrade of some packages
> (e.g. apache2, apache2-doc) to make sure that these modules are
> enabled, and re-enable them if they aren't?
As said, unless due to a bug, these modules are always enabled. However,
som
Hi,
On 2013-07-25 12:16:20 +0200, Arno Töll wrote:
> On 25.07.2013 11:52, Vincent Lefevre wrote:
> > thus depends on the alias module being there, but the dependency
> > is not enforced anywhere. What if for some reason the alias module
> > gets disabled in the future? Shouldn't a IfModule directi
Hi,
On 25.07.2013 11:52, Vincent Lefevre wrote:
> thus depends on the alias module being there, but the dependency
> is not enforced anywhere. What if for some reason the alias module
> gets disabled in the future? Shouldn't a IfModule directive be used
> in order to avoid the full Apache server b
On 2013-07-24 22:07:02 +0200, Stefan Fritsch wrote:
> Am Mittwoch, 24. Juli 2013, 21:37:18 schrieb Vincent Lefevre:
> > dpkg: apache2.2-common: dependency problems, but removing anyway as
> > you requested:
> >
> > apache2-mpm-worker depends on apache2.2-common (= 2.2.22-13).
> >
> > apache2 de
On 24.07.2013 22:47, Stefan Fritsch wrote:
>> The bug in apache2 is that we still treat this situation as an
>> upgrade in the postinst even if there is nothing left of the old
>> install. If we can detect it, we should probably treat it as a new
>> install instead.
I do not think we could in a d
Am Mittwoch, 24. Juli 2013, 22:07:02 schrieb Stefan Fritsch:
> This is the problem. You have used --purge-unused (with aptitude)
> or --purge (with apt-get) while upgrading. Or the respective
> config options have been set in the apt/aptitude configuration
> files. This won't work and we will docu
Am Mittwoch, 24. Juli 2013, 21:37:18 schrieb Vincent Lefevre:
> dpkg: apache2.2-common: dependency problems, but removing anyway as
> you requested:
>
> apache2-mpm-worker depends on apache2.2-common (= 2.2.22-13).
>
> apache2 depends on apache2.2-common (= 2.2.22-13).
>
...
>
> Removing ap
On 2013-07-24 21:13:53 +0200, Stefan Fritsch wrote:
> Do you maybe still have the apt-get/aptitude output from the upgrade?
> There should be a copy in /var/log/apt/term.log* if the relevant file
> has not been rotated away, yet.
Log started: 2013-07-14 01:37:08
(Reading database ...
(Reading
Am Mittwoch, 24. Juli 2013, 11:30:49 schrieb Vincent Lefevre:
> On 2013-07-24 10:12:56 +0200, Arno Töll wrote:
> > > THere have been several reports, mine, another in the bug
> > > report,
> > > that confirm that mods get disabled by upgrading.
> >
> >
> >
> > I did not say your issue does not exi
On 24.07.2013 13:54, Norbert Preining wrote:
> Removal does not work easily, since gnome depends on apache2.
Gnome depends on apache2-bin which works fine without apache2 and any
configuration file as they are all in apache2.
> So how should I know what modules etc should be active and what not?
On Mi, 24 Jul 2013, Arno Töll wrote:
> I did not say your issue does not exist. But it does not happen under
> normal circumstances. In fact I am not even able to reproduce it, and
Then at least provide a way to resolve the issue!
There is *no* way to know or recreate the proper or default initia
On 2013-07-24 10:12:56 +0200, Arno Töll wrote:
> > THere have been several reports, mine, another in the bug report,
> > that confirm that mods get disabled by upgrading.
>
> I did not say your issue does not exist. But it does not happen under
> normal circumstances.
The bug occurred for me in a
Processing commands for cont...@bugs.debian.org:
> severity 711925 important
Bug #711925 [apache2-doc] apache2-doc's config file breaks apache itself
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
711925: http://bugs.deb
severity 711925 important
thanks
Playing severity ping pong does not exactly convince me to prioritize
your issue.
> THere have been several reports, mine, another in the bug report,
> that confirm that mods get disabled by upgrading.
I did not say your issue does not exist. But it does not happ
Processing commands for cont...@bugs.debian.org:
> severity 711925 serious
Bug #711925 [apache2-doc] apache2-doc's config file breaks apache itself
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
711925: http://bugs.debia
severity 711925 serious
thanks
On Di, 11 Jun 2013, Arno Töll wrote:
> we enable mod_alias unconditionally in postinst of apache2. Just like
> "essential" packages in Debian we allow people (and so ourselvses) to
> use directives from this core set unconditionally.
THere have been several reports,
On 2013-06-11 10:02:21 +0200, Arno Töll wrote:
> > # env -i LANG=C PATH=/usr/local/bin:/usr/bin:/bin /usr/sbin/apache2ctl
> > configtest
> > AH00526: Syntax error on line 1 of
> > /etc/apache2/conf-enabled/apache2-doc.conf:
> > Invalid command 'Alias', perhaps misspelled or defined by a module no
On Di, 11 Jun 2013, Arno Töll wrote:
> What does "a2query -m" give you?
php5 (enabled by maintainer script)
authz_core (enabled by maintainer script)
mpm_prefork (enabled by site administrator)
perl (enabled by maintainer script)
access_compat (enabled by maintainer script)
filter (enabled by main
On 11.06.2013 10:41, Norbert Preining wrote:
> Hi Arno,
>
> On Di, 11 Jun 2013, Arno Töll wrote:
>> Thus, either mod_alias was disabled by you, or not enabled on your
>> system for some other reason (which then might be the "real" bug). Could
>> you help us on that and tell us more?
>
> I didn't
Hi Arno,
On Di, 11 Jun 2013, Arno Töll wrote:
> Thus, either mod_alias was disabled by you, or not enabled on your
> system for some other reason (which then might be the "real" bug). Could
> you help us on that and tell us more?
I didn't do anything to apache configurations at all, how can I che
severity 711925 important
thanks
On 11.06.2013 05:16, Norbert Preining wrote:
> # env -i LANG=C PATH=/usr/local/bin:/usr/bin:/bin /usr/sbin/apache2ctl
> configtest
> AH00526: Syntax error on line 1 of /etc/apache2/conf-enabled/apache2-doc.conf:
> Invalid command 'Alias', perhaps misspelled or de
Processing commands for cont...@bugs.debian.org:
> severity 711925 important
Bug #711925 [apache2-doc] apache2-doc's config file breaks apache itself
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
711925: http://bugs.debia
Package: apache2-doc
Version: 2.4.4-6
Severity: grave
# /etc/init.d/apache2 start
[FAIL] Starting web server: apache2 failed!
The apache2 configtest failed. Please run 'env -i LANG=C
PATH=/usr/local/bin:/usr/bin:/bin /usr/sbin/apache2ctl configtest' manually and
read the log file to discover pro
31 matches
Mail list logo
