Comment 5 for bug 1813442

I think that from an error, another unpredicted error can be derived.

I would first notify landscape-server to let the administrator decide about this scenario, take responsibility for it and give the admin some choices:
- Bypass the package
- Try to install at any cost (we would take the description and, in general, many of the fields with a default value if we can not read them from the package)
- Mark the package not to upgrade
- Uninstall this package to avoid this situation in the future
- Some other?

As a first version, we can bypass the broken package, make landscape-client keep going, and notify in the logs.
This would be a temporal solution not to prevent the system from upgrading until a final scenario is decided.