Fedora 18

This bug affect amazon ec2 instances creation with MariaDB-Galera-Server

please Fix It

sudo yum -y install MariaDB-Galera-server
...
...
Transaction check error:
file /usr/bin from install of galera-25.3.2-1.rhel6.x86_64 conflicts with file from package filesystem-2.4.30-3.8.amzn1.x86_64

remove /usr/bin from rpm build process.!

Nirbhay,

Could you please take a look whether it can be fixed on our side (e.g. if we repackage the library for Fedora now), or it still has to be done by Codership, in which case maybe escalate somehow.

We don't provide Fedora 18 packages anymore, and Fedora 19 does not seem to have the problem, so there is nothing else can be done now except for closing it.

Perhaps this issue needs to be renamed and re-opened. This is not an issue with F18 alone, it is affecting EC2 instances created with Amazon's linux image.

Could you please provide more details on how it affects the instances?

The original issue was related to installing the package from MariaDB F18 repository. But there is no F18 repository anymore, so what is the chain of events that causes the problem on Amazon? Which repo are you using that causes the trouble?

Sure:

lsb_release -a
LSB Version: :base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch
Distributor ID: AmazonAMI
Description: Amazon Linux AMI release 2013.09
Release: 2013.09
Codename: n/a

cat /etc/yum.repos.d/mariadb.repo

1. MariaDB 5.5 CentOS repository list - created 2013-06-08 00:43 UTC
2. http://mariadb.org/mariadb/repositories/
   [mariadb]
   name = MariaDB
   baseurl = http://yum.mariadb.org/5.5/centos6-amd64
   gpgkey=https://yum.mariadb.org/RPM-GPG-KEY-MariaDB
   gpgcheck=1

yum update
[snip]
Transaction check error:
file /usr/bin from install of galera-25.3.2-1.rhel6.x86_64 conflicts with file from package filesystem-2.4.30-3.8.amzn1.x86_64

If there's something else I can provide, please let me know!

Joe, thanks.

Nirbhay,
could you please take a look?
I've set it to 5.5.37-galera for now so that it is not missed/forgotten again, but it's up to you to amend priority and the target version.

=== modified file 'scripts/packages/galera.spec'
— scripts/packages/galera.spec 2013-12-01 16:29:42 +0000
+++ scripts/packages/galera.spec 2014-04-04 20:48:38 +0000
@@ -99,7 +99,6 @@
%config(noreplace,missingok) %{_sysconfdir}/sysconfig/garb
%attr(0755,root,root) %{_sysconfdir}/init.d/garb

-%attr(0755,root,root) %dir %{_bindir}
%attr(0755,root,root) %{_bindir}/garbd

%attr(0755,root,root) %dir %

Duplicate: https://bugs.launchpad.net/galera/+bug/1199000

The related galera issue has been fixed.

FYI: the fix went into galera version 25.3.6 & 25.2.10.

It should be noted here, that as of today: the version of galera from the MariaDB repo is still 25.3.5, which means that I cannot install MariaDB-Galera on a newly built CentOS 6 system. From my perspective: this issue has not yet been fixed.

please reopen this issue until the repository (http://yum.mariadb.org) is updated with the working version.

Hi dbart

The proposed fix is already in galera source tree. So until Codership releases 25.3.6, is it possible for us to release/publish galera 25.3.5 packages just with this fix for our users? Any other workaround?

refer : https://bugs.launchpad.net/galera/+bug/1199000

dbart

The updated galera packages have been copied to /home/nirbhay/galera_updated on hasky.

The available galera packages should have the fix.