package libsgutils2-1.46-2 (not installed) failed to install/upgrade: tentata sovrascrittura di "/usr/lib/x86_64-linux-gnu/libsgutils2-1.46.so.2.0.0" presente anche nel pacchetto libsgutils2-2:amd64 1.46-1ubuntu0.22.04.1

[igi]

Happened on wmWare virtual machine (24.04 Daily build).

ProblemType: Package
DistroRelease: Ubuntu 24.04
Package: libsgutils2-1.46-2 (not installed)
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: pass
Date: Sat Nov 4 16:57:15 2023
ErrorMessage: tentata sovrascrittura di "/usr/lib/x86_64-linux-gnu/libsgutils2-1.46.so.2.0.0" presente anche nel pacchetto libsgutils2-2:amd64 1.46-1ubuntu0.22.04.1
InstallationDate: Installed on 2022-04-21 (570 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.22.0ubuntu1
 apt 2.7.3
SourcePackage: sg3-utils
Title: package libsgutils2-1.46-2 (not installed) failed to install/upgrade: tentata sovrascrittura di "/usr/lib/x86_64-linux-gnu/libsgutils2-1.46.so.2.0.0" presente anche nel pacchetto libsgutils2-2:amd64 1.46-1ubuntu0.22.04.1
UpgradeStatus: No upgrade log present (probably fresh install)

[Athos Ribeiro (athos-ribeiro)]

Thanks for reporting this bug!

This happens because of the strict breaks/replaces relation set in the package.

For context, libsgutils2-2 has been renamed to libsgutils2-1.46-2 from mantic and on.

Back then, the greatest version number of libsgutils2-2 in the archive was 1.46-1build1. We then added a delta to change the Debian's break/replaces relation to 1.46-1build1.

SRUs have been released for this package. Now, the version (in the -updates pocket) for jammy and lunar are 1.46-1ubuntu0.22.04.1 and 1.46-1ubuntu0.23.04.1, respectively.

Now, we should support the following upgrade paths: jammy->noble, lunar->mantic - both are currently broken.

While this could be done by replacing the breaks/replaces in noble and mantic (each with the proper version to support the upgrade path) if we consider that upgrade paths for systems without the -updates pocket enabled are unsupported, I wonder if we want to loosen the breaks/replaces relation here, otherwise, future SRUs to jammy/lunar would require SRUs to noble(once it is released)/mantic.

[Lucas Kanashiro (lucaskanashiro)]

Thanks Igor for reporting the bug and Athos for triaging it.

This is an interesting corner case that we did not consider when releasing this SRU. This is a good case to keep in mind for futures SRUs in general, existence of a very strict version constraint (=) in a breaks/replace statement.

I think the best solution here is updating the version constraint in Mantic and Noble to '>= 1.46-1build1', which will avoid this breakage in future SRUs. I tried to think in some corner cases that could prove this is not a good fix, but I was not able to identify any.

[Robie Basak (racb)]

I'm not sure I follow why a strict version B/R was added in the first place. Wouldn't '<< 1.46-3~' be better, and follow the usual pattern? Is there something I'm missing as to why this wasn't done this way in the first place?