thanks for the quick reply and the bugfix.
it seems the new internal su-stuff makes openpkg much easier to handle
than in the old versions. thanks to that, there is no need to install
sudo at all, since i just needed sudo to call "openpkg build" as
managing user with the -P option. good job!
andi
Ralf S. Engelschall schrieb:
On Fri, Dec 21, 2007, Andreas Schmidt wrote:
it's quite a while since i had to setup a new openpkg instance.
my old bootstrap scripts (written for openpkg 2.5) fail, but i can't
see, what has changed since then and how to do things now. hope someone
can can give me an hint:
(1) the regular bootstrap works like a charm; since "openpkg build" is
now part of the core, no need to download any rpms anymore.
(2) next i try to install the sudo package as root with
openpkg build -N "-su - OPKGUSR -c" sudo | sh
back in 2.5 this worked fine; with CURRENT i run into several problems:
- although i call this as root, i'm forced to enter a password for user
OPKGUSR; before i never gave my managing users a password; instead i su
from root; now i have to define one and enter the password multiple
times within this call, which is very annoying; especially if you make a
typo and have to start all over again.
No, you are not su(1)'ing from root as the "openpkg" frontend switches
the UID according to the command and "openpkg build" already uses the
command of option -N for running its "openpkg rpm" query commands.
Usually you no longer need the -N option of "openpkg build". The
"openpkg" frontend does already "the right thing" for you.
- the generated shell script of openpkg build has syntax-errors; it
misses line-breaks after the ending quotes of the "su" commands
This certainly is a buglet in the build program. But as I said, one
today no longer uses the -N feature at all today, so instead of fixing
it I guess we should just remove -N at all.
- adding these linebreaks by hand and calling the script starts the
download and build of sudo; unfortunately the build exits with an linker
error:
cc -o sudo check.o env.o getspwuid.o gettime.o goodpath.o fileops.o
find_path.o interfaces.o logging.o parse.o set_perms.o sudo.o
sudo_edit.o tgetpass.o zero_bytes.o sudo_auth.o passwd.o sudo.tab.o
lex.yy.o alloc.o defaults.o strlcpy.o strlcat.o closefrom.o
-L/opt/svn/lib -lfsl -lnsl -lpam -ldl -lcrypt
/usr/bin/ld: cannot find -lpam
i have no pam installed on my debian 3.1 box. this had not been a
problem with 2.5; and since with_pam defaults to no i would expect
sudo to work without pam too.
Yes, this was a bug in the latest sudo configure script.
We need an explicit --without-pam now. Now fixed.
any chance to install openpkg / sudo on my box?
Sure, just manually perform the "openpkg rpm --rebuild" and "openpkg rpm
-Uvh" command to install "sudo" or even just use "openpkg build" without
option -N, please. For non-privileged commands the "openpkg" frontend
automatically switches to your the OpenPKG instance management user...
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
OpenPKG http://openpkg.org
User Communication List openpkg-users@openpkg.org
______________________________________________________________________
OpenPKG http://openpkg.org
User Communication List openpkg-users@openpkg.org
