On Sun, Jun 10, 2018 at 04:04:13PM +0200, Andreas Metzler wrote:
> On 2018-06-10 Colin Watson <cjwat...@debian.org> 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
> >> change is persistent and breaks the maintainerscript.
>
> > Does this patch help?
>
> 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 this way, then I'd
rather just separate out the assignments altogether.
diff --git a/confmodule b/confmodule
index 8347c0b0..3ef7a309 100644
--- a/confmodule
+++ b/confmodule
@@ -42,10 +42,11 @@ _db_cmd () {
_db_internal_IFS="$IFS"
IFS=' '
printf '%s\n' "$*" >&3
- IFS="$_db_internal_IFS"
# Set to newline to get whole line.
IFS='
-' read -r _db_internal_line
+'
+ read -r _db_internal_line
+ IFS="$_db_internal_IFS"
# Disgusting, but it's the only good way to split the line,
# preserving all other whitespace.
RET="${_db_internal_line#[! ][ ]}"
(This does still seem like a bash bug though, unless there's some arcane
interpretation of the standards that I'm unaware of.)
Cheers,
--
Colin Watson [cjwat...@debian.org]
