On 12/21/2010 02:17 PM, PICCA Frédéric-Emmanuel wrote:
> Hello
>
>> 22 # what is the name of the tango host
>> 23 db_input high tango-common/tango-host || true
>> 24 db_go || true
>
>> Hi,
>
>> WIth your script here, there are cases where there's no db_set
>> tango-common/tango-host. That
Hello
> 22 # what is the name of the tango host
> 23 db_input high tango-common/tango-host || true
> 24 db_go || true
> Hi,
> WIth your script here, there are cases where there's no db_set
> tango-common/tango-host. That shouldn't happen. You should set it
> unconditionally (eg: always)!
On 12/20/2010 03:43 PM, PICCA Frédéric-Emmanuel wrote:
>1 #!/bin/sh
>2 CONFIGFILE=/etc/tangorc
>3 set -e
>4 . /usr/share/debconf/confmodule
>5
>6 # Load config file, if it exists.
>7 if [ -e $CONFIGFILE ]; then
>8 . $CONFIGFILE || true
>9
> 10 # Store
Hello
thanks for your answer
> If there's only host and port in your config file, don't try
> to re-read it in your postinst. What you have done in your
> config script should be enough to read the value that was
> previously in the config file, or the one that was set using
> debconf (with prior
On 12/17/2010 04:27 PM, Picca Frédéric-Emmanuel wrote:
> now my problem is when I generate the configure file from this db entry in
> the postinst script.
> Here the code :
>
>1 #!/bin/sh
>2 CONFIGFILE=/etc/tangorc
>3 set -e
>4 . /usr/share/debconf/confmodule
>5
>6 # Gener
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 13 July 2004 01:46 pm, Brian Nelson wrote:
> Adrian 'Dagurashibanipal' von Bidder <[EMAIL PROTECTED]> writes:
> > And while I'm at it: the behaviour change is not really dangerous, but
> > can cause people to get more spam. (Background: post
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 13 July 2004 01:46 pm, Brian Nelson wrote:
> Adrian 'Dagurashibanipal' von Bidder <[EMAIL PROTECTED]> writes:
> > And while I'm at it: the behaviour change is not really dangerous, but
> > can cause people to get more spam. (Background: post
Adrian 'Dagurashibanipal' von Bidder <[EMAIL PROTECTED]> writes:
> And while I'm at it: the behaviour change is not really dangerous, but
> can cause people to get more spam. (Background: postgrey changed from
> --lookup-by-host to --lookup-by-subnet in Version 1.14) So, is a
> debconf notice e
Adrian 'Dagurashibanipal' von Bidder <[EMAIL PROTECTED]> writes:
> And while I'm at it: the behaviour change is not really dangerous, but
> can cause people to get more spam. (Background: postgrey changed from
> --lookup-by-host to --lookup-by-subnet in Version 1.14) So, is a
> debconf notice e
On Tuesday 13 July 2004 12.24, martin f krafft wrote:
> also sprach martin f krafft <[EMAIL PROTECTED]> [2004.07.13.1217
+0200]:
> > case "$2" in
> > 0.13*) [...]
> After looking over debconf-devel(7), this should be in the
> postgrey.config script and use db_input rather than db_get. B
On 2004-07-13 Adrian 'Dagurashibanipal' von Bidder <[EMAIL PROTECTED]> wrote:
> [Madduck cc:ed as he is my sponsor - but he tells me he's certainly not
> a debconf expert]
> How do I display a debconf note only on upgrades from versions older
> than x to x or newer? No need to annoy all users...
also sprach martin f krafft <[EMAIL PROTECTED]> [2004.07.13.1217 +0200]:
> AFAICT, the display of a 'note' is triggered by db_get in postinst.
> Since postinst gets the previous version as arguments to an
> upgrade/configure action, it's a simple case/if statement.
>
> case "$1" in
> configure)
also sprach Adrian 'Dagurashibanipal' von Bidder <[EMAIL PROTECTED]>
[2004.07.13.1204 +0200]:
> How do I display a debconf note only on upgrades from versions
> older than x to x or newer? No need to annoy all users...
AFAICT, the display of a 'note' is triggered by db_get in postinst.
Since post
On Tuesday 13 July 2004 12.24, martin f krafft wrote:
> also sprach martin f krafft <[EMAIL PROTECTED]> [2004.07.13.1217
+0200]:
> > case "$2" in
> > 0.13*) [...]
> After looking over debconf-devel(7), this should be in the
> postgrey.config script and use db_input rather than db_get. B
On 2004-07-13 Adrian 'Dagurashibanipal' von Bidder <[EMAIL PROTECTED]> wrote:
> [Madduck cc:ed as he is my sponsor - but he tells me he's certainly not
> a debconf expert]
> How do I display a debconf note only on upgrades from versions older
> than x to x or newer? No need to annoy all users...
also sprach martin f krafft <[EMAIL PROTECTED]> [2004.07.13.1217 +0200]:
> AFAICT, the display of a 'note' is triggered by db_get in postinst.
> Since postinst gets the previous version as arguments to an
> upgrade/configure action, it's a simple case/if statement.
>
> case "$1" in
> configure)
also sprach Adrian 'Dagurashibanipal' von Bidder <[EMAIL PROTECTED]> [2004.07.13.1204
+0200]:
> How do I display a debconf note only on upgrades from versions
> older than x to x or newer? No need to annoy all users...
AFAICT, the display of a 'note' is triggered by db_get in postinst.
Since post
On Mon, Jul 22, 2002 at 04:42:57PM +0200, Andreas Rottmann wrote:
> Hi!
>
> I'd like to know how to have debconf templates displayed only if one,
> say upgrades his package "foo" from a version <= "baz".
>
> Any hints?
Use
dpkg --compare-versions
Example from masqmail.config:
if [ "$1" == "con
On Mon, Jul 22, 2002 at 04:42:57PM +0200, Andreas Rottmann wrote:
> Hi!
>
> I'd like to know how to have debconf templates displayed only if one,
> say upgrades his package "foo" from a version <= "baz".
>
> Any hints?
Use
dpkg --compare-versions
Example from masqmail.config:
if [ "$1" == "co
On Tue, Jul 31, 2001 at 08:24:41PM -0400, Joey Hess wrote:
> Viral wrote:
> > My problem is that, there will be a variable number of nodes for which
> > information is required. This will be only known at runtime.
>
> No problem. A single debconf template can instantiate into an unlimited
> number
On Tue, Jul 31, 2001 at 08:24:41PM -0400, Joey Hess wrote:
> Viral wrote:
> > My problem is that, there will be a variable number of nodes for which
> > information is required. This will be only known at runtime.
>
> No problem. A single debconf template can instantiate into an unlimited
> numbe
Viral wrote:
> My problem is that, there will be a variable number of nodes for which
> information is required. This will be only known at runtime.
No problem. A single debconf template can instantiate into an unlimited
number of individual questions. See the REGISTER command. You can also
use su
Viral wrote:
> My problem is that, there will be a variable number of nodes for which
> information is required. This will be only known at runtime.
No problem. A single debconf template can instantiate into an unlimited
number of individual questions. See the REGISTER command. You can also
use s
Em Tue, 31 Jul 2001 23:08:40 +0530
Viral <[EMAIL PROTECTED]> escreveu:
Hi Viral,
> I'm trying to use debconf to get inputs from the user in the package
> update-cluster.
>
> My problem is that, there will be a variable number of nodes for which
> information is required. This will be only known
On Tue, Jul 31, 2001 at 11:08:40PM +0530, Viral wrote:
> My problem is that, there will be a variable number of nodes for which
> information is required. This will be only known at runtime. It will
> be impossible to enter the nodes information separated by ':" or some
> such thing.
don't use deb
Em Tue, 31 Jul 2001 23:08:40 +0530
Viral <[EMAIL PROTECTED]> escreveu:
Hi Viral,
> I'm trying to use debconf to get inputs from the user in the package
> update-cluster.
>
> My problem is that, there will be a variable number of nodes for which
> information is required. This will be only known
On Tue, Jul 31, 2001 at 11:08:40PM +0530, Viral wrote:
> My problem is that, there will be a variable number of nodes for which
> information is required. This will be only known at runtime. It will
> be impossible to enter the nodes information separated by ':" or some
> such thing.
don't use de
Joey Hess wrote:
> J?r?me Marant wrote:
Sorry about the quoting here -- looks like a mutt bug.
--
see shy jo
J?r?me Marant wrote:
> I have a package using debconf. This package is restarting a daemon
> in its postinst after generating configuration scripts.
>
> When I run dpkg-reconfigure, I would like to regenerate configuration
> scripts and restart the daemon.
> Am I allow to do this in a
Joey Hess wrote:
> J?r?me Marant wrote:
Sorry about the quoting here -- looks like a mutt bug.
--
see shy jo
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
J?r?me Marant wrote:
> I have a package using debconf. This package is restarting a daemon
> in its postinst after generating configuration scripts.
>
> When I run dpkg-reconfigure, I would like to regenerate configuration
> scripts and restart the daemon.
> Am I allow to do this in a
On Sun, Mar 26, 2000 at 01:37:43PM +0200, Tom Cato Amundsen wrote:
> I have just started to use debconf, and lintian complaints about:
> E: solfege: unknown-control-file config
> E: solfege: unknown-control-file templates
>
> The package is called solfege, and the files are debian/solfege.config
>
32 matches
Mail list logo
