avoiding frontend "falllback" on dpkg-reconfigure

Hello all, I'd like to know if there's a way to tell dpkg-reconfigure to avoid falling back to another frontend returning an error in case of a failure in the main frontend. It is because I'm creating a program to call dpkg-reconfigure -f Gnome, and that doesn't need a terminal opened to run, but

avoiding frontend "falllback" on dpkg-reconfigure

Hello all, I'd like to know if there's a way to tell dpkg-reconfigure to avoid falling back to another frontend returning an error in case of a failure in the main frontend. It is because I'm creating a program to call dpkg-reconfigure -f Gnome, and that doesn't need a terminal opened to run, but

Re: dpkg-gencontrol: warning: unknown substitution variable ${shlibs:Depends}

Hi ... On Mon, Oct 29, 2001 at 02:37:25PM +0100, Robert Bihlmeyer wrote: >Jan-Hendrik Palic <[EMAIL PROTECTED]> writes: >> subvars: >Depending on the exact conditions, you should have a file named >substvars or one or more .substvars files. Was this a >typo, or is that the source of the problem?

Re: dpkg-gencontrol: warning: unknown substitution variable ${shlibs:Depends}

Hi ... On Mon, Oct 29, 2001 at 02:37:25PM +0100, Robert Bihlmeyer wrote: >Jan-Hendrik Palic <[EMAIL PROTECTED]> writes: >> subvars: >Depending on the exact conditions, you should have a file named >substvars or one or more .substvars files. Was this a >typo, or is that the source of the problem?