Comments

481 Comments

LGTM =)

BZ#1339847 erlang-goldrush-0.1.9 is available

I'd recommend you consider replacing this build (which still has broken deps per bug #1306561 btw), with ugene-1.22.0-6.fc24 which fixes this, bug #1342268 (missing -debuginfo) , as well as several other cosmetic issues.

karma

Works for me on my F24 ejabberd test box!

I also have this problem when compiling caffe on F23. Is there any update?

karma

works

BZ#871155 Remove bundled ejson library from CouchDB

This update has been unpushed.

I'm having this error when I try to start the server:

rabbitmq-server.service: Failed at step EXEC spawning /usr/lib/rabbitmq/bin/rabbitmq-server: No such file or directory

BZ#1309683 rabbitmq-server-3.6.1 is available
BZ#1323610 Broken since 3.6.1
BZ#1324488 rabbitmq-server unable to start due to /usr/lib/rabbitmq/bin/ being missing in 3.6.1-1

Working on 4.4.6-300.fc23.x86_64 #1 SMP Wed Mar 16 22:10:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

BZ#1323610 Broken since 3.6.1
BZ#1324488 rabbitmq-server unable to start due to /usr/lib/rabbitmq/bin/ being missing in 3.6.1-1

Server fails to run

karma: -1

openstack seams to be operational.

BZ#1323610 Broken since 3.6.1
BZ#1324488 rabbitmq-server unable to start due to /usr/lib/rabbitmq/bin/ being missing in 3.6.1-1

With this update, rabbit doesn't even start because the systemd unit file tries to run a script which doesn't exist anymore

karma: -1

The package is broken work.

/usr/lib/rabbitmq/bin/rabbitmq-plugins

/usr/lib/rabbitmq/bin/rabbitmq-server

/usr/lib/rabbitmq/bin/rabbitmqctl

are missing

karma: -1

BZ#1309683 rabbitmq-server-3.6.1 is available

I mean -1 of course (even if too late... already in stable)

See #1323610

This package has a problem. When I try to link a package built with it with the current version of glog in F23 I get this linking error:

/usr/lib/gcc/x86_64-redhat-linux/5.3.1/../../../../lib64/libglog.so: undefined reference to `gflags::FlagRegisterer::FlagRegisterer(char const*, char const*, char const*, char const*, void*, void*)'

There's also a curious thing in the exported fields. Besides _init, the first two fields exported are:

00000000000075f0 T _ZN6google14FlagRegistererC1EPKcS2_S2_S2_PvS3_
00000000000075f0 T _ZN6google14FlagRegistererC2EPKcS2_S2_S2_PvS3_

These look nearly the same, except one is C1 and the other is C2. They both demangle underr c++filt to the same value:

00000000000075f0 T google::FlagRegisterer::FlagRegisterer(char const*, char const*, char const*, char const*, void*, void*)

In principle I don't see why you can't have two symbols with the same value, and they both have the type expected by glog. However, this is beyond my C++ symbol mangling expertise.

karma: -1

BZ#1312597 Review request: upgrade gflags from 2.1.1 to 2.1.2