#32620 closed update (fixed)
rabbitmq-server: Update to version 2.7.1
| Reported by: | steve@… | Owned by: | ryandesign (Ryan Carsten Schmidt) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | haspatch | Cc: | meyer@… |
| Port: | rabbitmq-server |
Description
rabbitmq-server version 2.7.1 has been released (see http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/2011-December/016941.html). The attached patch updates the portfile.
Attachments (1)
Change History (8)
Changed 13 years ago by steve@…
| Attachment: | rabbitmq-server-2.7.1-port.patch added |
|---|
comment:1 follow-up: 2 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
| Summary: | Update rabbitmq-server to version 2.7.1 → rabbitmq-server: Update to version 2.7.1 |
|---|
Your patch undoes r87628... Does 2.7.1's build process no longer read from or write to $HOME like 2.7.0 did?
comment:2 Changed 13 years ago by steve.powell@…
Replying to ryandesign@…:
Your patch undoes r87628... Does 2.7.1's build process no longer read from or write to $HOME like 2.7.0 did?
Removing that line was unintentional, thank you for spotting it. Is there some way we can be notified if our portfile is updated under us? I'll supply a new patch in a few minutes.
comment:3 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
| Owner: | changed from macports-tickets@… to ryandesign@… |
|---|---|
| Status: | new → assigned |
That's ok, I can commit it without that one change.
You can subscribe to the macports-changes mailing list, but will receive an email for every change, not just for your ports. But you could then configure a mail filter to discard emails that don't contain the name of one of your ports.
comment:4 follow-up: 5 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
comment:5 Changed 13 years ago by steve.powell@…
Replying to ryandesign@…:
Thank you for doing that. Our automated build is supposed to generate the required patch, and of course while I was updating it just now (or rather the driving files for it) you updated the macports directory for me, so I was getting the wrong patches out. Rather confusing for a bit.
We will be updating our own portfile server, too, of course.
comment:6 follow-up: 7 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
Ok, well please do manually inspect your diffs before you submit them to us, to ensure the diffs are what you intend.
comment:7 Changed 13 years ago by steve@…
Replying to ryandesign@…:
Ok, well please do manually inspect your diffs before you submit them to us, to ensure the diffs are what you intend.
Sorry for the delay -- yes I've manually inspected our diffs. But I couldn't understand why you added this HOME setting in the build phase.
Now I'm convinced that you don't need this. What made you think we did?
Portfile patch for rabbitmq-server 2.7.1