Bug 1213059
Summary: | git instaweb depends on lighttpd | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Matěj Cepl <mcepl> | ||||
Component: | git | Assignee: | Pavel Cahyna <pcahyna> | ||||
Status: | CLOSED ERRATA | QA Contact: | Leos Pol <lpol> | ||||
Severity: | low | Docs Contact: | Marie Hornickova <mdolezel> | ||||
Priority: | low | ||||||
Version: | 7.2 | CC: | dkutalek, isenfeld, lmiksik, lpol, ovasik, pcahyna, psklenar, pstodulk, qe-baseos-apps, qe-baseos-daemons, vslavik | ||||
Target Milestone: | rc | Keywords: | FastFix, Patch | ||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | git-1.8.3.1-19.el7 | Doc Type: | Bug Fix | ||||
Doc Text: |
*git instaweb* now works without any additional configuration and it is available in a separate subpackage
Previously, the *git instaweb* command required a web server and did not work in the default installation. With this update, *git instaweb* has been moved into the separate _git-instaweb_ subpackage, which depends on the *Apache* web server, and is configured to use the web server automatically. As a result, *git instaweb* now works without any further configuration when _git-instaweb_ is installed. To install the subpackage:
# yum install git-instaweb
|
Story Points: | --- | ||||
Clone Of: | Environment: | ||||||
Last Closed: | 2018-10-30 11:38:28 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Bug Depends On: | 1598184 | ||||||
Bug Blocks: | |||||||
Attachments: |
|
Description
Matěj Cepl
2015-04-18 09:29:52 UTC
Is it actually possible to use other http as suggested - one which is included in RHEL? If so we could possibly patch to use different default? (In reply to David Kutálek from comment #2) > Is it actually possible to use other http as suggested - one which is > included in RHEL? If so we could possibly patch to use different default? Do we really want to have git pulling in Apache as a dependency (plus some configuration stuff)? Anyway, I would really split git-instaweb into a separate package so that such disaster is at least a little bit mitigated. (In reply to Matěj Cepl from comment #3) > (In reply to David Kutálek from comment #2) > > Is it actually possible to use other http as suggested - one which is > > included in RHEL? If so we could possibly patch to use different default? > > Do we really want to have git pulling in Apache as a dependency (plus some > configuration stuff)? > > Anyway, I would really split git-instaweb into a separate package so that > such disaster is at least a little bit mitigated. Sure, split makes a lot of sense to me here. Created attachment 1019804 [details]
patch
What's up with this bug? Thanks for remind. Git ia on ACL, but as I hear QA will have limited capacity. I will talk with them about that. It would be great do this split at once with the planned split of git-libgnome-keyring from the git package (bug #1284081). It is on QA only. I am prepared to apply the fix when I will have permission to do that. # rpm -q git-instaweb git-instaweb-1.8.3.1-18.el7.noarch # rpm -qR git-instaweb-1.8.3.1-18.el7.noarch /bin/sh git = 1.8.3.1-18.el7 gitweb = 1.8.3.1-18.el7 httpd mod_ssl rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(PayloadIsXz) <= 5.2-1 Leos, can you add it to tests, please? Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:3275 |