Opened 12 years ago

Closed 12 years ago

#33685 closed update (duplicate)

rabbitmq-server: update to version 2.8.0

Reported by: steve@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version:
Keywords: haspatch Cc: meyer@…, steve@…
Port: rabbitmq-server

Description

rabbitmq-server version 2.8.0 has been released (see http://lists.rabbitmq.com/pipermail/rabbitmq-announce/2012-March/000044.html). The attached patch updates the Portfile and wrapper scripts.

Attachments (1)

rabbitmq-port-2.8.0.patch (4.3 KB) - added by steve@… 12 years ago.
Patch Portfile and wrapper-script for 2.8.0

Download all attachments as: .zip

Change History (9)

Changed 12 years ago by steve@…

Attachment: rabbitmq-port-2.8.0.patch added

Patch Portfile and wrapper-script for 2.8.0

comment:1 Changed 12 years ago by mf2k (Frank Schima)

It would be preferable to change the sha1 checksum to sha256 as that is now recommended.

comment:2 in reply to:  1 Changed 12 years ago by steve.powell@…

Replying to macsforever2000@…:

It would be preferable to change the sha1 checksum to sha256 as that is now recommended.

Thank you -- this will probably happen in the next release. I assume it is not essential for this one.

comment:3 Changed 12 years ago by steve@…

Cc: steve@… added

Cc Me!

comment:4 in reply to:  1 Changed 12 years ago by steve@…

Replying to macsforever2000@…:

It would be preferable to change the sha1 checksum to sha256 as that is now recommended.

Is there a reason why this update hasn't been applied?

comment:5 Changed 12 years ago by steve@…

This patch should NOT be applied, now. Version 2.8.2 is available and we can update directly from 2.7.1 on macports.

comment:6 Changed 12 years ago by danielluke (Daniel J. Luke)

Resolution: invalid
Status: newclosed

comment:7 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)

Resolution: invalid
Status: closedreopened

comment:8 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)

Resolution: duplicate
Status: reopenedclosed

Superseded by #34285.

Note: See TracTickets for help on using tickets.