Details
-
Type:
Bug
-
Status: Open
-
Priority:
Critical
-
Resolution: Unresolved
-
Affects Version/s: 10.1
-
Fix Version/s: 10.1
-
Component/s: Packaging, Platform Debian, Tests
-
Labels:None
Description
It's MDEV-5977 all over again, only the next generation of it – new Ubuntu, new MariaDB.
If MariaDB 10.0 is installed, even from MariaDB's own packages, and either vivid-security universe or vivid-updates universe are in the sources.list (which has both normally), installation of 10.1 mariadb-server fails in the same way as it did in MDEV-5977:
- mariadb-server fails to install pointing at mariadb-server-10.1;
- mariadb-server-10.1 fails to install pointing at mariadb-server-core-10.1;
- mariadb-server-core-10.1, if requested explicitly, installs all right and pulls other packages.
That's the reason of Buildbot's upgrade2 failures on Vivid:
http://buildbot.askmonty.org/buildbot/builders/kvm-deb-vivid-amd64/builds/201/steps/test_2/logs/stdio
So, there are two workarounds for the problem:
- disable vivid-security universe and vivid-updates universe to upgrade MariaDB;
- specify mariadb-server-core-10.1 on apt-get install command line.
None of these is good enough when 10.1 goes GA.
Gliffy Diagrams
Attachments
Issue Links
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
For the record, I solved these issues a few days ago in my repo https://github.com/ottok/mariadb/tree/ok-debpkg-10.1 but I cannot open a pull request as the buildbot column is not all green yet. due to test failures that most likely are inherited from failing master 10.1 branch, though I am not sure.
It's possible there is also the 3rd workaround, having 10.0 repo in the source list along with 10.1 (I believe on whatever reason it worked in my experiments), but it will need to be confirmed if we don't have a real solution for the problem. I still hope that we will.