incorrect phasing published in the archive
Whilst phasing https:/
is unset on the package, in the published packages file on all mirrors it is set to zero (Phased-
Package: libnvidia-
Architecture: all
Version: 535.104.
Multi-Arch: foreign
Priority: optional
Section: restricted/libs
Source: nvidia-
Origin: Ubuntu
Maintainer: Ubuntu Core Developers <email address hidden>
Bugs: https:/
Installed-Size: 54
Provides: libnvidia-common
Conflicts: libnvidia-common
Breaks: libnvidia-gl-535 (<< 390.25-0ubuntu2~)
Replaces: libnvidia-common, libnvidia-gl-535 (<< 390.25-0ubuntu2~)
Filename: pool/restricted
Size: 15394
MD5sum: b70771b4c0cfbae
SHA1: e8e6c4512f1d5fd
SHA256: 3d501380d1ccd52
SHA512: d39a471b86684c8
Homepage: http://
Description: Shared files used by the NVIDIA libraries
Description-md5: 259c61ba4e777f5
Phased-
This prevents upgrading to this version as the variable should not be set or be set to 100.
As archive admins have unset phasing already on the binary, and yet publications doesn't refresh it something is wrong.
Can you check if binary package overrides are correctly propagated to apt-ftparchive? Can you fix the ovveride manually, or for example trigger careful publication? Can you please double check that all restricted binaries in all suites for amd64 arm64 i386 architectures do not have phasing set?
This is a customer escalation, and kernel team escalation. I have escalated this to foundations & archive admin teams, who refused to do anything about this.
Question information
- Language:
- English Edit question
- Status:
- Open
- Assignee:
- Simone Pelosi Edit question
- Last query:
- Last reply:
Can you help with this problem?
Provide an answer of your own, or ask Dimitri John Ledkov for more information if necessary.