[gentoo-dev] News item: Upgrading Apache from 2.2 to 2.4

[gentoo-dev] News item: Upgrading Apache from 2.2 to 2.4

[Dirkjan Ochtman]

Hi all,

After what feels like ages, we're just about ready to stabilize
apache-2.4. Since this is a major upgrade that in many cases require
configuration changes, we wanted to do a news item. After some
discussion with Lars (Poly-C), here's an initial attempt at a draft.

===

Title: Upgrading Apache from 2.2 to 2.4
Author: Dirkjan Ochtman <djc@gentoo.org>
Content-Type: text/plain
Posted: 2016-01-13
Revision: 1
News-Item-Format: 1.0
Display-If-Installed: www-servers/apache

Upstream released the 2.4 version of the Apache HTTPD almost 4 years
ago. Though many users have moved to other HTTP servers, Portage still
has quite a few reverse dependencies, so it took the small team of
maintainers until now to bring Apache 2.4 to stable. In part, this is
because Apache 2.4 overhauls some often-used parts of the
configuration; chances that you will have to make some changes to your
configuration are quite high. On the other hand, apache-2.4.18
includes support for HTTP 2.0, so you get that (almost) for free!

Rather than trying to enumerate all the differences here, we'd like to
point you to the upstream upgrading document, which can be found here:

https://httpd.apache.org/docs/2.4/upgrading.html

For more information on all the new features, start here:

https://httpd.apache.org/docs/trunk/new_features_2_4.html

===

Please use your usual 72 hours of feedback window fruitfully!

Cheers,

Dirkjan

Re: [gentoo-dev] News item: Upgrading Apache from 2.2 to 2.4

[Daniel Campbell]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 01/13/2016 09:13 AM, Dirkjan Ochtman wrote:
> In part, this is because Apache 2.4 overhauls some often-used parts
> of the configuration; chances that you will have to make some
> changes to your configuration are quite high. On the other hand,
> apache-2.4.18 includes support for HTTP 2.0, so you get that
> (almost) for free!
> 
> Rather than trying to enumerate all the differences here, we'd like
> to point you to the upstream upgrading document, which can be found
> here:

I would change this to:

- ---

With this comes changes to configuration that will likely need
attention.  Upstream's upgrading document outlines any major
configuration changes that may be necessary when upgrading. It can be
found at:

- ---

The reason I suggest cutting it a little is because the HTTP 2.0 mention
comes, and then right after there was the "rather than enumerate the
changes..." part. If HTTP 2.0 is listed among the changes on Apache's
upgrade guide, it's redundant to put it in the news item.

Also, tone. Maybe I'm wrong in thinking this, but generally I think news
should be neutral and absent of "you" and "we", if possible. The primary
impact here is configurations may need changing, and instead of creating
a massive news item with all the changes, we're just referring to
upstream's extant documentation, which is a good call. I just feel the
tone should be a bit more "keep it to the facts". Otherwise, it looks
good to me. :)

- -- 
Daniel Campbell - Gentoo Developer
OpenPGP Key: 0x1EA055D6 @ hkp://keys.gnupg.net
fpr: AE03 9064 AE00 053C 270C  1DE4 6F7A 9091 1EA0 55D6
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJWlu0kAAoJEAEkDpRQOeFw8zIP/2y4keg3lLt4v4uFSbuh4d2z
bkzqD1vflPvK4wm6GhOLj8ou7g4uIAV3tE3Kz6l4Y6PxMM/o5sBFZX1lZqaCr84x
24ZCo7wE6WgnHpswAwRIwEoRf/movvWD5xmwGoQGSriO3b6l7L0xM4CRoT+EOxCu
Sc7ly/a/vq2nW0dusixD56bcF7CsHSTEU8aCrcw+7iMz/rHtQY+hTLs9mAkJ1pvH
KYddbcfs01OmuCa4Wkj5NOThlobBxzspKF+V+qV+bUzTTFv+wwKhWWY6+yV195QB
PU+5hTw2oI088e9w4cZTaops0egjceStZSNtcOOvQ74ed2gGemDkFO1uGzXk0x2S
odjOPjCruTcgvBecBHi99E9ESgcSHERah8aU+iunB+fod0b2kwTYxIl4shwW5mbx
DV/ufQT98uaiibB3jp3Sq54Zg4fX0q8qrS7cfkIxOLjodykupmwhfWo7WqQMCkHy
a2FdZ7RlIG5u+CcGELDQkfE1uVGg3o2aRBKf1/69lU7QpD3tNjwDSytQ5IbqlunB
wHcZpZMFKrKe6aEGhxQXrsJ1/nl0Q0b5FWF/ayACuSnTYxkKft3ow9Dxs15isNGG
EMdhzKdg9scyfS99xAFSqCb5VM8IPK8VTh71Zqclpt70agk0a+Mc94WDXepxrGy2
iiB3FA7ySG/Ph1w2Kx6C
=lGj6
-----END PGP SIGNATURE-----

[gentoo-dev] Re: News item: Upgrading Apache from 2.2 to 2.4

[Duncan]

Dirkjan Ochtman posted on Wed, 13 Jan 2016 18:13:41 +0100 as excerpted:

> Display-If-Installed: www-servers/apache

Can't that be made <www-servers/apache-2.4 ?  Why would people already on 
2.4 need a news item about something they've already taken care of?

Then ensure that the news item hits before the 2.4 stabilization, so it's 
known to be there and trigger when people update, so they get the news 
item either before they do the update or with the same run.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

Re: [gentoo-dev] Re: News item: Upgrading Apache from 2.2 to 2.4

[Dirkjan Ochtman]

On Thu, Jan 14, 2016 at 10:53 AM, Duncan <1i5t5.duncan@cox.net> wrote:
>> Display-If-Installed: www-servers/apache
>
> Can't that be made <www-servers/apache-2.4 ?  Why would people already on
> 2.4 need a news item about something they've already taken care of?

This makes sense to me, though I imagine it could be annoying if
people (stupidly, but whatever) postpone reading their news items
until after the upgrade. Is this a canonical approach? Would like some
feedback from the experts, here!

Cheers,

Dirkjan

Re: [gentoo-dev] News item: Upgrading Apache from 2.2 to 2.4

[Marc Schiffbauer]

[-- Attachment #1: Type: text/plain, Size: 838 bytes --]

* Dirkjan Ochtman schrieb am 14.01.16 um 22:41 Uhr:
> On Thu, Jan 14, 2016 at 10:53 AM, Duncan <1i5t5.duncan@cox.net> wrote:
> >> Display-If-Installed: www-servers/apache
> >
> > Can't that be made <www-servers/apache-2.4 ?  Why would people already on
> > 2.4 need a news item about something they've already taken care of?
> 
> This makes sense to me, though I imagine it could be annoying if
> people (stupidly, but whatever) postpone reading their news items
> until after the upgrade. Is this a canonical approach? Would like some
> feedback from the experts, here!


Personally I'd not like it, when the news item will disappear right 
after the upgrade. So I'd prefer to not change it.

-Marc

> 
> Cheers,
> 
> Dirkjan
> 

-- 
0x35A64134 - 8AAC 5F46 83B4 DB70 8317
             3723 296C 6CCA 35A6 4134

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

[gentoo-dev] Re: News item: Upgrading Apache from 2.2 to 2.4

[Dirkjan Ochtman]

Second attempt!

===

Title: Upgrading Apache from 2.2 to 2.4
Author: Dirkjan Ochtman <djc@gentoo.org>
Content-Type: text/plain
Posted: 2016-01-17
Revision: 1
News-Item-Format: 1.0
Display-If-Installed: www-servers/apache

With the 2.4 branch released by upstream almost 4 years ago, stable
Gentoo systems will soon be upgraded from apache 2.2 to apache 2.4.
When upgrading, chances are some configuration changes have to be
made. Upstream has a handy guide:

https://httpd.apache.org/docs/2.4/upgrading.html

For more information on all the new features, start here:

https://httpd.apache.org/docs/trunk/new_features_2_4.html

===

A bit more concise and less personal. Better?

Cheers,

Dirkjan

Re: [gentoo-dev] Re: News item: Upgrading Apache from 2.2 to 2.4

[Daniel Campbell]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 01/17/2016 10:18 AM, Dirkjan Ochtman wrote:
> Second attempt!
> 
> ===
> 
> Title: Upgrading Apache from 2.2 to 2.4 Author: Dirkjan Ochtman
> <djc@gentoo.org> Content-Type: text/plain Posted: 2016-01-17 
> Revision: 1 News-Item-Format: 1.0 Display-If-Installed:
> www-servers/apache
> 
> With the 2.4 branch released by upstream almost 4 years ago,
> stable Gentoo systems will soon be upgraded from apache 2.2 to
> apache 2.4. When upgrading, chances are some configuration changes
> have to be made. Upstream has a handy guide:
> 
> https://httpd.apache.org/docs/2.4/upgrading.html
> 
> For more information on all the new features, start here:
> 
> https://httpd.apache.org/docs/trunk/new_features_2_4.html
> 
> ===
> 
> A bit more concise and less personal. Better?
> 
> Cheers,
> 
> Dirkjan
> 

Looks excellent!

- -- 
Daniel Campbell - Gentoo Developer
OpenPGP Key: 0x1EA055D6 @ hkp://keys.gnupg.net
fpr: AE03 9064 AE00 053C 270C  1DE4 6F7A 9091 1EA0 55D6
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJWnOVvAAoJEAEkDpRQOeFwz48QAMmRq40+TZhvekUuDnFfDP4c
0cl4p9gWvKNVpesuQf7fR8CZ13mHiu1JyHzgmb03Rk3WTbE4LiFj8uUz6p/fLoDk
8F2Zn7ZypXIw5GWZvWzw7BVx69NHF5hMLJMAJq5kj42LwGBewcYHRWaT1mPan3pb
4EtT9Mr8MJe4hp6RcRqSauJ0+TX12TZhv1y07SaWGoDAqUBpu+Iny8r/ObsQciql
nEbRQfOAQvg9vd5vxJsMqVvTrY9Q8h7TZ+iEUDWDWD7FGdVEbXbJZ3QQ1WqK+R4K
v2Jup+I2MD8fe2R9cXQzdh/vh4vrmSmsh7g1UScXeHRtO8ADRYy3ssCav+4RMBQ9
Cs9Q6iLnkvCrKsiHfpNTfcvx4hYrlzOIpFZHYJ3N6+Yafw5v17H3EE3qgtbIbZFL
B2UDDQ14CSjYo/oIG6DLBmgTIXidFHv4PljCgwB2sV3Gnh/Rk2zeDoil0JVNG8WB
weycIKebgcRlk5eWlz+iLKn+1DonPfaSkTxG+v0hRETEV9xd0XeTuT57QkMckXaz
h/R7XKe3KhMbb641tBOjZmRWZAJLUiRjgcqY+ztUj2hHZj2kXkpy1eLC0/PSvCFr
30dk+REHrM8pkQochK+EmmTelFPibUvEuANMU2ZMGdh0W/Mm/je75HGa2VRNP8o1
8Po3JXLXD4Qgng+N6Cx0
=TtSV
-----END PGP SIGNATURE-----

Re: [gentoo-dev] Re: News item: Upgrading Apache from 2.2 to 2.4

[Aaron W. Swenson]

[-- Attachment #1: Type: text/plain, Size: 1118 bytes --]

On 2016-01-17 19:18, Dirkjan Ochtman wrote:
> Second attempt!
> 
> ===
> 
> Title: Upgrading Apache from 2.2 to 2.4
> Author: Dirkjan Ochtman <djc@gentoo.org>
> Content-Type: text/plain
> Posted: 2016-01-17
> Revision: 1
> News-Item-Format: 1.0
> Display-If-Installed: www-servers/apache
> 
> With the 2.4 branch released by upstream almost 4 years ago, stable
> Gentoo systems will soon be upgraded from apache 2.2 to apache 2.4.
> When upgrading, chances are some configuration changes have to be
> made. Upstream has a handy guide:
> 
> https://httpd.apache.org/docs/2.4/upgrading.html
> 
> For more information on all the new features, start here:
> 
> https://httpd.apache.org/docs/trunk/new_features_2_4.html
> 
> ===
> 
> A bit more concise and less personal. Better?
> 
> Cheers,
> 
> Dirkjan
> 

I think the use of "chances" here depresses the importance of
configuration changes.

This is debatable, but I think it should be "there are some
configuration changes that must be made."

Primarily in regards to the Order directive being (re)moved to an
optional module.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 345 bytes --]

[gentoo-dev] Re: News item: Upgrading Apache from 2.2 to 2.4

[Dirkjan Ochtman]

On Wed, Jan 13, 2016 at 6:13 PM, Dirkjan Ochtman <djc@gentoo.org> wrote:
> After what feels like ages, we're just about ready to stabilize
> apache-2.4. Since this is a major upgrade that in many cases require
> configuration changes, we wanted to do a news item. After some
> discussion with Lars (Poly-C), here's an initial attempt at a draft.

I'm currently attempting this upgrade on a stable system I run. It
mostly just works, although I run into trouble when trying to load
modules that are not part of www-server/apache (e.g. mod_wsgi). I
resolved this by reemerging all packages listed in `equery b
/usr/lib/apache2/modules/*`, but maybe there's a different way? Should
this be in an elog message, or part of the news item?

Cheers,

Dirkjan

Re: [gentoo-dev] Re: News item: Upgrading Apache from 2.2 to 2.4

[Lars Wendler]

[-- Attachment #1: Type: text/plain, Size: 1178 bytes --]

Hi Dirkjan,

make it part of the news item please.

Kind regards
Lars

On Wed, 20 Jan 2016 13:16:19 +0100 Dirkjan Ochtman wrote:

>On Wed, Jan 13, 2016 at 6:13 PM, Dirkjan Ochtman <djc@gentoo.org>
>wrote:
>> After what feels like ages, we're just about ready to stabilize
>> apache-2.4. Since this is a major upgrade that in many cases require
>> configuration changes, we wanted to do a news item. After some
>> discussion with Lars (Poly-C), here's an initial attempt at a
>> draft.  
>
>I'm currently attempting this upgrade on a stable system I run. It
>mostly just works, although I run into trouble when trying to load
>modules that are not part of www-server/apache (e.g. mod_wsgi). I
>resolved this by reemerging all packages listed in `equery b
>/usr/lib/apache2/modules/*`, but maybe there's a different way? Should
>this be in an elog message, or part of the news item?
>
>Cheers,
>
>Dirkjan
>



-- 
Lars Wendler
Gentoo package maintainer
GPG: 21CC CF02 4586 0A07 ED93  9F68 498F E765 960E 9B39

Attention! New gpg key! See (self signed server cert for now)
http://www.gentoofan.org/blog/index.php?/archives/9-New-gpg-keys.html

[-- Attachment #2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

Re: [gentoo-dev] Re: News item: Upgrading Apache from 2.2 to 2.4

[Paul Varner]

On 01/21/2016 06:52 AM, Lars Wendler wrote:
> Hi Dirkjan,
>
> make it part of the news item please.
>
> Kind regards
> Lars
>
> On Wed, 20 Jan 2016 13:16:19 +0100 Dirkjan Ochtman wrote:
>
>> On Wed, Jan 13, 2016 at 6:13 PM, Dirkjan Ochtman <djc@gentoo.org>
>> wrote:
>>> After what feels like ages, we're just about ready to stabilize
>>> apache-2.4. Since this is a major upgrade that in many cases require
>>> configuration changes, we wanted to do a news item. After some
>>> discussion with Lars (Poly-C), here's an initial attempt at a
>>> draft.  
>> I'm currently attempting this upgrade on a stable system I run. It
>> mostly just works, although I run into trouble when trying to load
>> modules that are not part of www-server/apache (e.g. mod_wsgi). I
>> resolved this by reemerging all packages listed in `equery b
>> /usr/lib/apache2/modules/*`, but maybe there's a different way? Should
>> this be in an elog message, or part of the news item?
>>
The simple command to do this is: emerge -av1 /usr/lib/apache2/modules
--exclude=www-servers/apache

Regards,
Paul

Re: [gentoo-dev] Re: News item: Upgrading Apache from 2.2 to 2.4

[Dirkjan Ochtman]

Third attempt.

===

Title: Upgrading Apache from 2.2 to 2.4
Author: Dirkjan Ochtman <djc@gentoo.org>
Content-Type: text/plain
Posted: 2016-01-17
Revision: 1
News-Item-Format: 1.0
Display-If-Installed: www-servers/apache

With the 2.4 branch released by upstream almost 4 years ago, stable
Gentoo systems will soon be upgraded from apache 2.2 to apache 2.4.
When upgrading, some configuration changes will have to be made.
Upstream has a handy guide:

https://httpd.apache.org/docs/2.4/upgrading.html

For more information on all the new features, start here:

https://httpd.apache.org/docs/trunk/new_features_2_4.html

After emerging Apache 2.4, you will also need to rebuild any
third-party modules:

emerge -av1 /usr/lib/apache2/modules --exclude=www-servers/apache

===

Remaining question: how do get the timing of the news item to line up
with the stabilization? Or do we just start by sending out the news
item, then file the stabilization bugs so that people at least have
advance notice?

Cheers,

Dirkjan

Re: [gentoo-dev] Re: News item: Upgrading Apache from 2.2 to 2.4

[Kristian Fiskerstrand]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 01/22/2016 03:04 PM, Dirkjan Ochtman wrote:
> Third attempt.
> 

..

> 
> Remaining question: how do get the timing of the news item to line
>  up with the stabilization? Or do we just start by sending out the
>  news item, then file the stabilization bugs so that people at 
> least have advance notice?

Advanced notice, please


- -- 
Kristian Fiskerstrand
Public PGP key 0xE3EDFAE3 at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
-----BEGIN PGP SIGNATURE-----

iQEcBAEBCgAGBQJWojqUAAoJECULev7WN52FXD0IAKoAhGIB27lbYsWORQ6H8AMC
hStsuzOL4cYnWp/YJT2j31dCIZvnzt9dRByIYkZn+roPv3Cl1ij+TA2TGaLg8t5s
QGr2ASA4kYle8DIU2WmeR0VxBsv0QaHqVbY9YkT7++a2EkqaQAXBuoJIIZeMKvCI
6WiXj/rX2/9ORm7lIkwahp5ClbHMlCqxY4qUOurK+ki9TUDhDN6DnYrLQDG/+y88
aB6XbUqR2CCMc46QiKox+h1HxKf6poqSwBvDMUwWTsl5TBT1mVXh5PMemRBwhLN4
pRLexBhaCrMv3IdKmD20CrGtKGt3uw2FxRkMI8iJKR6BCeRV1JNL9BuHyDJVAd4=
=mE3l
-----END PGP SIGNATURE-----

Re: [gentoo-dev] Re: News item: Upgrading Apache from 2.2 to 2.4

[Dirkjan Ochtman]

On Fri, Jan 22, 2016 at 3:20 PM, Kristian Fiskerstrand <k_f@gentoo.org> wrote:
> Advanced notice, please

Committed 2016-01-27-upgrading-to-apache-2_4 to news.

Time to request stabilization?

Cheers,

Dirkjan

Re: [gentoo-dev] Re: News item: Upgrading Apache from 2.2 to 2.4

[Kristian Fiskerstrand]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 01/27/2016 03:17 PM, Dirkjan Ochtman wrote:
> On Fri, Jan 22, 2016 at 3:20 PM, Kristian Fiskerstrand
> <k_f@gentoo.org> wrote:
>> Advanced notice, please
> 
> Committed 2016-01-27-upgrading-to-apache-2_4 to news.
> 
> Time to request stabilization?

I'm not aware of any formal policy on it, but from perspective of a
sysadmin I'd say anything starting a week from now should be fine.

(Although my normal maintenance window this week is affected by FOSDEM
unless there are security critical patches.. but at least gives time
to get the news :) )

- -- 
Kristian Fiskerstrand
Public PGP key 0xE3EDFAE3 at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
-----BEGIN PGP SIGNATURE-----

iQEcBAEBCgAGBQJWqNK5AAoJECULev7WN52FrlkH/1jlyemX/mCwwQ6YWpLOFMp6
0srq7x2qjEW8SDl8osd6tNv9foN6zzbiSerlVjXCx5qCzQkYdw67+YmYvedzrwg3
Gp6xuu9A4OvYH9Yh3Xn1kcLFcnwstUotSJJ0E/ct8BQMgQRAZI4gabo8EmrqPeHX
MNMOOF10z0ABXugxYWAgK0nFhy6IKF9nPmxCGzObGlg+oZIAa4lreb2nprb8D1WC
WjSr0GZxX4hQRxxKnwYRvT+gSFzIhLzu+EAq5VWKdETR9ali7fNNfDbj1fE00OEM
4vCS3JEF7ob1KwVEgWqLTcpgxuFBJPqk6vFaS0IPlMYCUjEtXeiTMtIU32cq1bw=
=2XWG
-----END PGP SIGNATURE-----