On Tue, 12 Jun 2018 06:22:09 +0100 Colin Watson
wrote:
> On Mon, Jun 11, 2018 at 08:52:11PM +0200, Andreas Metzler wrote:
> > On 2018-06-11 Colin Watson wrote:
> > > On Sun, Jun 10, 2018 at 04:04:13PM +0200, Andreas Metzler wrote:
> > > > yes, resetting IFS to its default value in confmodule help
On Mon, Jun 11, 2018 at 08:52:11PM +0200, Andreas Metzler wrote:
> On 2018-06-11 Colin Watson wrote:
> > On Sun, Jun 10, 2018 at 04:04:13PM +0200, Andreas Metzler wrote:
> > > yes, resetting IFS to its default value in confmodule helps.
>
> > Thanks. For completeness, could you try this variant
On Mon, Jun 11, 2018 at 1:52 PM, Andreas Metzler wrote:
[..]
> Looking at the Open Group Base Specifications Issue 7 I also think this
> behavior is a bug, since "read" is not a "a special built-in utility or
> function".
FWIW, this is a bug in bash5, and has been reported to upstream
already: ht
On 2018-06-11 Colin Watson wrote:
> On Sun, Jun 10, 2018 at 04:04:13PM +0200, Andreas Metzler wrote:
[...]
> > yes, resetting IFS to its default value in confmodule helps.
> Thanks. For completeness, could you try this variant patch? If shells
> are going to be unreliable about setting IFS in
On Sun, Jun 10, 2018 at 04:04:13PM +0200, Andreas Metzler wrote:
> On 2018-06-10 Colin Watson wrote:
> > On Sun, Jun 10, 2018 at 03:03:28PM +0200, Andreas Metzler wrote:
> >> I have tried debugging the issue to get a minimal testcase. I have had
> >> some success. The issue is triggered by debconf
On 2018-06-10 Colin Watson wrote:
> On Sun, Jun 10, 2018 at 03:03:28PM +0200, Andreas Metzler wrote:
>> I have tried debugging the issue to get a minimal testcase. I have had
>> some success. The issue is triggered by debconf.
>> /usr/share/debconf/confmodule changes IFS to \n and with bash5 this
On Sun, Jun 10, 2018 at 03:03:28PM +0200, Andreas Metzler wrote:
> I have tried debugging the issue to get a minimal testcase. I have had
> some success. The issue is triggered by debconf.
> /usr/share/debconf/confmodule changes IFS to \n and with bash5 this
> change is persistent and breaks the ma
Hello bash maintainers (debconf Cced),
I have tried debugging the issue to get a minimal testcase. I have had
some success. The issue is triggered by debconf.
/usr/share/debconf/confmodule changes IFS to \n and with bash5 this
change is persistent and breaks the maintainerscript. i.e. installing a
On 2018-06-10 Eric Valette wrote:
> On 6/10/18 11:57 AM, Eric Valette wrote:
>> On 6/10/18 11:35 AM, Andreas Metzler wrote:
>>> exports both dc_directives and any variable listed in dc_directives,
>>> i.e. any external command will see both ${dc_directives} and
>>> ${dc_eximconfig_configtype} et
On 2018-06-10 Eric Valette wrote:
> On 6/10/18 11:35 AM, Andreas Metzler wrote:
> > exports both dc_directives and any variable listed in dc_directives,
> > i.e. any external command will see both ${dc_directives} and
> > ${dc_eximconfig_configtype} et al.
> right but did you intent that?
Yes I
On 6/10/18 11:57 AM, Eric Valette wrote:
On 6/10/18 11:35 AM, Andreas Metzler wrote:
exports both dc_directives and any variable listed in dc_directives,
i.e. any external command will see both ${dc_directives} and
${dc_eximconfig_configtype} et al.
right but did you intent that? The rest of
On 6/10/18 11:35 AM, Andreas Metzler wrote:
exports both dc_directives and any variable listed in dc_directives,
i.e. any external command will see both ${dc_directives} and
${dc_eximconfig_configtype} et al.
right but did you intent that? The rest of the script seems not to use
explicitly an
On 2018-06-10 Eric Valette wrote:
> On 6/10/18 10:51 AM, Eric Valette wrote:
>> On 6/10/18 10:34 AM, Eric Valette wrote:
>>> line 330 :export dc_directives ${dc_directives}
>> Shodul be export dc_directives=${dc_directives} as far as I understand.
[...]
> and it worked. But I still think there
On 2018-06-10 Eric Valette wrote:
> On 6/10/18 10:59 AM, Eric Valette wrote:
> > On 6/10/18 10:51 AM, Eric Valette wrote:
> > 2) mv /etc/exim4/update-exim4.conf.conf
> > /etc/exim4/update-exim4.conf.conf.old
exactly what I wrote ;-)
"installs/configures successfully once the broken
/etc/ex
On 6/10/18 10:59 AM, Eric Valette wrote:
On 6/10/18 10:51 AM, Eric Valette wrote:
2) mv /etc/exim4/update-exim4.conf.conf
/etc/exim4/update-exim4.conf.conf.old
On 6/10/18 10:51 AM, Eric Valette wrote:
On 6/10/18 10:34 AM, Eric Valette wrote:
line 330 :export dc_directives ${dc_directives}
Shodul be export dc_directives=${dc_directives} as far as I understand.
To fix I did :
1) use dash temporarilly
2) /etc/exim4/update-exim4.conf.c
On 6/10/18 10:34 AM, Eric Valette wrote:
line 330 :export dc_directives ${dc_directives}
Shodul be export dc_directives=${dc_directives} as far as I understand.
-- eric
On 6/10/18 10:33 AM, Debian Bug Tracking System wrote:
This is an automatic notification regarding your Bug report
which was filed against the exim4-config package:
But now how do we fix the problem? I will reopen until I have a fix.
Putting dash as /bin/sh does fix anything BTW.
-- eric
On 6/10/18 7:07 AM, Andreas Metzler wrote:
On 2018-06-10 積丹尼 Dan Jacobson wrote:
Oops. I mean just:
Setting up exim4-config (4.91-5) ...
/etc/exim4/update-exim4.conf.conf: line 26: dc_eximconfig_configtype: command
not found
Hello,
Are you running bash (or other stuff) from experimental? II
On 2018-06-10 積丹尼 Dan Jacobson wrote:
> Oops. I mean just:
> Setting up exim4-config (4.91-5) ...
> /etc/exim4/update-exim4.conf.conf: line 26: dc_eximconfig_configtype: command
> not found
Hello,
Are you running bash (or other stuff) from experimental? IIRC there is
some breakage there.
cu An
Oops. I mean just:
Setting up exim4-config (4.91-5) ...
/etc/exim4/update-exim4.conf.conf: line 26: dc_eximconfig_configtype: command
not found
Setting up exim4-config (4.91-5) ...
/var/lib/dpkg/info/exim4-config.postinst: line 330: export:
`dc_eximconfig_configtype dc_other_hostnames dc_local_interfaces dc_readhost
dc_relay_domains dc_minimaldns dc_relay_nets dc_smarthost CFILEMODE
dc_use_split_config dc_hide_mailname dc_mailname_in_oh
22 matches
Mail list logo
