forked from pool/mariadb
c692fa4a36
Fixup the build dependencies. Requiring systemd/systemd-devel is almost always wrong as it takes you out of the order in the build chain. In case of mariadb it even introduces a build cycle. Hence, update the BuildRequires to match what the build system (cmake) actually is looking for. There is not a single place it tries to find systemd.pc (which seems what caused your entire confusion - it happened to work when systemd.pc was in the -devel package, but broke when this was moved out). with this diff, the build log contains correctly: [ 185s] -- Checking for one of the modules 'libsystemd;libsystemd-daemon' [ 185s] -- Performing Test HAVE_SYSTEMD [ 185s] -- Performing Test HAVE_SYSTEMD - Success [ 185s] -- Looking for include file systemd/sd-daemon.h [ 185s] -- Looking for include file systemd/sd-daemon.h - found [ 186s] -- Systemd features enabled Just as one would expect to find there. OBS-URL: https://build.opensuse.org/request/show/452618 OBS-URL: https://build.opensuse.org/package/show/server:database/mariadb?expand=0&rev=187 |
||
---|---|---|
_constraints | ||
.gitattributes | ||
.gitignore | ||
baselibs.conf | ||
configuration-tweaks.tar.xz | ||
mariadb-10.1.20.tar.gz | ||
mariadb.changes | ||
mariadb.spec | ||
my.ini | ||
mysql-patches.tar.xz | ||
mysql-systemd-helper | ||
mysql.service | ||
mysql.SuSEfirewall2 | ||
mysql.target | ||
mysql@.service | ||
README.debug | ||
README.install | ||
README.SUSE | ||
series | ||
suse-test-run |
Notes about MySQL 5.1 package: ============================== With MySQL 5.1 package we introduced some changes you may like to know. Most of them will affect you only if you are upgrading from previous version and you did some changes to your configuration. 1) Plugins: =========== One of the new features in MySQL 5.1 is support for plugins. So some of the storage engines are now shipped like that. You can use following plugins: - archive - blackhole - federated - example InnoDB is still compiled as internal part of MySQL. If you are upgrading from version 5.0 or if this is your first installation of MySQL 5.1, all plugins will be enabled by default and you can disable them manually later (see http://dev.mysql.com/doc/refman/5.1/en/uninstall-plugin.html). With this change you need to remove skip-federated option from your my.cnf file if you have changed it manually. This option was there by default in previous versions of MySQL. 2) File locations: ================== There were some changes in files locations. Most of them were made in the default configuration file so if you are experiencing problems and you have made some manual adjustments to your /etc/my.cnf, try to merge this file with /etc/my.cnf.rpmnew. File locations changes: - MySQL socket file and pid file were moved from /var/lib/mysql to more reasonable location ( /var/run/mysql ) by default. - MySQL log files are in /var/log/mysql. 3) BerkeleyDB: ============== MySQL no longer contains BerkeleyDB as storage engine. There is no fix for that and if you used it before, you have to migrate your data to different storage engine BEFORE updating. This can be done for example using following command: ALTER TABLE foo ENGINE = INNODB; 4) MySQL Upgrade Log ==================== If you missed messages displayed during automatic MySQL database upgrade, you can find them from now on in /var/log/mysql/mysqld-upgrade.log