*Synopsis*: Cadmium breaks NetBeans 6.5 Mercurial support
Due to a change requested by <User 1-5Q-8204>,
<User 1-5Q-8204> is now the responsible engineer for:
CR 6777815 changed on Dec 12 2008 by <User 1-5Q-8204>
=== Field ============ === New Value ============= === Old Value =============
Commit to Fix in Build snv_106
Introduced in Build snv_97
Introduced in Release solaris_nevada
Responsible Engineer <User 1-5Q-8204>
Status 6-Fix Understood 1-Dispatched
====================== =========================== ===========================
*Change Request ID*: 6777815
*Synopsis*: Cadmium breaks NetBeans 6.5 Mercurial support
Product: solaris
Category: consolidation
Subcategory: os-net-tools
Type: Defect
Subtype: Functionality
Status: 6-Fix Understood
Substatus:
Priority: 2-High
Introduced In Release: solaris_nevada
Introduced In Build: snv_97
Responsible Engineer: <User 1-5Q-8204>
Keywords:
=== *Description* ============================================================
I'm trying to push changes using the Mercurial support in NetBeans 6.5, and I
get the following error:
==========
Mercurial Push
--------------
INFO Pushing To: ssh://<email address omitted>//hg/website/auth ...
ERROR Command failed:
Command: [hg, push, --repository, /home1/homedir/alanbur/tonic/auth,
ssh://<email address omitted>//hg/website/auth]
Output: [pushing to ssh://<email address omitted>//hg/website/auth, searching
for changes, abort: preoutgoing.cdm_pbconfirm hook failed]
INFO: End of Mercurial Push
==========
This means that an important Mercurial feature (pushing changes) can't be used
from NetBeans 6.5 if the Cadmium extension is installed.
*** (#1 of 2): 2008-11-29 12:42:59 GMT+00:00 <User 1-5Q-432>
Also, per recent e-mail:
> I'm finding that if I try to run 'hg -y push', I'm getting booted out of
> cdm.pbconfirm despite the fact that I've specified '-y' to answer "yes"
> to everything. Looking at the code for yes_no(), we manually check
> ui.interactive, and then always return the default answer ("no" in this
> case) for the non-interactive case. Why are we not just using
> ui.prompt(), which is supposed to return the default answer in a
> non-interactive case, and presumably knows how to replace it with 'y' if
> 'hg -y' is specified? I hacked up my cdm.py to always call ui.prompt()
> and let it do the work, and that seems to work.
...which seems to come down to the same (or similar) root cause.
*** (#2 of 2): 2008-12-01 23:13:07 GMT+00:00 <User 1-5Q-8204>
=== *Public Comments* ========================================================
=== *Workaround* =============================================================
Do the operation from the command-line
*** (#1 of 2): 2008-11-29 12:42:59 GMT+00:00 <User 1-5Q-432>
Disable Cadmium in the repo-specific .hg/hgrc:
[extensions]
hgext.cdm=!/ws/onnv-tools/onbld/lib/python/onbld/hgext/cdm.py
*** (#2 of 2): 2008-11-29 13:29:50 GMT+00:00 <User 1-5Q-432>
=== *Additional Details* =====================================================
Targeted Release: solaris_nevada
Commit To Fix In Build: snv_106
Fixed In Build:
Integrated In Build:
Verified In Build:
See Also:
Duplicate of:
Hooks:
Hook1:
Hook2:
Hook3:
Hook4:
Hook5:
Hook6:
Program Management:
Root Cause:
Fix Affects Documentation: No
Fix Affects Localization: No
=== *History* ================================================================
Date Submitted: 2008-11-29 12:42:58 GMT+00:00
Submitted By: <User 1-5Q-432>
Status Changed Date Updated Updated By
6-Fix Understood 2008-12-12 23:21:58 GMT+00:00 <User 1-5Q-8204>
=== *Service Request* ========================================================
Impact: Critical
Functionality: Primary
Severity: 1
Product Name: solaris
Product Release: solaris_nevada
Product Build:
Operating System: snv_103
Hardware: generic
Submitted Date: 2008-11-29 12:42:59 GMT+00:00
=== *Service Request* ========================================================
Impact: Significant
Functionality: Primary
Severity: 2
Product Name: solaris
Product Release: solaris_nevada
Product Build: snv_104
Operating System: solaris
Hardware: generic
Submitted Date: 2008-12-01 23:13:07 GMT+00:00
=== *Multiple Release (MR) Cluster* - 0 ======================================
