#28569 closed update (fixed)
apr0, apr0-util0, apache20 updates
Reported by: | ryandesign (Ryan Carsten Schmidt) | Owned by: | blair (Blair Zajac) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 1.9.2 |
Keywords: | Cc: | vulcan_@… | |
Port: | apr0, apr-util0, apache20 |
Description
Blair, here's a patch that:
- updates apr0 to 0.9.19
- removes Leopard and Snow Leopard reinplaces from apr0 (I verified it does nothing on Snow Leopard; I assume Leopard is the same)
- updates apr-util0 to 0.9.19
- changes apr-util0 db44 dependency to db46 since that's what apr-util uses
- updates apache20 to 2.0.64
- refreshes the openssl 1.0.0 patch in apache20
- adds perl5 dependency to apache20 and fixes path to perl in printenv cgi example (see #28564 -- you'll need to "svn cp" the patch from the apache2 port too)
This all builds for me on Snow Leopard and I have it staged in my working copy ready to commit, if you give the ok.
Attachments (1)
Change History (7)
Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)
Attachment: | apr0-apr-util0-apache20-updates.diff added |
---|
comment:1 Changed 14 years ago by vulcan_@…
i see this is happening today so i will add my input here in the hope of shortening the solution cycle: about 1 hour ago i did port selfupdate and saw that a new version of apache2 was available, so i did the update (using porticus) this was my result
Port command started with PID 77202 Computing dependencies for apache2 Dependencies to be installed: perl5 Activating perl5 @5.12.3_0+perl5_12 Error: Target org.macports.activate returned: Image error: /opt/local/bin/corelist is being used by the active p5-module-corelist port. Please deactivate this port first, or use 'port -f activate perl5' to force the activation. Error: The following dependencies were not installed: perl5 Error: Unable to upgrade port: 1 To report a bug, see <http://guide.macports.org/#project.tickets> Executing: /opt/local/bin/port -uR upgrade apache2 +preforkmpm
i can do the forced activate, but i thought that you should see this ASAP as it is possibly a rare side effect condition.
comment:2 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | vulcan_@… added |
---|
@vulcan_: That's not related to this ticket; please ask on the macports-users mailing list if you need help.
comment:3 follow-up: 4 Changed 14 years ago by blair (Blair Zajac)
Looks good to me, feel free to commit.
Out of curiosity, did you need to do this work for a project, since most people are on apache2?
Thanks, Blair
comment:4 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)
Resolution: | → fixed |
---|---|
Status: | new → closed |
Replying to blair@…:
Looks good to me, feel free to commit.
Thanks, r76573.
Out of curiosity, did you need to do this work for a project, since most people are on apache2?
You know I use apache2; I've asked you before about deleting apache20 :) but you wanted to keep it which is fine. When I resolved #28564 for apache2 I wanted to check if apache20 was also affected, and I discovered it also needed a patch for openssl 1.0.0 (#25621) and to be updated, then when I had trouble building apr0 I found it and apr-util0 needed an update too. So here we are.
comment:5 Changed 14 years ago by blair (Blair Zajac)
Well, I was surprised to see the effort put into apache20, which is why I asked.
So thanks for doing the work.
We can get rid of it since it's taking additional resources, but now that it's all update to date, maybe we should just wait till it breaks and then remove it :)
comment:6 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)
Or until the end-of-life announcement, whichever comes first :P
proposed patches