I could update successfully. But now every time I run apt upgrade it prompts to update again the 1325 packages I just upgraded. I already upgraded twice and stills says there are 1325 packages to upgrade.
Anyone else with this problem?
1 Like
Try installing dpkg from the proposed pocket:
sudo apt install dpkg/questing-proposed
1 Like
Update successful on Ubuntu 26.04 Resolute. No problem with subsequent update
corrado@corrado-n6-rr-1022:~$ echo 'APT::Architecture-Variants "amd64v3";' | sudo tee /etc/apt/apt.conf.d/99enable-amd64v3
sudo apt update
sudo apt upgrade
APT::Architecture-Variants "amd64v3";
Hit:1 http://security.ubuntu.com/ubuntu resolute-security InRelease
Hit:2 http://archive.ubuntu.com/ubuntu resolute InRelease
Hit:3 http://archive.ubuntu.com/ubuntu resolute-updates InRelease
Hit:4 http://archive.ubuntu.com/ubuntu resolute-backports InRelease
Get:5 http://archive.ubuntu.com/ubuntu resolute/main amd64v3 Packages [1,465 kB]
Get:6 http://archive.ubuntu.com/ubuntu resolute/restricted amd64v3 Packages [65.3 kB]
Get:7 http://archive.ubuntu.com/ubuntu resolute/universe amd64v3 Packages [15.6 MB]
Get:8 http://archive.ubuntu.com/ubuntu resolute/multiverse amd64v3 Packages [282 kB]
Fetched 17.4 MB in 3s (6,060 kB/s)
1083 packages can be upgraded. Run 'apt list --upgradable' to see them.
1 Like
Upgrade done and working. List of faced issues:
1st Problem: âapt upgradeâ failed in the middle of its run because of a problem with âlibgphoto2-6t64_2.5.31-4build1_amd64v3â package:
Preparando para desempaquetar .../038-libgphoto2-6t64_2.5.31-4build1_amd64v3.deb ...
Desempaquetando libgphoto2-6t64:amd64 (2.5.31-4build1) sobre (2.5.31-4build1) ...
dpkg: error al procesar el archivo /tmp/user/0/apt-dpkg-install-wtTjOL/038-libgphoto2-6t64_2.5.31-4build1_amd64v3.deb (--unpack):
intentando sobreescribir el compartido `/usr/share/doc/libgphoto2-6t64/changelog.Debian.gz', que es distinto de otras instancias del paquetes libgphoto2-6t64:amd64
/tmp/user/0/apt-dpkg-install-wtTjOL/038-libgphoto2-6t64_2.5.31-4build1_amd64v3.deb
I need to manually download the amd64v3 .deb package to install it with --force-all option and then rerun apt upgrade.
I think this is the problem: comparative of the .deb files âlibgphoto2-6t64_2.5.31-4build1_amd64.debâ and âlibgphoto2-6t64_2.5.31-4build1_amd64v3.debâ:
These are different filesâŠ
2nd problem: several packages shown as locally installed. This is the list of my current affected packages:
bind9 libssh mutter rmlint samba xorg-server xwayland
All of these packages have in common that amd64v3 builds failed. For instance, this is xwayland current situation:
I donât know if the packages in this situation will be updated with amd64 arch (a fallback) or will be just omitted. In any case I think that itâs a dangerous situation.
3rd Problem: apt-file doesnât work. It gives this error:
# apt-file search xwayland
Finding relevant cache files to search ...E: No Contents in the cache with the given restrictions
4th Problem: some message issued in every âapt updateâ with an external ppa like this one:
Notice: Skipping acquire of configured file 'main/binary-amd64v3/Packages' as repository 'https://packages.mozilla.org/apt mozilla InRelease' doesn't support architecture 'amd64v3'
I solved the problem upgrading with aptitude instead of apt. I think dpkg was not upgraded due to phasing.
Thanks for all these reports!
So what I think has happened here (and similar for the librsvg2-common issue other people have reported) is that you have libgphoto2-6t64:i386 installed and because of how we did the amd64v3 builds this was built a long time before the amd64v3 package and for some reason the changelog compressed differently. This wonât be a problem in 26.04 because we will rebuild all packages in the usual way and this wonât happen again.
What are you doing to show whether a package is locally installed or not? I guess we will need to pay special attention when SRUing / security fixing any packages in questing. For 26.04 again this should not be a problem as amd64v3 will be more fully supported.
This is something we need to look at. We do actually have amd64v3 Contents files but I guess apt-file needs to be taught how to be interpret them properly.
This message just means apt is falling back to the amd64 Packages. It should not be displayed at the default verbosity level, weâll fix that.
5 Likes
@mwhudson , thanks for answering.
I use this command:
#apt list --installed | grep local]
bind9-dnsutils/now 1:9.20.11-1ubuntu2.1 amd64 [installed,local]
bind9-host/now 1:9.20.11-1ubuntu2.1 amd64 [installed,local]
bind9-libs/now 1:9.20.11-1ubuntu2.1 amd64 [installed,local]
gir1.2-mutter-17/now 49.0-2ubuntu5 amd64 [installed,local]
libdvdcss2/now 1.5.0-1~local amd64 [installed,local]
libldb2/now 2:2.11.0+samba4.22.3+dfsg-4ubuntu2.1 amd64 [installed,local]
libmutter-17-0/now 49.0-2ubuntu5 amd64 [installed,local]
libsmbclient0/now 2:4.22.3+dfsg-4ubuntu2.1 amd64 [installed,local]
libssh-4/now 0.11.2-1ubuntu0.1 amd64 [installed,local]
libtalloc2/now 2:2.4.3+samba4.22.3+dfsg-4ubuntu2.1 amd64 [installed,local]
libtdb1/now 2:1.4.13+samba4.22.3+dfsg-4ubuntu2.1 amd64 [installed,local]
libtevent0t64/now 2:0.16.2+samba4.22.3+dfsg-4ubuntu2.1 amd64 [installed,local]
libwbclient0/now 2:4.22.3+dfsg-4ubuntu2.1 amd64 [installed,local]
mutter-common-bin/now 49.0-2ubuntu5 amd64 [installed,local]
rmlint/now 2.10.2-0.2ubuntu1 amd64 [installed,local]
samba-common-bin/now 2:4.22.3+dfsg-4ubuntu2.1 amd64 [installed,local]
samba-libs/now 2:4.22.3+dfsg-4ubuntu2.1 amd64 [installed,local]
winbind/now 2:4.22.3+dfsg-4ubuntu2.1 amd64 [installed,local]
xserver-xorg-core/now 2:21.1.18-1ubuntu1.1 amd64 [installed,local]
xwayland/now 2:24.1.6-1ubuntu1.1 amd64 [installed,local]
My concern is that this package situation where the package exists for amd64 but is broken for amd64v3, as apt detected it as locally installed I think apt omits the existence of the amd64 package in the repository. So, it probably will be not updated at all in this situation and, personally, I prefer that it will be update to amd64 than nothing so it may fallback.
1 Like
Works fine on a VM, otherwise got this:
Errors were encountered while processing:
/tmp/apt-dpkg-install-WYwJP1/455-libgphoto2-6t64_2.5.31-4build1_amd64v3.deb
/tmp/apt-dpkg-install-WYwJP1/745-librsvg2-common_2.60.0+dfsg-1build1_amd64v3.deb
Upgrading now in my main machine, since my ADHD requires constant flow of new, shiny things.
1 Like
I opened a separate issue
My system doesnât update anymore, just hangs.
OK, I have temporary fixed the issueâŠ
step 1, disable the file /etc/apt/apt.conf.d/50command-not-found so apt update will work.
sudo mv /etc/apt/apt.conf.d/50command-not-found /etc/apt/apt.conf.d/50command-not-found.disabled
step2: disable amd64v3:
sudo mv /etc/apt/apt.conf.d/99enable-amd64v3 /etc/apt/apt.conf.d/99enable-amd64v3.disabled
step3:
apt list --upgradable > /tmp/upgradable.txt
step4:
liviu@bobdenaut:/etc/apt$ grep -E 'apt|dpkg|libapt' /tmp/upgradable.txt
apt/questing 3.1.6ubuntu2 amd64 [upgradable from: 3.1.6ubuntu2]
dpkg/questing-updates 1.22.21ubuntu3.1 amd64 [upgradable from: 1.22.21ubuntu3.1]
libapt-pkg7.0/questing 3.1.6ubuntu2 amd64 [upgradable from: 3.1.6ubuntu2]
libfreeaptx0/questing 0.2.2-1 amd64 [upgradable from: 0.2.2-1]
libraptor2-0/questing 2.0.16-6 amd64 [upgradable from: 2.0.16-6]
python3-apt/questing 3.0.0ubuntu1 amd64 [upgradable from: 3.0.0ubuntu1]
So, as we can see, amd64v3 modifies :
- apt/questing
- dpkg/questing-updates
- libapt-pkg7.0/questing
- libfreeaptx0/questing
- libraptor2-0/questing
- python3-apt/questing
so, somewhere is a problem
For 26.04 can I specify the variant when I install? I think it would be very useful.
Otherwise I think there will be few of us testing the new architecture.
1 Like
I ran into similar issue during the packages upgrade to amd64v3 packages:
dpkg: error processing archive /var/cache/apt/archives/libgphoto2-6t64_2.5.31-4build1_amd64v3.deb (--unpack):
trying to overwrite shared '/usr/share/doc/libgphoto2-6t64/changelog.Debian.gz', which is different from other instances of package libgphoto2-6t64:amd64
Errors were encountered while processing:
/var/cache/apt/archives/libgphoto2-6t64_2.5.31-4build1_amd64v3.deb
Error: Sub-process /usr/bin/dpkg returned an error code (1)
Removing the file /usr/share/doc/libgphoto2-6t64/changelog.Debian.gz resolved the issue.
1 Like
The example shows how to set it for amd64v3 but does it also work for v2 and v4 supported CPUs?
No, there are only amd64 and amd64v3 packages.
If you have a v2 CPU you have to use amd64.
If you have a v3 or v4 CPU you can use amd64v3.
Iâm confused, for a completely new install on bare metal, how will this be implemented? Will there be options in the opening screen to pick one? Will there be a test button for users who have no idea what a v1 v2 v3 etc is? Or perhaps a subroutine which will run first and decide for you?
I can foresee lots of pain for lots of people who have no idea what they are doing, and that is the majority of new users.
I enabled amd64v3 on 25.10 and it updated ~1,000 packages or so. Now Iâm curious which packages I have installed with the amd64v3 variant, but I canât seem to find an easy way to get a list? I can see it for a specific package like this:
markus@pc ~ $ apt-cache policy bash
bash:
Installed: 5.2.37-2ubuntu5
Candidate: 5.2.37-2ubuntu5
Version table:
*** 5.2.37-2ubuntu5 500
500 http://mirror.arizona.edu/ubuntu questing/main amd64v3 Packages
100 /var/lib/dpkg/status
But if I use something like apt list --installed, it just says amd64 whether they are amd64 or amd64v3:
markus@pc ~ $ apt list --installed | grep bash/questing
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
bash/questing,now 5.2.37-2ubuntu5 amd64 [installed]
I would have thought apt list --installed would have specified amd64v3 but alas, it does not.
So is there a way to get a list of all installed packages that are of the amd64v3 variant?
It should be a nice addition to apt list to have that option.
I saw that the âArchitecture-Variant: amd64v3â is shown in the command âapt showâ so I use a command like this (not very tested and not reliable at all) to list all amd64v3 installed packages:
apt show `dpkg --get-selections | cut -f 1` | grep -e Package: -e Architecture-Variant: | tr '\n' ' ' | sed 's/Package: /\n/g' | sed 's/Architecture-Variant://g' | grep amd64v3
Thanks! That certainly helps but I donât think it catches everything. I have Plasma/KDE installed from the kubuntu-backports PPA and the output of your command does not list any Plasma related packages at all. Actually apt-cache gives me something I donât understand:
markus@pc ~ $ apt-cache policy plasma-session-wayland
plasma-session-wayland:
Installed: 4:6.5.1-0ubuntu1~ubuntu25.10~ppa1
Candidate: 4:6.5.1-0ubuntu1~ubuntu25.10~ppa1
Version table:
*** 4:6.5.1-0ubuntu1~ubuntu25.10~ppa1 100
100 /var/lib/dpkg/status
4:6.5.0-0ubuntu1~ubuntu25.10~ppa1 500
500 https://ppa.launchpadcontent.net/kubuntu-ppa/backports/ubuntu questing/main amd64v3 Packages
4:6.4.5-0ubuntu4 500
500 http://mirror.arizona.edu/ubuntu questing/universe amd64v3 Packages
So I have 6.5.1 installed and it must have come from the kubuntu-backports PPA, but it just says /var/lib/dpkg/status? I tried some other Plasma packages from the PPA and they all say /var/lib/dpkg/status and none show up in the output from your apt show command even though they should be amd64v3.
The command uses âapt showâ not âapt-cacheâ. In the case of âplasma-session-waylandâ itâs still amd64 (not amd64v3) in 25.10 Questing as you can check here:
https://launchpad.net/ubuntu/+source/plasma-workspace
Indeed, Itâs amd64v3 for 26.04 Resolute. I donât know why it wasnât converted for current release yet.
Also the package from kubuntu-backports PPA is still amd64. You can check it here:
I donât think that there will be many PPAs that uses amd64v3 yet.
1 Like