On Fri, 05 Sep 2025 10:51:52 +0100 "Jonathan Dowland" <[email protected]> wrote: > On Thu Sep 4, 2025 at 7:31 PM BST, Thierry wrote: > > it is currently impossible to deploy a new ikiwiki instance on Debian > > trixie: > ... > > Note that it works well on bookworm, while the files > > /etc/ikiwiki/auto.setup and /usr/share/perl5/IkiWiki/Setup/Automator.pm > > have not been changed between the two releases. > > Thanks. Confirmed. Ouch! > > As a workaround you can do something like > > ikiwiki --dumpsetup my.setup ./src ./dest > > and then manually adjust my.setup. > > I suspect the breakage to auto.setup occurred with > libterm-readline-gnu-perl moving to 1.47 but that's not confirmed.
I have also encountered this problem. The check for multiple instances was added in Term::ReadLine::Gnu 1.46: https://metacpan.org/release/HAYASHI/Term-ReadLine-Gnu-1.46 and https://github.com/hirooih/perl-trg/issues/16#issuecomment-1615775088 A workaround is to force Term::ReadLine to use the Perl implementation instead of the Gnu one by placing PERL_RL=Perl before the ikiwiki invocation. This has the unfortunate effect of not prefilling any of the suggested answers to the questions. The permanent fix is to alter IkiWiki/Setup/Automator.pm to place the Term::ReadLine creation outside of the ask sub: ---- @@ -11,10 +11,11 @@ use File::Path; use Encode; +my $r=Term::ReadLine->new("ikiwiki"); + sub ask ($$) { my ($question, $default)=@_; - my $r=Term::ReadLine->new("ikiwiki"); $r->ornaments("md,me"); $r->readline(encode_utf8($question)." ", $default); } ---- Hope this helps. -- Philip Searle
