We don't ship a xen-upstream package in Ubuntu, which makes me believe that you probably have third-party repositories enabled, or maybe built a Xen package manually. If that's indeed the case, then this is an unsupported scenario where bad interactions between official and non-official Ubuntu packages are likely to happen. In the interest of being thorough, I fired up a VM, installed xen-hypervisor-amd64, removed "xen libxen*", and then tried reinstalling xen-hypervisor-amd64. I could not reproduce the problem you're having.
Since there is not enough information in your report to begin triage or to
differentiate between a local configuration problem and a bug in Ubuntu, I
am marking this bug as "Incomplete". We would be grateful if you would:
provide a more complete description of the problem, explain why you
believe this is a bug in Ubuntu rather than a problem specific to your
system, and then change the bug status back to "New".
Thank you for taking the time to file a bug report.
On your DpkgHistoryLog.txt file, I see the following:
Start-Date: 2023-03-21 17:45:55
Commandline: apt-get remove xen-upstream
Requested-By: hovan (1000)
Remove: xen-upstream:amd64 (4.17.0)
End-Date: 2023-03-21 17:45:55
We don't ship a xen-upstream package in Ubuntu, which makes me believe that you probably have third-party repositories enabled, or maybe built a Xen package manually. If that's indeed the case, then this is an unsupported scenario where bad interactions between official and non-official Ubuntu packages are likely to happen. In the interest of being thorough, I fired up a VM, installed xen-hypervisor- amd64, removed "xen libxen*", and then tried reinstalling xen-hypervisor- amd64. I could not reproduce the problem you're having.
Since there is not enough information in your report to begin triage or to
differentiate between a local configuration problem and a bug in Ubuntu, I
am marking this bug as "Incomplete". We would be grateful if you would:
provide a more complete description of the problem, explain why you
believe this is a bug in Ubuntu rather than a problem specific to your
system, and then change the bug status back to "New".
For local configuration issues, you can find assistance here: www.ubuntu. com/support/ community
http://