You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
dzil setup asks "Do you want to enter your PAUSE account dtails?";
if the reply is "yes" but the user just presses ENTER when asked for their PAUSE password, an error occurs:
Use of uninitialized value $input in scalar chomp at <home>/perl5/lib/perl5/Dist/Zilla/Chrome/Term.pm line 152, <FIN> line 8.
$HOME/.dzil/config.ini is created anyway, with
[%PAUSE]
username = jimavera
(with no password = ...).
dzil (Dist::Zilla::App) version 6.029
====
UPDATE: The resulting config.ini does not work: dzil new <Module> fails with Your global configuration file couldn't be loaded. It's a file matching ~/.dzil/config.*. No other error information is given, but removing the [%PAUSE] section containing only username fixed the problem.
Therefore IMO dzil setup should hard fail or at least inform the user that a PAUSE password is required if any PAUSE configuration stuff is specified at all (assuming that's the case, and the dzil new error is not itself a bug.) And not emit the "uninitialized..." warning.
Actually I was hoping that a PAUSE username could be stored but not the pw.
The text was updated successfully, but these errors were encountered:
jimav
changed the title
dzil setup should allow PAUSE password to not be specified
dzil setup gives 'uninitialized...' warning if PAUSE password is not specified
Feb 7, 2023
dzil setup
asks "Do you want to enter your PAUSE account dtails?";if the reply is "yes" but the user just presses ENTER when asked for their PAUSE password, an error occurs:
$HOME/.dzil/config.ini is created anyway, with
(with no password = ...).
dzil (Dist::Zilla::App) version 6.029
====
UPDATE: The resulting config.ini does not work:
dzil new <Module>
fails withYour global configuration file couldn't be loaded. It's a file matching ~/.dzil/config.*
. No other error information is given, but removing the [%PAUSE] section containing onlyusername
fixed the problem.Therefore IMO
dzil setup
should hard fail or at least inform the user that a PAUSE password is required if any PAUSE configuration stuff is specified at all (assuming that's the case, and thedzil new
error is not itself a bug.) And not emit the "uninitialized..." warning.Actually I was hoping that a PAUSE username could be stored but not the pw.
The text was updated successfully, but these errors were encountered: