Details
-
Type:
Task
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Fix Version/s: 5.5.28a-galera
-
Component/s: None
-
Labels:
Description
something needs to be done with DEB and RPM package names - not the file names (which is fixed already), but subpackage names. The reason is that packages should be distinguished from regular/vanilla MariaDB.
also obsoletes/conflicts should ensure these packages cannot be installed together with regular mariadb packages
we'll put galera packages in our apt/yum repositories, so that the package manager will be able to satisfy dependencies automatically (MDEV-527)
Gliffy Diagrams
Attachments
Issue Links
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
mariadb-galera rpms are now tested in buildbot. but only on centos6-amd64 the test succeeds.
This is the fixing debian packaging for Galera task
I have a simple question: When can we expect a .db release for MariaDB Galera in the repositories ?
Proposed patch. Part I
http://lists.askmonty.org/pipermail/commits/2012-November/003872.html
Looks almost ok. Just one comment:
I've run 'make install' and found seven new files. I mean, 5.5-galera tree installs seven extra files, as compared to the vanilla mariadb. You need to add these files to the package, to ensure they're installed in .deb too. They are:
./README-wsrep
./bin/wsrep_sst_common
./bin/wsrep_sst_mysqldump
./bin/wsrep_sst_rsync
./bin/wsrep_sst_xtrabackup
./support-files/wsrep.cnf
./support-files/wsrep_notify
From IRC
<elenst> wlad: but if we rename the packages, won't they lose the ability to replace the "normal" MariaDB packages?
<wlad> elenst, I frankly do not know what is intended
<wlad> should they be able to replace vanilla mariadb or not.. this is perhaps also to think about
<wlad> actually such questions should be though about every time a new product is released
<wlad> this time we did not do that