Debconf readline frontend does not show options

Status changed to 'Confirmed' because the bug affects multiple users.

Hello Tobias, or anyone else affected,

Accepted debconf into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/debconf/1.5.71ubuntu1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello Tobias, or anyone else affected,

Accepted debconf into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/debconf/1.5.69ubuntu1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello Tobias, or anyone else affected,

Accepted debconf into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/debconf/1.5.66ubuntu1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello Tobias, or anyone else affected,

Accepted debconf into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/debconf/1.5.58ubuntu2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Validated debconf from disco-proposed according to test case from description:

root@disco:~# dpkg -l | grep debconf
ii debconf 1.5.71ubuntu1 all Debian configuration management system

root@disco:~# run-parts --exit-on-error --arg=5.0.0 /etc/kernel/postinst.d --report
...
/etc/kernel/postinst.d/x-grub-legacy-ec2:
debconf: unable to initialize frontend: Dialog
debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 76.)
debconf: falling back to frontend: Readline
Searching for GRUB installation directory ... found: /boot/grub
Searching for default file ... found: /boot/grub/default
Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
Searching for splash image ... none found, skipping ...
A new version of /boot/grub/menu.lst is available, but the version installed currently has been locally modified.

  1. install the package maintainer's version 3. show the differences between the versions 5. show a 3-way difference between available versions 7. start a new shell to examine the situation
  2. keep the local version currently installed 4. show a side-by-side difference between the versions 6. do a 3-way merge between available versions (experimental)

What would you like to do about menu.lst?

Validated debconf from cosmic-proposed according to test case from description:

root@cosmic:~# dpkg -l | grep debconf
ii debconf 1.5.69ubuntu1 all Debian configuration management system

root@cosmic:~# run-parts --exit-on-error --arg=5.0.0 /etc/kernel/postinst.d --report
...
/etc/kernel/postinst.d/x-grub-legacy-ec2:
debconf: unable to initialize frontend: Dialog
debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 76.)
debconf: falling back to frontend: Readline
Searching for GRUB installation directory ... found: /boot/grub
Searching for default file ... found: /boot/grub/default
Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
Searching for splash image ... none found, skipping ...
A new version of /boot/grub/menu.lst is available, but the version installed currently has been locally modified.

  1. install the package maintainer's version 3. show the differences between the versions 5. show a 3-way difference between available versions 7. start a new shell to examine the situation
  2. keep the local version currently installed 4. show a side-by-side difference between the versions 6. do a 3-way merge between available versions (experimental)

What would you like to do about menu.lst?

Validated debconf from bionic-proposed according to test case from description:

root@bionic:~# dpkg -l | grep debconf
ii debconf 1.5.66ubuntu1 all Debian configuration management system

root@bionic:~# run-parts --exit-on-error --arg=5.0.0 /etc/kernel/postinst.d --report
...
/etc/kernel/postinst.d/x-grub-legacy-ec2:
debconf: unable to initialize frontend: Dialog
debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 76.)
debconf: falling back to frontend: Readline
Searching for GRUB installation directory ... found: /boot/grub
Searching for default file ... found: /boot/grub/default
Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
Searching for splash image ... none found, skipping ...
A new version of /boot/grub/menu.lst is available, but the version installed currently has been locally modified.

  1. install the package maintainer's version 3. show the differences between the versions 5. show a 3-way difference between available versions 7. start a new shell to examine the situation
  2. keep the local version currently installed 4. show a side-by-side difference between the versions 6. do a 3-way merge between available versions (experimental)

What would you like to do about menu.lst?

Validated debconf from xenial-proposed according to test case from description:

root@xenial:~# dpkg -l | grep debconf
ii debconf 1.5.58ubuntu2 all Debian configuration management system

root@xenial:~# run-parts --exit-on-error --arg=5.0.0 /etc/kernel/postinst.d --report
...
/etc/kernel/postinst.d/x-grub-legacy-ec2:
debconf: unable to initialize frontend: Dialog
debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 76.)
debconf: falling back to frontend: Readline
Searching for GRUB installation directory ... found: /boot/grub
Searching for default file ... found: /boot/grub/default
Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
Searching for splash image ... none found, skipping ...
A new version of /boot/grub/menu.lst is available, but the version installed currently has been locally modified.

  1. install the package maintainer's version 3. show the differences between the versions 5. show a 3-way difference between available versions 7. start a new shell to examine the situation
  2. keep the local version currently installed 4. show a side-by-side difference between the versions 6. do a 3-way merge between available versions (experimental)

What would you like to do about menu.lst?

Some comments on the autopkgtest regressions:

# Disco
- prometheus-blackbox-exporter and open-isns fail due to package dependency problems, unrelated to debconf

- makedumpfile fails with "sudo: /tmp/autopkgtest-run-wrapper: command not found", which has happened in other previous autopkgtests (perl/5.28.1-6, file/1:5.35-4, elfutils/0.176-1). This does not seem to be related to the debconf update

# Cosmic
- murano seems to fail due to a syntax error in python3-murano, preventing dpkg from successfully configuring it. It has been failing since before the debconf change was introduced

- cacti fails due to "ERROR PHP WARNING: A non-numeric value encountered in file: /usr/share/cacti/site/poller.php on line: 652", which is not related to the debconf changes

- pbuilder is failing due to a missing Eoan script, might be related to LP: #1825994

- glibc fails due to a timeout on the test suite, and doesn't look related to our debconf changes

# Bionic
- pbuilder is still failing due to a missing Eoan script, might be related to LP: #1825994

- redmine is failing due to not being able to pull some packages for the test setup

- makedumpfile has been failing since before the debconf changes with "makedumpfile: ERROR: crash test: kdump is not ready"

- cacti fails due to "Unexpected output in /var/log/cacti/cacti.log:
05/08/2019 19:45:00 - AUTOM8 WARNING: The Network ID: 1 is disabled. You must use the 'force' option to force it's execution."

- open-iscsi is failing since debconf/1.5.66, so it doesn't look to be caused by our changes

makedumpfile failures in bionic probably are due to bug 1790788 which is in -proposed, and so should be ignorable

This bug was fixed in the package debconf - 1.5.71ubuntu1

---------------
debconf (1.5.71ubuntu1) disco; urgency=medium

  * Fix readline prompts when run via run-parts (LP: #1822270)
    - Debconf/FrontEnd/Readline.pm: force output to stdout if both stdout and
      stderr are pipes

 -- Heitor Alves de Siqueira <email address hidden> Mon, 06 May 2019 13:16:57 -0300

The verification of the Stable Release Update for debconf has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

This bug was fixed in the package debconf - 1.5.69ubuntu1

---------------
debconf (1.5.69ubuntu1) cosmic; urgency=medium

  * Fix readline prompts when run via run-parts (LP: #1822270)
    - Debconf/FrontEnd/Readline.pm: force output to stdout if both stdout and
      stderr are pipes

 -- Heitor Alves de Siqueira <email address hidden> Mon, 06 May 2019 13:27:55 -0300

This bug was fixed in the package debconf - 1.5.66ubuntu1

---------------
debconf (1.5.66ubuntu1) bionic; urgency=medium

  * Fix readline prompts when run via run-parts (LP: #1822270)
    - Debconf/FrontEnd/Readline.pm: force output to stdout if both stdout and
      stderr are pipes

 -- Heitor Alves de Siqueira <email address hidden> Mon, 06 May 2019 13:30:30 -0300

This bug was fixed in the package debconf - 1.5.58ubuntu2

---------------
debconf (1.5.58ubuntu2) xenial; urgency=medium

  * Fix readline prompts when run via run-parts (LP: #1822270)
    - Debconf/FrontEnd/Readline.pm: force output to stdout if both stdout and
      stderr are pipes

 -- Heitor Alves de Siqueira <email address hidden> Mon, 06 May 2019 13:31:57 -0300