Package Base Details: mysql

Git Clone URL: https://aur.archlinux.org/mysql.git (read-only, click to copy)
Submitter: Barthalion
Maintainer: Muflone
Last Packager: Muflone
Votes: 81
Popularity: 0.82
First Submitted: 2013-04-25 19:13 (UTC)
Last Updated: 2023-11-15 01:11 (UTC)

Pinned Comments

Muflone commented on 2023-08-16 17:21 (UTC) (edited on 2023-08-16 20:41 (UTC) by Muflone)

Warning

https://dev.mysql.com/doc/refman/8.1/en/downgrading.html

Downgrade from MySQL 8.1 to MySQL 8.0 or earlier is not supported. The only supported alternative is to restore a backup taken before upgrading. It is therefore imperative that you back up your data before starting the upgrade process.

MySQL 8.0 is available in https://aur.archlinux.org/packages/mysql80

Latest Comments

« First ‹ Previous 1 .. 11 12 13 14 15 16 17 18 19 Next › Last »

lucc commented on 2015-07-30 13:23 (UTC)

Is it possible that the upstream website does not support the https links in the PKGBUILD? I had trouble opening the website or downloading the tarball until I removed the "s".

Muflone commented on 2014-12-23 23:04 (UTC)

@nicolascevallos use pactree (and pactree -r) to discover why your installation requires you to install mysql-connector-c. The forum is the best way to try to solve your issues. I cannot help you as the issue doesn't seem related in any way to any of my packages.

nicolascevallos commented on 2014-12-23 17:59 (UTC)

Muflone, thanks for your response. I downloaded the last shared component in a rpm file from http://dev.mysql.com/downloads/mysql/ and I see that the file of libmysqlclient.so is libmysqlclient.so.18.1.0 and it is different from the last version of Connector/C (libmysqlclient) package in http://dev.mysql.com/downloads/connector/c/ As in my last message of mysql-connector-c package, I don't know why mysql-connector-c need an update if it's not installed :( And I don't understand why mysql-connector-c needs libmariadbclient/libmysqlclient. Please, notify me if I can do something to help! :)

Muflone commented on 2014-12-23 16:02 (UTC)

Indeed the package mysql is out of date, a new 5.6.22 version was released a couple of days ago [1]. I'll update this package very soon after a short test. However about the conflicting files there's nothing that I can do. The package libmysqlclient provides the libmysqlclient library, and the mysql-connector-c packages provides its copy of libmysqlclient, then the two packages conflicts. I think the mysql-connector-c package shouldn't provide its copy of the libmysqlclient library or if it must have such version, then it should be installed in a dedicated folder. Obviously the same applies also to all the other similar conflicting files. The final option would be that mysql-connector-c applies a conflicts options in the PKGBUILD to avoid conflicting files and then avoiding that both mysql and mysql-connector-c would be installed together. [1] http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-22.html

nicolascevallos commented on 2014-12-22 23:17 (UTC)

The last changes in this package causes an update in mysql-connector-c, even if is not installed. The installation of mysql-connector-c causes an error because any files exists in the file system, such as /usr/bin/perror, /usr/bin/my_config and /usr/lib/libmysqlclient* links. I hack the problem renaming the filenames in conflict and the package mysql-connector-c compiles the libmysqlclient.so.18.3.0, when the package libmysqlclient compiles the libmysqlclient.so.18.1.0 !!! This package is out of date?

Muflone commented on 2014-11-28 17:43 (UTC)

Package updated to version 5.6.21

Muflone commented on 2014-11-17 10:29 (UTC)

@sparse you should download the source again, the checksum is correct to me

sparse commented on 2014-11-17 07:45 (UTC)

Validating source files with sha256sums... mysql-5.6.20.tar.gz ... FAILED mysqld-post.sh ... Passed mysqld-tmpfile.conf ... Passed mysqld.service ... Passed mysql-srv_buf_size.patch ... Passed

Muflone commented on 2014-11-12 12:34 (UTC)

Please discuss the whole thing in the ML https://lists.archlinux.org/pipermail/aur-general/2014-November/029798.html I'm open to suggest but actually I'm not convinced the issue should be searched in this package, built with the same no-rtti flag as the mariadb-clients