After do-release-upgrade to lunar finishes, we confirm the bug is ther:
$ grep "trying to overwrite" /var/log/dist-upgrade/apt-term.log -B 2
Unpacking winbind (2:4.17.7+dfsg-1ubuntu2) over (2:4.16.8+dfsg-0ubuntu1.2) ...
dpkg: warning: overriding problem because --force enabled:
dpkg: warning: trying to overwrite '/usr/share/man/man8/idmap_rfc2307.8.gz', which is also in package samba-libs:amd64 2:4.16.8+dfsg-0ubuntu1.2
dpkg: warning: overriding problem because --force enabled:
dpkg: warning: trying to overwrite '/usr/share/man/man8/idmap_script.8.gz', which is also in package samba 2:4.16.8+dfsg-0ubuntu1.2
We can also see this used the non-proposed samba packages from lunar: 2:4.17.7+dfsg-1ubuntu2
Repeating the process now, but with proposed enabled:
Confirmed lunar-proposed was used by do-release-upgrade:
Checking for installed snaps
Note this will get not just samba from lunar-proposed, but whatever else is there. It's deemed ok for this SRU verification. A better test would be to enable lunar-proposed and pin only the samba packages.
After do-release-upgrade --allow-third-party is finished, there are messages about "trying to overwrite", like before:
ubuntu@k-samba-2024663:~$ grep "trying to overwrite" /var/log/dist-upgrade/apt-term.log -B 2
ubuntu@k-samba-2024663:~$
And winbind was unpacked just fine:
ubuntu@k-samba-2024663:~$ grep "Unpacking winbind" /var/log/dist-upgrade/apt-term.log -4
Unpacking samba (2:4.17.7+dfsg-1ubuntu2.2) over (2:4.16.8+dfsg-0ubuntu1.2) ...
Preparing to unpack .../18-samba-libs_2%3a4.17.7+dfsg-1ubuntu2.2_amd64.deb ...
Unpacking samba-libs:amd64 (2:4.17.7+dfsg-1ubuntu2.2) over (2:4.16.8+dfsg-0ubuntu1.2) ...
Preparing to unpack .../19-winbind_2%3a4.17.7+dfsg-1ubuntu2.2_amd64.deb ...
Unpacking winbind (2:4.17.7+dfsg-1ubuntu2.2) over (2:4.16.8+dfsg-0ubuntu1.2) ...
Preparing to unpack .../20-samba-common-bin_2%3a4.17.7+dfsg-1ubuntu2.2_amd64.deb ...
Unpacking samba-common-bin (2:4.17.7+dfsg-1ubuntu2.2) over (2:4.16.8+dfsg-0ubuntu1.2) ...
Preparing to unpack .../21-samba-vfs-modules_2%3a4.17.7+dfsg-1ubuntu2.2_amd64.deb ...
Unpacking samba-vfs-modules:amd64 (2:4.17.7+dfsg-1ubuntu2.2) over (2:4.16.8+dfsg-0ubuntu1.2) ...
And finally, we can see that the lunar-proposed version was used: 2:4.17.7+dfsg-1ubuntu2.2
Lunar verification
Reproducing the bug. Starting on kinetic with:
ubuntu@ k-samba- 2024663: ~$ apt-cache policy samba-libs 8+dfsg- 0ubuntu1. 2 8+dfsg- 0ubuntu1. 2 8+dfsg- 0ubuntu1. 2 500 br.archive. ubuntu. com/ubuntu kinetic- updates/ main amd64 Packages br.archive. ubuntu. com/ubuntu kinetic- security/ main amd64 Packages dpkg/status
samba-libs:
Installed: 2:4.16.
Candidate: 2:4.16.
Version table:
*** 2:4.16.
500 http://
500 http://
100 /var/lib/
After do-release-upgrade to lunar finishes, we confirm the bug is ther: dist-upgrade/ apt-term. log -B 2 7+dfsg- 1ubuntu2) over (2:4.16. 8+dfsg- 0ubuntu1. 2) ... man/man8/ idmap_rfc2307. 8.gz', which is also in package samba-libs:amd64 2:4.16. 8+dfsg- 0ubuntu1. 2 man/man8/ idmap_script. 8.gz', which is also in package samba 2:4.16. 8+dfsg- 0ubuntu1. 2
$ grep "trying to overwrite" /var/log/
Unpacking winbind (2:4.17.
dpkg: warning: overriding problem because --force enabled:
dpkg: warning: trying to overwrite '/usr/share/
dpkg: warning: overriding problem because --force enabled:
dpkg: warning: trying to overwrite '/usr/share/
We can also see this used the non-proposed samba packages from lunar: 2:4.17. 7+dfsg- 1ubuntu2
Repeating the process now, but with proposed enabled:
Confirmed lunar-proposed was used by do-release-upgrade:
Checking for installed snaps
Calculating snap size requirements
Updating repository information br.archive. ubuntu. com/ubuntu lunar InRelease [267 kB] br.archive. ubuntu. com/ubuntu lunar-proposed InRelease [255 kB] br.archive. ubuntu. com/ubuntu lunar-updates InRelease [109 kB] br.archive. ubuntu. com/ubuntu lunar-backports InRelease [99.8 kB] br.archive. ubuntu. com/ubuntu lunar-security InRelease [109 kB]
Get:1 http://
Get:2 http://
Get:3 http://
Get:4 http://
Get:5 http://
(...)
Note this will get not just samba from lunar-proposed, but whatever else is there. It's deemed ok for this SRU verification. A better test would be to enable lunar-proposed and pin only the samba packages.
After do-release-upgrade --allow-third-party is finished, there are messages about "trying to overwrite", like before:
ubuntu@ k-samba- 2024663: ~$ grep "trying to overwrite" /var/log/ dist-upgrade/ apt-term. log -B 2 k-samba- 2024663: ~$
ubuntu@
And winbind was unpacked just fine: k-samba- 2024663: ~$ grep "Unpacking winbind" /var/log/ dist-upgrade/ apt-term. log -4 7+dfsg- 1ubuntu2. 2) over (2:4.16. 8+dfsg- 0ubuntu1. 2) ... samba-libs_ 2%3a4.17. 7+dfsg- 1ubuntu2. 2_amd64. deb ... 7+dfsg- 1ubuntu2. 2) over (2:4.16. 8+dfsg- 0ubuntu1. 2) ... winbind_ 2%3a4.17. 7+dfsg- 1ubuntu2. 2_amd64. deb ... 7+dfsg- 1ubuntu2. 2) over (2:4.16. 8+dfsg- 0ubuntu1. 2) ... samba-common- bin_2%3a4. 17.7+dfsg- 1ubuntu2. 2_amd64. deb ... 7+dfsg- 1ubuntu2. 2) over (2:4.16. 8+dfsg- 0ubuntu1. 2) ... samba-vfs- modules_ 2%3a4.17. 7+dfsg- 1ubuntu2. 2_amd64. deb ... modules: amd64 (2:4.17. 7+dfsg- 1ubuntu2. 2) over (2:4.16. 8+dfsg- 0ubuntu1. 2) ...
ubuntu@
Unpacking samba (2:4.17.
Preparing to unpack .../18-
Unpacking samba-libs:amd64 (2:4.17.
Preparing to unpack .../19-
Unpacking winbind (2:4.17.
Preparing to unpack .../20-
Unpacking samba-common-bin (2:4.17.
Preparing to unpack .../21-
Unpacking samba-vfs-
And finally, we can see that the lunar-proposed version was used: 2:4.17. 7+dfsg- 1ubuntu2. 2
Lunar verification succeeded.