Hrm ??
This updated lvm2 migrated to -release with the field: Recommends: thin-provisioning-tools
But I have not seen an update here that it was promoted and it really seems not in main yet:
root@e:~# apt-cache policy thin-provisioning-tools thin-provisioning-tools: Candidate: 0.7.6-2.1ubuntu1 Version table: 0.7.6-2.1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu eoan/universe amd64 Packages
root@e:~# apt-cache policy lvm2 lvm2: Candidate: 2.03.02-2ubuntu6 Version table: 2.03.02-2ubuntu6 500 500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages
I'm missing something, shouldn't that be a component mismatch that triggers the handling of this MIR?
Hrm ??
This updated lvm2 migrated to -release ng-tools
with the field:
Recommends: thin-provisioni
But I have not seen an update here that it was promoted and it really seems not in main yet:
root@e:~# apt-cache policy thin-provisioni ng-tools ng-tools: 7.6-2.1ubuntu1 500 archive. ubuntu. com/ubuntu eoan/universe amd64 Packages
thin-provisioni
Candidate: 0.7.6-2.1ubuntu1
Version table:
0.
500 http://
root@e:~# apt-cache policy lvm2 03.02-2ubuntu6 500 archive. ubuntu. com/ubuntu eoan/main amd64 Packages
lvm2:
Candidate: 2.03.02-2ubuntu6
Version table:
2.
500 http://
I'm missing something, shouldn't that be a component mismatch that triggers the handling of this MIR?