"getwd cache" was removed but the removal is not listed in WHATSNEW and the option is still listed in libgpo/admx/samba.admx. Both should get fixed for the final release.
Created attachment 19195 [details] Patch
Attached find a patch for mentioning the removed parameter in WHATSNEW. To be honest, I need assistance how to remove the file from both the English as well as the Russian admx files. I could of course edit the text by hand, but I have no clue about the internal structure of the (what looks to me like) XML, so I really don't know if I would leave correct XML behind.
git blame?
This bug was referenced in samba v4-25-test: fc973f7fac40bb20118ea61a958a888de08ab26c
git blame points at cb994befb0c89c8a, which does not give me enough hints towards how to recreate the files using the group management console in Windows. Is this a release blocker?
I meant git blame to find the assistance person mainly. It would be really good to get deleted parameters out of out gpo file for new .0 releases (but it's not strictly a blocker...)
Hi, David! Do you remember how you created the admx files? Can you either tell me how to do that or recreate them? Thanks, Volker
(In reply to Volker Lendecke from comment #7) I used ADMX Migrator. It's a legacy Windows tool. You used to be able to download it from the Microsoft website. Looks like you can still find it on archive sites. I ran it in Wine, and it worked just fine.
Thanks David.
This problem is much larger. libgpo/admx is basically unmaintained, but in theory should follow smb.conf. For example git grep "ldap ssl ads" shows the same, but it also shows that this is still referenced in a different manpage.
Next one: In addition to libgpo/admx/en-US/samba.adml, which I would dare to keep up to date. However I don't speak Russian, so I would not feel confident maintaining that one.
Just some thoughts: Isn't this a typical case for maintaining i18n with gettext here? It isn't easy for us to keep the English version up-to-date, it seems to be a really bad idea to try to maintain another version in a different language. Or maybe we should just drop the translation, I'm not sure if it's worth the hassle. Having outdated and diverging files here is definetely the worst option.
This bug was referenced in samba v4-25-stable (Release samba-4.25.0): fc973f7fac40bb20118ea61a958a888de08ab26c