Apache2 rev bump for OpenSSL update

Juan Manuel Palacios jmpp at macports.org
Wed Mar 2 22:18:33 PST 2016


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.

> On Mar 2, 2016, at 10:38 PM, Juan Manuel Palacios <jmpp at macports.org> wrote:
> 
> Yeah, that’s the one!
> 
>> On Mar 2, 2016, at 10:33 PM, Bradley Giesbrecht <pixilla at macports.org> wrote:
>> 
>> All the mysql ports with the exception of mysql5 are revbumped by incrementing the revision_client var just after the version number in the Portfile.
>> 
>> $ port echo name:^\(mariadb[0-9.-]*\|percona\|mysql5[0-9]*\)$
>> mariadb                         
>> mariadb-10.0                    
>> mariadb-10.1                    
>> mysql5                          
>> mysql51                         
>> mysql55                         
>> mysql56                         
>> mysql57                         
>> percona                         
>> 
>> I can do it, is this the openssl revision to reference in the commit message?
>> https://trac.macports.org/changeset/146162
>> 
>> 
>> Regards,
>> Bradley Giesbrecht (pixilla)
>> 
>> 
>> 
>> 
>>> On Mar 2, 2016, at 5:42 PM, Juan Manuel Palacios <jmpp at macports.org> wrote:
>>> 
>>> True enough. I’ll at least take care of the Apache 2 port in a bit if no one beats me to it, and I’ll see what can be done for the MySQL ports.
>>> 
>>>> On Mar 2, 2016, at 9:10 PM, Ryan Schmidt <ryandesign at macports.org> wrote:
>>>> 
>>>> On Mar 2, 2016, at 7:32 PM, Juan Manuel Palacios <jmpp at macports.org> wrote:
>>>>> 
>>>>>> On Mar 2, 2016, at 9:00 PM, Ryan Schmidt <ryandesign at macports.org> wrote:
>>>>>> 
>>>>>> On Mar 2, 2016, at 14:10, Juan Manuel Palacios <jmpp at macports.org> wrote:
>>>>>>> 
>>>>>>> Hey Ryan,
>>>>>>> 
>>>>>>> The Apache 2 port is failing a reload with the "Symbol not found: _SSLv2_client_method” error (Referenced from: /opt/local/apache2/modules/mod_ssl.so\n  Expected in: /opt/local/lib/libssl.1.0.0.dylib) due to the recent OpenSSL update, which removed SSLv2.
>>>>>>> 
>>>>>>> Shouldn’t we rev bump the Apache 2 port to force a rebuild against the new OpenSSL?
>>>>>> 
>>>>>> And all the other ports that link with openssl. 
>>>>> 
>>>>> Indeed, but I aint maintainer ;)
>>>>> 
>>>>> I got Apache to work simply by forcing a rebuild against new OpenSSL.
>>>> 
>>>> 
>>>> I consider it the responsibility of the committer who updated the openssl port to the version that changed its library ABI to revbump the ports that link with it, regardless of maintainer status. It should have been done at the same time that openssl was updated of course. I'm not working on it so someone else is welcome to do it.
>>>> 
>>>> 
>>>> 
>>> 
>>> _______________________________________________
>>> macports-dev mailing list
>>> macports-dev at lists.macosforge.org
>>> https://lists.macosforge.org/mailman/listinfo/macports-dev
>> 
> 
> _______________________________________________
> macports-dev mailing list
> macports-dev at lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev



More information about the macports-dev mailing list