Rather than implement a new feature via escalation as a bespoke source/origin option for the vaultlocker package, we need to solve vaultlocker's current distribution challenge.
We will do that by releasing vaultlocker in the Queens and Rocky Ubuntu Cloud Archives.
It will then be consumable via offline repos along with the rest of the cloud archive which is already being mirrored offline in the use cases behind this bug.
Rather than implement a new feature via escalation as a bespoke source/origin option for the vaultlocker package, we need to solve vaultlocker's current distribution challenge.
We will do that by releasing vaultlocker in the Queens and Rocky Ubuntu Cloud Archives.
It will then be consumable via offline repos along with the rest of the cloud archive which is already being mirrored offline in the use cases behind this bug.