Submitting ebuild for current yp-tools version
Steps to Reproduce:
1. download ebuild
2. emerge =yp-tools-4.2.2
Version bump for yp-tools with ebuild rewrite
Supports previous nls flag + adds "static" IUSE
Tested on ~amd64 and ~x86 systems but limited access to/for other archs
Bug 371387 remains open for pervious version
Created attachment 448748 [details]
are you willing to proxy maintain this?
I could proxy maintain this for now. Really need an updated up ypserv to match --current from portage doesn't build.
(In reply to Ted Rodgers from comment #3)
> Really need an updated up ypserv to match --current from portage doesn't build.
While I do agree that it would be really great to have a modern ypserv in Portage, as 2.26 is many years out of date, I do not concur with the assertion "current from Portage doesn't build." I am able to build net-nds/ypserv-2.26-r1 on ~amd64 with GCC 5.4.0 just fine.
Concur current from portage builds. Must have been a problem that new install on my build box fixed.
>>> Source compiled.
>>> net-nds/ypserv-2.26-r1 merged.
CCing proxy maint people
[master 3810c4ac9d8] net-nds/yp-tools: Version bump
2 files changed, 32 insertions(+)
create mode 100644 net-nds/yp-tools/yp-tools-4.2.2.ebuild
This change completely breaks any existing Gentoo installation that runs a complete NIS setup.
The problem is that both ypserv and ypbind in portage are too old to work correctly with the updated yp-tools package.
> # ypwhich
> Error: unsupported version (-1) from ypbind on 'localhost'
A workaround would be to specify version 2:
> # ypwhich -V2
But even this type of kludge still requires changes to the init.d script in net-nds/ypbind
I suggest that either all NIS packages (yp-tools, ypbind and ypserv) are all updated at the same time or the new (and incomaptible) yp-tools is masked for the time being.
Open bug reports asking to bump that packages then
I hope bugs #626050 and #626052 are sufficient for this purpose.