The handling of a failed package installed in text mode is currently completely backwards in tl-setup. It refuses to continue for optional packages, and gladly proceeds for non-optional packages. This should of course be the other way around.
This bug has been around since the beginning as far as I can tell.
Tested on a Fedora 34 machine without Python ldap installed.
This was done by writing a `sys.exit(1)` to /opt/thinlinc/libexec/dnfhelper after the resolve step when tl-setup installs Python ldap.
- 4.12.1: tl-setup exits even though the package is optional.
- Jenkins server build #2244: tl-setup lets us continue without ldap.
Marking as closed.