Hi, yes, I see that as a poor reply. At the time the bug was reported,
and so far as I know, the Wordpress package gave Apache2 as an explicit
dependency. In the real world, >95% of Wordpress installations use
Apache. Hardly any Debian user would assume in such a situation that
they need to look for and read the file -
/usr/share/doc/wordpress/examples/apache.conf -
- in order to figure out why their Wordpress installation was
mysteriously not working in the way they are expecting and they way that
is documented on many different corners of the Internet. Wordpress is
one of the main ways of delivering dynamic web pages nowadays, even at
large commercial sites...not just blogs. It is not a positive
situation for Debian to have it not working out of the box when
dependence on Apache is an enforced & documented feature of the Debian
packaging. Wordpress is also commonly seen as a suitable place to start
for Website newbies and expecting them to somehow find their way to
reading /usr/share/doc/wordpress/examples/apache.conf
in order to figure out what is specially wrong about their out of the
box Debian setup is a weak choice.
On 11/27/2016 04:39 AM, Debian Bug Tracking System wrote:
This is an automatic notification regarding your Bug report
which was filed against the wordpress package:
#838819: wordpress really needs apache2's mod_rewrite enabled - either as a
default, or well documented
It has been closed by Craig Small <[email protected]>.
Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Craig Small
<[email protected]> by
replying to this email.
On 09/25/2016 12:29 PM, Santiago Vila wrote:
Maybe the documentation you ask is in
/usr/share/doc/wordpress/examples/apache.conf.
Exactly! This example file does indeed mention you need to have
mod_rewrite enabled.
