package ubuntu-business-defaults 39 failed to install/upgrade

[Fernando Sanchez]

""Configurando ubuntu-business-defaults (39) ...
/var/lib/dpkg/info/ubuntu-business-defaults.postinst: línea 9: update-gconf-defaults: orden no encontrada
dpkg: error al procesar el paquete ubuntu-business-defaults (--configure):
 el subproceso instalado paquete ubuntu-business-defaults script post-installation devolvió el código de salida de error 127
Se encontraron errores al procesar:
 ubuntu-business-defaults
E: Sub-process /usr/bin/dpkg returned an error code (1)""

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: ubuntu-business-defaults 39
ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
AptOrdering:
 ispell:amd64: Install
 ienglish-common:amd64: Install
 iamerican:amd64: Install
 ubuntu-business-defaults:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: pass
Date: Tue Mar 19 18:08:58 2024
ErrorMessage: el subproceso instalado paquete ubuntu-business-defaults script post-installation devolvió el código de salida de error 127
InstallationDate: Installed on 2024-03-19 (0 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2)
PackageArchitecture: all
Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.3
 apt 2.4.11
SourcePackage: ubuntu-business-defaults
Title: package ubuntu-business-defaults 39 failed to install/upgrade: el subproceso instalado paquete ubuntu-business-defaults script post-installation devolvió el código de salida de error 127
UpgradeStatus: No upgrade log present (probably fresh install)

[Sudip Mukherjee (sudipmuk)]

I can reproduce the issue in Jammy, Mantic and Noble.

[Sudip Mukherjee (sudipmuk)]

Looks like this will need "update-gconf-defaults" from "gconf2" but that is not available in Mantic and Noble.

[Sudip Mukherjee (sudipmuk)]

Sadly I will have to unassign myself and move it back to Confirmed state.

SRU rules say that the development release should be fixed first. But in this case, even though Noble and Mantic are affected, since gconf2 is not available so there is no way to add it to runtime dependency to fix it.

I can not fix only Jammy, because the fixed package version in Jammy will be 39ubuntu0.1 but Mantic and Noble will still have the version 39 so any upgrade from Jammy to Mantic or Noble will fail.

The problem is coming from ubuntu-defaults-builder at: https://git.launchpad.net/ubuntu/+source/ubuntu-defaults-builder/tree/debhelper-scripts/postinst-ubuntu2d-launchers#n4

Only possible fix is to port the ubuntu-defaults-builder code to use gsettings instead of gconf2.