| 2023-10-13 13:33:07 |
Thomas Debesse |
bug |
|
|
added bug |
| 2023-10-18 15:05:14 |
Robie Basak |
tags |
amd64 apport-bug mantic package-from-proposed |
amd64 apport-bug mantic package-from-proposed server-todo |
|
| 2023-10-18 15:06:19 |
Robie Basak |
sg3-utils (Ubuntu): assignee |
|
Andreas Hasenack (ahasenack) |
|
| 2023-10-18 17:02:26 |
Andreas Hasenack |
sg3-utils (Ubuntu): status |
New |
Confirmed |
|
| 2023-10-18 17:03:35 |
Andreas Hasenack |
bug |
|
|
added subscriber Andreas Hasenack |
| 2023-10-25 12:31:47 |
Andreas Hasenack |
sg3-utils (Ubuntu): status |
Confirmed |
In Progress |
|
| 2023-10-25 12:48:48 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~ahasenack/ubuntu/+source/sg3-utils/+git/sg3-utils/+merge/454497 |
|
| 2023-10-25 13:29:25 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~ahasenack/ubuntu/+source/sg3-utils/+git/sg3-utils/+merge/454500 |
|
| 2023-10-25 13:42:07 |
Andreas Hasenack |
description |
While upgrading from lunar to mantic dpkg aborted with this error:
```
Preparing to unpack .../libsgutils2-1.46-2_1.46-3ubuntu2_amd64.deb ...
Unpacking libsgutils2-1.46-2:amd64 (1.46-3ubuntu2) ...
dpkg: error processing archive /var/cache/apt/archives/libsgutils2-1.46-2_1.46-3ubuntu2_amd64.deb (--unpack):
trying to overwrite '/usr/lib/x86_64-linux-gnu/libsgutils2-1.46.so.2.0.0', which is also in package libsgutils2-2:amd64 1.46-1ubuntu0.22.04.1
```
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: libsgutils2-2 1.46-1ubuntu0.22.04.1
ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16
Uname: Linux 6.2.0-33-generic x86_64
NonfreeKernelModules: vboxnetadp vboxnetflt vboxdrv amddrm_ttm_helper amdttm amdxcp amddrm_buddy amd_sched amdkcl
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Fri Oct 13 15:29:48 2023
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: sg3-utils
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2018-06-16T17:39:00.798346 |
[ Impact ]
* An explanation of the effects of the bug on users and
* justification for backporting the fix to the stable release.
* In addition, it is helpful, but not required, to include an
explanation of how the upload fixes this bug.
[ Test Plan ]
* detailed instructions how to reproduce the bug
* these should allow someone who is not familiar with the affected
package to reproduce the bug and verify that the updated package fixes
the problem.
* if other testing is appropriate to perform before landing this update,
this should also be described here.
[ Where problems could occur ]
* Think about what the upload changes in the software. Imagine the change is
wrong or breaks something else: how would this show up?
* It is assumed that any SRU candidate patch is well-tested before
upload and has a low overall risk of regression, but it's important
to make the effort to think about what ''could'' happen in the
event of a regression.
* This must '''never''' be "None" or "Low", or entirely an argument as to why
your upload is low risk.
* This both shows the SRU team that the risks have been considered,
and provides guidance to testers in regression-testing the SRU.
[ Other Info ]
* Anything else you think is useful to include
* Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board
* and address these questions in advance
[Original Description]
While upgrading from lunar to mantic dpkg aborted with this error:
```
Preparing to unpack .../libsgutils2-1.46-2_1.46-3ubuntu2_amd64.deb ...
Unpacking libsgutils2-1.46-2:amd64 (1.46-3ubuntu2) ...
dpkg: error processing archive /var/cache/apt/archives/libsgutils2-1.46-2_1.46-3ubuntu2_amd64.deb (--unpack):
trying to overwrite '/usr/lib/x86_64-linux-gnu/libsgutils2-1.46.so.2.0.0', which is also in package libsgutils2-2:amd64 1.46-1ubuntu0.22.04.1
```
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: libsgutils2-2 1.46-1ubuntu0.22.04.1
ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16
Uname: Linux 6.2.0-33-generic x86_64
NonfreeKernelModules: vboxnetadp vboxnetflt vboxdrv amddrm_ttm_helper amdttm amdxcp amddrm_buddy amd_sched amdkcl
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Fri Oct 13 15:29:48 2023
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: sg3-utils
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2018-06-16T17:39:00.798346 |
|
| 2023-10-25 13:47:21 |
Andreas Hasenack |
description |
[ Impact ]
* An explanation of the effects of the bug on users and
* justification for backporting the fix to the stable release.
* In addition, it is helpful, but not required, to include an
explanation of how the upload fixes this bug.
[ Test Plan ]
* detailed instructions how to reproduce the bug
* these should allow someone who is not familiar with the affected
package to reproduce the bug and verify that the updated package fixes
the problem.
* if other testing is appropriate to perform before landing this update,
this should also be described here.
[ Where problems could occur ]
* Think about what the upload changes in the software. Imagine the change is
wrong or breaks something else: how would this show up?
* It is assumed that any SRU candidate patch is well-tested before
upload and has a low overall risk of regression, but it's important
to make the effort to think about what ''could'' happen in the
event of a regression.
* This must '''never''' be "None" or "Low", or entirely an argument as to why
your upload is low risk.
* This both shows the SRU team that the risks have been considered,
and provides guidance to testers in regression-testing the SRU.
[ Other Info ]
* Anything else you think is useful to include
* Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board
* and address these questions in advance
[Original Description]
While upgrading from lunar to mantic dpkg aborted with this error:
```
Preparing to unpack .../libsgutils2-1.46-2_1.46-3ubuntu2_amd64.deb ...
Unpacking libsgutils2-1.46-2:amd64 (1.46-3ubuntu2) ...
dpkg: error processing archive /var/cache/apt/archives/libsgutils2-1.46-2_1.46-3ubuntu2_amd64.deb (--unpack):
trying to overwrite '/usr/lib/x86_64-linux-gnu/libsgutils2-1.46.so.2.0.0', which is also in package libsgutils2-2:amd64 1.46-1ubuntu0.22.04.1
```
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: libsgutils2-2 1.46-1ubuntu0.22.04.1
ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16
Uname: Linux 6.2.0-33-generic x86_64
NonfreeKernelModules: vboxnetadp vboxnetflt vboxdrv amddrm_ttm_helper amdttm amdxcp amddrm_buddy amd_sched amdkcl
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Fri Oct 13 15:29:48 2023
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: sg3-utils
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2018-06-16T17:39:00.798346 |
[ Impact ]
A release upgrade from lunar to mantic, or jammy to mantic when lunar goes EOL, will encounter a file conflict in the libgsutils2 library.
This is what the library package is named, and the library it ships, in each relevant ubuntu release:
Jammy: 1.46-1build1
package: libsgutils2-2
ships: libsgutils2-1.46.so.2 and libsgutils2-1.46.so.2.0.0
Lunar: 1.46-1ubuntu0.23.04.1
package: libsgutils2-2
ships: libsgutils2-1.46.so.2 and libsgutils2-1.46.so.2.0.0
Mantic and Noble: 1.46-3ubuntu2
package: libsgutils2-1.46-2
ships: libsgutils2-1.46.so.2 and libsgutils2-1.46.so.2.0.0
The problem is that in the jammy and lunar versions the file that libgsutils2-2 ships conflicts with mantic, where the package was renamed to libgsutils2-1.46-2.
This update corrects the version of the existing breaks/replaces in the mantic package to avoid this conflict.
Note that, if the upgrade is done with do-release-upgrade, the conflict does not cause an abort, because dpkg is called with --force (see comment #3 down below).
[ Test Plan ]
* detailed instructions how to reproduce the bug
* these should allow someone who is not familiar with the affected
package to reproduce the bug and verify that the updated package fixes
the problem.
* if other testing is appropriate to perform before landing this update,
this should also be described here.
[ Where problems could occur ]
* Think about what the upload changes in the software. Imagine the change is
wrong or breaks something else: how would this show up?
* It is assumed that any SRU candidate patch is well-tested before
upload and has a low overall risk of regression, but it's important
to make the effort to think about what ''could'' happen in the
event of a regression.
* This must '''never''' be "None" or "Low", or entirely an argument as to why
your upload is low risk.
* This both shows the SRU team that the risks have been considered,
and provides guidance to testers in regression-testing the SRU.
[ Other Info ]
* Anything else you think is useful to include
* Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board
* and address these questions in advance
[Original Description]
While upgrading from lunar to mantic dpkg aborted with this error:
```
Preparing to unpack .../libsgutils2-1.46-2_1.46-3ubuntu2_amd64.deb ...
Unpacking libsgutils2-1.46-2:amd64 (1.46-3ubuntu2) ...
dpkg: error processing archive /var/cache/apt/archives/libsgutils2-1.46-2_1.46-3ubuntu2_amd64.deb (--unpack):
trying to overwrite '/usr/lib/x86_64-linux-gnu/libsgutils2-1.46.so.2.0.0', which is also in package libsgutils2-2:amd64 1.46-1ubuntu0.22.04.1
```
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: libsgutils2-2 1.46-1ubuntu0.22.04.1
ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16
Uname: Linux 6.2.0-33-generic x86_64
NonfreeKernelModules: vboxnetadp vboxnetflt vboxdrv amddrm_ttm_helper amdttm amdxcp amddrm_buddy amd_sched amdkcl
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Fri Oct 13 15:29:48 2023
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: sg3-utils
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2018-06-16T17:39:00.798346 |
|
| 2023-10-25 13:47:27 |
Andreas Hasenack |
nominated for series |
|
Ubuntu Noble |
|
| 2023-10-25 13:47:27 |
Andreas Hasenack |
bug task added |
|
sg3-utils (Ubuntu Noble) |
|
| 2023-10-25 13:47:27 |
Andreas Hasenack |
nominated for series |
|
Ubuntu Mantic |
|
| 2023-10-25 13:47:27 |
Andreas Hasenack |
bug task added |
|
sg3-utils (Ubuntu Mantic) |
|
| 2023-10-25 13:47:42 |
Andreas Hasenack |
sg3-utils (Ubuntu Mantic): status |
New |
In Progress |
|
| 2023-10-25 13:47:45 |
Andreas Hasenack |
sg3-utils (Ubuntu Mantic): assignee |
|
Andreas Hasenack (ahasenack) |
|
| 2023-10-30 10:59:05 |
Gordon Lack |
bug |
|
|
added subscriber Gordon Lack |
| 2023-11-03 14:48:25 |
Blain Kristian Stocking |
bug |
|
|
added subscriber Blain Kristian Stocking |
| 2023-11-14 18:21:10 |
Andreas Hasenack |
description |
[ Impact ]
A release upgrade from lunar to mantic, or jammy to mantic when lunar goes EOL, will encounter a file conflict in the libgsutils2 library.
This is what the library package is named, and the library it ships, in each relevant ubuntu release:
Jammy: 1.46-1build1
package: libsgutils2-2
ships: libsgutils2-1.46.so.2 and libsgutils2-1.46.so.2.0.0
Lunar: 1.46-1ubuntu0.23.04.1
package: libsgutils2-2
ships: libsgutils2-1.46.so.2 and libsgutils2-1.46.so.2.0.0
Mantic and Noble: 1.46-3ubuntu2
package: libsgutils2-1.46-2
ships: libsgutils2-1.46.so.2 and libsgutils2-1.46.so.2.0.0
The problem is that in the jammy and lunar versions the file that libgsutils2-2 ships conflicts with mantic, where the package was renamed to libgsutils2-1.46-2.
This update corrects the version of the existing breaks/replaces in the mantic package to avoid this conflict.
Note that, if the upgrade is done with do-release-upgrade, the conflict does not cause an abort, because dpkg is called with --force (see comment #3 down below).
[ Test Plan ]
* detailed instructions how to reproduce the bug
* these should allow someone who is not familiar with the affected
package to reproduce the bug and verify that the updated package fixes
the problem.
* if other testing is appropriate to perform before landing this update,
this should also be described here.
[ Where problems could occur ]
* Think about what the upload changes in the software. Imagine the change is
wrong or breaks something else: how would this show up?
* It is assumed that any SRU candidate patch is well-tested before
upload and has a low overall risk of regression, but it's important
to make the effort to think about what ''could'' happen in the
event of a regression.
* This must '''never''' be "None" or "Low", or entirely an argument as to why
your upload is low risk.
* This both shows the SRU team that the risks have been considered,
and provides guidance to testers in regression-testing the SRU.
[ Other Info ]
* Anything else you think is useful to include
* Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board
* and address these questions in advance
[Original Description]
While upgrading from lunar to mantic dpkg aborted with this error:
```
Preparing to unpack .../libsgutils2-1.46-2_1.46-3ubuntu2_amd64.deb ...
Unpacking libsgutils2-1.46-2:amd64 (1.46-3ubuntu2) ...
dpkg: error processing archive /var/cache/apt/archives/libsgutils2-1.46-2_1.46-3ubuntu2_amd64.deb (--unpack):
trying to overwrite '/usr/lib/x86_64-linux-gnu/libsgutils2-1.46.so.2.0.0', which is also in package libsgutils2-2:amd64 1.46-1ubuntu0.22.04.1
```
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: libsgutils2-2 1.46-1ubuntu0.22.04.1
ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16
Uname: Linux 6.2.0-33-generic x86_64
NonfreeKernelModules: vboxnetadp vboxnetflt vboxdrv amddrm_ttm_helper amdttm amdxcp amddrm_buddy amd_sched amdkcl
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Fri Oct 13 15:29:48 2023
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: sg3-utils
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2018-06-16T17:39:00.798346 |
[ Impact ]
A release upgrade from lunar to mantic, or jammy to mantic when lunar goes EOL, will encounter a file conflict in the libgsutils2 library.
This is what the library package is named, and the library it ships, in each relevant ubuntu release:
Jammy: 1.46-1build1
package: libsgutils2-2
ships: libsgutils2-1.46.so.2 and libsgutils2-1.46.so.2.0.0
Lunar: 1.46-1ubuntu0.23.04.1
package: libsgutils2-2
ships: libsgutils2-1.46.so.2 and libsgutils2-1.46.so.2.0.0
Mantic and Noble: 1.46-3ubuntu2
package: libsgutils2-1.46-2
ships: libsgutils2-1.46.so.2 and libsgutils2-1.46.so.2.0.0
The problem is that in the jammy and lunar versions the file that libgsutils2-2 ships conflicts with mantic, where the package was renamed to libgsutils2-1.46-2.
This update corrects the version of the existing breaks/replaces in the mantic package to avoid this conflict.
Note that, if the upgrade is done with do-release-upgrade, the conflict does not cause an abort, because dpkg is called with --force (see comment #3 down below).
[ Test Plan ]
Perform a release upgrade from lunar to mantic, with mantic-proposed enabled (I'm not yet sure how to have mantic-proposed enabled for do-release-upgrade: I'll come back to this once the package is in proposed). Check the upgrade logs in /var/log/dist-upgrade/apt-term.log and look for the part where libsgutils2 is being unpacked.
For example, this shows the problem:
Preparing to unpack .../125-libsgutils2-1.46-2_1.46-3ubuntu2_amd64.deb ...^M
Unpacking libsgutils2-1.46-2:amd64 (1.46-3ubuntu2) ...^M
dpkg: warning: overriding problem because --force enabled:^M
dpkg: warning: trying to overwrite '/usr/lib/x86_64-linux-gnu/libsgutils2-1.46.so.2.0.0', which is also in package libsgutils2-2:amd64 1.46-1ubuntu0.23.04.1^M
dpkg: warning: overriding problem because --force enabled:^M
dpkg: warning: trying to overwrite '/usr/lib/x86_64-linux-gnu/libsgutils2-1.46.so.2', which is also in package libsgutils2-2:amd64 1.46-1ubuntu0.23.04.1^M
This grep command can also be used:
$ grep "trying to overwrite" /var/log/dist-upgrade/apt-term.log
dpkg: warning: trying to overwrite '/usr/lib/x86_64-linux-gnu/libsgutils2-1.46.so.2.0.0', which is also in package libsgutils2-2:amd64 1.46-1ubuntu0.23.04.1
dpkg: warning: trying to overwrite '/usr/lib/x86_64-linux-gnu/libsgutils2-1.46.so.2', which is also in package libsgutils2-2:amd64 1.46-1ubuntu0.23.04.1
With the fixed version, there will be no such dpkg warning when unpacking libsgutils2 (example with a PPA, since the package is not yet in proposed, but the file to check, and grep command, are the same):
$ grep "trying to overwrite" /var/log/dist-upgrade/apt-term.log
$ # empty result, no hits
Locating the unpacking section in that log, we see that the conflicting package is removed before (took the example from a ppa build):
Removing libsgutils2-2:amd64 (1.46-1ubuntu0.23.04.1) ...^M
Selecting previously unselected package libsgutils2-1.46-2:amd64.^M
(Reading database ... ^M(Reading database ... 5%^M(Reading database ... 10%^M(Reading database ... 15%^M(Reading database ... 20%^M(Reading database ... 25%^M(Reading databas
Preparing to unpack .../libsgutils2-1.46-2_1.46-3ubuntu2.1~ppa3_amd64.deb ...^M
Unpacking libsgutils2-1.46-2:amd64 (1.46-3ubuntu2.1~ppa3) ...^M
[ Where problems could occur ]
Should this package ever get a version bump in an SRU, then the breaks/replaces version might need a bump, which can easily be forgotten. Something similar happened to a samba security update[1] a while ago. Looking at the history of sg3-utils in SRUs, however, shows that such a bump was never done, so it's unlikely. But if it happens, then this bug will resurface.
1. https://bugs.launchpad.net/bugs/2024663
[ Other Info ]
* Anything else you think is useful to include
* Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board
* and address these questions in advance
[Original Description]
While upgrading from lunar to mantic dpkg aborted with this error:
```
Preparing to unpack .../libsgutils2-1.46-2_1.46-3ubuntu2_amd64.deb ...
Unpacking libsgutils2-1.46-2:amd64 (1.46-3ubuntu2) ...
dpkg: error processing archive /var/cache/apt/archives/libsgutils2-1.46-2_1.46-3ubuntu2_amd64.deb (--unpack):
trying to overwrite '/usr/lib/x86_64-linux-gnu/libsgutils2-1.46.so.2.0.0', which is also in package libsgutils2-2:amd64 1.46-1ubuntu0.22.04.1
```
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: libsgutils2-2 1.46-1ubuntu0.22.04.1
ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16
Uname: Linux 6.2.0-33-generic x86_64
NonfreeKernelModules: vboxnetadp vboxnetflt vboxdrv amddrm_ttm_helper amdttm amdxcp amddrm_buddy amd_sched amdkcl
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Fri Oct 13 15:29:48 2023
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: sg3-utils
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2018-06-16T17:39:00.798346 |
|
| 2023-11-14 18:22:12 |
Andreas Hasenack |
description |
[ Impact ]
A release upgrade from lunar to mantic, or jammy to mantic when lunar goes EOL, will encounter a file conflict in the libgsutils2 library.
This is what the library package is named, and the library it ships, in each relevant ubuntu release:
Jammy: 1.46-1build1
package: libsgutils2-2
ships: libsgutils2-1.46.so.2 and libsgutils2-1.46.so.2.0.0
Lunar: 1.46-1ubuntu0.23.04.1
package: libsgutils2-2
ships: libsgutils2-1.46.so.2 and libsgutils2-1.46.so.2.0.0
Mantic and Noble: 1.46-3ubuntu2
package: libsgutils2-1.46-2
ships: libsgutils2-1.46.so.2 and libsgutils2-1.46.so.2.0.0
The problem is that in the jammy and lunar versions the file that libgsutils2-2 ships conflicts with mantic, where the package was renamed to libgsutils2-1.46-2.
This update corrects the version of the existing breaks/replaces in the mantic package to avoid this conflict.
Note that, if the upgrade is done with do-release-upgrade, the conflict does not cause an abort, because dpkg is called with --force (see comment #3 down below).
[ Test Plan ]
Perform a release upgrade from lunar to mantic, with mantic-proposed enabled (I'm not yet sure how to have mantic-proposed enabled for do-release-upgrade: I'll come back to this once the package is in proposed). Check the upgrade logs in /var/log/dist-upgrade/apt-term.log and look for the part where libsgutils2 is being unpacked.
For example, this shows the problem:
Preparing to unpack .../125-libsgutils2-1.46-2_1.46-3ubuntu2_amd64.deb ...^M
Unpacking libsgutils2-1.46-2:amd64 (1.46-3ubuntu2) ...^M
dpkg: warning: overriding problem because --force enabled:^M
dpkg: warning: trying to overwrite '/usr/lib/x86_64-linux-gnu/libsgutils2-1.46.so.2.0.0', which is also in package libsgutils2-2:amd64 1.46-1ubuntu0.23.04.1^M
dpkg: warning: overriding problem because --force enabled:^M
dpkg: warning: trying to overwrite '/usr/lib/x86_64-linux-gnu/libsgutils2-1.46.so.2', which is also in package libsgutils2-2:amd64 1.46-1ubuntu0.23.04.1^M
This grep command can also be used:
$ grep "trying to overwrite" /var/log/dist-upgrade/apt-term.log
dpkg: warning: trying to overwrite '/usr/lib/x86_64-linux-gnu/libsgutils2-1.46.so.2.0.0', which is also in package libsgutils2-2:amd64 1.46-1ubuntu0.23.04.1
dpkg: warning: trying to overwrite '/usr/lib/x86_64-linux-gnu/libsgutils2-1.46.so.2', which is also in package libsgutils2-2:amd64 1.46-1ubuntu0.23.04.1
With the fixed version, there will be no such dpkg warning when unpacking libsgutils2 (example with a PPA, since the package is not yet in proposed, but the file to check, and grep command, are the same):
$ grep "trying to overwrite" /var/log/dist-upgrade/apt-term.log
$ # empty result, no hits
Locating the unpacking section in that log, we see that the conflicting package is removed before (took the example from a ppa build):
Removing libsgutils2-2:amd64 (1.46-1ubuntu0.23.04.1) ...^M
Selecting previously unselected package libsgutils2-1.46-2:amd64.^M
(Reading database ... ^M(Reading database ... 5%^M(Reading database ... 10%^M(Reading database ... 15%^M(Reading database ... 20%^M(Reading database ... 25%^M(Reading databas
Preparing to unpack .../libsgutils2-1.46-2_1.46-3ubuntu2.1~ppa3_amd64.deb ...^M
Unpacking libsgutils2-1.46-2:amd64 (1.46-3ubuntu2.1~ppa3) ...^M
[ Where problems could occur ]
Should this package ever get a version bump in an SRU, then the breaks/replaces version might need a bump, which can easily be forgotten. Something similar happened to a samba security update[1] a while ago. Looking at the history of sg3-utils in SRUs, however, shows that such a bump was never done, so it's unlikely. But if it happens, then this bug will resurface.
1. https://bugs.launchpad.net/bugs/2024663
[ Other Info ]
* Anything else you think is useful to include
* Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board
* and address these questions in advance
[Original Description]
While upgrading from lunar to mantic dpkg aborted with this error:
```
Preparing to unpack .../libsgutils2-1.46-2_1.46-3ubuntu2_amd64.deb ...
Unpacking libsgutils2-1.46-2:amd64 (1.46-3ubuntu2) ...
dpkg: error processing archive /var/cache/apt/archives/libsgutils2-1.46-2_1.46-3ubuntu2_amd64.deb (--unpack):
trying to overwrite '/usr/lib/x86_64-linux-gnu/libsgutils2-1.46.so.2.0.0', which is also in package libsgutils2-2:amd64 1.46-1ubuntu0.22.04.1
```
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: libsgutils2-2 1.46-1ubuntu0.22.04.1
ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16
Uname: Linux 6.2.0-33-generic x86_64
NonfreeKernelModules: vboxnetadp vboxnetflt vboxdrv amddrm_ttm_helper amdttm amdxcp amddrm_buddy amd_sched amdkcl
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Fri Oct 13 15:29:48 2023
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: sg3-utils
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2018-06-16T17:39:00.798346 |
[ Impact ]
A release upgrade from lunar to mantic, or jammy to mantic when lunar goes EOL, will encounter a file conflict in the libgsutils2 library.
This is what the library package is named, and the library it ships, in each relevant ubuntu release:
Jammy: 1.46-1build1
package: libsgutils2-2
ships: libsgutils2-1.46.so.2 and libsgutils2-1.46.so.2.0.0
Lunar: 1.46-1ubuntu0.23.04.1
package: libsgutils2-2
ships: libsgutils2-1.46.so.2 and libsgutils2-1.46.so.2.0.0
Mantic and Noble: 1.46-3ubuntu2
package: libsgutils2-1.46-2
ships: libsgutils2-1.46.so.2 and libsgutils2-1.46.so.2.0.0
The problem is that in the jammy and lunar versions the file that libgsutils2-2 ships conflicts with mantic, where the package was renamed to libgsutils2-1.46-2.
This update corrects the version of the existing breaks/replaces in the mantic package to avoid this conflict.
Note that, if the upgrade is done with do-release-upgrade, the conflict does not cause an abort, because dpkg is called with --force (see comment #3 down below).
[ Test Plan ]
Perform a release upgrade from lunar to mantic, with mantic-proposed enabled (I'm not yet sure how to have mantic-proposed enabled for do-release-upgrade: I'll come back to this once the package is in proposed). Check the upgrade logs in /var/log/dist-upgrade/apt-term.log and look for the part where libsgutils2 is being unpacked.
For example, this shows the problem:
Preparing to unpack .../125-libsgutils2-1.46-2_1.46-3ubuntu2_amd64.deb ...^M
Unpacking libsgutils2-1.46-2:amd64 (1.46-3ubuntu2) ...^M
dpkg: warning: overriding problem because --force enabled:^M
dpkg: warning: trying to overwrite '/usr/lib/x86_64-linux-gnu/libsgutils2-1.46.so.2.0.0', which is also in package libsgutils2-2:amd64 1.46-1ubuntu0.23.04.1^M
dpkg: warning: overriding problem because --force enabled:^M
dpkg: warning: trying to overwrite '/usr/lib/x86_64-linux-gnu/libsgutils2-1.46.so.2', which is also in package libsgutils2-2:amd64 1.46-1ubuntu0.23.04.1^M
This grep command can also be used:
$ grep "trying to overwrite" /var/log/dist-upgrade/apt-term.log
dpkg: warning: trying to overwrite '/usr/lib/x86_64-linux-gnu/libsgutils2-1.46.so.2.0.0', which is also in package libsgutils2-2:amd64 1.46-1ubuntu0.23.04.1
dpkg: warning: trying to overwrite '/usr/lib/x86_64-linux-gnu/libsgutils2-1.46.so.2', which is also in package libsgutils2-2:amd64 1.46-1ubuntu0.23.04.1
With the fixed version, there will be no such dpkg warning when unpacking libsgutils2 (example with a PPA, since the package is not yet in proposed, but the file to check, and grep command, are the same):
$ grep "trying to overwrite" /var/log/dist-upgrade/apt-term.log
$ # empty result, no hits
Locating the unpacking section in that log, we see that the conflicting package is removed before (took the example from a ppa build):
Removing libsgutils2-2:amd64 (1.46-1ubuntu0.23.04.1) ...^M
Selecting previously unselected package libsgutils2-1.46-2:amd64.^M
(Reading database ... ^M(Reading database ... 5%^M(Reading database ... 10%^M(Reading database ... 15%^M(Reading database ... 20%^M(Reading database ... 25%^M(Reading databas
Preparing to unpack .../libsgutils2-1.46-2_1.46-3ubuntu2.1~ppa3_amd64.deb ...^M
Unpacking libsgutils2-1.46-2:amd64 (1.46-3ubuntu2.1~ppa3) ...^M
[ Where problems could occur ]
Should this package ever get a version bump in an SRU, then the breaks/replaces version might need a bump, which can easily be forgotten. Something similar happened to a samba security update[1] a while ago. Looking at the history of sg3-utils in SRUs, however, shows that such a bump was never done, so it's unlikely. But if it happens, then this bug will resurface.
1. https://bugs.launchpad.net/bugs/2024663
[ Other Info ]
N/A
[Original Description]
While upgrading from lunar to mantic dpkg aborted with this error:
```
Preparing to unpack .../libsgutils2-1.46-2_1.46-3ubuntu2_amd64.deb ...
Unpacking libsgutils2-1.46-2:amd64 (1.46-3ubuntu2) ...
dpkg: error processing archive /var/cache/apt/archives/libsgutils2-1.46-2_1.46-3ubuntu2_amd64.deb (--unpack):
trying to overwrite '/usr/lib/x86_64-linux-gnu/libsgutils2-1.46.so.2.0.0', which is also in package libsgutils2-2:amd64 1.46-1ubuntu0.22.04.1
```
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: libsgutils2-2 1.46-1ubuntu0.22.04.1
ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16
Uname: Linux 6.2.0-33-generic x86_64
NonfreeKernelModules: vboxnetadp vboxnetflt vboxdrv amddrm_ttm_helper amdttm amdxcp amddrm_buddy amd_sched amdkcl
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Fri Oct 13 15:29:48 2023
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: sg3-utils
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2018-06-16T17:39:00.798346 |
|
| 2023-11-15 17:36:43 |
Launchpad Janitor |
sg3-utils (Ubuntu Noble): status |
In Progress |
Fix Released |
|
| 2023-11-17 12:26:27 |
Timo Aaltonen |
sg3-utils (Ubuntu Mantic): status |
In Progress |
Fix Committed |
|
| 2023-11-17 12:26:28 |
Timo Aaltonen |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2023-11-17 12:26:29 |
Timo Aaltonen |
bug |
|
|
added subscriber SRU Verification |
| 2023-11-17 12:26:32 |
Timo Aaltonen |
tags |
amd64 apport-bug mantic package-from-proposed server-todo |
amd64 apport-bug mantic package-from-proposed server-todo verification-needed verification-needed-mantic |
|
| 2023-11-21 20:27:13 |
Aleksandr |
attachment added |
|
20231121_221538.jpg https://bugs.launchpad.net/bugs/2039279/+attachment/5721863/+files/20231121_221538.jpg |
|
| 2023-11-27 17:44:56 |
Robin Dupont |
bug |
|
|
added subscriber Robin Dupont |
| 2023-12-06 20:17:19 |
Andreas Hasenack |
description |
[ Impact ]
A release upgrade from lunar to mantic, or jammy to mantic when lunar goes EOL, will encounter a file conflict in the libgsutils2 library.
This is what the library package is named, and the library it ships, in each relevant ubuntu release:
Jammy: 1.46-1build1
package: libsgutils2-2
ships: libsgutils2-1.46.so.2 and libsgutils2-1.46.so.2.0.0
Lunar: 1.46-1ubuntu0.23.04.1
package: libsgutils2-2
ships: libsgutils2-1.46.so.2 and libsgutils2-1.46.so.2.0.0
Mantic and Noble: 1.46-3ubuntu2
package: libsgutils2-1.46-2
ships: libsgutils2-1.46.so.2 and libsgutils2-1.46.so.2.0.0
The problem is that in the jammy and lunar versions the file that libgsutils2-2 ships conflicts with mantic, where the package was renamed to libgsutils2-1.46-2.
This update corrects the version of the existing breaks/replaces in the mantic package to avoid this conflict.
Note that, if the upgrade is done with do-release-upgrade, the conflict does not cause an abort, because dpkg is called with --force (see comment #3 down below).
[ Test Plan ]
Perform a release upgrade from lunar to mantic, with mantic-proposed enabled (I'm not yet sure how to have mantic-proposed enabled for do-release-upgrade: I'll come back to this once the package is in proposed). Check the upgrade logs in /var/log/dist-upgrade/apt-term.log and look for the part where libsgutils2 is being unpacked.
For example, this shows the problem:
Preparing to unpack .../125-libsgutils2-1.46-2_1.46-3ubuntu2_amd64.deb ...^M
Unpacking libsgutils2-1.46-2:amd64 (1.46-3ubuntu2) ...^M
dpkg: warning: overriding problem because --force enabled:^M
dpkg: warning: trying to overwrite '/usr/lib/x86_64-linux-gnu/libsgutils2-1.46.so.2.0.0', which is also in package libsgutils2-2:amd64 1.46-1ubuntu0.23.04.1^M
dpkg: warning: overriding problem because --force enabled:^M
dpkg: warning: trying to overwrite '/usr/lib/x86_64-linux-gnu/libsgutils2-1.46.so.2', which is also in package libsgutils2-2:amd64 1.46-1ubuntu0.23.04.1^M
This grep command can also be used:
$ grep "trying to overwrite" /var/log/dist-upgrade/apt-term.log
dpkg: warning: trying to overwrite '/usr/lib/x86_64-linux-gnu/libsgutils2-1.46.so.2.0.0', which is also in package libsgutils2-2:amd64 1.46-1ubuntu0.23.04.1
dpkg: warning: trying to overwrite '/usr/lib/x86_64-linux-gnu/libsgutils2-1.46.so.2', which is also in package libsgutils2-2:amd64 1.46-1ubuntu0.23.04.1
With the fixed version, there will be no such dpkg warning when unpacking libsgutils2 (example with a PPA, since the package is not yet in proposed, but the file to check, and grep command, are the same):
$ grep "trying to overwrite" /var/log/dist-upgrade/apt-term.log
$ # empty result, no hits
Locating the unpacking section in that log, we see that the conflicting package is removed before (took the example from a ppa build):
Removing libsgutils2-2:amd64 (1.46-1ubuntu0.23.04.1) ...^M
Selecting previously unselected package libsgutils2-1.46-2:amd64.^M
(Reading database ... ^M(Reading database ... 5%^M(Reading database ... 10%^M(Reading database ... 15%^M(Reading database ... 20%^M(Reading database ... 25%^M(Reading databas
Preparing to unpack .../libsgutils2-1.46-2_1.46-3ubuntu2.1~ppa3_amd64.deb ...^M
Unpacking libsgutils2-1.46-2:amd64 (1.46-3ubuntu2.1~ppa3) ...^M
[ Where problems could occur ]
Should this package ever get a version bump in an SRU, then the breaks/replaces version might need a bump, which can easily be forgotten. Something similar happened to a samba security update[1] a while ago. Looking at the history of sg3-utils in SRUs, however, shows that such a bump was never done, so it's unlikely. But if it happens, then this bug will resurface.
1. https://bugs.launchpad.net/bugs/2024663
[ Other Info ]
N/A
[Original Description]
While upgrading from lunar to mantic dpkg aborted with this error:
```
Preparing to unpack .../libsgutils2-1.46-2_1.46-3ubuntu2_amd64.deb ...
Unpacking libsgutils2-1.46-2:amd64 (1.46-3ubuntu2) ...
dpkg: error processing archive /var/cache/apt/archives/libsgutils2-1.46-2_1.46-3ubuntu2_amd64.deb (--unpack):
trying to overwrite '/usr/lib/x86_64-linux-gnu/libsgutils2-1.46.so.2.0.0', which is also in package libsgutils2-2:amd64 1.46-1ubuntu0.22.04.1
```
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: libsgutils2-2 1.46-1ubuntu0.22.04.1
ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16
Uname: Linux 6.2.0-33-generic x86_64
NonfreeKernelModules: vboxnetadp vboxnetflt vboxdrv amddrm_ttm_helper amdttm amdxcp amddrm_buddy amd_sched amdkcl
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Fri Oct 13 15:29:48 2023
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: sg3-utils
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2018-06-16T17:39:00.798346 |
[ Impact ]
A release upgrade from lunar to mantic, or jammy to mantic when lunar goes EOL, will encounter a file conflict in the libgsutils2 library.
This is what the library package is named, and the library it ships, in each relevant ubuntu release:
Jammy: 1.46-1build1
package: libsgutils2-2
ships: libsgutils2-1.46.so.2 and libsgutils2-1.46.so.2.0.0
Lunar: 1.46-1ubuntu0.23.04.1
package: libsgutils2-2
ships: libsgutils2-1.46.so.2 and libsgutils2-1.46.so.2.0.0
Mantic and Noble: 1.46-3ubuntu2
package: libsgutils2-1.46-2
ships: libsgutils2-1.46.so.2 and libsgutils2-1.46.so.2.0.0
The problem is that in the jammy and lunar versions the file that libgsutils2-2 ships conflicts with mantic, where the package was renamed to libgsutils2-1.46-2.
This update corrects the version of the existing breaks/replaces in the mantic package to avoid this conflict.
Note that, if the upgrade is done with do-release-upgrade, the conflict does not cause an abort, because dpkg is called with --force (see comment #3 down below).
[ Test Plan ]
Perform a release upgrade from lunar to mantic, with mantic-proposed enabled (I'm not yet sure how to have mantic-proposed enabled for do-release-upgrade: I'll come back to this once the package is in proposed).
UPDATE: instructions on how to test with the package in mantic-proposed
a) create /etc/apt/sources.list.d/proposed.list with this content (yes, with "lunar-proposed"):
deb http://br.archive.ubuntu.com/ubuntu lunar-proposed main restricted universe multiverse
b) create /etc/apt/preferences.d/sg3-utils with this content:
Package: libsgutils2-1.46-2 sg3-utils sg3-utils-udev libsgutils2-dev
Pin: release a=mantic-proposed
Pin-Priority: 500
c) Run:
sudo do-release-upgrade
Check the upgrade logs in /var/log/dist-upgrade/apt-term.log and look for the part where libsgutils2 is being unpacked.
For example, this shows the problem:
Preparing to unpack .../125-libsgutils2-1.46-2_1.46-3ubuntu2_amd64.deb ...^M
Unpacking libsgutils2-1.46-2:amd64 (1.46-3ubuntu2) ...^M
dpkg: warning: overriding problem because --force enabled:^M
dpkg: warning: trying to overwrite '/usr/lib/x86_64-linux-gnu/libsgutils2-1.46.so.2.0.0', which is also in package libsgutils2-2:amd64 1.46-1ubuntu0.23.04.1^M
dpkg: warning: overriding problem because --force enabled:^M
dpkg: warning: trying to overwrite '/usr/lib/x86_64-linux-gnu/libsgutils2-1.46.so.2', which is also in package libsgutils2-2:amd64 1.46-1ubuntu0.23.04.1^M
This grep command can also be used:
$ grep "trying to overwrite" /var/log/dist-upgrade/apt-term.log
dpkg: warning: trying to overwrite '/usr/lib/x86_64-linux-gnu/libsgutils2-1.46.so.2.0.0', which is also in package libsgutils2-2:amd64 1.46-1ubuntu0.23.04.1
dpkg: warning: trying to overwrite '/usr/lib/x86_64-linux-gnu/libsgutils2-1.46.so.2', which is also in package libsgutils2-2:amd64 1.46-1ubuntu0.23.04.1
With the fixed version, there will be no such dpkg warning when unpacking libsgutils2 (example with a PPA, since the package is not yet in proposed, but the file to check, and grep command, are the same):
$ grep "trying to overwrite" /var/log/dist-upgrade/apt-term.log
$ # empty result, no hits
Locating the unpacking section in that log, we see that the conflicting package is removed before (took the example from a ppa build):
Removing libsgutils2-2:amd64 (1.46-1ubuntu0.23.04.1) ...^M
Selecting previously unselected package libsgutils2-1.46-2:amd64.^M
(Reading database ... ^M(Reading database ... 5%^M(Reading database ... 10%^M(Reading database ... 15%^M(Reading database ... 20%^M(Reading database ... 25%^M(Reading databas
Preparing to unpack .../libsgutils2-1.46-2_1.46-3ubuntu2.1~ppa3_amd64.deb ...^M
Unpacking libsgutils2-1.46-2:amd64 (1.46-3ubuntu2.1~ppa3) ...^M
[ Where problems could occur ]
Should this package ever get a version bump in an SRU, then the breaks/replaces version might need a bump, which can easily be forgotten. Something similar happened to a samba security update[1] a while ago. Looking at the history of sg3-utils in SRUs, however, shows that such a bump was never done, so it's unlikely. But if it happens, then this bug will resurface.
1. https://bugs.launchpad.net/bugs/2024663
[ Other Info ]
N/A
[Original Description]
While upgrading from lunar to mantic dpkg aborted with this error:
```
Preparing to unpack .../libsgutils2-1.46-2_1.46-3ubuntu2_amd64.deb ...
Unpacking libsgutils2-1.46-2:amd64 (1.46-3ubuntu2) ...
dpkg: error processing archive /var/cache/apt/archives/libsgutils2-1.46-2_1.46-3ubuntu2_amd64.deb (--unpack):
trying to overwrite '/usr/lib/x86_64-linux-gnu/libsgutils2-1.46.so.2.0.0', which is also in package libsgutils2-2:amd64 1.46-1ubuntu0.22.04.1
```
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: libsgutils2-2 1.46-1ubuntu0.22.04.1
ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16
Uname: Linux 6.2.0-33-generic x86_64
NonfreeKernelModules: vboxnetadp vboxnetflt vboxdrv amddrm_ttm_helper amdttm amdxcp amddrm_buddy amd_sched amdkcl
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Fri Oct 13 15:29:48 2023
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: sg3-utils
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2018-06-16T17:39:00.798346 |
|
| 2023-12-06 20:21:56 |
Andreas Hasenack |
tags |
amd64 apport-bug mantic package-from-proposed server-todo verification-needed verification-needed-mantic |
amd64 apport-bug mantic package-from-proposed server-todo verification-done-mantic verification-needed |
|
| 2023-12-12 17:34:56 |
Launchpad Janitor |
sg3-utils (Ubuntu Mantic): status |
Fix Committed |
Fix Released |
|
| 2023-12-12 17:34:59 |
Brian Murray |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
