NIS does not work with new glibc 2.32 nss_nis is missing. if you configure nis in /etc/nsswitch.conf and use ypbind-2.7.2-3.1 (now in update_testing) ypbind is working correctly, but the maps of ypserver are not use. nss_nis or libnss_nis is needed for nis to work. cf : https://github.com/thkukuk/libnss_nis
cc'ing tmb to have his opinion :)
CC: (none) => geiger.david68210, tmb
with nss_nis-3.1-6.fc33.x86_64.rpm and ypbind-2.7.2-3.1 nis is working and I did not find a bug.
yeah, I suspected we might be missing some nis bits when we switched to new glibc, but I did not dig into all bits as I dont use it and I wasn't sure we had users of it... but as we now have it confirmed we missed some bits, and people need and actually use it, we need to introduce it in Cauldron and mga 8 updates
Thanks for taking this on, Thomas. Excuse me assigning it to you in the light of the previous comment.
Assignee: bugsquad => tmb
Hello, is there some news about nss_nis ? For now I'm using nss_nis-3.1-6.fc33.x86_64.rpm but this is still a bad workaround. Thank you all for the work.
Sorry, I got sidetracked fixing other issues... I've just built: SRPM: nss_nis-3.1-1.mga8.src.rpm i586: libnss_nis2-3.1-1.mga8.i586.rpm x86_64: lib64nss_nis2-3.1-1.mga8.x86_64.rpm please test if it works
I've just tested it. It works fine ! Thanks for all.
(In reply to marco tux4ever from comment #7) > I've just tested it. It works fine ! > Thanks for all. Great to hear and I assume you tested the x86_64 rpm ?
--> and I assume you tested the x86_64 rpm ? : Yes that's it. I didn't have a way to test the i586.rpm.
(In reply to marco tux4ever from comment #9) > --> and I assume you tested the x86_64 rpm ? : > Yes that's it. I didn't have a way to test the i586.rpm. No worries about that, it's just so we know what arch it's tested & known to work on before validating it and pushing to updates
validating based on comment 7 and comment 9.
Whiteboard: (none) => MGA8-64-OKAssignee: tmb => qa-bugsKeywords: (none) => advisory, validated_updateCC: (none) => sysadmin-bugs
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2021-0093.html
Status: NEW => RESOLVEDResolution: (none) => FIXED