legacy-dist is a package that assists (in varying ways) with upgrading from one version of Whonix to another. Currently its main functions are to provide a release upgrade script, and a warning popup letting you know when your version of Whonix has been deprecated and it’s time to update. You can see the package’s code at GitHub - Kicksecure/legacy-dist: Prepare older Build Derivative Versions for Upgrade. (Note: Whonix is based on Kicksecure.)
Strange, but not necessarily alarming depending on your system’s speed (especially since Whonix on Qubes takes a while.
I don’t see this message or a similar message anywhere in the code for Kicksecure, Whonix, or Qubes OS. Is this verbatim what you were shown, or a translation? If a translation, could you share what the message said in its original language? (That will make it easier to find in a code search.) Also, were there any other logs around the message, or was the message itself longer? If so, sharing those logs and the rest of the message may be helpful.
The package isn’t strange, but the symptoms do seem strange. Without more info, it’s hard to tell what may have gone wrong for sure. It sounds vaguely like a qubes-gui-daemon issue to me initially, but since I can’t find the message in the code, I can’t confirm that for sure.
AFAIK, everything should be fine on our end. Kicksecure’s and Whonix’s packages are built in a trusted environment and cryptographically signed, so they shouldn’t be possible to tamper with them without causing apt to reject them.
I confirm that I uploaded the package legacy-dist to all repositories. Its purpose is to assist with release upgrades coming up soon that will be announced separately. For reference:
No user action required at time of writing. News as per usual:
Hello and thank you very much for the information. The legacy file was actually unknown to me.
I have performed the updates in other clones to reproduce the error message once again, as requested. However, this time there were no problems. Therefore, one can probably assume that it was either due to the hardware or the Qubes-Updater (which often causes some problems).
I think the problem is solved now. But I see, I need to take a closer look at some files in the future;-)