© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Hello and thank you for testing the update in -proposed!
From DpgkTerminalLog
Use of uninitialized value $_[1] in join or string at /usr/share/
Use of uninitialized value $val in substitution (s///) at /usr/share/
Use of uninitialized value $val in concatenation (.) or string at /usr/share/
Setting up php7.0-xml (7.0.13-
Use of uninitialized value $reply in scalar chomp at /usr/share/
Use of uninitialized value $reply in concatenation (.) or string at /usr/share/
Use of uninitialized value $reply in split at /usr/share/
Use of uninitialized value $reply in scalar chomp at /usr/share/
Use of uninitialized value $reply in concatenation (.) or string at /usr/share/
Use of uninitialized value $reply in split at /usr/share/
Use of uninitialized value $reply in scalar chomp at /usr/share/
Use of uninitialized value $reply in concatenation (.) or string at /usr/share/
Use of uninitialized value $reply in split at /usr/share/
dpkg: error processing package php7.0-xml (--configure):
subprocess installed post-installation script returned error exit status 128
Unfortunately, we have seen this before (not necessarily only with php7.0), and it's unclear why debconf is failing. I do not believe this is an actual issue in php7.0's update (and I can't reproduce this locally).
In the paste, we've wondered if perhaps a debconf prompt race is occurring (or perhaps was skipped/ignored?). You mentioned that 'process was stuck on php7.0-xml configuration '. Could you specify what exactly was emitted on your screen that seemed stuck? Do you have any local php7.0-xml configuration modifications?
Thanks again,
Nish