RabbitMQ RPM SUSE version detected in CentOS repository

[Vladislav Rastrusny]

Hi.

I'm trying to install RabbitMQ from PackageCloud repo: https://packagecloud.io/rabbitmq/rabbitmq-server/el/7/$basearch

My arch is x64. This is a list of packages in my system after the repo  and RabbitMQ itself is installed:

[vagrant@localhost ~]$ yum --showduplicates list rabbitmq-server | expand
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * base: mirror.corbina.net
 * epel: ftp.colocall.net
 * extras: mirror.corbina.net
 * remi: mirror.h1host.ru
 * remi-php56: mirror.h1host.ru
 * updates: mirror.corbina.net
Installed Packages
rabbitmq-server.noarch          3.5.6-1.suse           @rabbitmq_rabbitmq-server
Available Packages
rabbitmq-server.noarch          3.3.5-6.el7            epel
rabbitmq-server.noarch          3.5.6-1                rabbitmq_rabbitmq-server
rabbitmq-server.noarch          3.5.6-1.suse           rabbitmq_rabbitmq-server

It's strange, but there is 3.5.6-1.suse version of the package in this
CentOS repository and it is installed into my system now instead of a non-prefixed one.

With this SUSE package on a CentOS server RabbitMQ startup fails with the following error:

[vagrant@localhost ~]$ cat /var/log/rabbitmq/startup_err
/etc/rc.d/init.d/rabbitmq-server: line 64: startproc: command not found


There is no "startproc"-something in CentOS. This is a common problem
if you install suse-addressed package.

What can be done around this problem? I can switch to EPEL, but
RabbitMQ versions provided by it are too old for me to use.

I cannot provide full version string in my Ansible playbook since I
need latest version of RabbitMQ to be installed. I cannot tie myself
to something like "rabbitmq-server.noarch          3.5.6-1"

I've send an email to sup...@packagecloud.io two days ago, but no reply so far.

[Michael Klishin]

On 6 November 2015 at 18:08:37, Vladislav Rastrusny (fract...@yandex.ru) wrote:
> It's strange, but there is 3.5.6-1.suse version of the package
> in this
> CentOS repository and it is installed into my system now instead
> of a non-prefixed one.

TL;DR: Package Cloud repos are likely going away in the future. Use the RPMs from
rabbitmq.com, github, bintray. 

> I've send an email to sup...@packagecloud.io two days ago,
> but no reply so far.

Package Cloud developers do not maintain RabbitMQ packages there, Pivotal does.
It's not exactly polite to contact them about issues with packages they are not responsible for.
--
MK

Staff Software Engineer, Pivotal/RabbitMQ

[Vladislav Rastrusny]

TL;DR: Package Cloud repos are likely going away in the future. Use the RPMs from
rabbitmq.com, github, bintray. 

 

The problem is that I would like to write Ansible script for installing latest version of Rabbit, not a specific one. I'm looking for a way to fetch the latest stable RPM available.

 

> I've send an email to sup...@packagecloud.io two days ago,  
> but no reply so far.

Package Cloud developers do not maintain RabbitMQ packages there, Pivotal does.
It's not exactly polite to contact them about issues with packages they are not responsible for.

Well, they have them on their website. And they provide scripts for installation openly. And I disagree that my action is not polite. I'm reporting a problem, that takes place on their website with the tools they provide. Since when is this not polite?

Of course, I am not aware of internal relations between Pivotal and PackageCloud. I will try to hack into their business relations now of course ;) I will try to be polite this time ;))

[Michael Klishin]

On 6 November 2015 at 18:58:19, Vladislav Rastrusny (fract...@yandex.ru) wrote:
> I disagree that my action is not polite. I'm reporting a problem,
> that takes place on their website with the tools they provide.
> Since when is this not polite?

Package Cloud team does not maintain 99.999% of packages publicly hosted there.

Would you contact GitHub support whenever you have something to complain about
a project hosted there?

[Vladislav Rastrusny]

>
> Package Cloud team does not maintain 99.999% of packages publicly hosted there.
>
> Would you contact GitHub support whenever you have something to complain about
> a project hosted there?

Well, in case of GitHub I think I would know they can't do anything to
help me, so of course I will not contact them ;)

But I am sure, they would be polite enough not to accuse me of being
disrespectful or rude for asking an unrelated question or reporting a
nonse bug.
Thank you for your support.

> --
> MK
>
> Staff Software Engineer, Pivotal/RabbitMQ
>
>

> --
> You received this message because you are subscribed to a topic in the Google Groups "rabbitmq-users" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/topic/rabbitmq-users/8UXYb02x0xQ/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to rabbitmq-user...@googlegroups.com.
> To post to this group, send an email to rabbitm...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[thomas....@systrangroup.com]

Hi,

I ran into the same issue (and other ones):

On Friday, November 6, 2015 at 4:39:14 PM UTC+1, Michael Klishin wrote:

On 6 November 2015 at 18:08:37, Vladislav Rastrusny (fract...@yandex.ru) wrote:
> It's strange, but there is 3.5.6-1.suse version of the package  
> in this
> CentOS repository and it is installed into my system now instead  
> of a non-prefixed one.

TL;DR: Package Cloud repos are likely going away in the future. Use the RPMs from
rabbitmq.com, github, bintray.   

These solution only provide raw rpm hosting, no full yum repository, which is highly useful to maintain rabbitmq-server up-to-date. 

An apt repository was already provided on rabbitmq.com, but for the yum repository only Package Cloud finally brought that.

1/ What is the plan for the Package Cloud removal? When will it happen? Will there be another yum repository to replace it? Will there be a grace period to smoothly migrate to the new yum repository?

2/ If we need right now a yum repository for rabbitmq-server, is Package Cloud recommended or not?

2/a/ If yes, then the initial reported issue should be fixed: don't push suse special packages as same package name & version, with only "Release" changed: yum will pick "3.5.6-1.suse" as newer version than "3.5.6-1" for the same package name "rabbitmq-server", thereby rendering useless the yum repository (because the -1.suse version doesn't work on redhat/centos).

Also, there is an issue with rpm signing: they are signed with rabbitmq gpg key, but the Package Cloud installation documentation assumes the rpm are signed with their own key. This also breaks the yum repository (this can be worked-around by modifying the repo file in /etc/yum.repo.d).

2/b/ If no, then there should be a warning on the http://www.rabbitmq.com/install-rpm.html page stating that Package Cloud installation is deprecated, with known issues.

Thanks,

Thomas

[Michael Klishin]

We still do not have a permission to
use PC so it is not recommended.

A yum repo will be provided as time permits: we are a tiny team.

Community is welcome to take our packages and public key and host their own repos,
as long as it is updated reasonably quickly.