Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 29 Jan 2008 06:16:21 +0000
From:      "N.J. Mann" <njm@njm.f2s.com>
To:        freebsd-ports@freebsd.org
Cc:        dougb@freebsd.org
Subject:   portmaster: upgrade failed for security/sudo
Message-ID:  <20080129061621.GA40834@oberon.njm.f2s.com>

next in thread | raw e-mail | index | archive | help
Good morning,


I am using portmaster v2.0 and very good it is to, except...

This morning among the ports that needed updating following my
over-night CVSup was security/sudo (1.6.9.6 -> 1.6.9.12).  I am using
portmaster's new feature SU_CMD.  I am also using the new HIDE_BUILD
feature which I really like!  All went well until the install phase,
when portmaster could no longer find sudo.  It looks like portmaster got
into a chicken and egg situation: it needed to uninstall sudo in order
to complete the upgrade, but it needed to run sudo to perform the actual
install.  Oh, dear.

The solution to my failed upgrade was to cd into security/sudo and do a
make install which installed the new sudo fine.  I was then able to
re-run portmaster to upgrade the other ports which were out of date.

More details:

Tail of portmaster output during upgrade attempt:

===>>> Installation of sudo-1.6.9.12 (security/sudo) failed
===>>> Aborting update

===>>> Update for sudo-1.6.9.6 failed
===>>> Aborting update

Tail of sudo upgrade log:

cc -shared  .libs/sudo_noexec.o   -Wl,-soname -Wl,sudo_noexec.so -o .libs/sudo_noexec.so
creating sudo_noexec.la
(cd .libs && rm -f sudo_noexec.la && ln -s ../sudo_noexec.la sudo_noexec.la)
eval: /usr/local/bin/sudo: not found


Cheers,
       Nick.
-- 




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080129061621.GA40834>