Bug #595838 resulted in a major upgrade to yp-tools. Unfortunately that version is not compatible with the old version of ypbind and as a result this leaves Gentoo installations with broken NIS implementations. I suggest that either all NIS packages (yp-tools, ypbind and ypserv) are updated at the same time or the new (and incompatible) yp-tools is masked for the time being.
Upstream lists 2.4 as the current version: http://www.linux-nis.org/nis/ypbind-mt
And this needs a new library :S
Created attachment 486678 [details] ypbind-2.4.ebuild
Created attachment 486680 [details, diff] ypbind-2.4-systemd.patch
newer yp-tools went to stable because of glibc stabilization... and this is without maintainer and hard to bump... I would treeclean it then
The current version of ypbind and ypserv in the tree are perfectly fine if we bring back yp-tools 2.x. They don't need to be punted. We only needed an update to yp-tools 2.14 to build against current glibc. All that is required is to resurrect (and rename) the 2.12 ebuild and adjust SRC_URI to point to the new homepage.
Created attachment 513578 [details, diff] ypbind-2.4-systemd.patch @Pacho: Could you explain why you say this package is "hard to bump"? With a small fix in your systemd patch to support GCC 7 (by which "#if FOO" is invalid if FOO is undefined), your ypbind-2.4.ebuild builds fine on my system (USE=-systemd).
Created attachment 514024 [details, diff] Corrected patch file I was able to build and install with the ebuild attached to this bug, but the patch needed a tweak to work correctly without systemd. I also needed to copy the three files: /usr/portage/net-nds/ypbind/files/{ypbind.confd-r1,ypbind.initd,ypbind.service} since I am building this from /usr/local/portage. Of course, I also had to add a line to /etc/portage/package.unmask/package.unmask =net-nds/ypbind-2.4 I see no reason not to put this in portage and unmask it, but I'm not an expert on such things. As it is now, Gentoo simply doesn't work with NIS, which isn't really a good answer.
I'm running ypbind-2.4 with yp-tools-4.2.2-r1, and I'm not seeing any problems with the version differences between the two, so the version differences shouldn't be a blocking issue.
(In reply to Preston Crow from comment #9) > I'm running ypbind-2.4 with yp-tools-4.2.2-r1, and I'm not seeing any > problems with the version differences between the two, so the version > differences shouldn't be a blocking issue. Well, those versions will work together, as they both support ypbind protocol V3. The only version incompatibility is self-inflicted by Gentoo's decision to package yp-tools-4.x together with ypbind-1.x (the latter does not support protocol V3).
(In reply to Preston Crow from comment #8) > Created attachment 514024 [details, diff] [details, diff] > Corrected patch file > > I was able to build and install with the ebuild attached to this bug, but > the patch needed a tweak to work correctly without systemd. You forgot to call AC_SUBST(USE_SD_NOTIFY) in the "else" case of your AS_IF. Please see my corrected patch (attachment 513578 [details, diff]) for a version that handles this properly.
The new version of ypbind would also solve bug # 637502. If a proxy maintainer is needed to expedite this, I could step in.
CCing them then (for the three affected packages, that need to be coordinated)
Removed from the tree
