Of course, there are not the dependencies missing, it does just not find the packages, although they seem to b eexistent.

As the live-build process is downloading aslo from mirrors, please be so kind and check, if the sync to the mirrors were working correctly, too.
In the past I already got the same issue, which was caused by a bad sync of the repos. Just an idea...

after looking at the build.log, it appears it's related to this issue https://bugs.kali.org/view.php?id=9853. openssh-client conflicts with openssh-client-gssapi

Might be, but if you take a closer look, you see, that a lot of packages are also involved and lots of packages can not be found.
I will try to find a workaround for the openssh-ciient problem, however, I believe(!), this is not the only cause for the issue.
After testing, I will be back again.

Tried some things now. Sadly did not work. I suppose, I have to wait, until the openssh-client bug is fixed if there is no other solution.

Look at the link i shared for the issue i submitted, my fix was installing openssh-client-gssapi package FIRST, then install everything else and it worked. I had to do it manually though during the install

your build log shows that this specific package conflict may be the problem

E: Unable to satisfy dependencies. Reached two conflicting assignments:
   1. kali-linux-core:amd64=2026.3.2 is selected for install
   2. kali-linux-core:amd64 Depends kali-system-core
      but none of the choices are installable:
      - kali-system-core:amd64 Depends openssh-client-gssapi
        but none of the choices are installable:
        - openssh-client-gssapi:amd64 is not selected for install because:
          1. openssh-client:amd64=1:10.4p1-4 is selected for install
          2. openssh-client-gssapi:amd64 Conflicts openssh-client

the rest of the stuff you mentioned i believe is a result of this one thing.

I read both reports. This one here and the one related to openssh-client.
For the native installed kali this was no problem and I used the solution you mentioned already.

However, for building a kali-live, this is sadly technical not possible, as it wants to install packages in a strict order. Of course, it is possible to remove packages AFTER the build process (which I for exaple do with
the not workiing package "gdm3", where is already a bug report existent to), but in the case of openssh-client, this does not work.

In the meantime I could already see, that openssh-client is related to a bunch of other packages.

Thus, as I already wrote, I have to wait until the openssh-client issue will be fixed.

Maybe we could merge these two bugreports?

Best regards

Hans

Kali-live can now be build again. Looks like the openssh-client issze (https://bugs.kali.org/view.php?id=9853) is solved.
Small reason, big impact. :)

IMHO this bug report can safely be closed.

Thank you very much for all the help!

Best regards

Hans

This is fixed with the latest version 2026.3.4 of kali-system-core, which just landed in kali-rolling.

The issue is that, in Debian, GSS-API support was moved out of the OpenSSH package, into the package openssh-client-gssapi, and as a result this package gained a Breaks relationship with package openssh-client. That broke Kali because we wanted to install openssh-client-gssapi, but during a complete system installation (like net install) or live build, there's alway something that pulls in the openssh-client as well. And it's not possible anymore to install both openssh-client and openssh-client-gssapi at the same time. So kali-system-core now depends on openssh-client.

That said, if users still need support for GSS-API for some reason, they can still install openssh-client-gssapi manually: that will work, and the package will replace openssh-client.

Thanks for the report, and sorry for the disruption.