#34966 closed update (fixed)
rabbitmq-server: update to version 2.8.4
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.8.4 has been released (see website news item). The attached patch updates the Portfile and wrapper scripts.
Attachments (1)
Change History (7)
Changed 12 years ago by steve@…
Attachment: | rabbitmq-2.8.4.patch added |
---|
comment:1 follow-up: 3 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)
Owner: | changed from macports-tickets@… to ryandesign@… |
---|---|
Status: | new → assigned |
Thanks.
Note that I had to edit this patch before applying it, because it wants to delete the file "Portfile-e", which does not exist.
comment:2 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
comment:3 Changed 12 years ago by steve@…
Replying to ryandesign@…:
Note that I had to edit this patch before applying it, because it wants to delete the file "Portfile-e", which does not exist.
Thank you for doing that. I noticed that this file was deleted. The patches are generated by obtaining the public Macports version and comparing it to our own current one. If it tried to delete Portfile-e it is because we got this file when we got the public Macports port via:
svn checkout http://svn.macports.org/repository/macports/trunk/dports/net/rabbitmq-server/
If this is not the right way to get them, we need to update our procedures.
comment:4 follow-up: 5 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)
That procedure should be fine. There is no file called Portfile-e in our repository. You can verify this by visiting the above URL in a web browser.
comment:5 follow-up: 6 Changed 12 years ago by steve@…
Replying to ryandesign@…:
That procedure should be fine. There is no file called Portfile-e in our repository. You can verify this by visiting the above URL in a web browser.
Just trawled and found we've had this annoyance before. It is caused by a sed -i -e
... command in our procedures.
This behaves differently on MacOS and Linux, and the problem is masked by the patches often being generated on a Linux. We will update our procedures. Sorry to have caused you work.
comment:6 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)
Replying to steve@…:
Just trawled and found we've had this annoyance before. It is caused by a
sed -i -e
... command in our procedures.
This behaves differently on MacOS and Linux, and the problem is masked by the patches often being generated on a Linux. We will update our procedures. Sorry to have caused you work.
No problem; thanks for letting me know what the problem was; I was curious. Yes, on BSD sed, such as is found in OS X, the argument to -i
is not optional. So you could use sed -i '' -e ...
, or you could install the gsed port to get a copy of GNU sed and then use gsed -i -e ...
.
Macports patch from 2.8.2 to 2.8.4