857061 - System template actions on the right pane will now close
whenever the new system template button is clicked.
839394 - Changes wording on sync management page when no repositories
are enabled to cross-link to custom repos and red hat provider link.
772199 - Adds a tool tip to explain that GPG keys are optional for
products and repositories.
845062 - Fixes typo with errata search icon tooltip.
871093 - Fix to show tags when "+ All" verbs is selected.
855945 - Content search now displays the Library if there are no environments.
843566 - Sets the chosen dropdown in Content Search to not display
a filter mechanism.
791345 - Deletes errant tick mark that was appearing after
list updates on the sync plan page.
817858 - Permission edits now show tags when appropriate.
858726 - Sets the compare repos button to disable if there are 0 or 1
repos enabled on content search.
remove requires rubygem(execjs) and rubygem(multi_json)

We do not use them directly, this is transitively required by rubygem(jshintrb), which has correct requires.
In fact it has more better requires, because multi_json should be in >= 1.3.
Lets leave those requirements where they should be (in rubygem-jshintrb) and remove them from here.
758813: Disable basic and trusted auth in the candlepin engine since it is not required.

This manifested as an an error seen by curl which when using basic auth there was an error
contacting the user service. Basic auth should never be used. With these settings, the output
is

[root@samdev ~]# curl -k -u admin:admin https://localhost:8443/candlepin/owners
{"displayMessage":"Invalid credentials."}

Note, this will make development harder since people may use curl to access candlepin.
Developers can set these to true and then restart candlepin
885261 - org deletion should remove rh provider
885261 - make data repair script to work from any dir
885261 - org deletion unit test correction
Fixes 790216 running changesets concurently

Instead of disallow creation of changeset immediately check whether new
promotion/deletion is conflicting with any other that is currently
running. If it is not it's registered and run. Conflicting promotions
and deletion are refused in same way they were up to now. There are good
reasons for this - see bugzilla for more.

Conflicting (collision) is considered another runnin changeset (in state
promoting or deleting) which fits to one of these conditions:
* starts and ends on same environment
* starts on environment that is end for current changest
* ends on environment that is start for current changeset

All other cases are considered safe. With more than one worker they can
even run concurently.
Consumer.get was returning a 410 and surfacing that instead of continuing to delete the deletion record
when finishing, reset title of progress bar back to original state
Removing OR for pipeor
stop foreman only if it is running

addressing:
katello-configure --reset-data=YES
Starting Katello configuration
The top-level log file is [/var/log/katello/katello-configure-20121217-102554/main.log]
err: /Stage[main]/Foreman::Config/Exec[reset_foreman_db]/returns: change from notrun to 0 failed: rm -f /var/lib/katello/foreman_db_migrate_done; /usr/sbin/service-wait foreman stop returned 1 instead of one of [0] at /usr/share/katello/install/puppet/modules/foreman/manifests/config.pp:113