package mariadb-common 1:10.6.7-2ubuntu1 failed to install/upgrade: installed mariadb-common package post-installation script subprocess returned error exit status 2

Bug #1970536 reported by Russel Santos
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
mariadb-10.6 (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

The following packages were automatically installed and are no longer required:
  libconfig-inifiles-perl libdbd-mysql-perl libdbi-perl libmariadb3
  libmysqlclient21 libterm-readkey-perl mariadb-client-core-10.6
  mariadb-common mysql-common
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
  mariadb-client-10.6*
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
3 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] Y
Setting up mariadb-common (1:10.6.7-2ubuntu1) ...
update-alternatives: error: alternative path /etc/mysql/mariadb.cnf doesn't exist
dpkg: error processing package mariadb-common (--configure):
 installed mariadb-common package post-installation script subprocess returned error exit status 2
dpkg: dependency problems prevent configuration of mariadb-client-core-10.6:
 mariadb-client-core-10.6 depends on mariadb-common (>= 1:10.6.7-2ubuntu1); howe
ver:
  Package mariadb-common is not configured yet.

dpkg: error processing package mariadb-client-core-10.6 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libmariadb3:amd64:
 libmariadb3:amd64 depends on mariadb-common; however:
  Package mariadb-common is not configured yet.

dpkg: error processing package libmariadb3:amd64 (--configure):
 dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup erro
r from a previous failure.
                          No apport report written because the error message ind
icates its a followup error from a previous failure.
                                                    Errors were encountered whil
e processing:
 mariadb-common
 mariadb-client-core-10.6
 libmariadb3:amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: mariadb-common 1:10.6.7-2ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
Date: Wed Apr 27 14:02:51 2022
Dependencies: mysql-common 5.8+1.0.8
ErrorMessage: installed mariadb-common package post-installation script subprocess returned error exit status 2
InstallationDate: Installed on 2022-04-22 (4 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
PackageArchitecture: all
Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2
 apt 2.4.5
SourcePackage: mariadb-10.6
Title: package mariadb-common 1:10.6.7-2ubuntu1 failed to install/upgrade: installed mariadb-common package post-installation script subprocess returned error exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.mysql.mariadb.cnf: [deleted]

Revision history for this message
Russel Santos (rgsantos) wrote :
Revision history for this message
Faustin (fauust) wrote :

Hi Russel,
thanks for your report and your help making Ubuntu better.

Without more information, I can not try to reproduce this.
At least I need to understand the context:
- which version of ubuntu are you upgrading?
- which version of mariadb are you upgrading?

Regards.

Changed in mariadb-10.6 (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for mariadb-10.6 (Ubuntu) because there has been no activity for 60 days.]

Changed in mariadb-10.6 (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.