Edit report at http://bugs.php.net/bug.php?id=53211&edit=1
ID: 53211
User updated by: clicky at erebot dot net
Reported by: clicky at erebot dot net
Summary: Missing command-line option in Pyrus to prevent
signing
Status: Bogus
Type: Feature/Change Request
Package: Unknown/Other Function
Operating System: Ubuntu 10.04
PHP Version: Irrelevant
Block user comment: N
New Comment:
That's what I thought at first, but I could not find a link to said
tracker on pear's website and the general pear bug tracker doesn't list
"pyrus" as a valid package.
I'll try asking the pear folks on IRC to point me to the right URL.
Thank you for your time.
Previous Comments:
------------------------------------------------------------------------
[2010-10-31 02:49:16] paj...@php.net
Please report pyrus bugs to the pyrus bugs tracker.
------------------------------------------------------------------------
[2010-10-30 23:57:34] clicky at erebot dot net
Description:
------------
I configured my Pyrus installation so that it will use a certificate to
sign packages I produce.
The problem is, I now have a buildbot using the same user account which
builds nightly snapshots of my code as unsigned packages too.
Whenever the slave starts the packaging process, Pyrus prompts it to
choose whether the package should be signed or not. Since the slave has
no way to answer that prompt, it just sits there, until the timeout for
the task is reached, at which point pyrus gets killed.
I know a simple workaround would be to use different user accounts with
different Pyrus installations (configurations), but I think it would be
valuable to have a command-line option to accept/refuse package signing.
Test script:
---------------
$ pyrus.phar package --sign=no --phar --tgz
Expected result:
----------------
Pyrus should build the phar & tgz archives without prompting the user
whether a signature should be used or not.
Actual result:
--------------
Pyrus asks me whether I want a signature to be added or not:
Sign package?
Please choose:
yes
no
[yes] :
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/bug.php?id=53211&edit=1
