Re: NSS library dependencies

2002-12-19 Thread Grant Bowman
* Sami Haahtinen <[EMAIL PROTECTED]> [021217 15:13]: > On Tue, Dec 17, 2002 at 10:43:27AM -0600, Steve Langasek wrote: > > What information are you trying to store in LDAP that is so essential to > > the system prior to mounting of /usr? > > > > It is entirely valid for /usr to be located on a net

Re: NSS library dependencies

2002-12-19 Thread Grant Bowman
* Sami Haahtinen <[EMAIL PROTECTED]> [021217 15:13]: > On Tue, Dec 17, 2002 at 10:43:27AM -0600, Steve Langasek wrote: > > What information are you trying to store in LDAP that is so essential to > > the system prior to mounting of /usr? > > > > It is entirely valid for /usr to be located on a net

Re: postinst and debconf again

2002-12-19 Thread pp
Colin Watson <[EMAIL PROTECTED]> wrote: > On Thu, Dec 19, 2002 at 05:50:21PM +0100, pp wrote: > > I made > > db_reset midgard/error > > #added > > db_input "medium" midgard/error > > #changed from high > > db_go > > db_get midgard/error > > > > now works (even if it is not good) ;) > > If that'

Re: postinst and debconf again

2002-12-19 Thread Colin Watson
On Thu, Dec 19, 2002 at 05:50:21PM +0100, pp wrote: > I made > db_reset midgard/error > #added > db_input "medium" midgard/error > #changed from high > db_go > db_get midgard/error > > now works (even if it is not good) ;) If that's in debian/config, it's likely to be actively bad. When preconfi

Re: postinst and debconf again

2002-12-19 Thread Steve Langasek
On Thu, Dec 19, 2002 at 05:50:21PM +0100, pp wrote: > I made > db_reset midgard/error > #added > db_input "medium" midgard/error > #changed from high > db_go > db_get midgard/error > now works (even if it is not good) ;) The 'db_get' at the end is probably unnecessary, if all you're doing is dis

Re: postinst and debconf again

2002-12-19 Thread Colin Watson
On Thu, Dec 19, 2002 at 04:43:33PM +0100, pp wrote: > Steve Langasek <[EMAIL PROTECTED]> wrote: > > You're missing a '|| true' after the prompt for midgard/error. The > > question is being skipped by debconf, probably because it's been shown > > before, and this results in a different return code.

Re: postinst and debconf again

2002-12-19 Thread Colin Watson
On Thu, Dec 19, 2002 at 03:45:14PM +0100, pp wrote: > Colin Watson <[EMAIL PROTECTED]> wrote: > > On Thu, Dec 19, 2002 at 02:58:11PM +0100, pp wrote: > > > if $mysqlcmd -D mysql -e 'use midgard;' >/dev/null 2>&1 ; then > > > > > > db_input "high" midgard/error > > > > db_input can return

Re: postinst and debconf again

2002-12-19 Thread pp
Steve Langasek <[EMAIL PROTECTED]> wrote: > > > > db_input "high" midgard/error > > db_go > > db_stop > > You're missing a '|| true' after the prompt for midgard/error. The > question is being skipped by debconf, probably because it's been shown > before, and this resul

Re: postinst and debconf again

2002-12-19 Thread pp
Colin Watson <[EMAIL PROTECTED]> wrote: > On Thu, Dec 19, 2002 at 05:50:21PM +0100, pp wrote: > > I made > > db_reset midgard/error > > #added > > db_input "medium" midgard/error > > #changed from high > > db_go > > db_get midgard/error > > > > now works (even if it is not good) ;) > > If that'

Re: postinst and debconf again

2002-12-19 Thread Steve Langasek
On Thu, Dec 19, 2002 at 04:43:33PM +0100, pp wrote: > > > dpkg: error processing libmidgard (--install): > > > subprocess post-installation script returned error exit status 30 > > > Errors were encountered while processing: > > > libmidgard > > > debconf -s postinst > > > runs without any prob

Re: postinst and debconf again

2002-12-19 Thread Bastian Kleineidam
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, Dec 19, 2002 at 04:21:13PM +0100, pp wrote: > so my question is : > how to display message without db_input?? db_input ... || true Same is for other db_ commands which might fail: db_go || true db_stop || true Cheers, Bastian -BEGIN PGP S

Re: postinst and debconf again

2002-12-19 Thread Colin Watson
On Thu, Dec 19, 2002 at 05:50:21PM +0100, pp wrote: > I made > db_reset midgard/error > #added > db_input "medium" midgard/error > #changed from high > db_go > db_get midgard/error > > now works (even if it is not good) ;) If that's in debian/config, it's likely to be actively bad. When preconfi

Re: postinst and debconf again

2002-12-19 Thread Steve Langasek
On Thu, Dec 19, 2002 at 05:50:21PM +0100, pp wrote: > I made > db_reset midgard/error > #added > db_input "medium" midgard/error > #changed from high > db_go > db_get midgard/error > now works (even if it is not good) ;) The 'db_get' at the end is probably unnecessary, if all you're doing is dis

Re: postinst and debconf again

2002-12-19 Thread pp
Steve Langasek <[EMAIL PROTECTED]> wrote: > > dpkg: error processing libmidgard (--install): > > subprocess post-installation script returned error exit status 30 > > Errors were encountered while processing: > > libmidgard > > > debconf -s postinst > > runs without any problem > > You're mis

Re: postinst and debconf again

2002-12-19 Thread Colin Watson
On Thu, Dec 19, 2002 at 04:43:33PM +0100, pp wrote: > Steve Langasek <[EMAIL PROTECTED]> wrote: > > You're missing a '|| true' after the prompt for midgard/error. The > > question is being skipped by debconf, probably because it's been shown > > before, and this results in a different return code.

Re: postinst and debconf again

2002-12-19 Thread Colin Watson
On Thu, Dec 19, 2002 at 03:45:14PM +0100, pp wrote: > Colin Watson <[EMAIL PROTECTED]> wrote: > > On Thu, Dec 19, 2002 at 02:58:11PM +0100, pp wrote: > > > if $mysqlcmd -D mysql -e 'use midgard;' >/dev/null 2>&1 ; then > > > > > > db_input "high" midgard/error > > > > db_input can return

Re: postinst and debconf again

2002-12-19 Thread pp
Steve Langasek <[EMAIL PROTECTED]> wrote: > > > > db_input "high" midgard/error > > db_go > > db_stop > > You're missing a '|| true' after the prompt for midgard/error. The > question is being skipped by debconf, probably because it's been shown > before, and this resul

Re: postinst and debconf again

2002-12-19 Thread pp
pp <[EMAIL PROTECTED]> wrote: > Colin Watson <[EMAIL PROTECTED]> wrote: > > > On Thu, Dec 19, 2002 at 02:58:11PM +0100, pp wrote: > > > if $mysqlcmd -D mysql -e 'use midgard;' >/dev/null 2>&1 ; then > > > > > > db_input "high" midgard/error > > > > db_input can return with exit code 30

Re: postinst and debconf again

2002-12-19 Thread Steve Langasek
On Thu, Dec 19, 2002 at 03:12:26PM +0100, Bastian Kleineidam wrote: > On Thu, Dec 19, 2002 at 02:58:11PM +0100, pp wrote: > > I posted my problem some time ago. > > postinst script: > Hmm, this looks like a debian/config script, not a postinst script. > But the debconf docs are fading already in m

Re: postinst and debconf again

2002-12-19 Thread Steve Langasek
On Thu, Dec 19, 2002 at 02:58:11PM +0100, pp wrote: > I posted my problem some time ago. > postinst script: > > #! /bin/sh -ex > > . /usr/share/debconf/confmodule > db_version 2.0 > db_title "Midgard library package." > > if $mysqlcmd -D mysql -e 'use midgard;' >/dev/null 2>&1 ; then > >

Re: postinst and debconf again

2002-12-19 Thread Steve Langasek
On Thu, Dec 19, 2002 at 04:43:33PM +0100, pp wrote: > > > dpkg: error processing libmidgard (--install): > > > subprocess post-installation script returned error exit status 30 > > > Errors were encountered while processing: > > > libmidgard > > > debconf -s postinst > > > runs without any prob

Re: postinst and debconf again

2002-12-19 Thread pp
Colin Watson <[EMAIL PROTECTED]> wrote: > On Thu, Dec 19, 2002 at 02:58:11PM +0100, pp wrote: > > if $mysqlcmd -D mysql -e 'use midgard;' >/dev/null 2>&1 ; then > > > > db_input "high" midgard/error > > db_input can return with exit code 30 if the question is skipped. In > that case, yo

Re: postinst and debconf again

2002-12-19 Thread Colin Watson
On Thu, Dec 19, 2002 at 02:58:11PM +0100, pp wrote: > if $mysqlcmd -D mysql -e 'use midgard;' >/dev/null 2>&1 ; then > > db_input "high" midgard/error db_input can return with exit code 30 if the question is skipped. In that case, your postinst will fail. -- Colin Watson

Re: postinst and debconf again

2002-12-19 Thread Bastian Kleineidam
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, Dec 19, 2002 at 04:21:13PM +0100, pp wrote: > so my question is : > how to display message without db_input?? db_input ... || true Same is for other db_ commands which might fail: db_go || true db_stop || true Cheers, Bastian -BEGIN PGP S

Re: postinst and debconf again

2002-12-19 Thread pp
Bastian Kleineidam <[EMAIL PROTECTED]> wrote: > > > > postinst script: > Hmm, this looks like a debian/config script, not a postinst script. hmmm. what is the difference ? > But the debconf docs are fading already in my minds, so it might be ok. > > else > > db_input high midgard/do_setup

Re: postinst and debconf again

2002-12-19 Thread pp
Steve Langasek <[EMAIL PROTECTED]> wrote: > > dpkg: error processing libmidgard (--install): > > subprocess post-installation script returned error exit status 30 > > Errors were encountered while processing: > > libmidgard > > > debconf -s postinst > > runs without any problem > > You're mis

Re: postinst and debconf again

2002-12-19 Thread Bastian Kleineidam
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, Dec 19, 2002 at 02:58:11PM +0100, pp wrote: > I posted my problem some time ago. > > > postinst script: Hmm, this looks like a debian/config script, not a postinst script. But the debconf docs are fading already in my minds, so it might be ok

postinst and debconf again

2002-12-19 Thread pp
I posted my problem some time ago. postinst script: #! /bin/sh -ex . /usr/share/debconf/confmodule db_version 2.0 db_title "Midgard library package." if $mysqlcmd -D mysql -e 'use midgard;' >/dev/null 2>&1 ; then db_input "high" midgard/error db_go db_stop else db_inp

Re: postinst and debconf again

2002-12-19 Thread pp
pp <[EMAIL PROTECTED]> wrote: > Colin Watson <[EMAIL PROTECTED]> wrote: > > > On Thu, Dec 19, 2002 at 02:58:11PM +0100, pp wrote: > > > if $mysqlcmd -D mysql -e 'use midgard;' >/dev/null 2>&1 ; then > > > > > > db_input "high" midgard/error > > > > db_input can return with exit code 30

Re: postinst and debconf again

2002-12-19 Thread Steve Langasek
On Thu, Dec 19, 2002 at 03:12:26PM +0100, Bastian Kleineidam wrote: > On Thu, Dec 19, 2002 at 02:58:11PM +0100, pp wrote: > > I posted my problem some time ago. > > postinst script: > Hmm, this looks like a debian/config script, not a postinst script. > But the debconf docs are fading already in m

Re: postinst and debconf again

2002-12-19 Thread Steve Langasek
On Thu, Dec 19, 2002 at 02:58:11PM +0100, pp wrote: > I posted my problem some time ago. > postinst script: > > #! /bin/sh -ex > > . /usr/share/debconf/confmodule > db_version 2.0 > db_title "Midgard library package." > > if $mysqlcmd -D mysql -e 'use midgard;' >/dev/null 2>&1 ; then > >

Re: postinst and debconf again

2002-12-19 Thread pp
Colin Watson <[EMAIL PROTECTED]> wrote: > On Thu, Dec 19, 2002 at 02:58:11PM +0100, pp wrote: > > if $mysqlcmd -D mysql -e 'use midgard;' >/dev/null 2>&1 ; then > > > > db_input "high" midgard/error > > db_input can return with exit code 30 if the question is skipped. In > that case, yo

Re: postinst and debconf again

2002-12-19 Thread Colin Watson
On Thu, Dec 19, 2002 at 02:58:11PM +0100, pp wrote: > if $mysqlcmd -D mysql -e 'use midgard;' >/dev/null 2>&1 ; then > > db_input "high" midgard/error db_input can return with exit code 30 if the question is skipped. In that case, your postinst will fail. -- Colin Watson

Re: postinst and debconf again

2002-12-19 Thread pp
Bastian Kleineidam <[EMAIL PROTECTED]> wrote: > > > > postinst script: > Hmm, this looks like a debian/config script, not a postinst script. hmmm. what is the difference ? > But the debconf docs are fading already in my minds, so it might be ok. > > else > > db_input high midgard/do_setup

Re: postinst and debconf again

2002-12-19 Thread Bastian Kleineidam
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, Dec 19, 2002 at 02:58:11PM +0100, pp wrote: > I posted my problem some time ago. > > > postinst script: Hmm, this looks like a debian/config script, not a postinst script. But the debconf docs are fading already in my minds, so it might be ok

postinst and debconf again

2002-12-19 Thread pp
I posted my problem some time ago. postinst script: #! /bin/sh -ex . /usr/share/debconf/confmodule db_version 2.0 db_title "Midgard library package." if $mysqlcmd -D mysql -e 'use midgard;' >/dev/null 2>&1 ; then db_input "high" midgard/error db_go db_stop else db_inp

Re: ifeq( PACKAGE, "mypackage")

2002-12-19 Thread Mark Howard
On Thu, 2002-12-19 at 11:11, Andrew Lau wrote: > On Thu, Dec 19, 2002 at 10:50:18AM +, Mark Howard wrote: > > so that only the parts required for the current package are built? > > (and also so that they aren't build twice). > > Isn't upstream's Makefile doing its job properly in only building

Re: ifeq( PACKAGE, "mypackage")

2002-12-19 Thread Andrew Stribblehill
Quoting Bastian Kleineidam <[EMAIL PROTECTED]> (2002-12-19 11:21:21 GMT): > On Thu, Dec 19, 2002 at 10:50:18AM +, Mark Howard wrote: > > Hi, > > is it possible to determine the name of the current package at the > > build stage of debian/rules (multi-binary source), so that only the > > parts

Re: ifeq( PACKAGE, "mypackage")

2002-12-19 Thread Colin Watson
On Thu, Dec 19, 2002 at 10:50:18AM +, Mark Howard wrote: > is it possible to determine the name of the current package at the > build stage of debian/rules (multi-binary source), so that only the > parts required for the current package are built? What does "current package" mean in the buil

[OT] Build systems / make (was: Re: ifeq( PACKAGE, "mypackage"))

2002-12-19 Thread Emile van Bergen
Hi, On Thu, Dec 19, 2002 at 10:11:25PM +1100, Andrew Lau wrote: > On Thu, Dec 19, 2002 at 10:50:18AM +, Mark Howard wrote: > > so that only the parts required for the current package are built? > > (and also so that they aren't build twice). > > Isn't upstream's Makefile doing its job proper

Re: ifeq( PACKAGE, "mypackage")

2002-12-19 Thread Bastian Kleineidam
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, Dec 19, 2002 at 10:50:18AM +, Mark Howard wrote: > Hi, > is it possible to determine the name of the current package at the > build stage of debian/rules (multi-binary source), so that only the > parts required for the current package are

Re: ifeq( PACKAGE, "mypackage")

2002-12-19 Thread Andrew Lau
On Thu, Dec 19, 2002 at 10:50:18AM +, Mark Howard wrote: > so that only the parts required for the current package are built? > (and also so that they aren't build twice). Isn't upstream's Makefile doing its job properly in only building something that doesn't exist instead of rebuilding every

ifeq( PACKAGE, "mypackage")

2002-12-19 Thread Mark Howard
Hi, is it possible to determine the name of the current package at the build stage of debian/rules (multi-binary source), so that only the parts required for the current package are built? (and also so that they aren't build twice). thanks -- .''`. Mark Howard : :' : `. `' http://www.tilde

Re: ifeq( PACKAGE, "mypackage")

2002-12-19 Thread Mark Howard
On Thu, 2002-12-19 at 11:11, Andrew Lau wrote: > On Thu, Dec 19, 2002 at 10:50:18AM +, Mark Howard wrote: > > so that only the parts required for the current package are built? > > (and also so that they aren't build twice). > > Isn't upstream's Makefile doing its job properly in only building

Re: ifeq( PACKAGE, "mypackage")

2002-12-19 Thread Andrew Stribblehill
Quoting Bastian Kleineidam <[EMAIL PROTECTED]> (2002-12-19 11:21:21 GMT): > On Thu, Dec 19, 2002 at 10:50:18AM +, Mark Howard wrote: > > Hi, > > is it possible to determine the name of the current package at the > > build stage of debian/rules (multi-binary source), so that only the > > parts

Re: ifeq( PACKAGE, "mypackage")

2002-12-19 Thread Colin Watson
On Thu, Dec 19, 2002 at 10:50:18AM +, Mark Howard wrote: > is it possible to determine the name of the current package at the > build stage of debian/rules (multi-binary source), so that only the > parts required for the current package are built? What does "current package" mean in the buil

[OT] Build systems / make (was: Re: ifeq( PACKAGE, "mypackage"))

2002-12-19 Thread Emile van Bergen
Hi, On Thu, Dec 19, 2002 at 10:11:25PM +1100, Andrew Lau wrote: > On Thu, Dec 19, 2002 at 10:50:18AM +, Mark Howard wrote: > > so that only the parts required for the current package are built? > > (and also so that they aren't build twice). > > Isn't upstream's Makefile doing its job proper

Re: ifeq( PACKAGE, "mypackage")

2002-12-19 Thread Bastian Kleineidam
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, Dec 19, 2002 at 10:50:18AM +, Mark Howard wrote: > Hi, > is it possible to determine the name of the current package at the > build stage of debian/rules (multi-binary source), so that only the > parts required for the current package are

Re: ifeq( PACKAGE, "mypackage")

2002-12-19 Thread Andrew Lau
On Thu, Dec 19, 2002 at 10:50:18AM +, Mark Howard wrote: > so that only the parts required for the current package are built? > (and also so that they aren't build twice). Isn't upstream's Makefile doing its job properly in only building something that doesn't exist instead of rebuilding every

ifeq( PACKAGE, "mypackage")

2002-12-19 Thread Mark Howard
Hi, is it possible to determine the name of the current package at the build stage of debian/rules (multi-binary source), so that only the parts required for the current package are built? (and also so that they aren't build twice). thanks -- .''`. Mark Howard : :' : `. `' http://www.tilde