Comment 66 for bug 2027716

@Andreas I cannot use your setup-dc script as I am running a live instance of samba as an AD-DC in a real existing network and I use the bind DLZ backend not samba internal, and that script uses samba internal. I also am not sure if that script is viable for users who use the resolvconf system service.

For installing the update, I always use aptitude because it provides realtime feedback on if a proposed package change will cause any dependency problems and suggests conflict resolutions, and will revert a proposed package update request if it will result in broken dependencies. I altered the line in /etc/apt/sources.list for main to say jammy-proposed instead of jammy, ran aptitude, looked for samba, told it to update, then went in and did the suggested resolution to fix every conflict that caused, one of which required uninstalling ctdb since there was no corresponding update package for ctdb but it was dependent on the old version of samba-libs whereas all the other packages I was updating depended on the new version. I am wondering if the fact that I did not uninstall ctdb first in a separate aptitude session first, then do the samba package update, may have contributed to the problem, or the fact that samba was running at the time of the update and did not like something about my setup perhaps, but my setup is not particularly complicated as I am not a Samba or package apt package management expert and do not want to break our entire AD setup by running the wrong command or something.

I hope that explanation helps somehow.