Clone of noVNC should use git:// protocol

Bug #1097984 reported by Scott Devoid
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
devstack
Fix Released
Undecided
Scott Devoid

Bug Description

Under "stable/essex", stack.sh uses the https:// protocol to clone the noVNC. This prompts the user to authenticate, which stalls the script until the user authenticates or cancels. If the git:// protocol were used, this prompt would not occur.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to devstack (stable/essex)

Fix proposed to branch: stable/essex
Review: https://review.openstack.org/20528

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to devstack (stable/essex)

Reviewed: https://review.openstack.org/20528
Committed: http://github.com/openstack-dev/devstack/commit/b47ced7456be53e505e7595b9362f7efb1a93c02
Submitter: Jenkins
Branch: stable/essex

commit b47ced7456be53e505e7595b9362f7efb1a93c02
Author: Scott Devoid <email address hidden>
Date: Fri Jan 25 15:15:11 2013 -0600

    Update clone URL for noVNC

    * Update noVNC to use https://github.com/kanaka/noVNC.git remote. The
      http://github.com/couldbuilders/noVNC.git repo is either no longer
      public or deleted now.

    Change-Id: Ia027886af69e36fd6f626931adfea635bc751c7d
    Fixes: bug #1097984

tags: added: in-stable-essex
Changed in devstack:
assignee: nobody → Scott Devoid (scott-devoid)
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.