Upstream has released MariaDB 10.1.25 on July 4: https://mariadb.com/kb/en/mariadb/mariadb-10125-release-notes/ It may or may not fix security issues that'll be announced later. We should update it either way.
Whiteboard: (none) => MGA6TOO
Assigning to the registered maintainer, but CC'ing all packagers collectively, in case the maintainer is unavailable.
CC: (none) => marja11, pkg-bugsAssignee: bugsquad => alien
perl-libintl-perl needs to be rebuilt in Cauldron before I can build this update.
CC: (none) => alienAssignee: alien => mageia
(In reply to David Walser from comment #2) > perl-libintl-perl needs to be rebuilt in Cauldron before I can build this > update. Now that's fixed, but now there's: perl-File-HomeDir-1.2.0-1.mga7.noarch (due to unsatisfied perl(Mac::SystemDirectory)[>= 0.40.0])
CC: (none) => shlomif, thierry.vignaud
"Mac::SystemDirectory - Locate Mac OS X Standard System Directories" i don't know if we need this deps or just need to be filtered out
I've synced File::HomeDir's exclude list with FC. It should be OK in ~15mn
Updated package uploaded for Mageia 6 and Cauldron. Advisory: ---------------------------------------- This is a maintenance and bugfix release that upgrades MariaDB to the latest 10.1.25 version which resolves various upstream bugs. References: https://mariadb.com/kb/en/mariadb/mariadb-10125-release-notes/ https://mariadb.com/kb/en/mariadb-10125-changelog/ ---------------------------------------- Updated packages in core/updates_testing: ---------------------------------------- mariadb-10.1.25-1.mga6 mysql-MariaDB-10.1.25-1.mga6 mariadb-cassandra-10.1.25-1.mga6 mariadb-feedback-10.1.25-1.mga6 mariadb-connect-10.1.25-1.mga6 mariadb-sphinx-10.1.25-1.mga6 mariadb-mroonga-10.1.25-1.mga6 mariadb-sequence-10.1.25-1.mga6 mariadb-spider-10.1.25-1.mga6 mariadb-extra-10.1.25-1.mga6 mariadb-obsolete-10.1.25-1.mga6 mariadb-core-10.1.25-1.mga6 mariadb-common-core-10.1.25-1.mga6 mariadb-common-10.1.25-1.mga6 mariadb-client-10.1.25-1.mga6 mariadb-bench-10.1.25-1.mga6 libmariadb18-10.1.25-1.mga6 libmariadb-devel-10.1.25-1.mga6 libmariadb-embedded18-10.1.25-1.mga6 libmariadb-embedded-devel-10.1.25-1.mga6 from mariadb-10.1.25-1.mga6.src.rpm
CC: (none) => mageiaAssignee: mageia => qa-bugsVersion: Cauldron => 6Whiteboard: MGA6TOO => (none)
MGA6-32 on Asus A6000VM MATE No installation issues Ref to bug 20917 for testing procedure, but at CLI after starting mysqld: # mysqladmin -u root password New password: Confirm new password: mysqladmin: You cannot use 'password' command as mysqld runs with grant tables disabled (was started with --skip-grant-tables). Use: "mysqladmin flush-privileges password '*'" instead [root@mach6 ~]# mysqladmin flush-privileges password New password: Confirm new password: mysqladmin: You cannot use 'password' command as mysqld runs with grant tables disabled (was started with --skip-grant-tables). Use: "mysqladmin flush-privileges password '*'" instead Googling brought me this: # mysql_secure_installation NOTE: RUNNING ALL PARTS OF THIS SCRIPT IS RECOMMENDED FOR ALL MariaDB SERVERS IN PRODUCTION USE! PLEASE READ EACH STEP CAREFULLY! In order to log into MariaDB to secure it, we'll need the current password for the root user. If you've just installed MariaDB, and you haven't set the root password yet, the password will be blank, so you should just press enter here. Enter current password for root (enter for none): OK, successfully used password, moving on... Setting the root password ensures that nobody can log into the MariaDB root user without the proper authorisation. Set root password? [Y/n] y New password: Re-enter new password: Password updated successfully! Reloading privilege tables.. ... Success! By default, a MariaDB installation has an anonymous user, allowing anyone to log into MariaDB without having to have a user account created for them. This is intended only for testing, and to make the installation go a bit smoother. You should remove them before moving into a production environment. Remove anonymous users? [Y/n] n ... skipping. Normally, root should only be allowed to connect from 'localhost'. This ensures that someone cannot guess at the root password from the network. Disallow root login remotely? [Y/n] y ... Success! By default, MariaDB comes with a database named 'test' that anyone can access. This is also intended only for testing, and should be removed before moving into a production environment. Remove test database and access to it? [Y/n] n ... skipping. Reloading the privilege tables will ensure that all changes made so far will take effect immediately. Reload privilege tables now? [Y/n] ... Success! Cleaning up... All done! If you've completed all of the above steps, your MariaDB installation should now be secure. Thanks for using MariaDB! Note that at the first demand for root password, just press enter, otherwise you end up in Connection refused. Thereafter I could login with phpadmin, connect as root with the newly defined database and create a new database and a new table within.
Whiteboard: (none) => MGA6-32-OKCC: (none) => herman.viaene
Whiteboard: MGA6-32-OK => advisory MGA6-32-OK
Validating under the temorary policy of accepting just 1 OK; for which thanks yet again to Herman!
Keywords: (none) => validated_updateCC: (none) => lewyssmith, sysadmin-bugs
An update for this issue has been pushed to the Mageia Updates repository. http://advisories.mageia.org/MGAA-2017-0039.html
Resolution: (none) => FIXEDStatus: NEW => RESOLVED