Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Getting error E: Version '3.1.4' for 'rabbitmq-server' was not found #110

Closed
hamzasa opened this issue Aug 18, 2013 · 11 comments
Closed

Getting error E: Version '3.1.4' for 'rabbitmq-server' was not found #110

hamzasa opened this issue Aug 18, 2013 · 11 comments

Comments

@hamzasa
Copy link

hamzasa commented Aug 18, 2013

Hi
i'm trying to install version 3.1.4 and i'm getting the following error:
E: Version '3.1.4' for 'rabbitmq-server' was not found
please advise

@jlambert121
Copy link

Could you provide some more details? OS, module version, how you are defining the rabbitmq version?

@hamzasa
Copy link
Author

hamzasa commented Aug 19, 2013

I'm running it on ubuntu 12.0.4 with version 3.0.0 and defining the version
with package_insure parameter

From: Justin Lambert [mailto:notifications@github.com]
Sent: Monday, August 19, 2013 5:11 PM
To: puppetlabs/puppetlabs-rabbitmq
Cc: hamzasa
Subject: Re: [puppetlabs-rabbitmq] Getting error E: Version '3.1.4' for
'rabbitmq-server' was not found (#110)

Could you provide some more details? OS, module version, how you are
defining the rabbitmq version?


Reply to this email directly or view it on
GitHubhttps://github.com//issues/110#issuecomment-22874353
.

This e-mail, as well as any attached document, may contain material which
is confidential and privileged and may include trademark, copyright and
other intellectual property rights that are proprietary to Kenshoo Ltd,
its subsidiaries or affiliates ("Kenshoo"). This e-mail and its
attachments may be read, copied and used only by the addressee for the
purpose(s) for which it was disclosed herein. If you have received it in
error, please destroy the message and any attachment, and contact us
immediately. If you are not the intended recipient, be aware that any
review, reliance, disclosure, copying, distribution or use of the contents
of this message without Kenshoo's express permission is strictly prohibited.

@jlambert121
Copy link

It looks like for Debian based distros the apt provider gets set up the rabbitmq repo and not being familiar with apt, it appears only 3.1.5 is available: http://www.rabbitmq.com/debian/pool/main/r/rabbitmq-server/. Someone else may be able to correct me, but it appears you may need to find a different repo that has 3.1.4 for you.

@apenney
Copy link
Contributor

apenney commented Aug 19, 2013

The RabbitMQ authors are crazy and annoying for this - they remove all but the very latest versions from the repo. I don't know why or what the hell they think it accomplishes other than making life difficult for end users, but that's what is causing this. Sorry for the pain it causes but I don't know of a less terrible repo that we can rely on. I honestly considered a fact that parsed the rabbitmq site to figure out the latest version but it's even worse.

@bodepd
Copy link
Contributor

bodepd commented Aug 19, 2013

what about just supporting versions that are packaged by distros?

@jlambert121
Copy link

Rather than hard code a version the params could be "latest" and an optional apt repo install for rabbitmq for those who want newer than the latest distro package.

@jlambert121
Copy link

I just looked again now that I'm on a real computer, Debian defaults to ensure => 'installed' for the package. By default not specifying a version then would install the most current on new machines and not change it once it was deployed. This seems like a reasonable way to go and I'm not sure there is much that can be done by this module if the RabbitMQ team is yanking previous versions as soon as there is a newer version other than making the RabbitMQ repo optionally installed and hosting the versions you want to keep in a private repo managed outside of this module.

@apenney
Copy link
Contributor

apenney commented Aug 26, 2013

I promised Dan before I would tackle making it use distro packages by default (even if they are out of date) and then have a toggle for the more up to date upstream packages so I'll work on that. My concern was that distro versions will have different cli output/flags that'll break the providers but that's a problem we'll deal with when we face it.

@bodepd
Copy link
Contributor

bodepd commented Aug 26, 2013

@apenney This aspect of module development can be especially difficult. Either the providers/manifests need to contain tons of conditional logic, or the modules need to maintain a branching scheme that maps to application major versions. I've never been able to figure out the right balance when dealing with versions of everything...

@hamzasa
Copy link
Author

hamzasa commented Sep 2, 2013

all releases could be found in this under this url:
http://www.rabbitmq.com/releases/rabbitmq-server/

@wyardley
Copy link
Contributor

Closed via #493

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants