[Kolab-devel] [issue1708] Openpkg install fails because kolab user's shell is /bin/false
Gunnar Wrobel
wrobel at pardus.de
Thu May 3 17:23:26 CEST 2007
Graeme Mathieson <kolab-issues at intevation.de> writes:
> New submission from Graeme Mathieson <mathie at rubaidh.com>:
>
> I'm just trying out Kolab 2.1-rc2 on a freshly built Ubuntu 7.04 install. It
> successfully installs openpkg itself, but fails to build or install any of the
> kolab packages or dependencies.
>
> Tracking it down a bit further, I discovered that the line:
>
> su "${BUILDUSER}" -c "${BUILDEXEC}" | tee /tmp/${PRG}-${PKG}.rebuild.log
>
> (in the @rebuild function of the obmtool script) was doing nothing. It turns
> out that ${BUILDUSER} is set to kolab, and that kolab's shell is /bin/false.
> When su is used in this manner, it runs the command passed through the user's
> default shell which, being /bin/false, silently does nothing but exit with a
> status code of 1.
>
> Two solutions:
>
> * Set the kolab user's shell to /kolab/lib/openpkg/bash. This is the solution I
> chose because it was, well, the easiest one. :-)
I thought this happens by default. At least I have this in my
/etc/passwd and I don't think I modified it.
But maybe setting it to /bin/false would be a safer option anyhow.
--
____ http://www.pardus.de _________________ http://gunnarwrobel.de _
>> Mail at ease - Rent a kolab groupware server at p at rdus <<
p at rdus Kolab work is funded in part by KDAB and the Kolab Konsortium
More information about the devel
mailing list