Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

First time dialog unable to finish #17

Open
andk opened this issue May 15, 2014 · 0 comments
Open

First time dialog unable to finish #17

andk opened this issue May 15, 2014 · 0 comments

Comments

@andk
Copy link

andk commented May 15, 2014

On a new VM, new user, new perl I ran the cpan shell for the first time interactively. I had already installed Bundle-CPANReporter2, so I expected I would only run 'o conf init /report/' and choose only defaults. So in the output below you see me hitting ENTER quite often. Then I tried with ^Z and doing things on the commandline. Sorry, this is a bit long. Note that I had to answer 'n' to reach the end, with 'y' it was an endless loop.

cpan[1]> o conf init /report/
The goal of the CPAN Testers project (http://testers.cpan.org/) is to
test as many CPAN packages as possible on as many platforms as
possible.  This provides valuable feedback to module authors and
potential users to identify bugs or platform compatibility issues and
improves the overall quality and value of CPAN.

One way you can contribute is to send test results for each module
that you install.  If you install the CPAN::Reporter module, you have
the option to automatically generate and deliver test reports to CPAN
Testers whenever you run tests on a CPAN package.

See the CPAN::Reporter documentation for additional details and
configuration settings.  If your firewall blocks outgoing traffic,
you may need to configure CPAN::Reporter before sending reports.

 <test_report>
Generate test reports if CPAN::Reporter is installed (yes/no)? [no] yes

Would you like me configure CPAN::Reporter now? [yes] yes


Proceeding to configure CPAN::Reporter.

Some of the following configuration options require one or more "grade:action"
pairs that determine what grade-specific action to take for that option.
These pairs should be space-separated and are processed left-to-right. See
CPAN::Reporter documentation for more details.

    GRADE   :   ACTION  ======> EXAMPLES
    -------     -------         --------
    pass        yes             default:no
    fail        no              default:yes pass:no
    unknown     ask/no          default:ask/no pass:yes fail:no
    na          ask/yes
    default


CPAN::Reporter: no config file found; creating a new one.

CPAN::Reporter requires a valid email address to identify senders
in the body of a test report.  Please use a standard email format
like: "John Doe" <[email protected]>

email_from? [] [email protected]

Before test reports are sent, you may want to review or edit the test
report and add additional comments about the result or about your system
or Perl configuration.  By default, CPAN::Reporter will ask after
each report is generated whether or not you would like to edit the
report. This option takes "grade:action" pairs.

(Recommended: 'default:ask/no pass/na:no')

edit_report? [default:ask/no pass/na:no]

By default, CPAN::Reporter will prompt you for confirmation that
the test report should be sent before actually doing it. This
gives the opportunity to skip sending particular reports if
you need to (e.g. if you caused the failure). This option takes
"grade:action" pairs.

(Recommended: 'default:ask/yes pass/na:yes')

send_report? [default:ask/yes pass/na:yes]

CPAN::Reporter sends your reports over HTTPS using Metabase. This option lets
you set a different uri, transport mechanism and metabase profile path. If you
are receiving HTTPS errors, you may change the uri to use plain HTTP, though
this is not recommended. Unless you know what you're doing, just accept
the default value.

(Recommended: 'Metabase uri https://metabase.cpantesters.org/api/v1/ id_file metabase_id.json')

transport? [Metabase uri https://metabase.cpantesters.org/api/v1/ id_file metabase_id.json]

Would you like to run 'metabase-profile' now to create '/home/sand/.cpanreporter/metabase_id.json'? [y]
transport? [Metabase uri https://metabase.cpantesters.org/api/v1/ id_file metabase_id.json]

Would you like to run 'metabase-profile' now to create '/home/sand/.cpanreporter/metabase_id.json'? [y]
transport? [Metabase uri https://metabase.cpantesters.org/api/v1/ id_file metabase_id.json]

Would you like to run 'metabase-profile' now to create '/home/sand/.cpanreporter/metabase_id.json'? [y] ^Z
zsh: suspended  ~/src/perl/repoperls/installed-perls/host/freebsd10/v5.18.2/d58a/bin/cpan
>sand@freebsd10:~/src/perl/repoperls/perl5.git.perl.org/perl[(detached from v5.18.2)]% mkdir ~/.metabase
>sand@freebsd10:~/src/perl/repoperls/perl5.git.perl.org/perl[(detached from v5.18.2)]% fg
[1]  + continued  ~/src/perl/repoperls/installed-perls/host/freebsd10/v5.18.2/d58a/bin/cpan

transport? [Metabase uri https://metabase.cpantesters.org/api/v1/ id_file metabase_id.json]

Would you like to run 'metabase-profile' now to create '/home/sand/.cpanreporter/metabase_id.json'? [y]
transport? [Metabase uri https://metabase.cpantesters.org/api/v1/ id_file metabase_id.json]

Would you like to run 'metabase-profile' now to create '/home/sand/.cpanreporter/metabase_id.json'? [y] ^Z
zsh: suspended  ~/src/perl/repoperls/installed-perls/host/freebsd10/v5.18.2/d58a/bin/cpan
zsh: exit 18
>sand@freebsd10:~/src/perl/repoperls/perl5.git.perl.org/perl[(detached from v5.18.2)]% vi ~/.metabase/id.json

[...now editing that file and filling it with the contents from another smoker...]

/home/sand/.metabase/id.json: new file: 33 lines, 3183 characters
>sand@freebsd10:~/src/perl/repoperls/perl5.git.perl.org/perl[(detached from v5.18.2)]% fg
[1]  + continued  ~/src/perl/repoperls/installed-perls/host/freebsd10/v5.18.2/d58a/bin/cpan

transport? [Metabase uri https://metabase.cpantesters.org/api/v1/ id_file metabase_id.json]

Would you like to run 'metabase-profile' now to create '/home/sand/.cpanreporter/metabase_id.json'? [y] y
transport? [Metabase uri https://metabase.cpantesters.org/api/v1/ id_file metabase_id.json]

Would you like to run 'metabase-profile' now to create '/home/sand/.cpanreporter/metabase_id.json'? [y] n
You can create a Metabase profile by typing 'metabase-profile' in your
command prompt and moving the resulting file to the location you specified.
If you did not specify an absolute path, put it in your .cpanreporter
directory.  You will need to do this before continuing.
transport? [Metabase uri https://metabase.cpantesters.org/api/v1/ id_file metabase_id.json]

Would you like to run 'metabase-profile' now to create '/home/sand/.cpanreporter/metabase_id.json'? [y]
transport? [Metabase uri https://metabase.cpantesters.org/api/v1/ id_file metabase_id.json] ^Z
zsh: suspended  ~/src/perl/repoperls/installed-perls/host/freebsd10/v5.18.2/d58a/bin/cpan
zsh: exit 18
>sand@freebsd10:~/src/perl/repoperls/perl5.git.perl.org/perl[(detached from v5.18.2)]% mv ~/.metabase/id.json /home/sand/.cpanreporter/metabase_id.json
>sand@freebsd10:~/src/perl/repoperls/perl5.git.perl.org/perl[(detached from v5.18.2)]% fg
[1]  + continued  ~/src/perl/repoperls/installed-perls/host/freebsd10/v5.18.2/d58a/bin/cpan


CPAN::Reporter: writing config file to '/home/sand/.cpanreporter/config.ini'.

Returning to CPAN configuration.
When a distribution has already been tested by CPAN::Reporter on
this machine, CPAN can skip the test phase and just rely on the
test report history instead.

Note that this will not apply to distributions that failed tests
because of missing dependencies.  Also, tests can be run
regardless of the history using "force".

 <trust_test_report_history>
Do you want to rely on the test report history (yes/no)? [no]


Please remember to call 'o conf commit' to make the config permanent!
cpan[2]> commit                     
Unknown shell command 'commit'. Type ? for help.

cpan[3]> o conf commit
commit: wrote '/home/sand/.cpan/CPAN/MyConfig.pm'
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant