chocolatey package is outdated

[RiskManagementGroup]

The chocolatey package is outdated. The last version released to chocolatey is v3.10.6.
See: https://community.chocolatey.org/packages/rabbitmq
As of writing the newest version is v.3.11.0

[michaelklishin]

We submit every version but a month or two ago Chocolatey started rejecting them with a single desktop screen for explanation. We are not sure what we can do and what has to change in the package.
If you know how to contact Chocolatey maintainers directly, let us know.

[pauby]

If you go to the package page and click 'Contact Maintainers' then it allows you to send a message directly to the maintainers. If that doesn't get a response, then on the same package click 'Contact Site Admins' to send a message to the Site Admins and Moderators.

[michaelklishin]

Here is the package source: https://github.com/rabbitmq/chocolatey-package.

[garrmark]

I pulled this and ran it locally on a windows 11 machine, the silent install isn't completely silent, it popped this error for me

I then ran the install exe to get the error on installing the service, it shows this:
Installing RabbitMQ service...
C:\Program Files\Erlang OTP\erts-13.0.4\bin\erlsrv: Service RabbitMQ added to system.
C:\Program Files\Erlang OTP\erts-13.0.4\bin\erlsrv: Unrecognized option neighbours:.

That's about as far as I got

[garrmark]

so the installer errored out, but left the files so here's the output of trying to install the service:

.\rabbitmq-service.bat install

---

ERLANG_SERVICE_MANAGER_PATH not set correctly.

---

"\erlsrv.exe" not found
Please set ERLANG_SERVICE_MANAGER_PATH to the folder containing "erlsrv.exe".

[garrmark]

my issue was respolved by setting
$env:HOMEDRIVE=C:

[garrmark]

I submitted rabbitmq/chocolatey-package#59

I don't know if it'll fix the chocolatey install test, but if you could try resubmitting to chocolatey for v3.10.10, that would be cool @michaelklishin

[michaelklishin]

I have submitted a 3.9.23 version and now we do see a specific error message: it can be that the Erlang dependency in Chocolatey package metadata is out of date.

Unfortunately previously we had a blank (as in, just a desktop) screen without any details. 3.10 and 3.11 might still run into that, we will see possibly even later today.

[lukebakken]

[garrmark]

when you do a local install and set the source to your current directory, I believe it only looks there for dependencies.

https://docs.chocolatey.org/en-us/create/create-packages#testing-your-package

You'll need to append the API path like so: --source "'.;https://community.chocolatey.org/api/v2/'" (note the double quotes bookending the apostrophes here, use %cd% in cmd.exe or $pwd in Powershell.exe if . doesn't resolve).

[michaelklishin]

But there is a 25.0.4 release of the erlang package according to chcolatey.org :/

[michaelklishin]

A few potentially relevant installer issues addressed recently:

• Windows: Fix Erlang/OTP version detection in the installer rabbitmq-packaging#22
• Windows: Fix the value of $ERLANG_HOME environment variable rabbitmq-packaging#23
• Re-set RABBITMQ_PLUGINS_DIR after INSTDIR is read from dialog rabbitmq-packaging#29

[henebb]

Any updates on the chocolatey package? The latest version still seems to be 3.10.6.

[pauby]

If you go to the message in the moderation comments on that page it gives you a link to the logs in the gist. That message is also sent by email to all of the maintainers.

The last message in that log says:

Elevating permissions and running ["C:\Users\Administrator\AppData\Local\Temp\chocolatey\rabbitmq\3.11.3\rabbitmq-server-3.11.3.exe" /S ]. This may take a while, depending on the statements.

Which means that the install timed out. The screenshot at the bottom of the gist also shows a black window. This generally means that the installer is not silent and waiting on input.

Have you tested the package in the Chocolatey Test Environment? You may find the software needs a dependency (maybe a version of .NET as an example) that is not present on the system and should be added as a package dependency.

[lukebakken]

Yes, I followed that link and noticed that the log didn't say anything useful. It would be great if there were an actual "installer timed out" message somewhere.

Which means that the install timed out

...and yet the RabbitMQ team knows that the Windows installer works just fine, because people who use Windows and pay for RabbitMQ support would have raised hell about it by now.

The only dependency RabbitMQ needs is Erlang. This has not changed since the dawn of time.

I'll try to find time to rectify this situation but as you can imagine, there are higher priorities. Nobody who pays for RabbitMQ support has requested this fix. That would raise its priority.

[michaelklishin]

Yes, recently there were improvements around debugging of Chocolatey package submissions. It's just hasn't been a priority compared to other things.

[lukebakken]

@pauby I appreciate you pointing out the chocolatey test environment and I'll give that a try.

[lukebakken]

Installing 3.11.5 worked just fine using the test environment:

[lukebakken]

@pauby @michaelklishin @henebb @garrmark @RiskManagementGroup

RabbitMQ 3.11.5 has been approved. I have no idea why other versions did not work:

https://community.chocolatey.org/packages/rabbitmq

[henebb]

Nice work! 👏

[pauby]

@lukebakken

...and yet the RabbitMQ team knows that the Windows installer works just fine, because people who use Windows and pay for RabbitMQ support would have raised hell about it by now.

I'll try to find time to rectify this situation but as you can imagine, there are higher priorities. Nobody who pays for RabbitMQ support has requested this fix. That would raise its priority.

Just to be very clear, I jumped in here to help out. I know it's difficult and inadvisable to read tone into messages, but the tone of yours was frustration with me.

RabbitMQ 3.11.5 has been approved. I have no idea why other versions did not work:

I'm going to take a guess.

We recently (as in the last few days) upgraded our test environment to use Windows Server 2019 as a base. We are still working on tweaking this so, we have not updated the test environment repository I pointed you to. That will likely be updated in the new year when a blog post will also follow.

Having said that, it doesn't make a lot of sense when you tried it in the 2012 R2 test environment and it worked. Because that is the same version that the previous versions used. So, I have to throw my hands up and say I don't know.

It's working now and that is all that matters.

If you need to have those other versions that were rejected, available, please let me know.

[lukebakken]

I know it's difficult and inadvisable to read tone into messages, but the tone of yours was frustration with me

I'm appreciative of your assistance, thank you.

I'm frustrated with other users who have repeatedly commented "where's the latest version" without doing anything to assist. You know how it is with free software.

I can't explain why it worked using Windows 2012 in my environment. The only thing I could say is that I logged into the running VM and ran choco install... there, and didn't use the provisioning script. That could be where the difference lies.

I don't think we need to worry about the other versions at this time.

Thanks again for your assistance and Merry Christmas / Happy New Year!

[pauby]

I'm frustrated with other users who have repeatedly commented "where's the latest version" without doing anything to assist. You know how it is with free software.

😂 I was actually thinking the very same thing not less than 30 minutes ago. Unfortunately, I completely appreciate that feeling.

Thanks again for your assistance and Merry Christmas / Happy New Year!

To you, and the whole team!

We appreciate you maintaining the package and persevering through the issues. If you have problems in the future, please let me know.

[lukebakken]

Thanks again! Our conversation reminded me that it's time to renew my chocolatey pro license.