I added a pinned configuration like below:

Package: cinder*
Pin: version 2:13.0.7*
Pin-Priority: 1001

The version of the package installed is 2:13.0.5-0ubuntu1~cloud0. When I execute the command apt list --upgradable, we can see that the version will be installed.

cinder-common/bionic-updates 2:13.0.8-0ubuntu1~cloud0 all [upgradable from: 2:13.0.5-0ubuntu1~cloud0]

In fact the version is no longer available in the repository. However I don't understand why the system wants to upgrade to version; could someone explain?


A pin defines a priority for packages matching the pin: in your case, packages whose name starts with cinder, and whose version starts with Packages which don’t match the pin, which includes cinder packages with another version, follow any other matching pin, or the default priorities.

Since is no longer in the archives, and isn’t currently installed, there’s no artifact matching the pin, and no artifact given priority 1001. presumably gets the default priority of 500 or 990, and is a legitimate candidate for upgrade; nothing has a higher priority so it ends up being the candidate.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.