Re: Apache2 rev bump for OpenSSL update

[Jim Jagielski]

As a macports maintainer myself, as well as someone who is on the Apache httpd 
project itself, I volunteer to help out with this. 

--
Jim Jagielski
Brief? Mobile

> On Mar 3, 2016, at 7:29 PM, Marius Schamschula  wrote:
> 
> I agree that it’s time to do something about apache. The ticket bellow is 
> four years old, and I added myself to the CCs 21 months ago…
> 
> As someone that has used apache 2.4.x since 2012 (my old hmug.org builds), 
> and under MacPorts as apache24-devel for over two years (although I’m down to 
> a single machine using it, and I may end up replacing it with nginx), it 
> boggles my mind that Apple has been shipping apache 2.4.x with OS X since 
> Yosemite, and MacPorts is still stuck at 2.2.x.
> 
> Using apache24-devel with php is somewhat complicated, as building the 
> php-apache2handler against apache24-devel requires me to maintain my own 
> branch of php, as php-apache2handler forces apache2 to be installed. Having 
> apache24 would make this easier for others. I have not had any luck getting 
> php-fpm to work with apache24-devel, though it works nicely with nginx.
> 
> Of course, all my Linux and FreeBSD machines use apache 2.4.x, and I like 
> consistency in server setup.
> 
> On Mar 3, 2016, at 5:54 PM, Bradley Giesbrecht  wrote:
> 
 On Mar 3, 2016, at 12:09 AM, Juan Manuel Palacios  
 wrote:
> On Mar 3, 2016, at 3:35 AM, Ryan Schmidt  wrote:
> On Mar 3, 2016, at 00:18, Juan Manuel Palacios  wrote:
> 
> Apache 2 rev-bumped, cf. r146274.
> 
> On a side note, and if I may in this same thread, do we have any policy 
> for not moving the Apache 2.4 port out of “dev”?  Not too sure when it 
> became the recommended release series by the ASF, but it certainly isn’t 
> dev any longer.
 
 There's a ticket you can read. We can't just replace the current apache2 
 port with the current apache24-devel port because it also changes the 
 directory layout.
>> 
>>> 
>>> Yeah, that I understand, we keep versioned ports for other packages too, 
>>> e.g. mysql55, mysql56, mysql57, and other examples. And we don’t replace 
>>> one with the other for a myriad of reasons.
>> 
>> With versioned apache24 modules like apache24-mod_python27.
>> 
>>> So we could deprecate the apache24-devel port and create apache24, maybe 
>>> even also deprecating apache2 and eventually replacing it with apache22, 
>>> which needless to say would be compatible with the former, and would live 
>>> on in parallel to apache24, just as mysql55 does to mysql56, etc.
>>> 
>>> You have a URL for that ticket that you mention?
>> 
>> https://trac.macports.org/ticket/35824
>> 
>> —
>> Brad
>> 
>> ___
>> macports-dev mailing list
>> macports-dev@lists.macosforge.org
>> https://lists.macosforge.org/mailman/listinfo/macports-dev
> 
> Marius
> --
> Marius Schamschula
> 
> 
> 
> 
> ___
> macports-dev mailing list
> macports-dev@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Apache2 rev bump for OpenSSL update

[Marius Schamschula]

I agree that it’s time to do something about apache. The ticket bellow is four 
years old, and I added myself to the CCs 21 months ago…

As someone that has used apache 2.4.x since 2012 (my old hmug.org builds), and 
under MacPorts as apache24-devel for over two years (although I’m down to a 
single machine using it, and I may end up replacing it with nginx), it boggles 
my mind that Apple has been shipping apache 2.4.x with OS X since Yosemite, and 
MacPorts is still stuck at 2.2.x.

Using apache24-devel with php is somewhat complicated, as building the 
php-apache2handler against apache24-devel requires me to maintain my own branch 
of php, as php-apache2handler forces apache2 to be installed. Having apache24 
would make this easier for others. I have not had any luck getting php-fpm to 
work with apache24-devel, though it works nicely with nginx.

Of course, all my Linux and FreeBSD machines use apache 2.4.x, and I like 
consistency in server setup.

On Mar 3, 2016, at 5:54 PM, Bradley Giesbrecht  wrote:

>> On Mar 3, 2016, at 12:09 AM, Juan Manuel Palacios  wrote:
>>> On Mar 3, 2016, at 3:35 AM, Ryan Schmidt  wrote:
 On Mar 3, 2016, at 00:18, Juan Manuel Palacios  wrote:
 
 Apache 2 rev-bumped, cf. r146274.
 
 On a side note, and if I may in this same thread, do we have any policy 
 for not moving the Apache 2.4 port out of “dev”?  Not too sure when it 
 became the recommended release series by the ASF, but it certainly isn’t 
 dev any longer.
>>> 
>>> There's a ticket you can read. We can't just replace the current apache2 
>>> port with the current apache24-devel port because it also changes the 
>>> directory layout. 
> 
>> 
>> Yeah, that I understand, we keep versioned ports for other packages too, 
>> e.g. mysql55, mysql56, mysql57, and other examples. And we don’t replace one 
>> with the other for a myriad of reasons.
> 
> With versioned apache24 modules like apache24-mod_python27.
> 
>> So we could deprecate the apache24-devel port and create apache24, maybe 
>> even also deprecating apache2 and eventually replacing it with apache22, 
>> which needless to say would be compatible with the former, and would live on 
>> in parallel to apache24, just as mysql55 does to mysql56, etc.
>> 
>> You have a URL for that ticket that you mention?
> 
> https://trac.macports.org/ticket/35824
> 
> —
> Brad
> 
> ___
> macports-dev mailing list
> macports-dev@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev

Marius
--
Marius Schamschula




___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: [146276] trunk/dports/databases

[Bradley Giesbrecht]

> On Mar 3, 2016, at 12:14 AM, Juan Manuel Palacios  wrote:
> 
> Bradley,
> 
> I think you and I already discussed this in some thread, but I can’t remember 
> right now… 
> 
> What’s the point of the mysql5 port now a-days? I’d say it’s redundant with 
> mysql51, but not even, ‘cause it’s outdated with respect to it, 5.1.72 Vs. 
> 5.1.73. Shouldn’t we just obsolete that port and have it replaced by mysql51?


These ports have dependencies on mysql5 either directly or through variants:
port info --name --variants depends:"(\W|^)mysql5(\W|$)" or 
variant:"(\W|^)mysql5(\W|$)" | grep -E "^name:|^variants:.*mysql5|—"

Ticket discussing issue:
https://trac.macports.org/ticket/43431


Regards,
Bradley Giesbrecht (pixilla)


___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Apache2 rev bump for OpenSSL update

[Bradley Giesbrecht]

> On Mar 3, 2016, at 12:09 AM, Juan Manuel Palacios  wrote:
>> On Mar 3, 2016, at 3:35 AM, Ryan Schmidt  wrote:
>>> On Mar 3, 2016, at 00:18, Juan Manuel Palacios  wrote:
>>> 
>>> Apache 2 rev-bumped, cf. r146274.
>>> 
>>> On a side note, and if I may in this same thread, do we have any policy for 
>>> not moving the Apache 2.4 port out of “dev”?  Not too sure when it became 
>>> the recommended release series by the ASF, but it certainly isn’t dev any 
>>> longer.
>> 
>> There's a ticket you can read. We can't just replace the current apache2 
>> port with the current apache24-devel port because it also changes the 
>> directory layout. 

> 
> Yeah, that I understand, we keep versioned ports for other packages too, e.g. 
> mysql55, mysql56, mysql57, and other examples. And we don’t replace one with 
> the other for a myriad of reasons.

With versioned apache24 modules like apache24-mod_python27.

> So we could deprecate the apache24-devel port and create apache24, maybe even 
> also deprecating apache2 and eventually replacing it with apache22, which 
> needless to say would be compatible with the former, and would live on in 
> parallel to apache24, just as mysql55 does to mysql56, etc.
> 
> You have a URL for that ticket that you mention?

https://trac.macports.org/ticket/35824

—
Brad

___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Apache2 rev bump for OpenSSL update

[Daniel J. Luke]

On Mar 3, 2016, at 11:42 AM, Juan Manuel Palacios  wrote:
> I’m sure there’s a lot of people running Apache 2.2 whose systems (probably 
> highly customized configurations) would break if we did that without some 
> kind of transition, because it’d definitely be a backwards-incompatible change

we don't really do anything generally to help people update configs for ports 
when the config format changes. Keeping old versions of stuff around forever 
isn't really a good solution (apache22 is OK for now, but once upstream stops 
releasing security updates for it, we're doing a dis-service to our users if we 
keep it around).

Anyone using macports-provided software to provide critical services can't 
blindly do 'port upgrade outdated' anyway.

>> If there is, I think it's reasonable to have apache2 be the upstream 
>> recommended apache 2 (2.4.x)
> 
> But this would not be possible without the backwards incompatible change, 
> because even if we introduce apache22, the plain apache2 would move from 2.2 
> to 2.4, which I don’t think we should do, at least not without some kind of 
> transition.

If someone is willing to put the effort in to maintain it, I'm not opposed - 
but I don't think we need to do more than have some port notes with a reference 
to the upstream "upgrading to 2.4" docs.

Creating a bunch of 'dead end' ports may "keep things working" for users at the 
expense of not letting them know they're running old/outdated versions of 
things.

-- 
Daniel J. Luke



___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Apache2 rev bump for OpenSSL update

[Juan Manuel Palacios]

> On Mar 3, 2016, at 12:03 PM, Daniel J. Luke  wrote:
> 
> On Mar 3, 2016, at 11:26 AM, Juan Manuel Palacios  wrote:
>> The approach I suggested wouldn’t change layout in any way. apache2 would be 
>> obsoleted and replaced by apache22, which would be the exact same port as 
>> the previous apache2. Parallel to that, apache24-devel would be obsoleted 
>> and replaced by apache24, which again would be the exact same port as the 
>> one it’s replacing. This would create suite of Apache ports similar to what 
>> we now have for MySQL, i.e. mysql51, mysql55, mysql56, etc.
> 
> I don't think there's a compelling need to keep apache22 around.

I’m sure there’s a lot of people running Apache 2.2 whose systems (probably 
highly customized configurations) would break if we did that without some kind 
of transition, because it’d definitely be a backwards-incompatible change

> 
> If there is, I think it's reasonable to have apache2 be the upstream 
> recommended apache 2 (2.4.x)

But this would not be possible without the backwards incompatible change, 
because even if we introduce apache22, the plain apache2 would move from 2.2 to 
2.4, which I don’t think we should do, at least not without some kind of 
transition.


- jmpp

> 
> I would just remove apache24-devel and upgrade the apache2 port to 2.4.x
> 
>> So both ports would essentially just be renamed, preserving everything about 
>> them. Do you guys see a problem with that? I could do it if you don’t….
> 
> -- 
> Daniel J. Luke
> 
> 
> 

___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Apache2 rev bump for OpenSSL update

[Daniel J. Luke]

On Mar 3, 2016, at 11:26 AM, Juan Manuel Palacios  wrote:
> The approach I suggested wouldn’t change layout in any way. apache2 would be 
> obsoleted and replaced by apache22, which would be the exact same port as the 
> previous apache2. Parallel to that, apache24-devel would be obsoleted and 
> replaced by apache24, which again would be the exact same port as the one 
> it’s replacing. This would create suite of Apache ports similar to what we 
> now have for MySQL, i.e. mysql51, mysql55, mysql56, etc.

I don't think there's a compelling need to keep apache22 around.

If there is, I think it's reasonable to have apache2 be the upstream 
recommended apache 2 (2.4.x)

I would just remove apache24-devel and upgrade the apache2 port to 2.4.x

> So both ports would essentially just be renamed, preserving everything about 
> them. Do you guys see a problem with that? I could do it if you don’t….

-- 
Daniel J. Luke



___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Apache2 rev bump for OpenSSL update

[Juan Manuel Palacios]

> On Mar 3, 2016, at 11:08 AM, Ryan Schmidt  wrote:
> 
>> 
>> On Mar 3, 2016, at 9:21 AM, Daniel J. Luke  wrote:
>> 
>> On Mar 3, 2016, at 3:05 AM, Ryan Schmidt  wrote:
>>> On Mar 3, 2016, at 00:18, Juan Manuel Palacios  wrote:
 
 Apache 2 rev-bumped, cf. r146274.
 
 On a side note, and if I may in this same thread, do we have any policy 
 for not moving the Apache 2.4 port out of “dev”?  Not too sure when it 
 became the recommended release series by the ASF, but it certainly isn’t 
 dev any longer.
>>> 
>>> There's a ticket you can read. We can't just replace the current apache2 
>>> port with the current apache24-devel port because it also changes the 
>>> directory layout.
>> 
>> I think it's a mistake to tie upgrading the apache port to 2.4.x and 
>> changing the layout (we could just do a simple version bump with the current 
>> port + make modifications to any apache modules that need them and tackle 
>> changing the layout separately).
> 
> Yes I think you've said that before. I don't disagree at this point, but I'm 
> not working on this issue right now. Someone else is welcome to.

The approach I suggested wouldn’t change layout in any way. apache2 would be 
obsoleted and replaced by apache22, which would be the exact same port as the 
previous apache2. Parallel to that, apache24-devel would be obsoleted and 
replaced by apache24, which again would be the exact same port as the one it’s 
replacing. This would create suite of Apache ports similar to what we now have 
for MySQL, i.e. mysql51, mysql55, mysql56, etc.

So both ports would essentially just be renamed, preserving everything about 
them. Do you guys see a problem with that? I could do it if you don’t….


-jmpp
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Apache2 rev bump for OpenSSL update

[Ryan Schmidt]

> On Mar 3, 2016, at 9:21 AM, Daniel J. Luke  wrote:
> 
> On Mar 3, 2016, at 3:05 AM, Ryan Schmidt  wrote:
>> On Mar 3, 2016, at 00:18, Juan Manuel Palacios  wrote:
>>> 
>>> Apache 2 rev-bumped, cf. r146274.
>>> 
>>> On a side note, and if I may in this same thread, do we have any policy for 
>>> not moving the Apache 2.4 port out of “dev”?  Not too sure when it became 
>>> the recommended release series by the ASF, but it certainly isn’t dev any 
>>> longer.
>> 
>> There's a ticket you can read. We can't just replace the current apache2 
>> port with the current apache24-devel port because it also changes the 
>> directory layout.
> 
> I think it's a mistake to tie upgrading the apache port to 2.4.x and changing 
> the layout (we could just do a simple version bump with the current port + 
> make modifications to any apache modules that need them and tackle changing 
> the layout separately).

Yes I think you've said that before. I don't disagree at this point, but I'm 
not working on this issue right now. Someone else is welcome to.


___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Apache2 rev bump for OpenSSL update

[Daniel J. Luke]

On Mar 3, 2016, at 3:05 AM, Ryan Schmidt  wrote:
> On Mar 3, 2016, at 00:18, Juan Manuel Palacios  wrote:
>> 
>> Apache 2 rev-bumped, cf. r146274.
>> 
>> On a side note, and if I may in this same thread, do we have any policy for 
>> not moving the Apache 2.4 port out of “dev”?  Not too sure when it became 
>> the recommended release series by the ASF, but it certainly isn’t dev any 
>> longer.
> 
> There's a ticket you can read. We can't just replace the current apache2 port 
> with the current apache24-devel port because it also changes the directory 
> layout.

I think it's a mistake to tie upgrading the apache port to 2.4.x and changing 
the layout (we could just do a simple version bump with the current port + make 
modifications to any apache modules that need them and tackle changing the 
layout separately).

-- 
Daniel J. Luke



___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: [146276] trunk/dports/databases

[Juan Manuel Palacios]

Bradley,

I think you and I already discussed this in some thread, but I can’t remember 
right now… 
> Modified: trunk/dports/databases/mysql5/Portfile (146275 => 146276)
> 
> --- trunk/dports/databases/mysql5/Portfile2016-03-03 06:16:58 UTC (rev 
> 146275)
> +++ trunk/dports/databases/mysql5/Portfile2016-03-03 07:25:10 UTC (rev 
> 146276)
> @@ -6,7 +6,7 @@
>  namemysql5
>  version 5.1.72
>  # Please set revision_client and revision_server to 0 if you bump version.
> -set revision_client 0
> +set revision_client 1
>  set revision_server 0
>  set version_branch  [join [lrange [split ${version} .] 0 1] .]
>  homepagehttp://www.mysql.com/ 
>  <>Modified: trunk/dports/databases/mysql51/Portfile (146275 => 146276)
> 
> --- trunk/dports/databases/mysql51/Portfile   2016-03-03 06:16:58 UTC (rev 
> 146275)
> +++ trunk/dports/databases/mysql51/Portfile   2016-03-03 07:25:10 UTC (rev 
> 146276)
> @@ -7,7 +7,7 @@
>  set name_mysql  ${name}
>  version 5.1.73
>  # Set revision_client and revision_server to 0 if you bump version.
> -set revision_client 2
> +set revision_client 3
>  set revision_server 0
>  set version_branch  [join [lrange [split ${version} .] 0 1] .]
>  categories  databases
>  <>
What’s the point of the mysql5 port now a-days? I’d say it’s redundant with 
mysql51, but not even, ‘cause it’s outdated with respect to it, 5.1.72 Vs. 
5.1.73. Shouldn’t we just obsolete that port and have it replaced by mysql51?


- jmpp

___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Apache2 rev bump for OpenSSL update

[Juan Manuel Palacios]

Yeah, that I understand, we keep versioned ports for other packages too, e.g. 
mysql55, mysql56, mysql57, and other examples. And we don’t replace one with 
the other for a myriad of reasons.

So we could deprecate the apache24-devel port and create apache24, maybe even 
also deprecating apache2 and eventually replacing it with apache22, which 
needless to say would be compatible with the former, and would live on in 
parallel to apache24, just as mysql55 does to mysql56, etc.

You have a URL for that ticket that you mention?

> On Mar 3, 2016, at 3:35 AM, Ryan Schmidt  wrote:
> 
> On Mar 3, 2016, at 00:18, Juan Manuel Palacios  wrote:
>> 
>> Apache 2 rev-bumped, cf. r146274.
>> 
>> On a side note, and if I may in this same thread, do we have any policy for 
>> not moving the Apache 2.4 port out of “dev”?  Not too sure when it became 
>> the recommended release series by the ASF, but it certainly isn’t dev any 
>> longer.
> 
> There's a ticket you can read. We can't just replace the current apache2 port 
> with the current apache24-devel port because it also changes the directory 
> layout. 

___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Apache2 rev bump for OpenSSL update

[Ryan Schmidt]

On Mar 3, 2016, at 00:18, Juan Manuel Palacios  wrote:
> 
> Apache 2 rev-bumped, cf. r146274.
> 
> On a side note, and if I may in this same thread, do we have any policy for 
> not moving the Apache 2.4 port out of “dev”?  Not too sure when it became the 
> recommended release series by the ASF, but it certainly isn’t dev any longer.

There's a ticket you can read. We can't just replace the current apache2 port 
with the current apache24-devel port because it also changes the directory 
layout. 
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev